Opened 9 years ago

Closed 9 years ago

#361 closed design (fixed)

ABNF requirements for recipients

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

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 (1)

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

Download all attachments as: .zip

Change History (6)

Changed 9 years ago by julian.reschke@…

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

comment:1 Changed 9 years ago by julian.reschke@…

From [1682]:

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

comment:2 Changed 9 years ago by julian.reschke@…

  • Milestone changed from unassigned to 20

comment:3 Changed 9 years ago by julian.reschke@…

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

comment:4 Changed 9 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:5 Changed 9 years ago by mnot@…

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