[precis] [Technical Errata Reported] RFC8265 (5479)

RFC Errata System <rfc-editor@rfc-editor.org> Sun, 26 August 2018 17:20 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16C52128CE4 for <precis@ietfa.amsl.com>; Sun, 26 Aug 2018 10:20:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y0l8ZzAY_yAR for <precis@ietfa.amsl.com>; Sun, 26 Aug 2018 10:20:13 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7445B126CB6 for <precis@ietf.org>; Sun, 26 Aug 2018 10:20:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 75779B817D7; Sun, 26 Aug 2018 10:19:56 -0700 (PDT)
To: stpeter@mozilla.com, alexey.melnikov@isode.com, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, Marc.Blanchet@viagenie.ca
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: poccil14@gmail.com, precis@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20180826171956.75779B817D7@rfc-editor.org>
Date: Sun, 26 Aug 2018 10:19:56 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/precis/QG_XcvfsDZJpUY9oSj2B0o5ll_8>
Subject: [precis] [Technical Errata Reported] RFC8265 (5479)
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Aug 2018 17:20:15 -0000

The following errata report has been submitted for RFC8265,
"Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5479

--------------------------------------
Type: Technical
Reported by: Peter Occil <poccil14@gmail.com>

Section: 3.1

Original Text
-------------
   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.


Corrected Text
--------------
   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.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC8265 (draft-ietf-precis-7613bis-11)
--------------------------------------
Title               : Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords
Publication Date    : October 2017
Author(s)           : P. Saint-Andre, A. Melnikov
Category            : PROPOSED STANDARD
Source              : Preparation and Comparison of Internationalized Strings
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG