Re: New Version Notification for draft-obispo-epp-idn-02.txt
Francisco Obispo <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <[email protected]> |
Hi Ben, On Apr 28, 2013, at 11:19 AM, Ben Levac <[email protected]> wrote: > Francisco, > > We are current planning on leveraging this extension for IDN registrations in our registry, but were wondering if you would consider making the uname element optional (minOccurs = 0)? Because most of the existing gTLDs currently don't expect the uname as part of the create request, we are worried that this could be a barrier to registrar adoption of our IDNs. They might not be prepared to send the uname in the create request (because the TLDs they support today don't expect it), and may or may not be willing to do the work required in order to pass that information. > I guess we could do that, since the validation of the name and uname, is a recommendation as appears on: http://tools.ietf.org/html/rfc5891#section-4.1 I'll add this to my list of changes. > If the UNAME element is provided by the registrar in the CREATE command, then the registry should have to validate that it matches the a-label form in the domain name field. An error should be returned otherwise. If the UNAME is not supplied, then the server would only validate that the characters are part of the language table supplied. > > We have no problem with the server returning the uname for all info requests for IDN names. > OK, I think this is good compromise. > Also, on a minor note, we should fix the indentation of the "idnDataType" complex type in the XSD definition to be at the same level as the "data" element. > Will do.! > Thank you. > > Ben Levac Francisco Obispo Director of Applications and Services - ISC email: [email protected] Phone: +1 650 423 1374 || INOC-DBA *3557* NOC PGP KeyID = B38DB1BE _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg