RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 5198, "Unicode Format for Network Interchange", March 2008

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 3991
Status: Rejected
Type: Editorial

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.

Report New Errata