Internet Engineering Task Force N. Kong Internet-Draft Consultant Intended status: Informational J. Yao Expires: March 23, 2020 L. Zhou CNNIC W. Tan Cloud Registry J. Xie September 20, 2019 Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for Strict Bundling Registration draft-ietf-regext-bundling-registration-10 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 https://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 March 23, 2020. Copyright Notice Copyright (c) 2019 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 March 23, 2020 [Page 1] Internet-Draft EPP bundled names Mapping September 2019 (https://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. 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 . . . . . . . . . . . . . . . . 15 8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 16 9. Internationalization Considerations . . . . . . . . . . . . . 18 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 11. Security Considerations . . . . . . . . . . . . . . . . . . . 19 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 20 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 14. Change History . . . . . . . . . . . . . . . . . . . . . . . 20 14.1. draft-ietf-regext-bundle-registration: Version 00 . . . 20 14.2. draft-ietf-regext-bundle-registration: Version 01 . . . 20 14.3. draft-ietf-regext-bundle-registration: Version 02 . . . 21 14.4. draft-ietf-regext-bundle-registration: Version 03 . . . 21 14.5. draft-ietf-regext-bundle-registration: Version 04 . . . 21 14.6. draft-ietf-regext-bundle-registration: Version 05 . . . 21 14.7. draft-ietf-regext-bundle-registration: Version 06 . . . 21 14.8. draft-ietf-regext-bundle-registration: Version 07 . . . 21 14.9. draft-ietf-regext-bundle-registration: Version 08 . . . 21 14.10. draft-ietf-regext-bundle-registration: Version 09 . . . 21 14.11. draft-ietf-regext-bundle-registration: Version 10 . . . 21 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 Kong, et al. Expires March 23, 2020 [Page 2] Internet-Draft EPP bundled names Mapping September 2019 15.1. Normative References . . . . . . . . . . . . . . . . . . 22 15.2. Informative References . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 1. Introduction Bundled domain names are those which share the same TLD but whose second level labels are variants, or those which have identical second level labels for which certain parameters are shared in different TLDs. For an example, Public Interest Registry has requested to implement bundling of second level domains for .NGO and .ONG. So we have two kinds of bundled domain names. The first one is in the form of "V-label.TLD" in which the second level label (V-label) is a variant sharing the same TLD; Second one is in the form of "LABEL.V-tld" in which the second level label(LABEL) remains the same but ending with a different TLD (V-tld). Bundled domain names normally share some attributes. Policy-wise bundling can be implemented in three ways. The first one is strict bundling, which requires all bundled names to share many same attributes. When creating, updating, or transferring of any of the bundled domain names, all bundled domain names will be created, updated or transferred atomically. The second one is partial bundling, which requires the bundled domain names to be registered by the same registrant. The third one is relaxed bundling, which has no specific requirements on the domain registration. This document mainly addresses the 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, most registries offering Chinese Domain Name (CDN) adopt a registration policy whereby a registrant can apply for 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 share a common set of attributes. The basic Extensible Provisioning Protocol (EPP) domain name mapping [RFC5731] provides the facility for single domain name registration. It does not specify how to register the strict bundled names which share many of the attributes. In order to meet the above requirements of strict bundled name 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 Extensible Markup Language (XML) 1.0 as described in [W3C.REC-xml-20040204] and XML Schema Kong, et al. Expires March 23, 2020 [Page 3] Internet-Draft EPP bundled names Mapping September 2019 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 mapping described in this document. This document uses many IDN concepts, so a thorough understanding of the IDNs for Application (IDNA, described in [RFC5890], [RFC5891], and [RFC5892]) and the variant approach discussed in [RFC4290] is assumed. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119][RFC8174] when, and only when, they appear in all capitals, as shown here. uLabel in this document is used to express the U-label of an internationalized domain name as a series of characters where non- ASCII characters will be represented in the format of U+XXXX where XXXX is a UNICODE point. U-Label is defined in [RFC5890]. The XML namespace prefix "b-dn" is used for the namespace "urn:ietf:params:xml:ns:epp:b-dn", but implementations MUST NOT rely on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents. 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 the initial registration. Kong, et al. Expires March 23, 2020 [Page 4] Internet-Draft EPP bundled names Mapping September 2019 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 places them in the registration package together with the RDN. The bundled names share many properties, such as expiration date and sponsoring registrar, by sharing the same 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 associated 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 March 23, 2020 [Page 5] Internet-Draft EPP bundled names Mapping September 2019 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 of the bundle names 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 registered, 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 are returned 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. 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" associated with is used to represent the U-label [RFC5890] form. Kong, et al. Expires March 23, 2020 [Page 6] Internet-Draft EPP bundled names Mapping September 2019 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 March 23, 2020 [Page 7] Internet-Draft EPP bundled names Mapping September 2019 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: S: S: xn--fsq270a.example S: S: S: S: xn--fsqz41a.example S: S: This associated domain name is S: a produced name based on bundle name policy. S: 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 registration policy. The element contains the which has the following child elements: o An element that contains the RDN, along with the attribute described below. Kong, et al. Expires March 23, 2020 [Page 8] Internet-Draft EPP bundled names Mapping September 2019 o An OPTIONAL element that contains the BDN, along with the attribute described below. The above elements contain the following attribute: 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: S: ClientX S: ClientY S: 2011-04-03T22:00:00.0Z S: S: 2012-04-03T22:00:00.0Z S: S: S: 2fooBAR S: S: S: S: S: S: S: S: xn--fsq270a.example S: S: Kong, et al. Expires March 23, 2020 [Page 9] Internet-Draft EPP bundled names Mapping September 2019 S: xn--fsqz41a.example S: 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 response 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 attribute described below. o An OPTIONAL element that contains the BDN, along with the attribute 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 March 23, 2020 [Page 10] Internet-Draft EPP bundled names Mapping September 2019 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 a child element that identifies the U-Label form of the registered domain name with the uLabel attribute. 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: 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 Kong, et al. Expires March 23, 2020 [Page 11] Internet-Draft EPP bundled names Mapping September 2019 this extension and based on its registration policy. The element contains the element. Example response: 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: S: xn--fsq270a.example S: S: S: xn--fsqz41a.example S: S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: 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. Kong, et al. Expires March 23, 2020 [Page 12] Internet-Draft EPP bundled names Mapping September 2019 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 registration policy. The element SHOULD contain the element. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: S: S: xn--fsq270a.example S: S: S: xn--fsqz41a.example S: 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 SHOULD be contained in the response if the domain object has data associated with bundled names. Kong, et al. Expires March 23, 2020 [Page 13] Internet-Draft EPP bundled names Mapping September 2019 This EPP element SHOULD contain the which contains element. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: xn--fsq270a.example S: 2012-04-03T22:00:00.0Z S: S: S: S: S: S: S: xn--fsq270a.example S: S: S: xn--fsqz41a.example S: S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: 7.2.4. EPP Command This extension does not add any element to the EPP command described in the EPP domain name mapping [RFC5731]. However, additional elements are defined for the response in the EPP object mapping. When the command has been processed successfully, the EPP element SHOULD be contained in the response if the domain object has data associated with bundled names. This EPP element SHOULD contain the which contains element. Kong, et al. Expires March 23, 2020 [Page 14] Internet-Draft EPP bundled names Mapping September 2019 Example response: S: S: S: S: S: Command completed successfully; action pending S: S: S: S: xn--fsq270a.example S: pending S: ClientX S: 2011-04-03T22:00:00.0Z S: ClientY S: 2011-04-08T22:00:00.0Z S: 2012-04-03T22:00:00.0Z S: S: S: S: S: S: S: xn--fsq270a.example S: S: S: xn--fsqz41a.example S: S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: 7.2.5. EPP Command This extension does not add any element to the EPP command described in the EPP domain name mapping [RFC5731]. However, additional elements are defined for the response in the EPP object mapping. When the command has been processed successfully, the EPP element SHOULD be contained in the response if the domain object has data associated with bundled names. This EPP Kong, et al. Expires March 23, 2020 [Page 15] Internet-Draft EPP bundled names Mapping September 2019 element SHOULD contain the which contains element. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: S: S: xn--fsq270a.example S: S: S: xn--fsqz41a.example S: S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: 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 Kong, et al. Expires March 23, 2020 [Page 16] Internet-Draft EPP bundled names Mapping September 2019 Extensible Provisioning Protocol v1.0 Bundle Domain Extension Schema v1.0 Kong, et al. Expires March 23, 2020 [Page 17] Internet-Draft EPP bundled names Mapping September 2019 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:epp:b-dn o Registrant Contact: See the "Author's Address" section of this document. Kong, et al. Expires March 23, 2020 [Page 18] Internet-Draft EPP bundled names Mapping September 2019 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:epp:b-dn o Registrant Contact: See the "Author's Address" section of this document. o XML: See the "Formal Syntax" section of this document. The EPP extension described in this document should be registered by IANA in the "Extensions for the Extensible Provisioning Protocol (EPP)" registry described in [RFC7451]. The details of the registration are as follows: o Name of Extension: "Domain Name Mapping Extension for Strict Bundling Registration" o Document status: Informational o Reference: This document o Registrant Name and Email Address: IESG, iesg@ietf.org o Top-Level Domains (TLDs): Any o IPR Disclosure: https://datatracker.ietf.org/ipr/ o Status: Active o Notes: None 11. Security Considerations Some registries and registrars have more than 15 years of the bundled registration of domain names (especially Chinese domain names). They have not found any significant security issues. One principle that the registry and registrar should let the registrants know is that bundled registered domain names will be created, transferred, updated, and deleted together as a group. The registrants for bundled domain names should remember this principle when doing some operations to these domain names. [RFC5730] also introduces some security consideration. This document does not take a position regarding whether or not the bundled domain names share a DS/DNSKEY key. The DNS administrator can choose whether DS/DNSKEY information can be shared or not. If a Kong, et al. Expires March 23, 2020 [Page 19] Internet-Draft EPP bundled names Mapping September 2019 DS/DNSKEY key is shared then the bundled domain names share fate if there is a key compromise. 12. Implementation Status Note to RFC Editor: Please remove this section before publication. o The Chinese Domain Name Consortium(CDNC) including CNNIC, TWNIC, HKIRC, MONIC, SGNIC and more have followed the principles defined in this document for many years. o CNNIC and TELEINFO have implemented this extension in their 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 an example, the NGO registrant is also registering and purchasing the corresponding name in the .ong TLD (and vice-versa for registrations in .ong). o Patrick Mevzek has released a new version of Net::DRI, an EPP client (Perl library, free software) implementing this extension. 13. Acknowledgements The authors especially thank the authors of [RFC5730] and [RFC5731] and the following ones of CNNIC: Weiping Yang, Chao Qi. Useful comments were made by John Klensin, Scott Hollenbeck, Patrick Mevzek and Edward Lewis. 14. Change History RFC Editor: Please remove this section. 14.1. draft-ietf-regext-bundle-registration: Version 00 o accepted as WG document. 14.2. draft-ietf-regext-bundle-registration: Version 01 o make this document to focus on the restrict bundled domain name registration. Kong, et al. Expires March 23, 2020 [Page 20] Internet-Draft EPP bundled names Mapping September 2019 14.3. draft-ietf-regext-bundle-registration: Version 02 o Update the section of implementation status. 14.4. draft-ietf-regext-bundle-registration: Version 03 o This document is changed to informational category. o Refine the text. 14.5. draft-ietf-regext-bundle-registration: Version 04 o Update the implementation section. o Refine the text. 14.6. draft-ietf-regext-bundle-registration: Version 05 o Scope the XML namespaces to include 'epp'. 14.7. draft-ietf-regext-bundle-registration: Version 06 o add some examples for the transfer, update and renew command o add some text to security consideration 14.8. draft-ietf-regext-bundle-registration: Version 07 o Update IANA consideration section based on Scott's comments o Update security consideration based on Chair and Patrick Mevzek's comments 14.9. draft-ietf-regext-bundle-registration: Version 08 o Refine some texts. 14.10. draft-ietf-regext-bundle-registration: Version 09 o Refine the texts. 14.11. draft-ietf-regext-bundle-registration: Version 10 o Update the texts based on IETF LC. Kong, et al. Expires March 23, 2020 [Page 21] Internet-Draft EPP bundled names Mapping September 2019 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, . [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, . [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, February 2015, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . Kong, et al. Expires March 23, 2020 [Page 22] Internet-Draft EPP bundled names Mapping September 2019 [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 [RFC4290] Klensin, J., "Suggested Practices for Registration of Internationalized Domain Names (IDN)", RFC 4290, DOI 10.17487/RFC4290, December 2005, . Authors' Addresses Ning Kong Consultant Email: ietfing@gmail.com Jiankang Yao CNNIC 4 South 4th Street,Zhongguancun,Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 3007 Email: yaojk@cnnic.cn Kong, et al. Expires March 23, 2020 [Page 23] Internet-Draft EPP bundled names Mapping September 2019 Linlin Zhou CNNIC 4 South 4th Street,Zhongguancun,Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 2677 Email: zhoulinlin@cnnic.cn 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 March 23, 2020 [Page 24]