Found 1 record.
Status: Rejected (1)
RFC 6729, "Indicating Email Handling States in Trace Fields", September 2012Source of RFC: appsawg (app)
Errata ID: 3337
Publication Format(s) : TEXT
Reported By: D. Stussy
Date Reported: 2012-09-06
Rejected by: Barry Leiba
Date Rejected: 2012-09-06
Section 3 says:
In Section 6, the "state" clause is added to the Additional- Registered-Clauses IANA sub-registry. The ABNF for this clause is: State = CFWS "state" FWS queue-state-keyword [ "/" value ] ...
Clarification needed: Does this "state" clause keyword place before, after, or in either order with the "priority" clause keyword specified in RFC 6710? RFC 5321 does not specify an order for additional "Received:" header clauses defined after its publication. The order of additional clauses may need to be defined for proper parsing to determine validity of messages for spam classification or determination of other subversive purposes (as invalid values may indicate bad messages).
(See also the note filed in errata #1 filed for RFC 6710.)
RFC 5321 gives no indication that the order of clauses in the Additional-Registered-Clauses group matters, and, indeed, the order should not matter. Each clause has a unique (registered) atom, and they can be parsed unambiguously from those.