RFC 4282, "The Network Access Identifier", December 2005
Note: This RFC has been obsoleted by RFC 7542Source of RFC: radext (ops)
Errata ID: 753
Publication Format(s) : TEXT
Reported By: Frank Ellermann
Date Reported: 2006-08-14
Rejected by: Dan Romascanu
Date Rejected: 2010-11-03
Section 2.1 says:
c =/ %x80-FF ; UTF-8-Octet allowed (not in RFC 2486) ; Where UTF-8-octet is any octet in the ; multi-octet UTF-8 representation of a ; unicode codepoint above %x7F. ; Note that c must also satisfy rules in ; Section 2.4, including, for instance, ; checking that no prohibited output is ; used (see also Section 2.3 of ; [RFC4013]). x = %x00-FF ; all 128 ASCII characters, no exception; ; as well as all UTF-8-octets as defined ; above (this was not allowed in ; RFC 2486). Note that x must nevertheless ; again satisfy the Section 2.4 rules.
It should say:
Shouldn't that be s/FF/F4/ as in STD 63, or maybe s/FF/FD/ ?
There is no clear suggested change. The chairs are aware about issues with RFC 4282, and believe that a new document is probably required to address them.