Internet Engineering Task Force N. Kong Internet-Draft J. Xie Intended status: Experimental H. Li Expires: September 6, 2012 CNNIC W. Tan Cloud Registry X. Li Chinese Academy of Sciences March 5, 2012 Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for Internationalized Domain Name (IDN) Variants draft-kong-epp-idn-variants-mapping-00 Abstract This document describes an extension of Extensible Provisioning Protocol (EPP) domain name mapping for the provisioning and management of Internationalized Domain Name (IDN) Variants. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for the provisioning of IDN variants. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on September 6, 2012. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents Kong, et al. Expires September 6, 2012 [Page 1] Internet-Draft EPP IDN Variants Mapping March 2012 (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Kong, et al. Expires September 6, 2012 [Page 2] Internet-Draft EPP IDN Variants Mapping March 2012 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 6 5.1. OIDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5.2. PIDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5.3. VIDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7 6.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 7 6.1.1. EPP Command . . . . . . . . . . . . . . . . . 7 6.1.2. EPP Command . . . . . . . . . . . . . . . . . . 7 6.1.3. EPP Query Command . . . . . . . . . . . . . 10 6.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 11 6.2.1. EPP Command . . . . . . . . . . . . . . . . . 12 6.2.2. EPP Command . . . . . . . . . . . . . . . . . 14 6.2.3. EPP Command . . . . . . . . . . . . . . . . . 15 6.2.4. EPP Command . . . . . . . . . . . . . . . . 17 6.2.5. EPP Command . . . . . . . . . . . . . . . . . 18 7. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 20 8. Internationalization Considerations . . . . . . . . . . . . . 23 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 10. Security Considerations . . . . . . . . . . . . . . . . . . . 24 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 24 12. Change History . . . . . . . . . . . . . . . . . . . . . . . . 24 12.1. draft-kong-epp-idn-variants-mapping: Version 00 . . . . . 24 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 13.1. Normative References . . . . . . . . . . . . . . . . . . . 25 13.2. Informative References . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26 Kong, et al. Expires September 6, 2012 [Page 3] Internet-Draft EPP IDN Variants Mapping March 2012 1. Introduction As stated in "The IDN Variant Issues Project Report [Final.Integrated.Issues.Report]", variant has been used variably to refer to, for example, a particular relationship between specific characters or code points in a particular script, or a set of alternate labels where some linkage relationship is articulated, or a desired procedure whereby names are registered in multiples, or a desired functionality causing shared behavior by some set of identifiers. Since the complexity of IDN variants, consideration is needed to be given to the registration policy on whether the variant IDN should be associated with the same registrant. Some registries adopt the policy that variant IDNs which are identified as equivalent are allocated or delegated to the same registrant. For example, the specified registration policy of Chinese Domain Name (CDN) is that a registrant can apply an original CDN in any forms: Simplified Chinese (SC) form, Traditional Chinese (TC) form, or other variant forms, then the corresponding variant CDN in SC form and that in TC form will also be delegated to the same registrant. All the other forms for the CDN are reserved and forbidden to be applied by other registrants. Moreover, any reserved variant CDN can be validated by the same registrant later. Based on such registration policy of CDN, all the variant CDNs contain same attributes. In order to meet above requirements of the IDN variants registration, this document describes an extension of the Extensible Provisioning Protocol (EPP) domain name mapping [RFC5731] for the provisioning and management of IDN variants. This document is specified using the Extensible Markup Language (XML) 1.0 as described in [W3C.REC-xml-20040204] and XML Schema notation as described in [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028]. The EPP core protocol specification [RFC5730] provides a complete description of EPP command and response structures. A thorough understanding of the base protocol specification is necessary to understand the extension of mapping described in this document. This document uses lots of the concepts of the IDN, so a thorough understanding of the IDNs for Application (IDNA, described in [RFC5890], [RFC5891], and [RFC5892]) and a thorough understanding of variant approach discussed in [RFC4290] are both required. 2. Terminology 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 [RFC2119]. Kong, et al. Expires September 6, 2012 [Page 4] Internet-Draft EPP IDN Variants Mapping March 2012 "idnv-1.0" in this document is used as an abbreviation for urn:ietf:params:xml:ns:idnv-1.0. In examples, "C:" represents lines sent by a protocol client and "S:" represents lines returned by a protocol server. Indentation and white space in examples are provided only to illustrate element relationships and are not a REQUIRED feature of this specification. XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented to develop a conforming implementation. 3. Definitions The following definitions are used in this document: o Original Internationalized Domain Name (OIDN), represents the valid IDN that users submitted for registration by the first time. o Preferred Internationalized Domain Name (PIDN), represents the IDN that are commonly used and recommended according to the corresponding IDN table. o Variant Internationalized Domain Name (VIDN), represents the IDN which is made up of the combinations of variant characters or code points, or a set of alternate domain labels according to the corresponding IDN table. In addition, OIDN and PIDN are excluded. o Internationalized Domain Name Bundle (IDN Bundle), represents a package of IDNs which may be OIDN, corresponding PIDN or corresponding VIDNs. All of the IDNs within a same bundle MUST contain same attributes. 4. Overview Domain registries have traditionally adopted a registration model whereby metadata relating to a domain name, such as its expiration date and sponsoring registrar, are stored as properties of the domain object. The domain object is then considered an atomic unit of registration, on which operations such as update, renewal and deletion may be performed. IDNs, particularly variants, brought about the need for multiple domain names to be registered and managed as a single package, or registration bundle. In this model, the registry typically accepts a domain registration request (i.e. EPP domain command) Kong, et al. Expires September 6, 2012 [Page 5] Internet-Draft EPP IDN Variants Mapping March 2012 containing the domain name to be registered. This domain name is referred to as the OIDN in this document. As part of the processing of the registration request, the registry generates a set of zero or more variants that are related to the OIDN, either programmatically or with the guidance of registration policies, and place them in the registration bundle together with the OIDN. Registration policies may dictate the need for identifying a PIDN out of the set of related variants. The document uses the term VIDN to refer to the remaining variants that are neither the OIDN nor PIDN. Together, the set of OIDN, PIDN and VIDNs make up an IDN Bundle. All of IDNs with the same bundle have the same properties, such as expiration date and sponsoring registrar, by sharing one domain object. So when users update any properties within a bundle, all of the domains' properties in the bundle will be changed. 5. Object Attributes This extension defines following additional elements to the EPP domain name mapping [RFC5731]. All of these additional elements can be got from command. 5.1. OIDN The OIDN is an IDN with the A-label [RFC5890] form which is converted from the corresponding OIDN. In this document, its corresponding element is . An attribute "uLabel" associated with is used to represent the U-label [RFC5890] form. An optional boolean "activated" attribute, with a default true value, is used to indicate the presence of the label in the zone file. For example: xn-- fsq270a.xn--fiqs8s 5.2. PIDN The PIDN is an IDN with the A-label [RFC5890] form which is converted from the corresponding PIDN. In this document, its corresponding element is . An attribute "uLabel" associated with is used to represent the U-label [RFC5890] form. An optional boolean "activated" attribute, with a default true value, is used to indicate the presence of the label in the zone file. For example: xn-- fsqz41a.xn--fiqz9s Kong, et al. Expires September 6, 2012 [Page 6] Internet-Draft EPP IDN Variants Mapping March 2012 5.3. VIDN The VIDN is an IDN with the A-label [RFC5890] form which is converted from the corresponding VIDN. In this document, its corresponding element is . An attribute "uLabel" associated with is used to represent the U-label [RFC5890] form. An optional boolean "activated" attribute, with a default true value, is used to indicate the presence of the label in the zone file. For example: xn-- fsq470a.xn--fiqz9s 6. EPP Command Mapping A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification [RFC5730]. The command mappings described here are specifically for use in provisioning and managing IDN variants via EPP. 6.1. EPP Query Commands EPP provides three commands to retrieve domain information: to determine if a domain object can be provisioned within a repository, to retrieve detailed information associated with a domain object, and to retrieve domain-object transfer status information. 6.1.1. EPP Command This extension does not add any element to the EPP command or response described in the EPP domain name mapping [RFC5731]. When a domain name has not been registered, but the domain which the user submitted for check is a registered domain name's variant, response SHOULD contain explanation in the reason field to tell the user that this domain name is an IDN variant of a registered domain name according to the corresponding IDN table, and can be validated by the registrant using command according to the server's policies. 6.1.2. EPP Command This extension does not add any element to the EPP command described in the EPP domain mapping [RFC5731]. However, additional elements are defined for the response. When an command has been processed successfully, the EPP element MUST contain child elements as described in the EPP Kong, et al. Expires September 6, 2012 [Page 7] Internet-Draft EPP IDN Variants Mapping March 2012 domain mapping [RFC5731]. In addition, the EPP element SHOULD contain a child element that identifies the extension namespace if the domain object has data associated with this extension and based on its service policy. The element contains the which has the following child elements: o An element that contains the OIDN, along with the attributes described below. o An OPTIONAL element that contains the PIDN, along with the attributes described below. o Zero or more elements that contain the VIDNs, along with the attributes described below. The above elements contain the following attributes: o A "uLabel" attribute represents the U-label of the element. o An optional "activated" attribute that defaults to true, indicating the presence of the variant in the zone file. Kong, et al. Expires September 6, 2012 [Page 8] Internet-Draft EPP IDN Variants Mapping March 2012 Example Response for an authorized client: S: S: S: S: S: Command completed successfully S: S: S: S: xn--fsq270a.xn--fiqs8s S: 58812678-domain S: S: 123 S: 123 S: 123 S: S: ns1.example.cn S: S: ClientX S: ClientY S: 2011-04-03T22:00:00.0Z S: 2012-04-03T22:00:00.0Z S: S: 2fooBAR S: S: S: S: S: S: S: xn--fsq270a.xn--fiqs8s S: xn--fsqz41a.xn--fiqz9s S: xn--fsq470a.xn--fiqz9s S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: Kong, et al. Expires September 6, 2012 [Page 9] Internet-Draft EPP IDN Variants Mapping March 2012 Response for the unauthorized client has not been changed,see [RFC5731] for detail. An EPP error response MUST be returned if an command cannot be processed for any reason. 6.1.3. EPP Query Command This extension does not add any element to the EPP command described in the EPP domain mapping [RFC5731]. However, additional elements are defined for the response. When a command has been processed successfully, the EPP element MUST contain child elements as described in the EPP domain mapping [RFC5731]. In addition, the EPP element SHOULD contain a child element that identifies the extension namespace if the domain object has data associated with this extension and based on its service policy. The element contains the which has the following child elements: o An element that contains the OIDN, along with the attributes described below. o An OPTIONAL element that contains the PIDN, along with the attributes described below. o Zero or more elements that contain the VIDNs, along with the attributes described below. The above elements contain the following attributes: o A "uLabel" attribute represents the U-label of the element. o An optional "activated" attribute that defaults to true, indicating the presence of the variant in the zone file. Kong, et al. Expires September 6, 2012 [Page 10] Internet-Draft EPP IDN Variants Mapping March 2012 Example Response for an authorized client: S: S: S: S: S: Command completed successfully S: S: S: S: xn--fsq270a.xn--fiqs8s S: pending S: ClientX S: 2010-06-06T22:00:00.0Z S: ClientY S: 2011-06-11T22:00:00.0Z S: 2012-09-08T22:00:00.0Z S: S: S: S: S: S: xn--fsq270a.xn--fiqs8s S: xn--fsqz41a.xn--fiqz9s S: xn--fsq470a.xn--fiqz9s S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. 6.2. EPP Transform Commands EPP provides five commands to transform domain objects: to create an instance of a domain object, to delete an instance of a domain object, to extend the validity period of a domain Kong, et al. Expires September 6, 2012 [Page 11] Internet-Draft EPP IDN Variants Mapping March 2012 object, to manage domain object sponsorship changes, and to change information associated with a domain object. 6.2.1. EPP Command This extension defines additional elements to extend the EPP command described in the EPP domain name mapping [RFC5731] for IDN variants registration. In addition to the EPP command elements described in the EPP domain mapping [RFC5731], the command SHALL contain an element. The element SHOULD contain a child element that identifies the IDN namespace and the location of the IDN schema. The element SHOULD contain one or more : Example command: C: C: C: C: C: C: xn--fsq270a.xn--fiqs8s C: 2 C: 123 C: 123 C: 123 C: C: 2fooBAR C: C: C: C: C: C: xn--fsq470a.xn--fiqz9s C: C: C: ABC-12345 C: C: When an command has been processed successfully, the EPP element MUST contain child elements as described in the EPP domain mapping [RFC5731]. In addition, the EPP element Kong, et al. Expires September 6, 2012 [Page 12] Internet-Draft EPP IDN Variants Mapping March 2012 SHOULD contain a child element that identifies the extension namespace if the domain object has data associated with this extension and based on its service policy. The element contains the which has the following child elements: o An element that contains the OIDN, along with the attributes described below. o An OPTIONAL element that contains the PIDN, along with the attributes described below. If the PIDN is allowed to be presented to the registrant by the registration policy, the PIDN SHALL be generated by the server during an command. After the command has been processed successfully, the response of the command SHOULD contain an element. o Zero or more elements that contain the VIDNs, along with the attributes described below. The above elements contain the following attributes: o A "uLabel" attribute represents the U-label of the element. o An optional "activated" attribute that defaults to true, indicating the presence of the variant in the zone file. Kong, et al. Expires September 6, 2012 [Page 13] Internet-Draft EPP IDN Variants Mapping March 2012 Example Response for an authorized client: S: S: S: S: S: Command completed successfully S: S: S: S: xn--fsq270a.xn--fiqs8s S: 1999-04-03T22:00:00.0Z S: 2001-04-03T22:00:00.0Z S: S: S: S: S: S: xn--fsq270a.xn--fiqs8s S: xn--fsqz41a.xn--fiqz9s S: xn--fsq470a.xn--fiqz9s S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: Response for the unauthorized client has not been changed,see [RFC5731] for detail. An EPP error response MUST be returned if an command cannot be processed for any reason. 6.2.2. EPP Command This extension does not add any element to the EPP command described in the EPP domain mapping [RFC5731]. However, additional elements are defined for the response. Kong, et al. Expires September 6, 2012 [Page 14] Internet-Draft EPP IDN Variants Mapping March 2012 When a command has been processed successfully, the EPP element MUST contain child elements as described in the EPP domain mapping [RFC5731]. In addition, the EPP element SHOULD contain a child element that identifies the extension namespace if the domain object has data associated with this extension and based on its service policy. The element SHOULD contain the which has the following child elements: o An element that contains the OIDN. o An OPTIONAL element that contains the PIDN. o Zero or more elements that contain the VIDNs. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: S: xn--fsq270a.xn--fiqs8s S: xn--fsqz41a.xn--fiqz9s S: xn--fsq470a.xn--fiqz9s S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. 6.2.3. EPP Command This extension does not add any element to the EPP command described in the EPP domain mapping [RFC5731]. However, additional Kong, et al. Expires September 6, 2012 [Page 15] Internet-Draft EPP IDN Variants Mapping March 2012 elements are defined for the response. When a command has been processed successfully, the EPP element MUST contain child elements as described in the EPP domain mapping [RFC5731]. In addition, the EPP element SHOULD contain a child element that identifies the extension namespace if the domain object has data associated with this extension and based on its service policy. The element SHOULD contain the which has the following child elements: o An element that contains the OIDN. o An OPTIONAL element that contains the PIDN. o Zero or more elements that contain the VIDNs. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: example.com S: 2012-04-03T22:00:00.0Z S: S: S: S: S: S: xn--fsq270a.xn--fiqs8s S: xn--fsqz41a.xn--fiqz9s S: xn--fsq470a.xn--fiqz9s S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: Kong, et al. Expires September 6, 2012 [Page 16] Internet-Draft EPP IDN Variants Mapping March 2012 S: An EPP error response MUST be returned if a command cannot be processed for any reason. 6.2.4. EPP Command This extension does not add any element to the EPP command described in the EPP domain mapping [RFC5731]. However, additional elements are defined for the response. When a command has been processed successfully, the EPP element MUST contain child elements as described in the EPP domain mapping [RFC5731]. In addition, the EPP element SHOULD contain the same child element defined in the transfer query response in this mapping. Kong, et al. Expires September 6, 2012 [Page 17] Internet-Draft EPP IDN Variants Mapping March 2012 Example Response for an authorized client: S: S: S: S: S: Command completed successfully S: S: S: S: xn--fsq270a.xn--fiqs8s S: pending S: ClientX S: 2010-06-06T22:00:00.0Z S: ClientY S: 2011-06-11T22:00:00.0Z S: 2012-09-08T22:00:00.0Z S: S: S: S: S: S: xn--fsq270a.xn--fiqs8s S: xn--fsqz41a.xn--fiqz9s S: xn--fsq470a.xn--fiqz9s S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. 6.2.5. EPP Command This extension defines additional elements for the EPP command described in the EPP domain mapping [RFC5731]. No additional elements are defined for the EPP response. Kong, et al. Expires September 6, 2012 [Page 18] Internet-Draft EPP IDN Variants Mapping March 2012 The EPP command provides a transform operation that allows a client to modify the attributes of a domain object. In addition to the EPP command elements described in the EPP domain mapping [RFC5731], the command SHOULD contain an element, and the element MUST contain a child element that identifies the extension namespace if the client wants to update the domain object with data defined in this extension. The element SHOULD contain one or more of the following elements: o An element with one or more child elements that represent VIDNs to be associated with the OIDN. o An element with one or more child elements that represent VIDNs to be disassociated from the OIDN. o An element with one or more child elements each identifying an already existing VIDN to be activated. A VIDN that is to be associated with the OIDN, as listed in the element of the same command, may also be specified to explicitly signal to the server that the VIDN to be added should be activated that the same time it is associated. o An element with one or more child elements each identifying an already existing VIDN to be deactivated. A VIDN that is to be associated with the OIDN, as listed in the element of the same command, may also be specified to explicitly signal to the server that the VIDN to be added should be in a deactivated state when it is associated. It is an error to include the same VIDN in an or element, and at the same time being included in the element. By definition, a VIDN to be disassociated from the OIDN will be deactivated and it would be contradictary to attempt to activate it, and redundant to request for deactivation. Example Command: C: C: C: C: C: C: xn--fsq270a.xn--fiqs8s C: C: C: ns2.example.cn C: Kong, et al. Expires September 6, 2012 [Page 19] Internet-Draft EPP IDN Variants Mapping March 2012 C: 234 C: Payment overdue. C: C: C: C: ns1.example.cn C: C: 123 C: C: C: C: 234 C: C: 2BARfoo C: C: C: C: C: C: C: C: xn--fsq470a.xn--fiqz9s C: C: C: xn--5tyft0a.xn--fiqz9s C: C: C: xn--fsq470a.xn--fiqz9s C: C: C: C: ABC-12345 C: C: When an extended command has been processed successfully, the EPP response is as described in the EPP domain name mapping [RFC5731]. 7. Formal Syntax An EPP object name mapping extension for IDN variants 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. The BEGIN and END tags are not part Kong, et al. Expires September 6, 2012 [Page 20] Internet-Draft EPP IDN Variants Mapping March 2012 of the schema; they are used to note the beginning and ending of the schema for URI registration purposes. BEGIN Extensible Provisioning Protocol v1.0 CNNIC Domain Extension Schema v1.0 Kong, et al. Expires September 6, 2012 [Page 22] Internet-Draft EPP IDN Variants Mapping March 2012 END 8. Internationalization Considerations EPP is represented in XML, which provides native support for encoding information using the Unicode character set and its more compact representations including UTF-8. Conformant XML processors recognize both UTF-8 and UTF-16. Though XML includes provisions to identify and use other character encodings through use of an "encoding" attribute in an declaration, use of UTF-8 is RECOMMENDED. As an extension of the EPP domain name mapping, the elements, element content described in this document MUST inherit the internationalization conventions used to represent higher-layer domain and core protocol structures present in an XML instance that includes this extension. 9. IANA Considerations This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. IANA is requested to assignment the following two URIs. Registration request for the IDN namespace: Kong, et al. Expires September 6, 2012 [Page 23] Internet-Draft EPP IDN Variants Mapping March 2012 o URI: urn:ietf:params:xml:ns:idnv-1.0 o Registrant Contact: See the "Author's Address" section of this document. o XML: None. Namespace URI does not represent an XML specification. Registration request for the IDN XML schema: o URI: urn:ietf:params:xml:schema:idnv-1.0 o Registrant Contact: See the "Author's Address" section of this document. o XML: See the "Formal Syntax" section of this document. 10. Security Considerations The object mapping extension described in this document does not provide any other security services or introduce any additional considerations beyond those described by [RFC5730] or those caused by the protocol layers used by EPP. 11. Acknowledgements The authors especially thank the authors of [RFC5730] and [RFC5731] and the following ones of CNNIC: Weiping Yang, Chao Qi, Linlin Zhou. Useful comments were made by John Klensin, Scott Hollenbeck and Edward Lewis. 12. Change History RFC Editor: Please remove this section. 12.1. draft-kong-epp-idn-variants-mapping: Version 00 o First draft. 13. References Kong, et al. Expires September 6, 2012 [Page 24] Internet-Draft EPP IDN Variants Mapping March 2012 13.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, August 2009. [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, August 2009. [RFC5890] Klensin, J., "Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework", RFC 5890, August 2010. [RFC5891] Klensin, J., "Internationalized Domain Names in Applications (IDNA): Protocol", RFC 5891, August 2010. [RFC5892] Faltstrom, P., "The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)", RFC 5892, August 2010. [W3C.REC-xml-20040204] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third Edition)", World Wide Web Consortium FirstEdition REC- xml-20040204", February 2004, . [W3C.REC-xmlschema-1-20041028] Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, ""XML Schema Part 1: Structures Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-1- 20041028", October 2004, . [W3C.REC-xmlschema-2-20041028] Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-2-20041028", October 2004, . Kong, et al. Expires September 6, 2012 [Page 25] Internet-Draft EPP IDN Variants Mapping March 2012 13.2. Informative References [Final.Integrated.Issues.Report] ICANN, "The IDN Variant Issues Project: A Study of Issues Related to the Management of IDN Variant TLDs", February 2012, . [RFC4290] Klensin, J., "Suggested Practices for Registration of Internationalized Domain Names (IDN)", RFC 4290, December 2005. Authors' Addresses Ning Kong CNNIC 4 South 4th Street,Zhongguancun,Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 3147 Email: nkong@cnnic.cn Jiagui Xie CNNIC 4 South 4th Street,Zhongguancun,Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 2639 Email: xiejiagui@cnnic.cn Hongtao Li CNNIC 4 South 4th Street,Zhongguancun,Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 3164 Email: lihongtao@cnnic.cn Kong, et al. Expires September 6, 2012 [Page 26] Internet-Draft EPP IDN Variants Mapping March 2012 Wil Tan Cloud Registry Suite 32 Seabridge House, 377 Kent St Sydney, NSW 2000 Australia Phone: +61 414 710899 Email: wil@cloudregistry.net Xiaodong Li Chinese Academy of Sciences 4 South 4th Street,Zhongguancun,Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 3020 Email: xl@cnic.cn Kong, et al. Expires September 6, 2012 [Page 27]