draft-ietf-regext-bundling-registration-01.txt   draft-ietf-regext-bundling-registration-02.txt 
Internet Engineering Task Force N. Kong Internet Engineering Task Force N. Kong
Internet-Draft J. Yao, Ed. Internet-Draft J. Yao, Ed.
Intended status: Standards Track X. Li Intended status: Standards Track X. Li
Expires: November 4, 2017 CNNIC Expires: April 29, 2018 CNNIC
W. Tan W. Tan
Cloud Registry Cloud Registry
J. Xie J. Xie
May 3, 2017 October 26, 2017
Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for
Strict Bundling Registration Strict Bundling Registration
draft-ietf-regext-bundling-registration-01 draft-ietf-regext-bundling-registration-02
Abstract Abstract
This document describes an extension of Extensible Provisioning This document describes an extension of Extensible Provisioning
Protocol (EPP) domain name mapping for the provisioning and Protocol (EPP) domain name mapping for the provisioning and
management of strict bundling registration of domain names. management of strict bundling registration of domain names.
Specified in XML, this mapping extends the EPP domain name mapping to Specified in XML, this mapping extends the EPP domain name mapping to
provide additional features required for the provisioning of bundled provide additional features required for the provisioning of bundled
domain names. domain names.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- 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 Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." 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 Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents 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 publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
skipping to change at page 3, line 8 skipping to change at page 3, line 8
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
11. Security Considerations . . . . . . . . . . . . . . . . . . . 17 11. Security Considerations . . . . . . . . . . . . . . . . . . . 17
12. Implementation Status . . . . . . . . . . . . . . . . . . . . 17 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 17
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17
14. Change History . . . . . . . . . . . . . . . . . . . . . . . 18 14. Change History . . . . . . . . . . . . . . . . . . . . . . . 18
14.1. draft-kong-epp-bundle-mapping: Version 00 . . . . . . . 18 14.1. draft-kong-epp-bundle-mapping: Version 00 . . . . . . . 18
14.2. draft-kong-epp-bundle-mapping: Version 01 . . . . . . . 18 14.2. draft-kong-epp-bundle-mapping: Version 01 . . . . . . . 18
14.3. draft-kong-epp-bundle-mapping: Version 02 . . . . . . . 18 14.3. draft-kong-epp-bundle-mapping: Version 02 . . . . . . . 18
14.4. draft-ietf-regext-bundle-mapping: Version 00 . . . . . . 18 14.4. draft-ietf-regext-bundle-mapping: Version 00 . . . . . . 18
14.5. draft-ietf-regext-bundle-mapping: Version 01 . . . . . . 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. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
15.1. Normative References . . . . . . . . . . . . . . . . . . 18 15.1. Normative References . . . . . . . . . . . . . . . . . . 18
15.2. Informative References . . . . . . . . . . . . . . . . . 19 15.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
Bundled domain names are those who share the same TLD but whose Bundled domain names are those which share the same TLD but whose
second level labels are variants, or those who has identical second second level labels are variants, or those which has identical second
level labels for which certain parameters are shared in different level labels for which certain parameters are shared in different
TLDs. For example, Public Interest Registry, request to implement TLDs. For example, Public Interest Registry, request to implement
technical bundling of second level domains for .NGO and .ONG. So we 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 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 "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 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 which the second level labels(LABEL) are same ending with the
(V-tld); different TLDs (V-tld);
There are several kinds of bundling. First one is strict bundling, There are several kinds of bundling. First one is strict bundling,
which requires all bundled names to share many same attributes. When which requires all bundled names to share many same attributes. When
creating, updating, or transfering of any of the bundled domain creating, updating, or transfering of any of the bundled domain
names, all bundled domain names will be created, updated or names, all bundled domain names will be created, updated or
transferred. Second one is partial bundling, which requires that at transferred. Second one is partial bundling, which requires that at
least the bundled domain names if registered should be registered by least the bundled domain names if registered should be registered by
the same registrant. Third one is relax bundling, which has not the same registrant. Third one is relax bundling, which has not
specific requirements to the domain registration. This document specific requirements to the domain registration. This document
mainly focus on strict bundling names registration. mainly focus on strict bundling names registration.
skipping to change at page 5, line 27 skipping to change at page 5, line 27
Bundled names, brought about the need for multiple domain names to be Bundled names, brought about the need for multiple domain names to be
registered and managed as a single package. In this model, the registered and managed as a single package. In this model, the
registry typically accepts a domain registration request (i.e. EPP registry typically accepts a domain registration request (i.e. EPP
domain <create> command) containing the domain name to be registered. domain <create> command) containing the domain name to be registered.
This domain name is referred to as the RDN in this document. As part This domain name is referred to as the RDN in this document. As part
of the processing of the registration request, the registry generates of the processing of the registration request, the registry generates
a set of bundled names that are related to the RDN, either a set of bundled names that are related to the RDN, either
programmatically or with the guidance of registration policies, and programmatically or with the guidance of registration policies, and
place them in the registration package together with the RDN. 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 and sponsoring registrar, by sharing one domain object. So when
users update any property of a domain object within a bundle package, users update any property of a domain object within a bundle package,
that property of all other domain objects in the bundle package will that property of all other domain objects in the bundle package will
be updated at the same time. be updated at the same time.
5. Requirement for Bundling Registration of Names 5. Requirement for Bundling Registration of Names
The bundled names whether they are in the form of "V-label.TLD" or in 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 the form of "LABEL.V-tld" should share some parameter or attributes
assoicated with domain names. Typically, Bundled names will share assoicated with domain names. Typically, Bundled names will share
skipping to change at page 17, line 29 skipping to change at page 17, line 29
The object mapping extension described in this document does not The object mapping extension described in this document does not
provide any other security services or introduce any additional provide any other security services or introduce any additional
considerations beyond those described by [RFC5730] or those caused by considerations beyond those described by [RFC5730] or those caused by
the protocol layers used by EPP. the protocol layers used by EPP.
12. Implementation Status 12. Implementation Status
Note to RFC Editor: Please remove this section before publication. Note to RFC Editor: Please remove this section before publication.
o CNNIC has implemented this extension in his EPP based Chinese o The Chinese Domain Name Consortium(CDNC) including CNNIC, TWNIC,
domain name registration system. 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 o Public Interest Registry, has requested to implement technical
bundling of second level domains for .NGO and .ONG. This means bundling of second level domains for .NGO and .ONG. This means
that by registering and purchasing a domain in the .ngo TLD, for that by registering and purchasing a domain in the .ngo TLD, for
example, the NGO registrant is also registering and purchasing the example, the NGO registrant is also registering and purchasing the
corresponding name in the .ong TLD (and vice-versa for corresponding name in the .ong TLD (and vice-versa for
registrations in .ong). registrations in .ong).
13. Acknowledgements 13. Acknowledgements
skipping to change at page 18, line 34 skipping to change at page 18, line 34
14.4. draft-ietf-regext-bundle-mapping: Version 00 14.4. draft-ietf-regext-bundle-mapping: Version 00
o accepted as WG document. o accepted as WG document.
14.5. draft-ietf-regext-bundle-mapping: Version 01 14.5. draft-ietf-regext-bundle-mapping: Version 01
o make this document to focus on the restrict bundled domain name o make this document to focus on the restrict bundled domain name
registration. registration.
14.6. draft-ietf-regext-bundle-mapping: Version 02
o Update the section of implementation status.
15. References 15. References
15.1. Normative References 15.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
<http://www.rfc-editor.org/info/rfc5730>. <https://www.rfc-editor.org/info/rfc5730>.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731, Domain Name Mapping", STD 69, RFC 5731,
DOI 10.17487/RFC5731, August 2009, DOI 10.17487/RFC5731, August 2009,
<http://www.rfc-editor.org/info/rfc5731>. <https://www.rfc-editor.org/info/rfc5731>.
[RFC5890] Klensin, J., "Internationalized Domain Names for [RFC5890] Klensin, J., "Internationalized Domain Names for
Applications (IDNA): Definitions and Document Framework", Applications (IDNA): Definitions and Document Framework",
RFC 5890, DOI 10.17487/RFC5890, August 2010, RFC 5890, DOI 10.17487/RFC5890, August 2010,
<http://www.rfc-editor.org/info/rfc5890>. <https://www.rfc-editor.org/info/rfc5890>.
[RFC5891] Klensin, J., "Internationalized Domain Names in [RFC5891] Klensin, J., "Internationalized Domain Names in
Applications (IDNA): Protocol", RFC 5891, Applications (IDNA): Protocol", RFC 5891,
DOI 10.17487/RFC5891, August 2010, DOI 10.17487/RFC5891, August 2010,
<http://www.rfc-editor.org/info/rfc5891>. <https://www.rfc-editor.org/info/rfc5891>.
[RFC5892] Faltstrom, P., Ed., "The Unicode Code Points and [RFC5892] Faltstrom, P., Ed., "The Unicode Code Points and
Internationalized Domain Names for Applications (IDNA)", Internationalized Domain Names for Applications (IDNA)",
RFC 5892, DOI 10.17487/RFC5892, August 2010, RFC 5892, DOI 10.17487/RFC5892, August 2010,
<http://www.rfc-editor.org/info/rfc5892>. <https://www.rfc-editor.org/info/rfc5892>.
[W3C.REC-xml-20040204] [W3C.REC-xml-20040204]
Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and
F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third
Edition)", World Wide Web Consortium FirstEdition REC-xml- Edition)", World Wide Web Consortium FirstEdition REC-xml-
20040204", February 2004, 20040204", February 2004,
<http://www.w3.org/TR/2004/REC-xml-20040204>. <http://www.w3.org/TR/2004/REC-xml-20040204>.
[W3C.REC-xmlschema-1-20041028] [W3C.REC-xmlschema-1-20041028]
Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn,
skipping to change at page 19, line 51 skipping to change at page 20, line 11
Second Edition", World Wide Web Consortium Recommendation Second Edition", World Wide Web Consortium Recommendation
REC-xmlschema-2-20041028", October 2004, REC-xmlschema-2-20041028", October 2004,
<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>. <http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
15.2. Informative References 15.2. Informative References
[bundle.name] [bundle.name]
ICANN, "Registry Services Technical Evaluation Panel ICANN, "Registry Services Technical Evaluation Panel
(RSTEP) Report on Public Interest Registry's Request to (RSTEP) Report on Public Interest Registry's Request to
Implement Technical Bundling in .NGO and .ONG", July 2014, Implement Technical Bundling in .NGO and .ONG", July 2014,
<https://www.icann.org/public-comments/rstep-technical- <https://www.icann.org/public-comments/
bundling-2014-07-29-en>. rstep-technical-bundling-2014-07-29-en>.
[Final.Integrated.Issues.Report] [Final.Integrated.Issues.Report]
ICANN, "The IDN Variant Issues Project: A Study of Issues ICANN, "The IDN Variant Issues Project: A Study of Issues
Related to the Management of IDN Variant TLDs", February Related to the Management of IDN Variant TLDs", February
2012, <http://www.icann.org/en/topics/idn/ 2012, <http://www.icann.org/en/topics/idn/
idn-vip-integrated-issues-final-clean-20feb12-en.pdf>. idn-vip-integrated-issues-final-clean-20feb12-en.pdf>.
[RFC4290] Klensin, J., "Suggested Practices for Registration of [RFC4290] Klensin, J., "Suggested Practices for Registration of
Internationalized Domain Names (IDN)", RFC 4290, Internationalized Domain Names (IDN)", RFC 4290,
DOI 10.17487/RFC4290, December 2005, DOI 10.17487/RFC4290, December 2005,
<http://www.rfc-editor.org/info/rfc4290>. <https://www.rfc-editor.org/info/rfc4290>.
Authors' Addresses Authors' Addresses
Ning Kong Ning Kong
CNNIC CNNIC
4 South 4th Street,Zhongguancun,Haidian District 4 South 4th Street,Zhongguancun,Haidian District
Beijing, Beijing 100190 Beijing, Beijing 100190
China China
Phone: +86 10 5881 3147 Phone: +86 10 5881 3147
 End of changes. 23 change blocks. 
25 lines changed or deleted 34 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/