RFC Errata
Found 3 records.
Status: Verified (1)
RFC 2919, "List-Id: A Structured Field and Namespace for the Identification of Mailing Lists", March 2001
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 3951
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Peter Occil
Date Reported: 2014-04-03
Verifier Name: Pete Resnick
Date Verified: 2014-04-04
Section 3 says:
The syntax of the List-Id header follows: list-id-header = "List-ID:" [phrase] "<" list-id ">" CRLF
It should say:
The syntax of the List-Id header follows: list-id-header = "List-ID:" [phrase / CFWS] "<" list-id ">" CRLF
Notes:
This change is needed to conform with the second and fifth examples
given just after the syntax definition. Without it, the case "List-ID: <list.example.com>" (with a space after "List-ID:") would not be valid; only "List-ID:<list.example.com>" (without a space) would be, especially since it states that "the List-Id header does not allow free insertion of whitespace and comments around tokens."
Status: Held for Document Update (1)
RFC 2919, "List-Id: A Structured Field and Namespace for the Identification of Mailing Lists", March 2001
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 2499
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Tony Hansen
Date Reported: 2010-08-23
Held for Document Update by: Peter Saint-Andre
Section 2 and 3 says:
[DRUMS]
It should say:
[RFC2822]
Notes:
When going from draft-chandhok-listid-04.txt to the RFC, various references were updated. The [DRUMS] reference to 2822 was updated to [RFC2822] within the References section, but was not changed within the text.
Status: Rejected (1)
RFC 2919, "List-Id: A Structured Field and Namespace for the Identification of Mailing Lists", March 2001
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 361
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Trish Lynch
Date Reported: 2002-08-08
Rejected by: Alexey Melnikov
Date Rejected: 2010-05-11
Section 3 says:
The syntax of the List-Id header follows: list-id-header = "List-ID:" [phrase] "<" list-id ">" CRLF
It should say:
The syntax of the List-Id header follows: list-id-header = "List-Id:" [phrase] "<" list-id ">" CRLF
Notes:
In order to bring it in line with the examples, and with common usage (by
the RFC, the List-ID is correct) most mail readers use the example and
do not consider the LHS case insensitive, since the RFC says:
The list header fields are subject to the encoding and character restrictions for mail headers as described in [RFC822].
RFC822, while it says that most headers are character insensitive, does
not mandate that, and RFC 2919 only mandates that the List-Id: header is
subject to *encoding* and *character restrictions*, and does not say it
needs to adhere to case insensitivity.
Therefore, the proposed change above will bring things more in line with common
usage.
--VERIFIER NOTES--
Header field names are case insensitive per use of string literals from RFC 2234.