Re: Publishing of the IDN Table EPP Mapping IETF Draft
Kim Davies <[email protected]> Wed, 4 Mar 2015 21:26:42 +0000
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <[email protected]> |
--===============7906528090260775783== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_14D87A78F5A2458C969B593FE732A822icannorg_" --_000_14D87A78F5A2458C969B593FE732A822icannorg_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable 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=F1oz from Uni= registry to provide a mechanism for getting IDN Table information for the r= egistration of IDNs, using the EPP domain name mapping, and optionally with= the IDN mapping extension ( draft-ietf-eppext-idnmap ). We would like thi= s draft to be included in a re-charting of the EPPEXT Working Group. The d= raft information is provided below. URL: http://www.ietf.org/internet-drafts/draft-gould-idn-table-0= 0.txt Status: https://datatracker.ietf.org/doc/draft-gould-idn-table/ Htmlized: http://tools.ietf.org/html/draft-gould-idn-table-00 Please review the draft and provide any feedback. I=92ve reviewed this draft, and the -01 update, and have some belated feedb= ack on this document. Along with colleagues in the community, I have been working on draft-davies= -idntables (https://tools.ietf.org/html/draft-davies-idntables) and its goa= l is to document a universal format for =93IDN tables=94, intended to super= sede and be a full superset of the panoply for formats that are out there t= oday. This format has a specific schema, is intended to be fully machine re= adable, and allow implementation using a generic LGR-capable engine. Based = on draft-gould-idn-table I believe it should be fully capable of representi= ng the IDN table data described in the document. I would recommend recasting this proposed mapping to utilise draft-davies-i= dntables as the mechanism for describing code point eligibility, and making= the <info> verb in the EPP extension a mechanism for transmitting fully-fo= rmed label generation rulesets (the term for IDN tables in draft-davies-idn= tables). It would provide for maximum reuse of the grammar, plus provide th= e additional benefit that should a registry have a more complex policy than= simple codepoint eligibility that it can be accurately conveyed. Given the term =93IDN tables=94 is being gradually replaced with =93label g= eneration rulesets=94 (LGRs) in ICANN=92s work, as a more generic term that= is not specific to IDNs, it is worth considering using this terminology el= sewhere in this document. If there are particular considerations that mean draft-davies-idntables wou= ldn=92t be a suitable format, that would be useful feedback to help us iter= ate the draft-davies-idntables document with additional requirements. cheers, kim --_000_14D87A78F5A2458C969B593FE732A822icannorg_ Content-Type: text/html; charset="Windows-1252" Content-ID: <[email protected]> Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> </head> <body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin= e-break: after-white-space;" class=3D""> Hi James, Hi all, <div class=3D""><br class=3D""> <div class=3D""> <div> <blockquote type=3D"cite" class=3D""> <div class=3D""> <div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line= -break: after-white-space;" class=3D""> <div class=3D"">The first draft of the IDN Table EPP Mapping has been submi= tted to the IETF. I co-authored this draft with Francisco Obispo and = Luis Mu=F1oz 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 ext= ension ( 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=3D""><br class=3D""> </div> <div class=3D"">URL: = <a href=3D"http://www.ietf.org/internet-drafts/draft-gould-idn-= table-00.txt" class=3D"">http://www.ietf.org/internet-drafts/draft-gould-id= n-table-00.txt</a><br class=3D""> Status: <a href=3D"https://= datatracker.ietf.org/doc/draft-gould-idn-table/" class=3D"">https://datatra= cker.ietf.org/doc/draft-gould-idn-table/</a><br class=3D""> Htmlized: <a href=3D"http://tools.ietf.= org/html/draft-gould-idn-table-00" class=3D"">http://tools.ietf.org/html/dr= aft-gould-idn-table-00</a><br class=3D""> </div> <br class=3D""> <div class=3D"">Please review the draft and provide any feedback.</div> </div> </div> </blockquote> <br class=3D""> </div> <div>I=92ve reviewed this draft, and the -01 update, and have some belated = feedback on this document.</div> <div><br class=3D""> </div> <div>Along with colleagues in the community, I have been working on draft-d= avies-idntables (<a href=3D"https://tools.ietf.org/html/draft-davies-idntab= les" class=3D"">https://tools.ietf.org/html/draft-davies-idntables</a>) and= its goal is to document a universal format for =93IDN tables=94, intended to supersede and be a full superset = of the panoply for formats that are out there today. This format has a spec= ific schema, is intended to be fully machine readable, and allow implementa= tion using a generic LGR-capable engine. Based on draft-gould-idn-table I believe it should be fully capable of rep= resenting the IDN table data described in the document.</div> <div><br class=3D""> </div> <div>I would recommend recasting this proposed mapping to utilise draft-dav= ies-idntables as the mechanism for describing code point eligibility, and m= aking the <info> verb in the EPP extension a mechanism for transmitti= ng 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 shou= ld a registry have a more complex policy than simple codepoint eligibility = that it can be accurately conveyed.</div> <div><br class=3D""> </div> <div>Given the term =93IDN tables=94 is being gradually replaced with =93la= bel generation rulesets=94 (LGRs) in ICANN=92s work, as a more generic term= that is not specific to IDNs, it is worth considering using this terminolo= gy elsewhere in this document.</div> <div><br class=3D""> </div> <div>If there are particular considerations that mean draft-davies-idntable= s wouldn=92t 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=3D""> </div> <div>cheers,</div> <div><br class=3D""> </div> <div>kim</div> <div><br class=3D""> </div> <div><br class=3D""> </div> <div><br class=3D""> </div> <div><br class=3D""> </div> <div><br class=3D""> </div> <div><br class=3D""> </div> <div><br class=3D""> </div> <br class=3D""> </div> </div> </body> </html> --_000_14D87A78F5A2458C969B593FE732A822icannorg_-- --===============7906528090260775783== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg --===============7906528090260775783==--