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

Chris Smiley <csmiley@amsl.com> Fri, 06 January 2023 22:17 UTC

Return-Path: <csmiley@amsl.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 BDA52C15154A for <idna-update@ietfa.amsl.com>; Fri, 6 Jan 2023 14:17:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.438
X-Spam-Level:
X-Spam-Status: No, score=-0.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nNCoAioh9eBs for <idna-update@ietfa.amsl.com>; Fri, 6 Jan 2023 14:16:57 -0800 (PST)
Received: from smtp.alvestrand.no (unknown [IPv6:2a01:4f9:c010:a44b::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E32E5C15152F for <idna-update@ietf.org>; Fri, 6 Jan 2023 14:16:56 -0800 (PST)
Received: by smtp.alvestrand.no (Postfix) id 0376144F10; Fri, 6 Jan 2023 23:16:53 +0100 (CET)
Delivered-To: idna-update@alvestrand.no
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=4.31.198.40; helo=c8a.amsl.com; envelope-from=csmiley@amsl.com; receiver=<UNKNOWN>
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) by smtp.alvestrand.no (Postfix) with ESMTPS id CC3D044F0F for <idna-update@alvestrand.no>; Fri, 6 Jan 2023 23:16:52 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 4F11C424FFEC; Fri, 6 Jan 2023 14:16:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JuSjfRNYq5do; Fri, 6 Jan 2023 14:16:49 -0800 (PST)
Received: from [192.168.1.11] (cpe-76-95-228-63.socal.res.rr.com [76.95.228.63]) by c8a.amsl.com (Postfix) with ESMTPSA id 0DFEC424FFE9; Fri, 6 Jan 2023 14:16:49 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Chris Smiley <csmiley@amsl.com>
In-Reply-To: <20221226175245.94FC3AFB68@rfcpa.amsl.com>
Date: Fri, 06 Jan 2023 14:16:48 -0800
Cc: John C Klensin <john-ietf@jck.com>, john+ietf@jck.com, idna-update@alvestrand.no, RFC Errata System <rfc-editor@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <517DA372-2A9F-4561-8C7A-4C04F0186099@amsl.com>
References: <20221226175245.94FC3AFB68@rfcpa.amsl.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, Francesca Palombini <francesca.palombini@ericsson.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/vfbRHpXLCAWCXXKp0PasxqAPjv8>
Subject: Re: [Idna-update] [Editorial Errata Reported] RFC5890 (7291)
X-BeenThere: idna-update@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 06 Jan 2023 22:17:00 -0000

Greetings Area Directors,

We are unable to verify this erratum that the submitter marked as editorial.  
Please note that we have changed the “Type” of the following errata 
report to “Technical”.  As Stream Approver, please review and set the 
Status and Type accordingly (see the definitions at 
https://www.rfc-editor.org/errata-definitions/).

You may review the report at: 
https://www.rfc-editor.org/errata/eid7291

Please see https://www.rfc-editor.org/how-to-verify/ for further 
information on how to verify errata reports.

Further information on errata can be found at: 
https://www.rfc-editor.org/errata.php.

Thank you.

RFC Editor/cs

> On Dec 26, 2022, at 9:52 AM, 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:
> https://www.rfc-editor.org/errata/eid7291
> 
> --------------------------------------
> Type: Editorial
> Reported by: John Klensin <john-ietf@jck.com>
> 
> Section: GLOBAL
> 
> Original Text
> -------------
> Request for Comments: 5890
> Obsoletes: 3490
> Category: Standards Track
> 
> 
> Corrected Text
> --------------
> Request for Comments: 5890
> Obsoletes: 3490
> Updates: 4343
> Category: Standards Track
> 
> 
> Notes
> -----
> I have no idea whether this correction is Editorial or Technical , nor what to use as a Section indication.  However...
> 
> RFC 5890 (or IDNA2008 more generally), should have updated RFC 4343 and the IDN discussion in its Section 5.  The latter references the IDNA2003 documents and makes some statements that are, at best, confusing in the context of IDNA2008.
> 
> See the extended notes for RFC 4343 in https://www.rfc-editor.org/errata/eid7290 for more discussion and details.
> 
> Recommendation: Hold for document update unless this appears to anyone to be a serious problem, in which case a separate RFC, using the notes on Errata ID 7290 as a starting point, may be in order.
> 
> 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
>