[Editorial Errata Reported] RFC5892 (3312)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 09 August 2012 09:08 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: idna-update@alvestrand.no
Delivered-To: idna-update@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id CF02539E129 for <idna-update@alvestrand.no>; Thu, 9 Aug 2012 11:08:08 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oWy7Uv+G4BtR for <idna-update@alvestrand.no>; Thu, 9 Aug 2012 11:08:07 +0200 (CEST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.6.8
Received: from rfc-editor.org (rfc-editor.org [12.22.58.47]) by eikenes.alvestrand.no (Postfix) with ESMTP id 6DCD539E031 for <idna-update@alvestrand.no>; Thu, 9 Aug 2012 11:08:07 +0200 (CEST)
Received: by rfc-editor.org (Postfix, from userid 30) id D0F53B1E002; Thu, 9 Aug 2012 02:06:59 -0700 (PDT)
To: paf@cisco.com, barryleiba@computer.org, presnick@qualcomm.com, vint@google.com
Subject: [Editorial Errata Reported] RFC5892 (3312)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20120809090659.D0F53B1E002@rfc-editor.org>
Date: Thu, 09 Aug 2012 02:06:59 -0700
Cc: paf@netnod.se, idna-update@alvestrand.no, rfc-editor@rfc-editor.org
X-BeenThere: idna-update@alvestrand.no
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IDNA update work <idna-update.alvestrand.no>
List-Unsubscribe: <http://www.alvestrand.no/mailman/options/idna-update>, <mailto:idna-update-request@alvestrand.no?subject=unsubscribe>
List-Archive: <http://www.alvestrand.no/pipermail/idna-update>
List-Post: <mailto:idna-update@alvestrand.no>
List-Help: <mailto:idna-update-request@alvestrand.no?subject=help>
List-Subscribe: <http://www.alvestrand.no/mailman/listinfo/idna-update>, <mailto:idna-update-request@alvestrand.no?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 09:08:09 -0000

The following errata report has been submitted for RFC5892,
"The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5892&eid=3312

--------------------------------------
Type: Editorial
Reported by: Patrik Fältström <paf@netnod.se>

Section: A and A.1

Original Text
-------------
In A:

Code point:

The code point, or code points, to which this rule is to be
applied.  Normally, this implies that if any of the code points in
a label is as defined, then the rules should be applied.  If
evaluated to True, the code point is OK as used; if evaluated to
False, it is not OK.

In A.1:

Rule Set:
  False;
  If Canonical_Combining_Class(Before(cp)) .eq.  Virama Then True;
  If RegExpMatch((Joining_Type:{L,D})(Joining_Type:T)*\u200C
    (Joining_Type:T)*(Joining_Type:{R,D})) Then True;


Corrected Text
--------------
In A:

Code point:

The code point, or code points, to which this rule is to be
applied.  Normally, this implies that if any of the code points in
a label is as defined, then the rules should be applied.  If
evaluated to True, the code point is OK as used; if evaluated to
False, it is not OK.

For the rule to be evaluated to True for the label, it MUST be
evaluated to True for every occurrence of Code point in the
label.

In A.1:

Rule Set:
  False;
  If Canonical_Combining_Class(Before(cp)) .eq.  Virama Then True;
  If cp .eq. \u200C And RegExpMatch((Joining_Type:{L,D})(Joining_Type:T)*cp
    (Joining_Type:T)*(Joining_Type:{R,D})) Then True;


Notes
-----
The original text did not make it clear whether the actual rule is to be applied once for every occurrence of the code point in the label. This is a regular expression that can be interpreted in multiple ways, plus it does not take into account the case where more than one U+200C exists in a label.

Instructions:
-------------
This errata 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 (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5892 (draft-ietf-idnabis-tables-09)
--------------------------------------
Title               : The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)
Publication Date    : August 2010
Author(s)           : P. Faltstrom, Ed.
Category            : PROPOSED STANDARD
Source              : Internationalized Domain Names in Applications (Revised)
Area                : Applications
Stream              : IETF
Verifying Party     : IESG