RFC Errata
Found 4 records.
Status: Verified (1)
RFC 5198, "Unicode Format for Network Interchange", March 2008
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 1402
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-03-31
Verifier Name: Alexey Melnikov
Date Verified: 2010-05-11
Section 2, mid-pg.4 says:
The use of LF without CR is questionable; see Appendix B for more
discussion. The newer control characters IND (U+0084) and NEL ("Next
Line", U+0085) might have been used to disambiguate the various line-
ending situations, but, because their use has not been established on
the Internet, because many protocols require CRLF, and because IND
| and NEL fall within the "C1 Controls" group (see below), they MUST
NOT be used. [...]
^^^^^
It should say:
The use of LF without CR is questionable; see Appendix B for more
discussion. The newer control characters IND (U+0084) and NEL ("Next
Line", U+0085) might have been used to disambiguate the various line-
ending situations, but, because their use has not been established on
the Internet, because many protocols require CRLF, and because IND
| and NEL fall within the "C1 Controls" group (see above), they MUST
NOT be used. [...]
^^^^^^
Notes:
The only relevant discussion of "C1 Controls" in the document
is in bullet 3 within the same section, on the preceding page.
Hence, "below" is misleading for the reader and needs to be
replaced to correctly say "above".
Status: Reported (1)
RFC 5198, "Unicode Format for Network Interchange", March 2008
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 7531
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Gordon Steemson
Date Reported: 2023-06-01
Section section 2, page 3 says:
3. The control characters in the ASCII range (U+0000 to U+001F and U+007F to U+009F) SHOULD generally be avoided.
It should say:
3. The control characters in the ASCII range (U+0000 to U+001F, and U+007F) SHOULD generally be avoided.
Notes:
Characters in the range U+0080 to U+009F are explicitly noted in the following text as lying outside the ASCII range, and in fact they are discussed separately at that point (which, given the phrasing error pointed out here, currently is duplicate coverage). They do not pertain to any range of ASCII characters and should not be treated as such.
Status: Held for Document Update (1)
RFC 5198, "Unicode Format for Network Interchange", March 2008
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 1401
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-03-31
Held for Document Update by: Pete Resnick
Date Held: 2014-05-16
Section 2, pg.3 says:
3. The control characters in the ASCII range (U+0000 to U+001F and
| U+007F to U+009F) SHOULD generally be avoided. Space (SP,
| U+0020), CR, LF, and Form Feed (FF, U+000C) are exceptions to
| this principle, but use of all but the first requires care as
discussed elsewhere in this document. The so-called "C1
Controls" (U+0080 through U+009F), which did not appear in ASCII,
MUST NOT appear.
It should say:
3. The control characters in the ASCII range (U+0000 to U+001F and
| U+007F to U+009F) SHOULD generally be avoided. CR, LF, and Form
| Feed (FF, U+000C) are exceptions to this principle, but use of
| these, as well as Space (SP, U+0020, which is often treated as a
| control character), requires care as discussed elsewhere in this
document. The so-called "C1 Controls" (U+0080 through U+009F),
which did not appear in ASCII, MUST NOT appear.
Notes:
Logical inconsistency:
SPACE is not contained in the enumeration in the first sentence;
thus, it is no *exception* to that rule, and the published text
does not make proper sense.
Status: Rejected (1)
RFC 5198, "Unicode Format for Network Interchange", March 2008
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 3991
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-03-31
Rejected by: Pete Resnick
Date Rejected: 2014-05-16
Section 2, pg.3 says:
3. The control characters in the ASCII range (U+0000 to U+001F and
| U+007F to U+009F) SHOULD generally be avoided. Space (SP,
| U+0020), CR, LF, and Form Feed (FF, U+000C) are exceptions to
| this principle, but use of all but the first requires care as
discussed elsewhere in this document. The so-called "C1
Controls" (U+0080 through U+009F), which did not appear in ASCII,
MUST NOT appear.
It should say:
3. The control characters in the ASCII range (U+0000 to U+001F and | U+007F to U+009F) SHOULD generally be avoided. CR, LF, and | Form Feed (FF, U+000C) are exceptions to | this principle, but use of these requires care as | discussed elsewhere in this document. | Space (SP, U+0020) is often treated as a control character and | described that way in many documents. It SHOULD NOT appear in | identifiers. When used in more general strings, it should be | used with caution because Unicode supports a number of other | spacing characters (see, e.g., NO-BREAK SPACE (U+00A0) and the | collection of characters in the range 2000..200B that may or may | not be considered equivalent depending on the normalization and | other rules used. The so-called "C1 Controls" (U+0080 through | U+009F), which did not appear in ASCII, MUST NOT appear.
Notes:
Logical inconsistency:
SPACE is not contained in the enumeration in the first sentence;
thus, it is no *exception* to that rule, and the published text
does not make proper sense.
--VERIFIER NOTES--
The part of this erratum which says:
It SHOULD NOT appear in identifiers. When used in more
general strings, it should be used with caution because
Unicode supports a number of other spacing characters
(see, e.g., NO-BREAK SPACE (U+00A0) and the collection
of characters in the range 2000..200B that may or may
not be considered equivalent depending on the
normalization and other rules used.
while possibly true, is not appropriate for an erratum. It is a substantive change.