RFC Errata
Found 3 records.
Status: Reported (1)
RFC 5646, "Tags for Identifying Languages", September 2009
Source of RFC: ltru (app)
Errata ID: 5457
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Peter Occil
Date Reported: 2018-08-12
Section 2.2.9 says:
A tag is considered "valid" if it satisfies these conditions:
o The tag is well-formed.
o Either the tag is in the list of grandfathered tags or all of its
primary language, extended language, script, region, and variant
subtags appear in the IANA Language Subtag Registry as of the
particular registry date.
o There are no duplicate variant subtags.
o There are no duplicate singleton (extension) subtags.
It should say:
A tag is considered "valid" if it satisfies these conditions:
o The tag is well-formed.
o Either the tag is in the list of grandfathered tags or all of its
primary language, extended language, script, region, and variant
subtags appear in the IANA Language Subtag Registry as of the
particular registry date.
o There are no duplicate variant subtags.
o There are no duplicate singleton (extension) subtags.
o There is no more than one extended language subtag.
Notes:
Sec. 2.2.2 contains an additional validity requirement (point 4): the existence of no more than one extended language subtag. This is not reflected in the definition of validity given in sec. 2.2.9 of the RFC.
Status: Held for Document Update (2)
RFC 5646, "Tags for Identifying Languages", September 2009
Source of RFC: ltru (app)
Errata ID: 8711
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Pétur Ingi Egilsson
Date Reported: 2026-01-22
Held for Document Update by: Andy Newton
Date Held: 2026-01-22
Section 3.1.5 says:
The field ’Description’ contains a description of the tag or subtag in the record. The ’Description’ field MAY appear more than once per record. The ’Description’ field MAY include the full range of Unicode characters. At least one of the ’Description’ fields MUST be written or transcribed into the Latin script; additional ’Description’ fields MAY be in any script or language.
It should say:
The field ’Description’ contains a description of the tag or subtag in the record. The ’Description’ field MAY appear more than once per record. The ’Description’ field MAY include the full range of Unicode characters. At least one of the 'Description' fields MUST be written or transcribed into the Latin script (i.e., using characters with Unicode Script property value Latin, as defined in UAX #24, plus characters with Script property value Common or Inherited when used in conjunction with Latin characters); additional ’Description’ fields MAY be in any script or language.
Notes:
The term "Latin script" is not defined anywhere in the document. This
creates implementation ambiguity: does it refer to:
(a) The US-ASCII letters A-Z, a-z (per ISO 646, which the RFC references
as the default restriction for registry fields in Section 3.1.1)
(b) Characters with Unicode Script property value "Latin" as defined
in UAX #24 (Unicode Standard Annex #24, "Unicode Script Property")
These interpretations differ substantially: option (a) covers 52 letters,
while option (b) covers approximately 1,500 code points including
characters such as é, ñ, ø, and ǁ (LATIN LETTER LATERAL CLICK).
The registry contains 516 Description fields using extended Latin
characters (e.g., "Norwegian Bokmål", "Volapük", "Arbëreshë Albanian"),
demonstrating that interpretation (a) is not the operational practice.
The RFC explicitly permits "the full range of Unicode characters" in
Description fields (Section 3.1.5), so referencing Unicode's script
property is consistent with the document's framework.
UAX #24 (https://www.unicode.org/reports/tr24/) is a stable Unicode
Standard Annex with clear definitions.
Errata ID: 8712
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Pétur Ingi Egilsson
Date Reported: 2026-01-22
Held for Document Update by: Andy Newton
Date Held: 2026-01-22
Section 3.5 says:
The ’Description’ fields provided in the request MUST contain at least one description written or transcribed into the Latin script;
It should say:
The 'Description' fields provided in the request MUST contain at least one description written or transcribed into the Latin script (i.e., using characters with Unicode Script property value Latin, as defined in UAX #24, plus characters with Script property value Common or Inherited when used in conjunction with Latin characters);
Notes:
Same notes as for Errata 8711.