Re: Perhaps out of scope, but valuable: IDN Codepoint

And not even that,

Since you're using XML to exchange the request, if you specify the appropriate character encoding and pass the document with entities such as:

<?xml version="1.0" encoding="utf-8" standalone="no"?>
 <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
   <command>
     <check>
       <domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
         <domain:name>espa&#241;ol.com</domain:name>
       </domain:check>
     </check>
   </command>
 </epp>

On the registry side, you should be able to decode it properly and generate a UTF-8 string with: español.com

Which can be validated in the registry.

IDNs should be obscured to the client as much as possible. There's no need for them to know at this level that this domain name translates into xn--espaol-zwa.com since that's something that the registry must handle internally. 

Francisco


On May 31, 2011, at 3:53 AM, Gavin Brown wrote:

>> [snip]
>> Is this obtuse to our focus?
> 
> I don't think it has any relevance to the LaunchPhase extension.
> 
> EPP currently has no way to signal any metadata relating to IDNs. There
> was a draft for an extension but it expired some time ago.
> 
> EPP is strictly a provisioning protocol, and therefore signalling of
> policy (such as what code points are permitted) is out of scope. The
> current best practice is for registries to submit their IDN tables to
> IANA for publication. These can then be used by registrars to
> pre-validate domains before attempting to register them.
> 
> Having said that, an EPP extension that extended the semantics of
> <check> might be useful - something like this:
> 
>  <?xml version="1.0" encoding="utf-8" standalone="no"?>
>  <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
>    <command>
>      <check>
>        <domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
>          <domain:name>xn--eqrt2g.xn--fiqs8s</domain:name>
>        </domain:check>
>      </check>
>    </command>
>    <extension>
>      <validate:check xmlns="urn:centralnic:params:xml:ns:validate-1.0">
>        <validate:language>zh</validate:language>
>      </validate:check>
>    </extension>
>  </epp>
> 
> We implemented a function in our HTTP Toolkit [1] to do something very
> similar.
> 
> G.
> 
> 1: https://www.centralnic.com/registrars/toolkit/doc/validate_domain
> 
> -- 
> Gavin Brown
> Chief Technology Officer
> CentralNic Ltd
> Innovative, Reliable and Flexible Registry Services
> for ccTLD, gTLD and private domain name registries
> https://www.centralnic.com/
> 
> CentralNic Ltd is a company registered in England and Wales with company
> number 4985780. Registered Offices: 35-39 Moorgate, London, EC2R 6AR.
> 
> _______________________________________________
> provreg mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/provreg

Francisco Obispo 
Hosted@ Programme Manager
email: [email protected]
Phone: +1 650 423 1374 || INOC-DBA *3557* NOC
Key fingerprint = 532F 84EB 06B4 3806 D5FA  09C6 463E 614E B38D B1BE




_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg