<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi James, Hi all,
<div class=""><br class="">
<div class="">
<div>
<blockquote type="cite" class="">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">URL: <a href="http://www.ietf.org/internet-drafts/draft-gould-idn-table-00.txt" class="">http://www.ietf.org/internet-drafts/draft-gould-idn-table-00.txt</a><br class="">
Status: <a href="https://datatracker.ietf.org/doc/draft-gould-idn-table/" class="">https://datatracker.ietf.org/doc/draft-gould-idn-table/</a><br class="">
Htmlized: <a href="http://tools.ietf.org/html/draft-gould-idn-table-00" class="">http://tools.ietf.org/html/draft-gould-idn-table-00</a><br class="">
</div>
<br class="">
<div class="">Please review the draft and provide any feedback.</div>
</div>
</div>
</blockquote>
<br class="">
</div>
<div>I’ve reviewed this draft, and the -01 update, and have some belated feedback on this document.</div>
<div><br class="">
</div>
<div>Along with colleagues in the community, I have been working on draft-davies-idntables (<a href="https://tools.ietf.org/html/draft-davies-idntables" class="">https://tools.ietf.org/html/draft-davies-idntables</a>) 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.</div>
<div><br class="">
</div>
<div>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.</div>
<div><br class="">
</div>
<div>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.</div>
<div><br class="">
</div>
<div>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.</div>
<div><br class="">
</div>
<div>cheers,</div>
<div><br class="">
</div>
<div>kim</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
<br class="">
</div>
</div>
</body>
</html>