[Idna-update] Updating the review procedure in RFC 5892 for new Unicode versions

John C Klensin <john-ietf@jck.com> Thu, 20 June 2019 22:52 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 7F982120235 for <idna-update@ietfa.amsl.com>; Thu, 20 Jun 2019 15:52:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 F9siT1bG68K0 for <idna-update@ietfa.amsl.com>; Thu, 20 Jun 2019 15:52:10 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82802120280 for <idna-update@ietf.org>; Thu, 20 Jun 2019 15:52:10 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1he5ub-0009RR-6P for idna-update@ietf.org; Thu, 20 Jun 2019 18:52:09 -0400
Date: Thu, 20 Jun 2019 18:52:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: idna-update@ietf.org
Message-ID: <B06E9C00290B5B0B21C0851D@PSB>
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: 198.252.137.10
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/VLExzEy3NHNBarT7erCWMCWXDqE>
Subject: [Idna-update] Updating the review procedure in RFC 5892 for new Unicode versions
X-BeenThere: idna-update@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 20 Jun 2019 22:52:18 -0000

Hi.

As many of you know, several things emerged from the urgent
effort to get IDNA tables based on Unicode 11.0 to IANA and
published.  One was a misconception that those tables were
somehow normative enough that their absence was blocking other
work.  Another was confusion about the review process itself and
what was expected.  Patrik and I have put together a first draft
of an update to RFC 5892 to address those issues and a few
others.  I'm trying to work with the i18n directorate and the
ADs to figure out how to process it (probably along with a list
of documents that have been pending discussion and action for
years).  In the interim, we would appreciate those on this list
(and interested in IDNA) to review it and comment rather than
waiting until the last minute.

https://datatracker.ietf.org/doc/draft-klensin-idna-unicode-review/

thanks,
   john