<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;">
Kim,
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>I will discuss draft-gould-idn-table at the Registration Operations Workshop ( <a href="http://www.regiops.net">http://www.regiops.net</a> ), that is being held immediately prior to IETF-92, on March 22nd. We hopefully can discuss this and other feedback
there. </div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
<div>
<div style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<p style="margin: 0px;"><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size: 15px;">—</span></font></p>
<p style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px;">
<font face="Calibri,Verdana,Helvetica,Arial" style="font-size: 14px;"><span style="font-size: 11pt;"><br>
</span></font></p>
<p style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px;">
<font face="Calibri,Verdana,Helvetica,Arial" style="font-size: 14px;"><span style="font-size: 11pt;">JG<br>
<br>
</span></font></p>
</div>
<span style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<span style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span><img height="64" width="73" apple-inline="yes" id="2602BE25-4A65-4BF7-A995-C4423155EE69" apple-width="yes" apple-height="yes" src="cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com"></span><font face="Calibri,Verdana,Helvetica,Arial" style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-size: 14px;"><span style="font-size: 11pt;"><br>
</span></font><font face="Times,Times New Roman" style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-size: 14px;"><span style="font-size: 12pt;"><br>
</span></font><font color="#006AAA" style="font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: Calibri, sans-serif; font-size: 14px;"><font size="2"><font face="Helvetica,Verdana,Arial"><span style="font-size: 10pt;"><b>James
Gould<br>
</b></span></font></font></font><font size="2" style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: Calibri, sans-serif;"><font face="Helvetica, Verdana, Arial"><span style="font-size: 10pt;"><font color="#6B6D71">Distinguished
Engineer<br>
<a href="jgould@Verisign.com">jgould@Verisign.com</a><br>
<br>
703-948-3271<br>
12061 Bluemont Way<br>
Reston, VA 20190<br>
<br>
</font><font color="#006AAA"><a href="http://VerisignInc.com">VerisignInc.com</a></font></span></font></font>
</span></span></div>
<br>
<div>
<div>On Mar 4, 2015, at 4:26 PM, Kim Davies <<a href="mailto:kim.davies@icann.org">kim.davies@icann.org</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div 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>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>