Re: [Idna-update] IDNA and combining sequences (was: Re: Expiration impending: <draft-klensin-idna-rfc5891bis-01.txt>)
"Patrik Fältström " <paf@frobbit.se> Sat, 10 March 2018 13:06 UTC
Return-Path: <paf@frobbit.se>
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 782A9129C6D
for <idna-update@ietfa.amsl.com>; Sat, 10 Mar 2018 05:06:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level:
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001,
T_RP_MATCHES_RCVD=-0.01] 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 s38LAyVW23gn for <idna-update@ietfa.amsl.com>;
Sat, 10 Mar 2018 05:06:17 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id E51CD126BF0
for <idna-update@ietf.org>; Sat, 10 Mar 2018 05:06:16 -0800 (PST)
Received: from [10.196.199.114] (unknown
[IPv6:2620:f:8000:210:8d4:be63:a857:690])
by mail.frobbit.se (Postfix) with ESMTPSA id 4E403232A5;
Sat, 10 Mar 2018 14:06:13 +0100 (CET)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "John C Klensin" <john-ietf@jck.com>
Cc: "Asmus Freytag" <asmusf@ix.netcom.com>, idna-update@ietf.org
Date: Sat, 10 Mar 2018 09:06:09 -0400
X-Mailer: MailMate (2.0BETAr6104)
Message-ID: <516E58F3-015D-4AD7-A3FD-0749A6890245@frobbit.se>
In-Reply-To: <1E562CDE39B4224F227E765D@PSB>
References: <C4FBCF12821031786F472AA2@PSB>
<02c29140-29f1-cc81-8c4f-8249d0f23b2c@ix.netcom.com>
<1E562CDE39B4224F227E765D@PSB>
MIME-Version: 1.0
Content-Type: multipart/signed;
boundary="=_MailMate_4BDAA92C-525B-4EF7-ADC9-527C83B57AF4_=";
micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/e5tLkAStnRFkgpctP9_JJHKbVzs>
Subject: Re: [Idna-update] IDNA and combining sequences (was: Re: Expiration
impending: <draft-klensin-idna-rfc5891bis-01.txt>)
X-BeenThere: idna-update@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 10 Mar 2018 13:06:18 -0000
On 9 Mar 2018, at 12:27, John C Klensin wrote: > * Your explanation below is very helpful, at least to me. Me too. > I am > confident that, if it was what we were given when we started the IDNA2008 design, some of the rules would have reflected it. We were given a different explanation and answer to our questions, one much closer to "there is no problem and will be no problem in the future, so don't worry - no special rules are needed". Correct. Being on the receiving side of the messages, and one of the persons that asked the questions, yes, we asked, they responded... > The question is what to do now. If we were to decide that your discussion would made a good addition to the protocol, we would run into at least two problems. One is that we promised the registry community that there would be no more disruptive > changes and, at least as important, the Unicode Consortium > outrage at our altering the way a handful of code points were treated would presumably be much greater if we were to make a change that would invalidate a large number of labels that might now be registered and in use somewhere in the tree. Another is the problem that started this thread -- there appears to be no energy in the IETF to consider and process changes to IDNA, even fairly trivial clarifications. I think we should do some scenario planning here. Remember that we do not have a world where IDNA2008 based on Unicode 6.x is what people use. People use all different kind of mix between IDNA2008, IDNA2003 and Unicode versions. I have myself worked with the curl library (that uses libidn) and to be honest, I do not think people KNOW what they use. Or they know, and they know they violate the rules. For the contracted parties, they have the LGR coming down the road anyways, so... And *if* we go down this path, is it "enough" to do in the LGR (i.e. ICANN) or should IETF do some adoption (and W3C?), or should IETF say "we can move forward in a more safe way AS WE KNOW ICANN DO LGR"... Or... Patrik
- [Idna-update] FWD: Expiration impending: <draft-k… John C Klensin
- Re: [Idna-update] [Ext] FWD: Expiration impending… Kim Davies
- Re: [Idna-update] [Ext] FWD: Expiration impending… Patrik Fältström
- Re: [Idna-update] [Ext] FWD: Expiration impending… Andrew Sullivan
- Re: [Idna-update] [Ext] FWD: Expiration impending… Patrik Fältström
- Re: [Idna-update] [Ext] FWD: Expiration impending… Patrik Fältström
- Re: [Idna-update] [Ext] FWD: Expiration impending… John R. Levine
- Re: [Idna-update] [Ext] FWD: Expiration impending… Suzanne Woolf
- Re: [Idna-update] [Ext] FWD: Expiration impending… Andrew Sullivan
- Re: [Idna-update] [Ext] FWD: Expiration impending… Asmus Freytag
- Re: [Idna-update] FWD: Expiration impending: <dra… Francisco Arias
- Re: [Idna-update] [Ext] FWD: Expiration impending… John C Klensin
- Re: [Idna-update] [Ext] FWD: Expiration impending… Asmus Freytag
- Re: [Idna-update] [Ext] FWD: Expiration impending… Andrew Sullivan
- Re: [Idna-update] [Ext] FWD: Expiration impending… Patrik Fältström
- Re: [Idna-update] [Ext] FWD: Expiration impending… Asmus Freytag
- Re: [Idna-update] [Ext] FWD: Expiration impending… Patrik Fältström
- Re: [Idna-update] Expiration impending: <draft-kl… Patrik Fältström
- Re: [Idna-update] Expiration impending: <draft-kl… John C Klensin
- Re: [Idna-update] Expiration impending: <draft-kl… Francisco Arias
- Re: [Idna-update] Expiration impending: <draft-kl… Patrik Fältström
- Re: [Idna-update] Expiration impending: <draft-kl… John C Klensin
- Re: [Idna-update] Expiration impending: <draft-kl… Andrew Sullivan
- Re: [Idna-update] Expiration impending: <draft-kl… John C Klensin
- Re: [Idna-update] Expiration impending: <draft-kl… Andrew Sullivan
- Re: [Idna-update] Expiration impending: <draft-kl… Asmus Freytag
- Re: [Idna-update] Expiration impending: <draft-kl… Asmus Freytag
- [Idna-update] IDNA and combining sequences (was: … John C Klensin
- Re: [Idna-update] Expiration impending: <draft-kl… John C Klensin
- Re: [Idna-update] IDNA and combining sequences (w… Patrik Fältström
- Re: [Idna-update] IDNA and combining sequences (w… John C Klensin
- Re: [Idna-update] IDNA and combining sequences (w… Mark Davis ☕️
- Re: [Idna-update] IDNA and combining sequences Asmus Freytag (c)
- Re: [Idna-update] IDNA and combining sequences (w… John Levine
- Re: [Idna-update] IDNA and combining sequences Asmus Freytag (c)
- Re: [Idna-update] Expiration impending: <draft-kl… Asmus Freytag
- Re: [Idna-update] IDNA and combining sequences Patrik Fältström
- Re: [Idna-update] IDNA and combining sequences John C Klensin
- Re: [Idna-update] IDNA and combining sequences (w… John C Klensin
- Re: [Idna-update] IDNA and combining sequences (w… John R Levine
- Re: [Idna-update] IDNA and combining sequences (w… Asmus Freytag
- Re: [Idna-update] IDNA and combining sequences (w… John Levine
- Re: [Idna-update] IDNA and combining sequences (w… Asmus Freytag (c)
- Re: [Idna-update] Expiration impending: <draft-kl… John C Klensin
- Re: [Idna-update] IDNA and combining sequences (w… John Levine
- Re: [Idna-update] IDNA and combining sequences (w… Asmus Freytag (c)
- Re: [Idna-update] IDNA and combining sequences (w… John R Levine