Re: [eppext] what to do about IDN tables

"Hollenbeck, Scott" <shollenbeck@verisign.com> Thu, 05 November 2015 00:17 UTC

Return-Path: <shollenbeck@verisign.com>
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 4FBD71ACC89 for <eppext@ietfa.amsl.com>; Wed, 4 Nov 2015 16:17:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 ixYaIu6r7Wr3 for <eppext@ietfa.amsl.com>; Wed, 4 Nov 2015 16:17:03 -0800 (PST)
Received: from mail-oi0-f98.google.com (mail-oi0-f98.google.com [209.85.218.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 028741ACE10 for <eppext@ietf.org>; Wed, 4 Nov 2015 16:17:03 -0800 (PST)
Received: by oiww189 with SMTP id w189so15234oiw.2 for <eppext@ietf.org>; Wed, 04 Nov 2015 16:17:02 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:accept-language:content-language :content-type:mime-version; bh=wBdSHMCarSJbGsBeLDYpdKySVx/qBTPCEAfabEcpKhQ=; b=IjzgCav7I4AOyJiGWCIIGQ3wMUoF9JYDghp9NBqAoFtPMTbllI5RjxOMBgqNG52HCn LjssFmOf5Ej4Uz8l7wyIR+41gP8vPqwpx1Sjh0y2yAsIjve41UmJswYus1/Ml351LU32 LU8UFTGNoRg9zzN4WhcRFYPQX7uQgwwTZ7aOcrMvKJHF8WxEbzBo3uHefKYmIJjTD1Re EOaLNPSp2TiZfNZn6ZZUgyHDwhJ6cxGRHR0ZXkrsskhoaeMPWCkEhyXlxJp8fGDvn9A2 NbqgHbxT4IWQYUuk6vSXLgQcOQatSTedga/KoW5bKgPvJLK/FRZJwd1DBII8AcAgqLBt wAIg==
X-Gm-Message-State: ALoCoQkeqTfq5HDbzBqbF52FV3zOkGNJWwuCUS+UDVY0GJ4bkxu6Nrv3AjD9fuZfPKuHfEEuS6d92yLViisweefA3jWTSAOj5Q==
X-Received: by 10.140.16.131 with SMTP id 3mr4499229qgb.51.1446682622106; Wed, 04 Nov 2015 16:17:02 -0800 (PST)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id x206sm55378qka.10.2015.11.04.16.17.01 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 04 Nov 2015 16:17:02 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01 [10.173.152.255]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id tA50H1Pi031916 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 4 Nov 2015 19:17:01 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Wed, 4 Nov 2015 19:17:01 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "Gould, James" <JGould@verisign.com>, James Galvin <galvin@elistx.com>
Thread-Topic: [eppext] what to do about IDN tables
Thread-Index: AQHRF0PjAgAVVwmUikSl1vTulkLKO56Ms2YAgAAFbYCAAAOsAP//vsFwgAAUgFA=
Date: Thu, 5 Nov 2015 00:17:00 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A0D9EEA@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <563A7219.1050605@elistx.com> <973C1210-541C-46DC-8754-D06B1799DC4A@verisign.com> <563A7BE1.4010805@elistx.com> <545D0511-1497-4767-B66E-4E03D0A17781@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-dg-ref: PG1ldGE+PGF0IG5tPSJpbWFnZTAwMS5wbmciIHA9IiIgc3o9IjAiIHQ9IjAiIGg9IiIgaWQ9IiIgYmw9IjAiLz48L21ldGE+
x-originating-ip: [10.173.152.4]
Content-Type: multipart/related; boundary="_004_831693C2CDA2E849A7D7A712B24E257F4A0D9EEABRN1WNEXMBX01vc_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/WjOm386C_Mt9ppcZWsac83lbUh4>
Cc: eppext <eppext@ietf.org>
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 00:17:09 -0000

Jack will be in the room for a few minutes at the beginning of the session. He said this in email:

“The objective of the draft is to be informative, to represent CIRA’s implementation, and to be used as a reference for/and we’re going to
seek publication in the EPP Extensions Registry.

I don’t see any overlap with any other draft because it reflects specially our implementation.”

Scott

From: Hollenbeck, Scott
Sent: Wednesday, November 04, 2015 6:03 PM
To: Gould, James; James Galvin
Cc: eppext
Subject: RE: [eppext] what to do about IDN tables

I know Jacques Latour is here. I’ll ask him.

Scott

From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Gould, James
Sent: Wednesday, November 04, 2015 4:56 PM
To: James Galvin
Cc: eppext
Subject: Re: [eppext] what to do about IDN tables

Can anyone speak to draft-wilcox-cira-idn-eppext at the meeting?
—

JG

[cid:image001.png@01D11735.5E35E170]

James Gould
Distinguished Engineer
jgould@Verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com<http://VerisignInc.com>

On Nov 4, 2015, at 4:42 PM, James Galvin <galvin@elistx.com<mailto:galvin@elistx.com>> wrote:

Thanks for bring this summary forward.

We just need to consider what to do with respect to the Wilcox document.

Jim



On 11/4/15 4:23 PM, Gould, James wrote:
Jim,

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.   The authors of
draft-ietf-eppext-idnmap and I created draft-gould-idn-table to address
one key item missing from draft-ietf-eppext-idnmap which was how to
identify the valid set of table identifiers to pass using
draft-ietf-eppext-idnmap for an IDN domain name.  We discussed the issue
on the list over a period of time, where I was proposing to use language
instead of a table identifier.  We agreed to stick with the table
identifier, but we needed a reliable way to determine the table
identifiers specific to the server, which is addressed with
draft-gould-idn-table.  Both draft-ietf-eppext-idnmap and
draft-gould-idn-table have been implemented in the Verisign EPP SDK that
includes a client and server implementation.  Ideally
draft-gould-idn-table and draft-ietf-eppext-idnmap would move up
together, but if not draft-gould-idn-table should be included in the
next set of working group documents.

Let me know if you have any additional questions.

Thanks,

—


JG




*James Gould
*Distinguished Engineer
jgould@Verisign.com<mailto:jgould@Verisign.com>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com <http://VerisignInc.com>

On Nov 4, 2015, at 4:01 PM, James Galvin <galvin@elistx.com
<mailto:galvin@elistx.com<mailto:galvin@elistx.com%0b%3cmailto:galvin@elistx.com>>> wrote:

A question that will be asked in the working group meeting today is
what to do about IDN tables?

There is a working group document that has recently expired:

draft-ietf-eppext-idnmap/

This document is languishing because Francisco has not gotten the
required implementation statements yet.  We can certainly revive it
but we may need to consider moving forward with incomplete
implementation reports.

In addition, there were two related individual submissions that have
also recently expired:

draft-gould-idn-table/
draft-wilcox-cira-idn-eppext/

These three documents are not all the same but they are related.  The
question is how to move forward.

Are Gould and Wilcox withdrawing their documents?  Are they going to
seek publication in the EPP Extensions Registry?

If they want to seek being adopted by the working group then we will
need to address the apparent relationship with the existing working
group document.

Comments and suggestions are welcome.

Thanks,

Jim

_______________________________________________
EppExt mailing list
EppExt@ietf.org<mailto:EppExt@ietf.org> <mailto:EppExt@ietf.org>
https://www.ietf.org/mailman/listinfo/eppext