RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 1 record.

Status: Reported (1)

RFC 8265, "Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords", October 2017

Source of RFC: precis (art)

Errata ID: 5479
Status: Reported
Type: Technical

Reported By: Peter Occil
Date Reported: 2018-08-26

Section 3.1 says:

   A userpart is allowed to contain only code
   points that are allowed by the PRECIS IdentifierClass defined in
   Section 4.2 of [RFC8264] and thus consists almost exclusively of
   letters and digits.

It should say:

   A userpart is allowed to contain only code
   points that are allowed by the PRECIS IdentifierClass defined in
   Section 4.2 of [RFC8264] (with respect to the userpart containing
   them, not to the username as a whole) and thus consists almost 
   exclusively of letters and digits.

Notes:

Because certain characters in IdentifierClass are CONTEXTO and are not valid unless the whole string doesn't contain certain other characters (an example is ARABIC-INDIC DIGITS), it is unclear whether the context-specific rules apply to the whole username or to individual userparts. However, section 3.5 strongly suggests that usernames (as opposed to userparts) are the matter of a higher-level protocol than this RFC. As a result, this erratum adds the text in parentheses to clarify that context-specific rules apply to individual userparts.

Report New Errata