Re: [Idna-update] [I18nrp] [art] Comments on draft-faltstrom-unicode11-02

"Asmus Freytag (c)" <asmusf@ix.netcom.com> Tue, 09 October 2018 05:37 UTC

Return-Path: <asmusf@ix.netcom.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 531B6131166; Mon, 8 Oct 2018 22:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ix.netcom.com; domainkeys=pass (2048-bit key) header.from=asmusf@ix.netcom.com header.d=ix.netcom.com
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 c2UBn-2TKmYN; Mon, 8 Oct 2018 22:37:05 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B089413115A; Mon, 8 Oct 2018 22:37:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ix.netcom.com; s=dk12062016; t=1539063425; bh=8K7LOVMZY93sl1Ifyfqp1fO8WfS5m/GouxKO 5ZRCMaE=; h=Received:Subject:To:Cc:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language: X-ELNK-Trace:X-Originating-IP; b=bkNYQfQH3tVhw9nvx/GWWah/BmtV3B+kk RJltmZF/RPA5EjUflhnHvijpc+oIa/Xg6d/p6BuI1WQHT/p7E78B75ojTn/KoVAG1qK l40uMBTXPaaB5HGHrRR7iJri9m8Xn7n2ptnZvyoBBlJgrYkDyEE83KXI4nGF4h0oYs4 a/q3kRRAdM7Fs8h8w9UlYN85zSxPeUcSwcopuSTCMB6/HUPHuVUaz86i/wB1wCPwe7/ ZdLSuu4toyJqKfeuDICd/CO+6rPU3Pumio9WM7VUgCZtc6mR5ZGj4ojPLoOaZhijmhw TWNq6iETcnzngGIXlC3iwyp1anuboZ8N2+3cpaLuA==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=ix.netcom.com; b=e1TGXEmWtqwTFwAdatUbuINH/2CTgXeNr8FWVInO7W371+pUddmhg2LVXWhLwfA6OyvEiea8pjRUv50aBTO85tlU7yvP5KawCBynn3jTwVP2xT1V1G+PmweJxlHUE9SJ2FQHPe/zFU6uScs11T0HLWNZf2FLXoI6GzkaNgK7tzpWsquauPyjHIYsPzVQPahEyysIxb0Js0QOuH3+p+aAAst3da7hrJYi11er4H1Sy0o4rvE8t4gmbKGNmiD1XXlJAvq1nOKhlRJayNORJvqGRjm+3Mo9DFs6CFjwaiT2T0w4IuGxpZTrglNz2DkQpZDCvk8NreeTftCAp0rUutYVsg==; h=Received:Subject:To:Cc:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [174.21.170.119] (helo=[192.168.1.108]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4) (envelope-from <asmusf@ix.netcom.com>) id 1g9khY-0005kh-OO; Tue, 09 Oct 2018 01:37:01 -0400
To: Patrik Fältström <paf@netnod.se>, Suzanne Woolf <suzworldwide@gmail.com>
Cc: Ted Hardie <ted.ietf@gmail.com>, i18nrp@ietf.org, nordmark@acm.org, Applications and Real-Time Area Discussion <art@ietf.org>, John C Klensin <john-ietf@jck.com>, idna-update@ietf.org
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org> <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se> <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com> <B0BA40527CB85EC369DD812D@PSB> <c4862804-9182-e446-02b2-dcdf5e552d11@ix.netcom.com> <D1115463-2780-49CB-851C-9FBAB7C1590A@gmail.com> <3F126D7C-7D3D-4561-A238-A6EFACF79EBB@netnod.se>
From: "Asmus Freytag (c)" <asmusf@ix.netcom.com>
Message-ID: <e102f061-81a3-e8fd-7f9b-58bb5ee9d907@ix.netcom.com>
Date: Mon, 08 Oct 2018 22:37:01 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <3F126D7C-7D3D-4561-A238-A6EFACF79EBB@netnod.se>
Content-Type: multipart/alternative; boundary="------------62972A07847AA92503EFA7F8"
Content-Language: en-US
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2b7eec10b52094b3e949cfd12a8bd0aa53155b74982b4360f350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 174.21.170.119
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/6wNiQFAeqPRSPnlpDovYS3rpZH8>
Subject: Re: [Idna-update] [I18nrp] [art] Comments on draft-faltstrom-unicode11-02
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: Tue, 09 Oct 2018 05:37:09 -0000

On 10/8/2018 9:37 PM, Patrik Fältström wrote:
>
>> On 9 Oct 2018, at 05:29, Suzanne Woolf <suzworldwide@gmail.com> wrote:
>>
>> 1. Updating the IDN parameters registry as the IAB requested. With apologies if I’m missing something, I don’t see the expert saying he can’t update the registry for some reason, or that there’s any ambiguity in what the update should be; it’s his judgment that “the right thing to do” about the code points that changed properties between Unicode 6.3 and Unicode 11 is consistent with what the standard tells him to do. So for the current situation, the standard, including the instructions to the expert, is adequate.
> The key thing here is that I do not see myself have the competence in actually ensuring what I propose in the I-D is the correct thing to do. There are other alternatives as well, such as adding an exception to the IDNA2008 rule set.
>
> IAB asked me to bring things forward, and my call is what I call path A:
> A.1. Suggest a path forward
> A.2. Ask IETF to ensure what I propose is the right thing.
>
> This is btw what was done last time we had an incompatible change like this.

Sounds like a good approach in any case.

 From where I sit, what you did looks fine, so my answer to A.2. would 
be affirmative.

A./

PS: if IAB agrees with your assessment re: rules, the more the better.

>
> Alternatives could have been:
>
> B. Be passive:
> B.1. I ask IETF what to do with the incompatible changes (but do not suggest anything)
> B.2. IETF tell me what to do
>
> C. Have IAB make the call
> C.1. IAB tell me not only to move things forward, but also “IAB have decided that the changes made in Unicode do not require backward compatible rules in IDNA2008”
> C.2. I move things forward based on B.1.
>
> FWIW, I did not interpret what IAB told me was “C” which I read in your note Suz. Maybe I misunderstand you.
>
> Now, IF IAB really told me C, then can you please clarify?
>
>     Patrik
>
> _______________________________________________
> IDNA-UPDATE mailing list
> IDNA-UPDATE@ietf.org
> https://www.ietf.org/mailman/listinfo/idna-update