Progress of 5/6 IDNABIS documents & mappings consistency issue

Lisa Dusseault <lisa.dusseault@gmail.com> Sun, 20 December 2009 23:00 UTC

Return-Path: <lisa.dusseault@gmail.com>
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 B9B2739E2B8 for <idna-update@alvestrand.no>; Mon, 21 Dec 2009 00:00:10 +0100 (CET)
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 mLQ1do7PbQo2 for <idna-update@alvestrand.no>; Mon, 21 Dec 2009 00:00:09 +0100 (CET)
X-Greylist: domain auto-whitelisted by SQLgrey-1.6.8
Received: from mail-vw0-f171.google.com (mail-vw0-f171.google.com [209.85.212.171]) by eikenes.alvestrand.no (Postfix) with ESMTP id 94B0039E217 for <idna-update@alvestrand.no>; Mon, 21 Dec 2009 00:00:09 +0100 (CET)
Received: by vws1 with SMTP id 1so1360000vws.23 for <idna-update@alvestrand.no>; Sun, 20 Dec 2009 15:00:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.126.214 with SMTP id d22mr6078373vcs.114.1261350020789; Sun, 20 Dec 2009 15:00:20 -0800 (PST)
Date: Sun, 20 Dec 2009 15:00:20 -0800
Message-ID: <ca722a9e0912201500p6e3a6379l3279b50241bf8535@mail.gmail.com>
Subject: Progress of 5/6 IDNABIS documents & mappings consistency issue
From: Lisa Dusseault <lisa.dusseault@gmail.com>
To: "idna-update@alvestrand.no" <idna-update@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-BeenThere: idna-update@alvestrand.no
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IDNA update work <idna-update.alvestrand.no>
List-Unsubscribe: <http://www.alvestrand.no/mailman/listinfo/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: Sun, 20 Dec 2009 23:00:10 -0000

As Vint has posted
(http://www.alvestrand.no/pipermail/idna-update/2009-December/006387.html),
we have had good discussions about ß, final sigma, and possible
transition strategies. These decisions and discussions have been
reflected in John's recent update to draft-ietf-idnabis-rationale-15.
Thus, I have put the rationale document, along with
draft-ietf-idnabis-bidi, draft-ietf-idnabis-defs,
draft-ietf-idnabis-protocol and draft-ietf-idnabis-tables, on the next
possible IESG Telechat (Jan 7) for IESG consideration.

On the topic of mappings, I've previously noted
(http://www.alvestrand.no/pipermail/idna-update/2009-December/005962.html)
that we had some IETF Last Call issues raised about how compatible our
idnabis-mapping list of mappings is with the mappings of IDNA2003.  I'd like
to be sure there's WG consensus on these issues before progressing the
mappings document.  If some links out there contain characters that were
required to be mapped in IDNA2003, and software is upgraded to IDNA2008
in a way that makes those links fail, that seems to be something we should
be concerned about.  The key issues seem to me to be what the WG opinion
is on having one set of optional mappings for better interoperability, or two
or more to encourage flexibility. Michel Suignard's recent message
(http://www.alvestrand.no/pipermail/idna-update/2009-December/006389.html)
seems like a good starting point for that discussion.

I'm hoping despite the holidays we can conclude these discussions in the
next few weeks, and idnabis-mappings may even be able to catch up with
the other documents.

Lisa