RFC 4282, "The Network Access Identifier", December 2005
Note: This RFC has been obsoleted by RFC 7542Source of RFC: radext (ops)
Errata ID: 1850
Publication Format(s) : TEXT
Reported By: Alan DeKok
Date Reported: 2009-09-08
Rejected by: Dan Romascanu
Date Rejected: 2010-05-10
Section 2.4 says:
o Unassigned code points are specified in Section 2.5 of [RFC4013]. The use of unassigned code points is prohibited.
It should say:
o Unassigned code points MUST be ignored
Unassigned code points sometimes go through a process called "assignment". This means that they suddenly become valid.
Implementations that forbid unassigned code points will not be updated when the standards change to assign them. Therefore, they should ignore unassigned code points.
Happily, this is what all implementations do.
The suggested change should be discussed with the WG as part of a possible revision of the document.