Re: New Version Notification for draft-obispo-epp-idn-00.txt
"Gould, James" <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <CB1898CB.1ED74%[email protected]> |
Francisco, This draft looks very similar to our custom "IDN Language Tag" extension available at the URL http://www.verisigninc.com/assets/idn-language-tag.pdf. In our custom extension only the create is extended; although I believe including it in the info response is an enhancement driven by the login extension services. We only require the extension for punycode encoded IDN domain names, so my question is if the extension is not included, is the default assumed to be language "en"? I'm assuming that this extension would only be required for IDN registrations based on its name, but it's not clear. Our custom extension includes the text "A valid language tag is a required field for ALL IDN registrations". We require puny code encoded domain name values for the IDN registrations, which is the key to determine if the extension is required. Some verbiage in the draft around when the extension is required and what is the expected behavior for registrations when it's not provided (e.g. default of "en") would be helpful. Use of the XML schema language type is flexible from a protocol perspective, but the registries would need to publish the supported language tag values most likely out-of-band. Hopefully we could define a consistent scheme for the possible language tag values. As far as the thread around adding the extension to the check, I don't see a driver for adding the extension to the check since the check command typically only does a simple availability check and doesn't implement all of the business logic validation that is done in the create. The check needs to be fast and it supports multiple domain names that could have different language tags, thus requiring the registrant to execute multiple checks or adding additional complexity to the idn language tag extension. -- JG James Gould Principal Software Engineer [email protected] 703-948-3271 21345 Ridgetop Circle LS2-2-1 Dulles, VA 20166 VerisignInc.com On 12/21/11 7:32 PM, "Francisco Obispo" <[email protected]> wrote: >Draft for EPP-IDN extension has been submitted. > > > >Begin forwarded message: > >> From: [email protected] >> Subject: New Version Notification for draft-obispo-epp-idn-00.txt >> Date: December 21, 2011 4:22:34 PM PST >> To: [email protected] >> Cc: [email protected], [email protected], [email protected] >> >> A new version of I-D, draft-obispo-epp-idn-00.txt has been successfully >>submitted by Paul Selkirk and posted to the IETF repository. >> >> Filename: draft-obispo-epp-idn >> Revision: 00 >> Title: Internationalized Domain Name Mapping Extension for the >>Extensible Provisioning Protocol (EPP) >> Creation date: 2011-12-21 >> WG ID: Individual Submission >> Number of pages: 8 >> >> Abstract: >> This document describes an Extensible Provisioning Protocol (EPP) >> extension mapping for the provisioning of Internationalized Domain >> Names (IDN) stored in a shared central repository. This mapping >> extends the EPP domain name mapping to provide additional features >> required to implement registrations of domain names in characters >> sets other than ASCII. >> >> >> >> >> The IETF Secretariat > >Francisco Obispo >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 _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg