IETF Logo Mail Archive

Re: Progress of 5/6 IDNABIS documents & mappings consistency issue

Vint Cerf <vint@google.com> Mon, 21 December 2009 07:22 UTC

Return-Path: <vint@google.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 6109339E2C0 for <idna-update@alvestrand.no>; Mon, 21 Dec 2009 08:22:23 +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 pLIusLBi0U36 for <idna-update@alvestrand.no>; Mon, 21 Dec 2009 08:22:22 +0100 (CET)
X-Greylist: domain auto-whitelisted by SQLgrey-1.6.8
Received: from smtp-out.google.com (smtp-out.google.com [216.239.33.17]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 1AC1439E17F for <idna-update@alvestrand.no>; Mon, 21 Dec 2009 08:22:22 +0100 (CET)
Received: from kpbe20.cbf.corp.google.com (kpbe20.cbf.corp.google.com [172.25.105.84]) by smtp-out.google.com with ESMTP id nBL7MXKS005813 for <idna-update@alvestrand.no>; Mon, 21 Dec 2009 07:22:33 GMT
Received: from pwi19 (pwi19.prod.google.com [10.241.219.19]) by kpbe20.cbf.corp.google.com with ESMTP id nBL7MVhD024100 for <idna-update@alvestrand.no>; Sun, 20 Dec 2009 23:22:32 -0800
Received: by pwi19 with SMTP id 19so3614498pwi.15 for <idna-update@alvestrand.no>; Sun, 20 Dec 2009 23:22:31 -0800 (PST)
Received: by 10.142.118.9 with SMTP id q9mr4666553wfc.49.1261380150880; Sun, 20 Dec 2009 23:22:30 -0800 (PST)
Received: from mobile-166-129-249-180.mycingular.net ([166.129.249.180]) by mx.google.com with ESMTPS id 23sm5044059pzk.0.2009.12.20.23.22.26 (version=SSLv3 cipher=RC4-MD5); Sun, 20 Dec 2009 23:22:29 -0800 (PST)
Message-Id: <F765A81D-CAAA-42EA-A150-A6D7E65FD590@google.com>
From: Vint Cerf <vint@google.com>
To: Lisa Dusseault <lisa.dusseault@gmail.com>
In-Reply-To: <ca722a9e0912201500p6e3a6379l3279b50241bf8535@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Progress of 5/6 IDNABIS documents & mappings consistency issue
Date: Mon, 21 Dec 2009 02:22:21 -0500
References: <ca722a9e0912201500p6e3a6379l3279b50241bf8535@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
X-System-Of-Record: true
Cc: "idna-update@alvestrand.no" <idna-update@alvestrand.no>
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: Mon, 21 Dec 2009 07:22:23 -0000

thanks Lisa - i will be working towards a possible resolution
of this last issue over the holidays.
vint


On Dec 20, 2009, at 6:00 PM, Lisa Dusseault wrote:

> 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
> _______________________________________________
> Idna-update mailing list
> Idna-update@alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/idna-update

v2.23.0 | Report a Bug | By Email