Re: [eppext] what to do about IDN tables

Francisco Arias <francisco.arias@icann.org> Thu, 05 November 2015 05:56 UTC

Return-Path: <francisco.arias@icann.org>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A76851B3A1F for <eppext@ietfa.amsl.com>; Wed, 4 Nov 2015 21:56:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.431
X-Spam-Level:
X-Spam-Status: No, score=-3.431 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 tGTLXjbHbayz for <eppext@ietfa.amsl.com>; Wed, 4 Nov 2015 21:56:42 -0800 (PST)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C67DC1B3A28 for <eppext@ietf.org>; Wed, 4 Nov 2015 21:56:42 -0800 (PST)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Wed, 4 Nov 2015 21:56:41 -0800
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1044.021; Wed, 4 Nov 2015 21:56:41 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: Patrick Mevzek <pm@dotandco.com>, "Gould, James" <JGould@verisign.com>
Thread-Topic: [eppext] what to do about IDN tables
Thread-Index: AQHRF0Pv5KVei5J/Eke/lHfbrOqH4J6M5bAAgAA4xgCAAO1dgA==
Date: Thu, 5 Nov 2015 05:56:41 +0000
Message-ID: <D2611E6F.78730%francisco.arias@icann.org>
References: <563A7219.1050605@elistx.com> <973C1210-541C-46DC-8754-D06B1799DC4A@verisign.com> <20151105004644.GA11762@home.patoche.org>
In-Reply-To: <20151105004644.GA11762@home.patoche.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.7.151005
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: text/plain; charset="utf-8"
Content-ID: <53C78B6465ED1543BFD7678969C9548C@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/H8SUk97a5VoToKTM54gYL3FlE7s>
Cc: eppext <eppext@ietf.org>, James Galvin <galvin@elistx.com>
Subject: Re: [eppext] what to do about IDN tables
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Nov 2015 05:56:44 -0000

Regarding IDN terminology, perhaps it would be a good idea to consider
reusing what is defined in the LAGER WG?

Regards,

-- 
Francisco.







On 11/5/15, 9:46 AM, "EppExt on behalf of Patrick Mevzek"
<eppext-bounces@ietf.org on behalf of pm@dotandco.com> wrote:

>Gould, James <JGould@verisign.com> 2015-11-04 22:25
>> I will be speaking to draft-gould-idn-table at meeting.
>> I haven’t reviewed draft-wilcox-cira-idn-eppext, so I’m unsure of the
>>overlap with draft-ietf-eppext-idnmap and draft-gould-idn-table.
>
>I've implemented draft-wilcox-cira-idn-eppext and plan to implement
>draft-gould-idn-table which I have read already.
>
>There is not so much overlap between them.
>
>First, the terminology is not the same, as I've outlined in the past
>here (repertoire vs table). It would maybe be a good idea if the WG can
>come to some terminology guidelines for IDNs so that at least various
>extensions are using the same words.
>
>The CIRA extension is more closely related to the problem of variants,
>and how one domain can block registration of another, so that one is
>able to query the server for one domain and having back the list of
>variants.
>
>I believe both extensions can advance forward independently from each
>other.
>But, if needed, draft-wilcox-cira-idn-eppext could use
>draft-gould-idn-table as a terminology basis.
>
>HTH,
>
>-- 
>Patrick Mevzek
>
>_______________________________________________
>EppExt mailing list
>EppExt@ietf.org
>https://www.ietf.org/mailman/listinfo/eppext