Re: [Idna-update] [Ext] FWD: Expiration impending: <draft-klensin-idna-rfc5891bis-01.txt>

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 05 March 2018 20:03 UTC

Return-Path: <ajs@anvilwalrusden.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 B322A1205D3 for <idna-update@ietfa.amsl.com>; Mon, 5 Mar 2018 12:03:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=jMpp98Kl; dkim=pass (1024-bit key) header.d=yitter.info header.b=JS29S1Dd
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 uMgG-TXgALOO for <idna-update@ietfa.amsl.com>; Mon, 5 Mar 2018 12:03:14 -0800 (PST)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 966A812EAA5 for <idna-update@ietf.org>; Mon, 5 Mar 2018 12:03:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id D7A60BE778; Mon, 5 Mar 2018 20:02:39 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1520280159; bh=bpbrqc/YnvnuFAm+zw2bq2Y8QkXCEbzJEXitqwXPNHY=; h=From:To:CC:Date:In-Reply-To:References:Subject:From; b=jMpp98KleLvq1hXlp5ebGZ9sVG49VSKD936Q71Irs9hsjfi7Zn4YEEfRc2NIg77ar mMNuSWlmEPskKJKKO3F/CHCCgGOLqhnkENuCa102et1LlpE1n55a6d8yy1eeyP04F9 c4t51L3r5ON0HdJGpGzwRFMVFIOZpfMEXaoQGIyI=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3j5EzXOLSd5y; Mon, 5 Mar 2018 20:02:38 +0000 (UTC)
From: Andrew Sullivan <ajs@anvilwalrusden.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1520280158; bh=bpbrqc/YnvnuFAm+zw2bq2Y8QkXCEbzJEXitqwXPNHY=; h=From:To:CC:Date:In-Reply-To:References:Subject:From; b=JS29S1DdR84XQV22lo76UAobmgekNGFxXcToldcKCoWwhyb6aumDqOfaI2/c0BsSF WQLINf4TTt8nKCs5QazwPsBwHRfX63rtxds1lF6+Y9CIpqtwVkX/2SwIbNUr1rj8R7 D/iP32OE2eNnGmHjFEmZeRhb/Ccb91l77uY/ptCA=
To: =?utf-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>, Kim Davies <kim.davies@icann.org>
CC: John C Klensin <john-ietf@jck.com>, <idna-update@ietf.org>
Date: Mon, 05 Mar 2018 15:02:36 -0500
Message-ID: <161f7c23760.2772.55b9c0b96417b0a70c4dcaded0d2e1c6@anvilwalrusden.com>
In-Reply-To: <822FD6FA-4FA5-449D-9491-01315DB57A9E@frobbit.se>
References: <0AAE384126E73857E6EEC32C@PSB> <20180305191527.GA99731@KIDA-6861.local> <822FD6FA-4FA5-449D-9491-01315DB57A9E@frobbit.se>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/yOJqNuCzt_IDECh6hKXTqcrr7ck>
Subject: Re: [Idna-update] [Ext] FWD: 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: Mon, 05 Mar 2018 20:03:18 -0000

Does the IAB know that, and have an opinion?

A

-- 
Please excuse my clumbsy thums



----------
On March 5, 2018 14:38:48 Patrik Fältström <paf@frobbit.se> wrote:

> On 5 Mar 2018, at 20:15, Kim Davies wrote:
>
>> Quoting John C Klensin on Monday March 05, 2018:
>>
>>> Given that there has been no discussion of this draft in the
>>> last few months, that there seems to be no interest in it in the
>>> IESG (although we have not pressed hard on it specifically), and
>>> that the possibly-complementary
>>> draft-freytag-troublesome-characters draft has already expired,
>>> I'm just going to let this expire unless someone gives me a good
>>> reason why not in the next few minutes (if a revision is not
>>> posted today, the draft will expire because, without special
>>> permission, nothing can be posted between tomorrow and the start
>>> of IETF).
>>>
>>> I hope no one interprets this as complete lack of interest in
>>> pursuing IDN issues, or even clarification of the IDNA
>>> standards, in the IETF.
>>
>>
>> With the expiry of these efforts, I am concerned more generally that the 
>> standing IAB guidance in
>> https://www.iab.org/documents/correspondence-reports-documents/2015-2/iab-statement-on-identifiers-and-unicode-7-0-0/
>> has kept the pre-computed IDNA tables published at IANA downgraded to 
>> Unicode 6.3.0 for a number of years. It seems appropriate to revisit 
>> publishing tables against contemporary Unicode editions if there is no 
>> active work on publishing clarifying RFCs in this regard.
>
> Speaking as the by IAB appointed expert that do approve new tables, I 
> simply can not unless there are some guidance and agreement in the IETF on 
> how to move forward.
>
> The few people involved that spend time on these issues makes it hard to 
> draw conclusions on "the right path forward". This given the situation we 
> are in, as described by John.
>
>    Patrik
>
>
>
> ----------
> _______________________________________________
> IDNA-UPDATE mailing list
> IDNA-UPDATE@ietf.org
> https://www.ietf.org/mailman/listinfo/idna-update
>