RFC Errata
Found 2 records.
Status: Held for Document Update (2)
RFC 5738, "IMAP Support for UTF-8", March 2010
Note: This RFC has been obsoleted by RFC 6855
Source of RFC: eai (app)
Errata ID: 2075
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2010-03-17
Held for Document Update by: Alexey Melnikov
Section 4, 3rd para says:
IMAP servers that do not advertise the "UTF8=APPEND" or "UTF8=ONLY" | capability SHOULD reject an APPEND command that includes any 8-bit in | the message headers with a "NO" response.
It should say:
IMAP servers that do not advertise the "UTF8=APPEND" or "UTF8=ONLY" | capability SHOULD reject an APPEND command that includes any 8-bit | character in message header fields with a "NO" response. or: IMAP servers that do not advertise the "UTF8=APPEND" or "UTF8=ONLY" | capability SHOULD reject an APPEND command that includes any 8-bit | character in a message header with a "NO" response.
Notes:
Rationale: improved language and precise terminology
Errata ID: 2076
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2010-03-17
Held for Document Update by: Alexey Melnikov
Section 8, 4th para says:
| Up-conversion of MIME header encoding of the following headers MUST also be implemented: Subject, Date ([RFC5322] comments only), Comments, Keywords, and Content-Description.
It should say:
| Up-conversion of MIME header encoding of the following header fields MUST also be implemented: Subject, Date ([RFC5322] comments only), Comments, Keywords, and Content-Description.
Notes:
Rationale: precise use of IETF standard terminology.
Note: Further nits in this RFC (keep for update):
- Section 5, last line
... Section 2.3 of SASLprep RFC 4013 [RFC4013].
should better say:
... Section 2.3 of SASLprep (RFC 4013 [RFC4013]).
- Section 10 (2 instances):
This adds ...
should better say:
This RFC adds ...
- Section 12.1 -- unexpected line break in Ref. [RFC2231] :
[RFC2231] Freed, N. and K. Moore, "MIME Parameter Value and Encoded
Word Extensions:
Character Sets, Languages, and Continuations", RFC 2231,
November 1997.
should say:
[RFC2231] Freed, N. and K. Moore, "MIME Parameter Value and Encoded
Word Extensions: Character Sets, Languages, and
Continuations", RFC 2231, November 1997.