IETF Logo Mail Archive

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

"Patrik Fältström " <paf@frobbit.se> Mon, 05 March 2018 20:09 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 6DC3912E8B1 for <idna-update@ietfa.amsl.com>; Mon, 5 Mar 2018 12:09:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 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, URIBL_BLOCKED=0.001] 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 yT9NbSToDSpX for <idna-update@ietfa.amsl.com>; Mon, 5 Mar 2018 12:09:14 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E185312DB71 for <idna-update@ietf.org>; Mon, 5 Mar 2018 12:09:11 -0800 (PST)
Received: from [192.168.10.145] (c-8cb1d954.028-114-73746f27.cust.bredbandsbolaget.se [84.217.177.140]) by mail.frobbit.se (Postfix) with ESMTPSA id AD1651FE80; Mon, 5 Mar 2018 21:09:08 +0100 (CET)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Andrew Sullivan" <ajs@anvilwalrusden.com>
Cc: "Kim Davies" <kim.davies@icann.org>, "John C Klensin" <john-ietf@jck.com>, idna-update@ietf.org
Date: Mon, 05 Mar 2018 21:09:08 +0100
X-Mailer: MailMate (2.0BETAr6104)
Message-ID: <9BA1DCD7-F981-461A-9D4B-EF5B0E6A8FEE@frobbit.se>
In-Reply-To: <161f7c23760.2772.55b9c0b96417b0a70c4dcaded0d2e1c6@anvilwalrusden.com>
References: <0AAE384126E73857E6EEC32C@PSB> <20180305191527.GA99731@KIDA-6861.local> <822FD6FA-4FA5-449D-9491-01315DB57A9E@frobbit.se> <161f7c23760.2772.55b9c0b96417b0a70c4dcaded0d2e1c6@anvilwalrusden.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_7602E980-9FBA-43FA-9233-7241CDC628E8_="; micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/yq50Orlx3Pt8hdXtHvVSl-0J390>
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:09:21 -0000

I hope they know, at least I have the view I have reported we have a stall. I have not heard any opinion part from more architectural questions and ideas on "what should we do in general as this is a hard question". Which is not answering this specific question.

   Patrik

On 5 Mar 2018, at 21:02, Andrew Sullivan wrote:

> 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
>>
>
>
> _______________________________________________
> IDNA-UPDATE mailing list
> IDNA-UPDATE@ietf.org
> https://www.ietf.org/mailman/listinfo/idna-update

v2.8.7 | Report a Bug | By Email