Re: [eppext] what to do about IDN tables

James Galvin <galvin@elistx.com> Thu, 05 November 2015 00:49 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 46B8A1B3513 for <eppext@ietfa.amsl.com>; Wed, 4 Nov 2015 16:49:16 -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 I-vZO1CO_2FD for <eppext@ietfa.amsl.com>; Wed, 4 Nov 2015 16:49:14 -0800 (PST)
Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (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 EF57D1B3509 for <eppext@ietf.org>; Wed, 4 Nov 2015 16:49:13 -0800 (PST)
Received: by qgeb1 with SMTP id b1so2025598qge.1 for <eppext@ietf.org>; Wed, 04 Nov 2015 16:49:13 -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=SfdmVi7B1P30SAdzR2JUvOlMm/g69Vh1RLNUyVUvOHM=; b=LfXQ6Ey5m8uOoE28leFpTQO4SOoqciZbwOEUHGLbK/Ay/qtekmTAqFPmyDPDE4hrqH uStpqzrcIgqriRXxF0yE+Je/pJUiTVDYXeuigyKurwnCgPsQ5JuYGweJpBKDtUAnixUk yoy5qfTuF2c+FjJjfzxU8erGkaPl8Ag1hBAV9Omc9duQdSV6onyj2fLNl9JqdbZYkhFy TPrDDkZ9V+gMEqhv40loKv/tgu7ZWyvKaipDANhoB84lNa24eRnj9O3GHjcLHSOP8XGW WYgGUfT/CEo0e6iRShXfX6oJivxKzTLQeYhqQxQQ24uAiC0AcGvo1u0FXJINtTu5tndY nNSw==
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=SfdmVi7B1P30SAdzR2JUvOlMm/g69Vh1RLNUyVUvOHM=; b=LQmHPw0HGKVxhwPiVgFHJmM4CMbPETbQCywoxMnDh+Gp8Tq4d+GVEAoCefziTdIWgg xXdwXwPduiKoWVFb0qZ212CWRHIZGNVnhBv8ngbWEw6ZSjFk5pQOuDMy3PtPGYLZFyyv gcabO1WtrgEsV4WKaQxxsF4wmzU99gX/MUyFnnjgZLX0uoeD5dXap8Bhqp0vlpqLxINh bJ6OVVaV8jvyYFHJtx9rL7zMltfkzkWZtFhKf7guxJvuYMinSz3sbnr8dxcGa0dcxRaY NDf5deX7S05yW/62P3+x2NSA0WVXAje+8iPWAVmFoe8DHPOKaQ+eSgcbanqyUuhkxy3Y 5w1g==
X-Gm-Message-State: ALoCoQkrUwr1QPKM4yLEIRHkYqU8si7eu3VRBLuUqSJkWJSb5Pab63bonaJVqUBN99e4h8GqTyIQ
X-Received: by 10.140.242.209 with SMTP id n200mr4915051qhc.59.1446684552999; Wed, 04 Nov 2015 16:49:12 -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 92sm1012621qgi.40.2015.11.04.16.49.11 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Nov 2015 16:49:11 -0800 (PST)
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "Gould, James" <JGould@verisign.com>
References: <563A7219.1050605@elistx.com> <973C1210-541C-46DC-8754-D06B1799DC4A@verisign.com> <563A7BE1.4010805@elistx.com> <545D0511-1497-4767-B66E-4E03D0A17781@verisign.com> <831693C2CDA2E849A7D7A712B24E257F4A0D9EEA@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
From: James Galvin <galvin@elistx.com>
Message-ID: <563AA7A7.2090001@elistx.com>
Date: Wed, 4 Nov 2015 19:49:43 -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: <831693C2CDA2E849A7D7A712B24E257F4A0D9EEA@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/f8xMf3G6aHEyMY9b1sQ050ee3Jw>
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:49:16 -0000

Thanks for this Scott.

My interpretation of this for the working group, particularly since the 
draft is currently expired, is that the authors of the other documents 
could consider if they provide the features documented in the Wilcox 
draft and, if not, consider if they could incorporate them.  However, 
they are under no obligation and the Wilcox document does not need to be 
a working group document.

Do folks agree?

Jim



On 11/4/15 7:17 PM, Hollenbeck, Scott wrote:
> 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
>
>
>
>
> *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
>