Re: [provreg] Publishing of the IDN Table EPP Mapping IETF Draft

"Gould, James" <> Fri, 13 March 2015 19:12 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id BBA701A0097 for <>; Fri, 13 Mar 2015 12:12:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uxQCWY-ncAbr for <>; Fri, 13 Mar 2015 12:12:29 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 34A611A0069 for <>; Fri, 13 Mar 2015 12:12:29 -0700 (PDT)
Received: by oiga141 with SMTP id a141so81227oig.0 for <>; Fri, 13 Mar 2015 12:12:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:mime-version; bh=R8xYPfPhOf5hQPLcQ2aTLNcmfy4pz54qqxUdBpkyQK0=; b=kJB7uFX9OwSem5qHmQZlz/aeyR5PqLFrARsAAzjCGyOsJoM7pnOVTwhe7hQhclsU/N F6diNe2qZ4lRfnB+Qj2sEBZ4qCRFvsFfa3YhrBqzEIBidTrCYjwnpUdgNmsJ9vwZkCfl YGeuRI4HnkFkqY2wSF4E51lyRe+30PT/kgZj5qurUJuZYWZjVk4lyZ/o+Jkj6OWe7nRW FJmyEUVGWrDKJPBG2qPREDq0HiEM1OzQH0CmcxjY4GP+CJDfEsDrZv1pzIOrYpCCTI1n irtXn98UR+VCNZoM0/PokEQyjDy+z1EQ90hNA7jfxssvwEPSBq58G811xy3GcOEI0Its MlVg==
X-Gm-Message-State: ALoCoQlhKnF/eIoksDFg38J/7kVpSNspyF/798QGoX6/MYMxnO/v6W4F3gI0woriwRIVJH8IbfncWocL/buxBrKgI4chat1eQA==
X-Received: by with SMTP id i14mr12139105qhc.0.1426273948366; Fri, 13 Mar 2015 12:12:28 -0700 (PDT)
Received: from ( []) by with ESMTPS id cg8sm798442qcb.1.2015. (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 13 Mar 2015 12:12:28 -0700 (PDT)
Received: from (brn1wnexcas01 []) by (8.13.8/8.13.8) with ESMTP id t2DJCRxh010453 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Mar 2015 15:12:27 -0400
Received: from ([::1]) by ([::1]) with mapi id 14.03.0174.001; Fri, 13 Mar 2015 15:12:27 -0400
From: "Gould, James" <>
To: Kim Davies <>
Thread-Topic: [provreg] Publishing of the IDN Table EPP Mapping IETF Draft
Thread-Index: AQHQQWJumxRDFmqfz0eXkuVv273QPp0NhymAgA27w4A=
Date: Fri, 13 Mar 2015 19:11:58 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/related; boundary="_004_F22B58EC84F14BD092170EF7849368B9verisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <>
Cc: "" <>, "" <>, EPP Provreg <>
Subject: Re: [provreg] Publishing of the IDN Table EPP Mapping IETF Draft
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPP discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 13 Mar 2015 19:12:31 -0000


Thank you for the feedback.  The main question that I have around draft-davies-idntables is whether it is meant for servers, for clients, or both.  Would the Registrars have the need for the IDN Table code points as defined in draft-gould-idn-table or have the need for the more extensive Label Generation Rules (LGR) as defined in draft-davies-idntables from within EPP?  I will provide separate feedback to draft-davies-idntables from a server perspective, but I would like to know what information the clients would like to have.  Inclusion of the code points in draft-gould-idn-table was based on feedback from a Registrar to support caching, when the idea for draft-gould-idn-table was formed.

I will discuss draft-gould-idn-table at the Registration Operations Workshop ( ), that is being held immediately prior to IETF-92, on March 22nd.  We hopefully can discuss this and other feedback there.





James Gould
Distinguished Engineer

12061 Bluemont Way
Reston, VA 20190<>

On Mar 4, 2015, at 4:26 PM, Kim Davies <<>> wrote:

Hi James, Hi all,

The first draft of the IDN Table EPP Mapping has been submitted to the IETF.  I co-authored this draft with Francisco Obispo and Luis Muñoz from Uniregistry to provide a mechanism for getting IDN Table information for the registration of IDNs, using the EPP domain name mapping, and optionally with the IDN mapping extension ( draft-ietf-eppext-idnmap ).  We would like this draft to be included in a re-charting of the EPPEXT Working Group.  The draft information is provided below.


Please review the draft and provide any feedback.

I’ve reviewed this draft, and the -01 update, and have some belated feedback on this document.

Along with colleagues in the community, I have been working on draft-davies-idntables ( and its goal is to document a universal format for “IDN tables”, intended to supersede and be a full superset of the panoply for formats that are out there today. This format has a specific schema, is intended to be fully machine readable, and allow implementation using a generic LGR-capable engine. Based on draft-gould-idn-table I believe it should be fully capable of representing the IDN table data described in the document.

I would recommend recasting this proposed mapping to utilise draft-davies-idntables as the mechanism for describing code point eligibility, and making the <info> verb in the EPP extension a mechanism for transmitting fully-formed label generation rulesets (the term for IDN tables in draft-davies-idntables). It would provide for maximum reuse of the grammar, plus provide the additional benefit that should a registry have a more complex policy than simple codepoint eligibility that it can be accurately conveyed.

Given the term “IDN tables” is being gradually replaced with “label generation rulesets” (LGRs) in ICANN’s work, as a more generic term that is not specific to IDNs, it is worth considering using this terminology elsewhere in this document.

If there are particular considerations that mean draft-davies-idntables wouldn’t be a suitable format, that would be useful feedback to help us iterate the draft-davies-idntables document with additional requirements.