Internationalized Domain Name Mapping Extension for the Extensible Provisioning Protocol (EPP)

The EPP protocol provides a complete description of EPP command and response structures. A thorough understanding of the base protocol specification is necessary to understand the mapping described in this document. This document is written in consideration with the Guidelines for Extending the Extensible Provisioning Protocol as defined in . To comply with the Guidelines for the Implementation of Internationalized Domain Names, it is required to associate each label to be registered with a single script, as defined by the code division of the Unicode code chart. This requirement imposes a challenge for registries using the EPP protocol, since there is no such field currently in the domain name mapping to allow for this information to be exchanged. In addition, registries intending to comply with the recommendation of section 4.1 of the IDNA2008 protocol, which implies the verification of both the name in ASCII Compatible Encoding and Unicode form, will be able to do so using this extension. This extension adds two additional data element to the EPP Domain Name mapping, to allow for association of a domain name to an IDN table identifier, and a the domain name in Unicode Normalization Form C (NFC ).

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL","SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in . XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case representation presented in order to develop a conforming specification. "idn-1.0" is used as an abbreviation for "urn:ietf:params:xml:ns:idn-1.0". The XML namespace prefix "idn" is used, but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents.

A detailed description of the EPP syntax and semantics can be found in .

This extension does not add any elements to the EPP <check>, <poll>, or <transfer> commands or responses.

This extension does not add any elements to the EPP <info> command, but does include elements in the response, when the extension has been selected during a <login> command. Example <info> command:

C: C: C: C: C: xn--espaol-zwa.example.com C: C: 2fooBAR C: C: C: C: ABC-12345 C: C: ]]> When the info command has been processed successfully, and the domain name is an IDN, the server must include in the <extension> section of the EPP response an <idn:data> element with the following elements: A <idn:table> element that contains the IDN table identifier. A <idn:uname> element that contains the domain name in Unicode NFC form. Example <info> response for an authorized client:

S: S: S: S: Command completed successfully S: S: S: S: xn--espaol-zwa.example.com S: EXAMPLE1-REP S: S: jd1234 S: sh8013 S: sh8013 S: S: ns1.example.com S: ns1.example.net S: S: ClientX S: ClientY S: 1999-04-03T22:00:00.0Z S: ClientX S: 1999-12-03T09:00:00.0Z S: 2005-04-03T22:00:00.0Z S: 2000-04-08T09:00:00.0Z S: S: 2fooBAR S: S: S: S: S: S: es S: español.example.com S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S:]]>

This extension does not add any elements to the EPP <delete>, <renew>, or <transfer> commands or responses.

This extension defines additional elements for the EPP <create> command. If the domain name is an IDN, the EPP command MUST contain an <extension> element, which MUST contain a child <idn:data> element with the following child elements: A <idn:table> element that contains the IDN table identifier as provided by the server. An optional <idn:uname> element that contains the domain name to be registered in Unicode NFC. Example <create> command:

C: C: C: C: C: xn--espaol-zwa.example.com C: 2 C: C: ns1.example.net C: ns2.example.net C: C: jd1234 C: sh8013 C: sh8013 C: C: 2fooBAR C: C: C: C: C: C: es C: español.example.com C: C: C: 123456 C: C:]]> The server MUST validate the name using the procedure described in section 4.2 of . If the validation of the IDN name failed because it contained a code point not available in the specified IDN table, the server MUST return an EPP error 2306. In the specific case that the <domain:name> provided did not map to the provided <idn:uname>, the server MUST respond with an EPP error 2005.

An EPP object mapping is specified in XML Schema notation. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances.

Extensible Provisioning Protocol v1.0 domain name extension schema for IDN Table selection. ]]>

This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. Two URI assignments have been registered by the IANA. Registration request for the contact namespace: URI: urn:ietf:params:xml:ns:idn-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: None. Namespace URIs do not represent an XML specification. Registration request for the contact XML schema: URI: urn:ietf:params:xml:schema:idn-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: See the "Formal Syntax" section of this document.

The mapping extensions described in this document do not provide any security services beyond those described by EPP the EPP domain name mapping , and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well.