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

"Patrik Fältström " <paf@frobbit.se> Tue, 06 March 2018 10:31 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 AB3BF127078 for <idna-update@ietfa.amsl.com>; Tue, 6 Mar 2018 02:31:44 -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 TQHiarX1RDIY for <idna-update@ietfa.amsl.com>; Tue, 6 Mar 2018 02:31:43 -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 F29C8127137 for <idna-update@ietf.org>; Tue, 6 Mar 2018 02:31:42 -0800 (PST)
Received: from [172.20.10.2] (unknown [IPv6:2a02:aa1:1002:1a12:2165:4e06:865b:c89e]) by mail.frobbit.se (Postfix) with ESMTPSA id A30FA22AD0; Tue, 6 Mar 2018 11:31:40 +0100 (CET)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Francisco Arias" <francisco.arias@icann.org>
Cc: idna-update@ietf.org
Date: Tue, 06 Mar 2018 11:31:39 +0100
X-Mailer: MailMate (2.0BETAr6104)
Message-ID: <0FB6F961-41C2-42EB-8713-C5B2F2CA83FD@frobbit.se>
In-Reply-To: <091044BC-5FE8-4050-911F-DACB83A4DDD4@icann.org>
References: <091044BC-5FE8-4050-911F-DACB83A4DDD4@icann.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_192C9D8B-4A6E-4137-A2B1-A9248F55FAE0_="; micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/lv2SU7gCPjM-A1Uob0YPLcyER28>
Subject: Re: [Idna-update] 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: Tue, 06 Mar 2018 10:31:45 -0000

How do you believe this is to be implemented in all TLDs? I.e. what do you believe is the enforcement mechanism?

   Patrik

On 5 Mar 2018, at 23:22, Francisco Arias wrote:

> Following on Asmus' comment below, perhaps the IDN Implementation Guidelines could help as a way to reach out to TLD registries?
>
> https://www.icann.org/resources/pages/implementation-guidelines-2012-02-25-en
>
> I believe the process to update them is ongoing https://community.icann.org/display/IDN/IDN+Implementation+Guidelines
>
> Regards,
>
> -- 
> Francisco
>
> On 3/5/18, 2:12 PM, "IDNA-UPDATE on behalf of Asmus Freytag" <idna-update-bounces@ietf.org on behalf of asmusf@ix.netcom.com> wrote:
>
>     Secondary to that is finding a way to communicate the to consumers of
>     these tables that simply allowing all PVALID code points isn't a robust
>     solution for many writing systems and additional due diligence needs to
>     be preformed - for example along the same lines as is being done now for
>     the Root Zone (which is quickly defining the state of the art in that
>     respect).
>
>
> _______________________________________________
> IDNA-UPDATE mailing list
> IDNA-UPDATE@ietf.org
> https://www.ietf.org/mailman/listinfo/idna-update