Re: [Idna-update] [Editorial Errata Reported] RFC5890 (5484)

John C Klensin <john-ietf@jck.com> Tue, 28 August 2018 15:22 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: idna-update@ietfa.amsl.com
Delivered-To: idna-update@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C761130E62 for <idna-update@ietfa.amsl.com>; Tue, 28 Aug 2018 08:22:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=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 4CsJtOiiSqhU for <idna-update@ietfa.amsl.com>; Tue, 28 Aug 2018 08:22:50 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD13D130DF2 for <idna-update@ietf.org>; Tue, 28 Aug 2018 08:22:46 -0700 (PDT)
Received: by mork.alvestrand.no (Postfix) id 167F37C0A48; Tue, 28 Aug 2018 17:22:45 +0200 (CEST)
Delivered-To: idna-update@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id F391C7C09CA for <idna-update@alvestrand.no>; Tue, 28 Aug 2018 17:22:44 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mJc5uSQDjmTZ for <idna-update@alvestrand.no>; Tue, 28 Aug 2018 17:22:43 +0200 (CEST)
X-Greylist: delayed 00:24:58 by SQLgrey-1.8.0
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received-SPF: None (no SPF record) identity=mailfrom; client-ip=70.88.254.51; helo=bsa2.jck.com; envelope-from=john-ietf@jck.com; receiver=idna-update@alvestrand.no
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by mork.alvestrand.no (Postfix) with ESMTPS id F28977C09B1 for <idna-update@alvestrand.no>; Tue, 28 Aug 2018 17:22:42 +0200 (CEST)
Received: from localhost ([::1] helo=JcK-T100) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1fufQz-000Bt1-LM; Tue, 28 Aug 2018 10:57:33 -0400
Date: Tue, 28 Aug 2018 10:57:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, vint@google.com
cc: poccil14@gmail.com, idna-update@alvestrand.no
Message-ID: <F578293C1FEB9ACE5B2E5EEB@[192.168.1.165]>
In-Reply-To: <20180828113938.173ADB8152A@rfc-editor.org>
References: <20180828113938.173ADB8152A@rfc-editor.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/9chZ0GW2A8tD3djxYypGogxeBbg>
Subject: Re: [Idna-update] [Editorial Errata Reported] RFC5890 (5484)
X-BeenThere: idna-update@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Internationalized Domain Names in Applications \(IDNA\) implementation and update discussions" <idna-update.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idna-update>, <mailto:idna-update-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idna-update/>
List-Post: <mailto:idna-update@ietf.org>
List-Help: <mailto:idna-update-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idna-update>, <mailto:idna-update-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Aug 2018 15:22:53 -0000

This erratum, as Vint indicates, is correct.  In the evolution
of 5890, the definitions were reshuffled several times and it is
easy to guess how the error might have occurred.  I don't know
why neither I nor the RFC Editor missed it in the final version,
but mea culpa.

For a future version, almost certainly the right fix is to
rearrange the text again so that all of the definitions either
follow or precede that comment.

Peter, thanks for the careful reading.
  john


--On Tuesday, August 28, 2018 04:39 -0700 RFC Errata System
<rfc-editor@rfc-editor.org> wrote:

> The following errata report has been submitted for RFC5890,
> "Internationalized Domain Names for Applications (IDNA):
> Definitions and Document Framework".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5484
> 
> --------------------------------------
> Type: Editorial
> Reported by: Peter Occil <poccil14@gmail.com>
> 
> Section: 2.3.2.1
> 
> Original Text
> -------------
>    For IDNA-aware applications, the three types of valid
> labels are    "A-labels", "U-labels", and "NR-LDH labels",
> each of which is defined    below.
> 
> 
> Corrected Text
> --------------
>    For IDNA-aware applications, the three types of valid
> labels are    "A-labels", "U-labels", and "NR-LDH labels",
> each of which is defined    below and in section 2.3.1.
> 
> Notes
> -----
> The term NR-LDH label is actually defined in section 2.3.1,
> not later in this section.
> 
> 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. 
> 
> --------------------------------------
> RFC5890 (draft-ietf-idnabis-defs-13)
> --------------------------------------
> Title               : Internationalized Domain Names for
> Applications (IDNA): Definitions and Document Framework
> Publication Date    : August 2010
> Author(s)           : J. Klensin
> Category            : PROPOSED STANDARD
> Source              : Internationalized Domain Names in
> Applications (Revised) Area                : Applications
> Stream              : IETF
> Verifying Party     : IESG