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

Kim Davies <> Wed, 04 March 2015 21:26 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 26AFC1A874A; Wed, 4 Mar 2015 13:26:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tPKp39Yc8byH; Wed, 4 Mar 2015 13:26:45 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 47C5A1A1ABF; Wed, 4 Mar 2015 13:26:45 -0800 (PST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.847.32; Wed, 4 Mar 2015 13:26:43 -0800
Received: from ([]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([]) with mapi id 15.00.0847.030; Wed, 4 Mar 2015 13:26:43 -0800
From: Kim Davies <>
To: "Gould, James" <>
Thread-Topic: [provreg] Publishing of the IDN Table EPP Mapping IETF Draft
Thread-Index: AQHQQWJumxRDFmqfz0eXkuVv273QPp0NhymA
Date: Wed, 04 Mar 2015 21:26:42 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-AU, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_14D87A78F5A2458C969B593FE732A822icannorg_"
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: Wed, 04 Mar 2015 21:26:48 -0000

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.