Internet Engineering Task Force N. Kong Internet-Draft J. Yao, Ed. Intended status: Standards Track X. Li Expires: November 4, 2017 CNNIC W. Tan Cloud Registry J. Xie May 3, 2017 Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for Strict Bundling Registration draft-ietf-regext-bundling-registration-01 Abstract This document describes an extension of Extensible Provisioning Protocol (EPP) domain name mapping for the provisioning and management of strict bundling registration of domain names. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for the provisioning of bundled domain names. 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 November 4, 2017. Copyright Notice Copyright (c) 2017 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 (http://trustee.ietf.org/license-info) in effect on the date of Kong, et al. Expires November 4, 2017 [Page 1] Internet-Draft EPP bundled names Mapping May 2017 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. Requirement for Bundling Registration of Names . . . . . . . 5 6. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 6 6.1. RDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6.2. BDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 7. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7 7.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7 7.1.1. EPP Command . . . . . . . . . . . . . . . . . 7 7.1.2. EPP Command . . . . . . . . . . . . . . . . . 8 7.1.3. EPP Query Command . . . . . . . . . . . . 10 7.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 10 7.2.1. EPP Command . . . . . . . . . . . . . . . . 11 7.2.2. EPP Command . . . . . . . . . . . . . . . . 12 7.2.3. EPP Command . . . . . . . . . . . . . . . . . 13 7.2.4. EPP Command . . . . . . . . . . . . . . . 14 7.2.5. EPP Command . . . . . . . . . . . . . . . . 14 8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 14 9. Internationalization Considerations . . . . . . . . . . . . . 16 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 11. Security Considerations . . . . . . . . . . . . . . . . . . . 17 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 17 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 14. Change History . . . . . . . . . . . . . . . . . . . . . . . 18 14.1. draft-kong-epp-bundle-mapping: Version 00 . . . . . . . 18 Kong, et al. Expires November 4, 2017 [Page 2] Internet-Draft EPP bundled names Mapping May 2017 14.2. draft-kong-epp-bundle-mapping: Version 01 . . . . . . . 18 14.3. draft-kong-epp-bundle-mapping: Version 02 . . . . . . . 18 14.4. draft-ietf-regext-bundle-mapping: Version 00 . . . . . . 18 14.5. draft-ietf-regext-bundle-mapping: Version 01 . . . . . . 18 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 15.1. Normative References . . . . . . . . . . . . . . . . . . 18 15.2. Informative References . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 1. Introduction Bundled domain names are those who share the same TLD but whose second level labels are variants, or those who has identical second level labels for which certain parameters are shared in different TLDs. For example, Public Interest Registry, request to implement technical bundling of second level domains for .NGO and .ONG. So we have two kinds of bundled domain names. First one is in the form of "V-label.TLD" in which the second level labels (V-label) are variants sharing the same TLD; Second one is in the form of "LABEL.V-tld" in which the second level labels(LABEL) are same with the different TLDs (V-tld); There are several kinds of bundling. First one is strict bundling, which requires all bundled names to share many same attributes. When creating, updating, or transfering of any of the bundled domain names, all bundled domain names will be created, updated or transferred. Second one is partial bundling, which requires that at least the bundled domain names if registered should be registered by the same registrant. Third one is relax bundling, which has not specific requirements to the domain registration. This document mainly focus on strict bundling names registration. For the name variants, 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 variant names in the same TLD contain same attributes. The basic Extensible Provisioning Protocol (EPP) domain name mapping [RFC5731] provides the domain name registration one by one. It does not specify how to register the strict bundled names which share many same attributes. Kong, et al. Expires November 4, 2017 [Page 3] Internet-Draft EPP bundled names Mapping May 2017 In order to meet above requirements of the strict bundled names registration, this document describes an extension of the EPP domain name mapping [RFC5731] for the provisioning and management of bundled names.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]. uLable is defined in [RFC 5890]. uLabel is expressed in this document as a number of characters with the format of U+XXXX where XXXX is a UNICODE point. "b-dn-1.0" in this document is used as an abbreviation for urn:ietf:params:xml:ns:b-dn-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 Registered Domain Name (RDN), represents the valid domain name that users submitted for registration by the first time. Kong, et al. Expires November 4, 2017 [Page 4] Internet-Draft EPP bundled names Mapping May 2017 o Bundled Domain Name (BDN), represents the bundled domain name produced according to the bundled domain name registration policy. 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. Bundled names, brought about the need for multiple domain names to be registered and managed as a single package. In this model, the registry typically accepts a domain registration request (i.e. EPP domain command) containing the domain name to be registered. This domain name is referred to as the RDN in this document. As part of the processing of the registration request, the registry generates a set of bundled names that are related to the RDN, either programmatically or with the guidance of registration policies, and place them in the registration package together with the RDN. The bundled names have the same properties, such as expiration date and sponsoring registrar, by sharing one domain object. So when users update any property of a domain object within a bundle package, that property of all other domain objects in the bundle package will be updated at the same time. 5. Requirement for Bundling Registration of Names The bundled names whether they are in the form of "V-label.TLD" or in the form of "LABEL.V-tld" should share some parameter or attributes assoicated with domain names. Typically, Bundled names will share the following parameters or attributes: o Registrar Ownership o Registration and Expiry Dates o Registrant, Admin, Billing, and Technical Contacts o Name Server Association o Domain Status o Applicable grace periods (Add Grace Period, Renewal Grace Period, Auto-Renewal Grace Period, Transfer Grace Period, and Redemption Grace Period) Because the domain names are bundled and share the same parameters or attributes, the EPP command should do some processing for these requirements: o When performing a domain check, either BDN or RDN can be queried for the EPP command, and will return the same response. Kong, et al. Expires November 4, 2017 [Page 5] Internet-Draft EPP bundled names Mapping May 2017 o When performing a domain info, either BDN or RDN can be queried, the same response will include both BDN and RDN information with the same attributes. o When performing a domain Create, either BDN or RDN will be accepted. If the domain name is available, both BDN and RDN will be registered. o When performing a domain Delete, either BDN or RDN will be accepted. If the domain name is available, both BDN and RDN will be deleted. o When performing a domain renew, either BDN or RDN will be accepted. Upon a successful domain renewal,both BDN and RDN will have their expiry date extended by the requested term. Upon a successful domain renewal, both BDN and RDN will conform to the same renew grace period. o When performing a domain transfer, either BDN or RDN will be accepted. Upon successful completion of a domain transfer request, both BDN and RDN will enter a pendingTransfer status. Upon approval of the transfer request, both BDN and RDN will be owned and managed by the same new registrant. o When performing a domain update, either BDN or RDN will be accepted. Any modifications to contact associations, name server associations, domain status values and authorization information will be applied to both BDN and RDN. 6. 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. 6.1. RDN The RDN is an ASCII name or an IDN with the A-label [RFC5890] form. In this document, its corresponding element is . An optional 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.example 6.2. BDN The BDN is an ASCII name or an IDN with the A-label [RFC5890] form which is converted from the corresponding BDN. In this document, its corresponding element is . An optional attribute "uLabel" Kong, et al. Expires November 4, 2017 [Page 6] Internet-Draft EPP bundled names Mapping May 2017 associated with is used to represent the U-label [RFC5890] form. For example: xn-- fsqz41a.example 7. 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 bundled names via EPP. 7.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. 7.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]. However, when either RDN or BDN is sent for check, response SHOULD contain both RDN and BDN information, which may also give some explanation in the reason field to tell the user that the associated domain name is a produced name according to some bundle domain name policy. Kong, et al. Expires November 4, 2017 [Page 7] Internet-Draft EPP bundled names Mapping May 2017 Example Response for an authorized client: S: S: S: S: S: Command completed successfully S: S: S: S: S: xn--fsq270a.example S: S: S: xn--fsqz41a.example S: This associated domain name is a produced name based on bundle name policy. S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: 7.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 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 RDN, along with the attributes described below. Kong, et al. Expires November 4, 2017 [Page 8] Internet-Draft EPP bundled names Mapping May 2017 o An OPTIONAL element that contains the BDN, along with the attributes described below. The above elements contain the following attributes: o An optional "uLabel" attribute represents the U-label of the element. Example Response for an authorized client: S: S: S: S: S: Command completed successfully S: S: S: S: xn--fsq270a.example 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.example S: xn--fsqz41a.example Kong, et al. Expires November 4, 2017 [Page 9] Internet-Draft EPP bundled names Mapping May 2017 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. 7.1.3. EPP Query Command This extension does not add any element to the EPP command or reponse described in the EPP domain mapping [RFC5731]. 7.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 object, to manage domain object sponsorship changes, and to change information associated with a domain object. When theses commands have been processed successfully, the EPP element MUST contain child elements as described in the EPP domain mapping [RFC5731]. This EPP element SHOULD contain the which has the following child elements: o An element that contains the RDN, along with the attributes described below. o An OPTIONAL element that contains the BDN, along with the attributes described below. The above elements contain the following attribute: o An optional "uLabel" attribute represents the U-label of the element. Kong, et al. Expires November 4, 2017 [Page 10] Internet-Draft EPP bundled names Mapping May 2017 7.2.1. EPP Command This extension defines additional elements to extend the EPP command described in the EPP domain name mapping [RFC5731] for bundled names 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 bundle namespace and the location of the bundle name schema. Example command: C: C: C: C: C: C: xn--fsq270a.example C: 2 C: 123 C: 123 C: 123 C: C: 2fooBAR C: C: C: C: C: C: C: xn--fsq270a.example 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 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 element. Kong, et al. Expires November 4, 2017 [Page 11] Internet-Draft EPP bundled names Mapping May 2017 Example Response for an authorized client: S: S: S: S: S: Command completed successfully S: S: S: S: xn--fsq270a.example S: 1999-04-03T22:00:00.0Z S: 2001-04-03T22:00:00.0Z S: S: S: S: S: S: xn--fsq270a.example S: xn--fsqz41a.example 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. 7.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. When a command has been processed successfully, the EPP element MUST contain child elements as described in the EPP Kong, et al. Expires November 4, 2017 [Page 12] Internet-Draft EPP bundled names Mapping May 2017 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 element. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: S: xn--fsq270a.example S: xn--fsqz41a.example 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. 7.2.3. EPP Command This extension does not add any element to the EPP command described in the EPP domain name mapping [RFC5731]. However, when either RDN or BDN is sent for renew, response SHOULD contain both RDN and BDN information. When the command has been processed successfully, the EPP element MUST contain child elements as described in the EPP domain mapping [RFC5731]. This EPP element SHOULD contain the which contains element. Kong, et al. Expires November 4, 2017 [Page 13] Internet-Draft EPP bundled names Mapping May 2017 7.2.4. EPP Command This extension does not add any element to the EPP command described in the EPP domain name mapping [RFC5731]. When the command has been processed successfully, the EPP element MUST contain child elements as described in the EPP domain mapping [RFC5731]. This EPP element SHOULD contain the which contains element. 7.2.5. EPP Command This extension does not add any element to the EPP command described in the EPP domain name mapping [RFC5731]. When the command has been processed successfully, the EPP element MUST contain child elements as described in the EPP domain mapping [RFC5731]. This EPP element SHOULD contain the which contains element. 8. Formal Syntax An EPP object name mapping extension for bundled names 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 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 Bundle Domain Extension Schema v1.0 Kong, et al. Expires November 4, 2017 [Page 14] Internet-Draft EPP bundled names Mapping May 2017 Kong, et al. Expires November 4, 2017 [Page 15] Internet-Draft EPP bundled names Mapping May 2017 END 9. 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. 10. 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: o URI: urn:ietf:params:xml:ns:b-dn-1.0 Kong, et al. Expires November 4, 2017 [Page 16] Internet-Draft EPP bundled names Mapping May 2017 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:b-dn-1.0 o Registrant Contact: See the "Author's Address" section of this document. o XML: See the "Formal Syntax" section of this document. 11. 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. 12. Implementation Status Note to RFC Editor: Please remove this section before publication. o CNNIC has implemented this extension in his EPP based Chinese domain name registration system. o Public Interest Registry, has requested to implement technical bundling of second level domains for .NGO and .ONG. This means that by registering and purchasing a domain in the .ngo TLD, for example, the NGO registrant is also registering and purchasing the corresponding name in the .ong TLD (and vice-versa for registrations in .ong). 13. Acknowledgements The authors especially thank the authors of [RFC5730] and [RFC5731] and the following ones of CNNIC: Weiping Yang, Chao Qi. This draft extends the draft draft-kong-epp-idn-variants-mapping to support both forms of bundled names: V-label.TLD and LABEL.V-tld. Useful comments were made by John Klensin, Scott Hollenbeck, Patrick Mevzek and Edward Lewis. Kong, et al. Expires November 4, 2017 [Page 17] Internet-Draft EPP bundled names Mapping May 2017 14. Change History RFC Editor: Please remove this section. 14.1. draft-kong-epp-bundle-mapping: Version 00 o EPP extensiton for bundled domain name registrations. 14.2. draft-kong-epp-bundle-mapping: Version 01 o Change the proposed category from EXP to STD. o Add the section of Implementation Status. o Refine the text, and update the examples. 14.3. draft-kong-epp-bundle-mapping: Version 02 o Refine the texts. 14.4. draft-ietf-regext-bundle-mapping: Version 00 o accepted as WG document. 14.5. draft-ietf-regext-bundle-mapping: Version 01 o make this document to focus on the restrict bundled domain name registration. 15. References 15.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, . Kong, et al. Expires November 4, 2017 [Page 18] Internet-Draft EPP bundled names Mapping May 2017 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, DOI 10.17487/RFC5731, August 2009, . [RFC5890] Klensin, J., "Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework", RFC 5890, DOI 10.17487/RFC5890, August 2010, . [RFC5891] Klensin, J., "Internationalized Domain Names in Applications (IDNA): Protocol", RFC 5891, DOI 10.17487/RFC5891, August 2010, . [RFC5892] Faltstrom, P., Ed., "The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)", RFC 5892, DOI 10.17487/RFC5892, 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, . 15.2. Informative References [bundle.name] ICANN, "Registry Services Technical Evaluation Panel (RSTEP) Report on Public Interest Registry's Request to Implement Technical Bundling in .NGO and .ONG", July 2014, . Kong, et al. Expires November 4, 2017 [Page 19] Internet-Draft EPP bundled names Mapping May 2017 [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, DOI 10.17487/RFC4290, 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 Jiankang Yao (editor) CNNIC 4 South 4th Street,Zhongguancun,Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 3007 Email: yaojk@cnnic.cn Xiaodong Li CNNIC 4 South 4th Street,Zhongguancun,Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 3020 Email: xl@cnnic.cn Kong, et al. Expires November 4, 2017 [Page 20] Internet-Draft EPP bundled names Mapping May 2017 Wil Tan Cloud Registry Suite 32 Seabridge House, 377 Kent St Sydney, NSW 2000 Australia Phone: +61 414 710899 Email: wil@cloudregistry.net Jiagui Xie Email: jiagui1984@163.com Kong, et al. Expires November 4, 2017 [Page 21]