* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #361 (closed design: fixed)

Opened 3 years ago

Last modified 2 years ago

ABNF requirements for recipients

Reported by: mnot@pobox.com Owned by:
Priority: normal Milestone: 20
Component: non-specific Severity: Active WG Document
Keywords: Cc:
Origin:

Description

Our conformance sections specify:

This document also uses ABNF to define valid protocol elements (Section 1.3). In addition to the prose requirements placed upon them, Senders must not generate protocol elements that are invalid.

However, it doesn't say anything about recipients. Should an explicit requirement be placed upon them too?

Attachments

361.diff (1.3 KB) - added by julian.reschke@gmx.de 2 years ago.
Proposed patch for P2; needs more changes for the other parts.

Change History

Changed 2 years ago by julian.reschke@gmx.de

Proposed patch for P2; needs more changes for the other parts.

comment:1 Changed 2 years ago by julian.reschke@gmx.de

From [1682]:

Clarify that in general recipients MUST be able to parse everything allowed by the ABNF (see #361)

comment:2 Changed 2 years ago by julian.reschke@gmx.de

  • Milestone changed from unassigned to 20

comment:3 Changed 2 years ago by julian.reschke@gmx.de

  • Status changed from new to closed
  • Resolution set to incorporated

comment:4 Changed 2 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:5 Changed 2 years ago by mnot@pobox.com

  • Status changed from reopened to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.