Re: [eppext] what to do about IDN tables

James Galvin <galvin@elistx.com> Wed, 04 November 2015 21:42 UTC

Return-Path: <galvin@elistx.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 B3C051B335D for <eppext@ietfa.amsl.com>; Wed, 4 Nov 2015 13:42:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, USER_IN_WHITELIST=-100] 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 SNHii5Z6ubXC for <eppext@ietfa.amsl.com>; Wed, 4 Nov 2015 13:42:28 -0800 (PST)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 D29A31B3357 for <eppext@ietf.org>; Wed, 4 Nov 2015 13:42:27 -0800 (PST)
Received: by qkct129 with SMTP id t129so25675555qkc.2 for <eppext@ietf.org>; Wed, 04 Nov 2015 13:42:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=elistx_com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=w+/I1g3kebXJsQTta7m8arcKXLPKgolqLKK60rALe2Y=; b=pTH2FB2FHcxGbdjG7zyWYq4rETHbS+y6f01Y3BV9fNUhCQfWRyeMB19gs1Dx8/AFqw IcQ81Tyfcy2ZwoQra/cd0saN1wBGSFzx5l4OnqRABXPq6Do9u40Uzpc2M4NcxawD6NFT HzblzzOe3hkmiMRga152bQoP0qNguJH8Bck6FWaU+4wXNr2rXGqnb7VjDfhgAXkjvjTa 482Lb3y/y5ki6nG1X8m+sjh5oAUT/XCAYGCyg5G1d+4wJK5U/GihAqfxK4dMwcNVc+at jh2Mfsd00zedoyy4bo6K0jwr8DWrf1huIq2Sm9/h+ZHGcFappDvjqnsOiUIX0OCQ1A4x Ng6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=w+/I1g3kebXJsQTta7m8arcKXLPKgolqLKK60rALe2Y=; b=lZyA5zt4Il97spOJjlx90CFOZIKDNthJDHE+UwL8nwLKYtxalm3oF8mXgoJ34pwdAM Vdjh9L0x0W/FcQFd0H5D922UVqken5z2RmXMboKKEW1zg/ZLpFXkHT6w8reOlU7+RvPC /VIUK9EtFHP+Snof0Rco7+rJj7rykJzLf5a5TMp8Vb7yoX5PN83JThzkdTqJilJmM25U XNnbQ/N1GiQNqhG/BZPjIukpyMIeIPnPeTSE0ZkXEZ9rHd2jn+Mgty53TI3Ma3luSMfV /XVRjeSw3DVZO08PS6gx4qjZXYCpmsv3WjyKTRVfSnYo5JL1hHQDZccwTW4Agh7wmau3 biSA==
X-Gm-Message-State: ALoCoQlkc62dW2ng9eb60TkarY9IP5YHuitUX9baoLpZXSUFqYmNPWoYdoXotGTw+tye7sJY3ayW
X-Received: by 10.55.79.86 with SMTP id d83mr4008857qkb.87.1446673346971; Wed, 04 Nov 2015 13:42:26 -0800 (PST)
Received: from jgalvin-lt.local (c-73-133-108-218.hsd1.md.comcast.net. [73.133.108.218]) by smtp.googlemail.com with ESMTPSA id j94sm829318qge.27.2015.11.04.13.42.25 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Nov 2015 13:42:25 -0800 (PST)
To: "Gould, James" <JGould@verisign.com>
References: <563A7219.1050605@elistx.com> <973C1210-541C-46DC-8754-D06B1799DC4A@verisign.com>
From: James Galvin <galvin@elistx.com>
Message-ID: <563A7BE1.4010805@elistx.com>
Date: Wed, 4 Nov 2015 16:42:57 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <973C1210-541C-46DC-8754-D06B1799DC4A@verisign.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/CzjpQLKHRv3C15Zwuor-C_ByN64>
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: Wed, 04 Nov 2015 21:42:29 -0000

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
>
> 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>> 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>
>> https://www.ietf.org/mailman/listinfo/eppext
>