--- 1/draft-ietf-regext-bundling-registration-10.txt 2019-10-06 03:13:22.769697638 -0700 +++ 2/draft-ietf-regext-bundling-registration-11.txt 2019-10-06 03:13:22.817698848 -0700 @@ -1,109 +1,111 @@ Internet Engineering Task Force N. Kong Internet-Draft Consultant Intended status: Informational J. Yao -Expires: March 23, 2020 L. Zhou +Expires: April 7, 2020 L. Zhou CNNIC W. Tan Cloud Registry J. Xie - September 20, 2019 + October 5, 2019 Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for Strict Bundling Registration - draft-ietf-regext-bundling-registration-10 + draft-ietf-regext-bundling-registration-11 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. + domain names. This is a non-standard proprietary extension. 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. + This Internet-Draft will expire on April 7, 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 (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 + 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. Requirement for Bundling Registration of Names . . . . . . . 5 6. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 6 6.1. RDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 6.2. BDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 + 6.2. BDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 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 - 15.1. Normative References . . . . . . . . . . . . . . . . . . 22 - 15.2. Informative References . . . . . . . . . . . . . . . . . 23 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 + 7.2.2. EPP Command . . . . . . . . . . . . . . . . 13 + 7.2.3. EPP Command . . . . . . . . . . . . . . . . . 14 + 7.2.4. EPP Command . . . . . . . . . . . . . . . 15 + 7.2.5. EPP Command . . . . . . . . . . . . . . . . 16 + 8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 17 + 9. Internationalization Considerations . . . . . . . . . . . . . 19 + 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 + 11. Security Considerations . . . . . . . . . . . . . . . . . . . 20 + 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 21 + 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 + 14. Change History . . . . . . . . . . . . . . . . . . . . . . . 21 + 14.1. draft-ietf-regext-bundle-registration: Version 00 . . . 21 + 14.2. draft-ietf-regext-bundle-registration: Version 01 . . . 21 + 14.3. draft-ietf-regext-bundle-registration: Version 02 . . . 22 + 14.4. draft-ietf-regext-bundle-registration: Version 03 . . . 22 + 14.5. draft-ietf-regext-bundle-registration: Version 04 . . . 22 + 14.6. draft-ietf-regext-bundle-registration: Version 05 . . . 22 + 14.7. draft-ietf-regext-bundle-registration: Version 06 . . . 22 + 14.8. draft-ietf-regext-bundle-registration: Version 07 . . . 22 + 14.9. draft-ietf-regext-bundle-registration: Version 08 . . . 22 + 14.10. draft-ietf-regext-bundle-registration: Version 09 . . . 22 + 14.11. draft-ietf-regext-bundle-registration: Version 10 . . . 22 + 14.12. draft-ietf-regext-bundle-registration: Version 11 . . . 23 + + 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 + 15.1. Normative References . . . . . . . . . . . . . . . . . . 23 + 15.2. Informative References . . . . . . . . . . . . . . . . . 24 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 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 @@ -133,24 +135,27 @@ 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 - notation as described in [W3C.REC-xmlschema-1-20041028] and - [W3C.REC-xmlschema-2-20041028]. + names. This document describes a non-standard proprietary extension. + + This extension is specially useful for registries of practising + Chinese domain name registration. This document is specified using + 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 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. @@ -158,22 +163,23 @@ 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]. + ASCII characters will be represented in the format of "&#xXXXX;" + where XXXX is a UNICODE point by using the XML escaping mechanism. + 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. @@ -268,32 +273,32 @@ 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-- + 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. - For example: xn-- + 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 @@ -346,21 +351,22 @@ 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 + domain mapping [RFC5731]. In addition, unless some registration + policy has some special processing, 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. o An OPTIONAL element that contains the BDN, along with @@ -400,24 +406,24 @@ S: S: S: 2fooBAR S: S: S: S: S: S: - S: + S: S: xn--fsq270a.example S: - S: + S: S: xn--fsqz41a.example S: S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: @@ -437,43 +443,45 @@ 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: + domain mapping [RFC5731]. Unless some registration policy has some + special processing, 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. 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. Unless some registration policy has some special + processing, 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: @@ -485,32 +493,32 @@ C: 123 C: 123 C: C: 2fooBAR C: 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 + domain mapping [RFC5731]. In addition, unless some registration + policy has some special processing, 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 element. Example response: S: S: S: @@ -522,24 +530,24 @@ S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> 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: S: xn--fsq270a.example S: - S: + S: S: xn--fsqz41a.example S: S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: @@ -549,42 +557,43 @@ 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 - domain mapping [RFC5731]. In addition, the EPP element + domain mapping [RFC5731]. In addition, unless some registration + policy has some special processing, 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: S: xn--fsq270a.example S: - S: + S: S: xn--fsqz41a.example S: S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: @@ -592,71 +601,72 @@ 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 + successfully, the EPP element SHALL be contained in the response if the domain object has data associated with bundled names. - - This EPP element SHOULD contain the which - contains element. + Unless some registration policy has some special processing, 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: S: xn--fsq270a.example S: - 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 + successfully, the EPP element SHALL be contained in the response if the domain object has data associated with bundled names. - This EPP element SHOULD contain the which - contains element. + Unless some registration policy has some special processing, this EPP + element SHOULD contain the which contains + element. Example response: S: S: S: S: S: Command completed successfully; action pending S: S: @@ -668,63 +678,64 @@ 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: S: xn--fsq270a.example S: - 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 - element SHOULD contain the which contains - element. + the EPP element SHALL be contained in the response if the + domain object has data associated with bundled names. Unless some + registration policy has some special processing, this EPP + element SHOULD contain the which contains + element. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: - S: + S: S: xn--fsq270a.example S: - S: + S: S: xn--fsqz41a.example S: S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: @@ -877,25 +886,25 @@ 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. + 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 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. @@ -976,20 +985,24 @@ 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. +14.12. draft-ietf-regext-bundle-registration: Version 11 + + o Update the texts based on AD's comment. + 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,