RFC Errata
Found 3 records.
Status: Verified (2)
RFC 4790, "Internet Application Protocol Collation Registry", March 2007
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 7
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Filip Navara
Date Reported: 2007-03-29
Section 3.1 says:
collation-id = collation-prefix ";" collation-core-name
It should say:
collation-id = collation-scope ";" collation-core-name
Notes:
Submitted to the RFC Editor by Chris Newman.
Also reported by Alfred Hoenes 2007-04-10.
Errata ID: 3510
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: John Klensin
Date Reported: 2013-03-08
Verifier Name: Barry Leiba
Date Verified: 2013-03-08
Section Global says:
US-ASCII (most places)
It should say:
ASCII (but see note)
Notes:
The terms "US-ASCII" and "ASCII" are used interchangeably in this document, sometimes in the same paragraph (see the first paragraph of 9.2.1). Neither is anchored in a reference to either X3.4-1986 (e.g., the "us-ascii charset") or to X3.4-1968 or RFC 20 (e.g., NVT ASCII). There is one explicit mention of the "US-ASCII charset" (Section 5) but all the rest, including the section titles that use "ASCII" already, appear to be talking about the ASCII repertoire with terms like "ASCII" (or "US-ASCII") letters. Except where the charset, or some very special property of X3.4-1986, is intended, I believe that all of these should be just "ASCII".
I don't think this is likely to cause any significant confusion among anyone who is likely to read this spec, much less confusion sufficient to cause interoperability problems (hence, it is not a technical error), but it is confusing and should be cleaned up --both to rationalize the terminology and to provide citations for the terminology that is used-- if the document is ever updated.
Status: Held for Document Update (1)
RFC 4790, "Internet Application Protocol Collation Registry", March 2007
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 2851
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Mykyta Yevstifeyev
Date Reported: 2011-07-01
Held for Document Update by: Pete Resnick
Section 3.4 says:
other-uri = <absoluteURI>
; excluding the IANA collation namespace.
It should say:
other-uri = absolute-URI
; excluding the IANA collation namespace.
The ABNF production "absolute-URI" is imported from URI: Generic Syntax [4].
Notes:
In the current definition it is assumed "absoluteURI" is a <prose-val> of RFC 4234. However it actually refers to the <absolute-URI> of RFC 3986, which I propose to be fixed.