--- 1/draft-ietf-regext-bundling-registration-01.txt 2017-10-26 20:13:09.639167918 -0700 +++ 2/draft-ietf-regext-bundling-registration-02.txt 2017-10-26 20:13:09.679168872 -0700 @@ -1,58 +1,58 @@ Internet Engineering Task Force N. Kong Internet-Draft J. Yao, Ed. Intended status: Standards Track X. Li -Expires: November 4, 2017 CNNIC +Expires: April 29, 2018 CNNIC W. Tan Cloud Registry J. Xie - May 3, 2017 + October 26, 2017 Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for Strict Bundling Registration - draft-ietf-regext-bundling-registration-01 + draft-ietf-regext-bundling-registration-02 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/. + 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 November 4, 2017. + This Internet-Draft will expire on April 29, 2018. 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 + (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. 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 @@ -91,37 +91,38 @@ 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 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 + 14.6. draft-ietf-regext-bundle-mapping: Version 02 . . . . . . 18 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 15.1. Normative References . . . . . . . . . . . . . . . . . . 18 - 15.2. Informative References . . . . . . . . . . . . . . . . . 19 + 15.2. Informative References . . . . . . . . . . . . . . . . . 20 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 + Bundled domain names are those which share the same TLD but whose + second level labels are variants, or those which 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); + which the second level labels(LABEL) are same ending 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. @@ -203,21 +204,21 @@ 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 + The bundled names share many 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 @@ -758,22 +759,26 @@ 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 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 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 @@ -807,56 +812,60 @@ 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. +14.6. draft-ietf-regext-bundle-mapping: Version 02 + + o Update the section of implementation status. + 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, - . + . [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, @@ -870,33 +879,33 @@ 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, - . + . [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