draft-ietf-regext-bundling-registration-06.txt   draft-ietf-regext-bundling-registration-07.txt 
Internet Engineering Task Force N. Kong Internet Engineering Task Force N. Kong
Internet-Draft Consultant Internet-Draft Consultant
Intended status: Informational J. Yao, Ed. Intended status: Informational J. Yao, Ed.
Expires: April 14, 2019 L. Zhou Expires: May 21, 2019 L. Zhou
CNNIC CNNIC
W. Tan W. Tan
Cloud Registry Cloud Registry
J. Xie J. Xie
October 11, 2018 November 17, 2018
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-06 draft-ietf-regext-bundling-registration-07
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.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 https://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 April 14, 2019. This Internet-Draft will expire on May 21, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://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
skipping to change at page 2, line 48 skipping to change at page 2, line 48
7.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 10 7.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 10
7.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 10 7.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 10
7.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 11 7.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 11
7.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 12 7.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 12
7.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 13 7.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 13
7.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 14 7.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 14
7.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 15 7.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 15
8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 16 8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 16
9. Internationalization Considerations . . . . . . . . . . . . . 18 9. Internationalization Considerations . . . . . . . . . . . . . 18
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
11. Security Considerations . . . . . . . . . . . . . . . . . . . 19 11. Security Considerations . . . . . . . . . . . . . . . . . . . 20
12. Implementation Status . . . . . . . . . . . . . . . . . . . . 19 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 20
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20
14. Change History . . . . . . . . . . . . . . . . . . . . . . . 20 14. Change History . . . . . . . . . . . . . . . . . . . . . . . 21
14.1. draft-kong-epp-bundle-mapping: Version 00 . . . . . . . 20 14.1. draft-kong-epp-bundle-mapping: Version 00 . . . . . . . 21
14.2. draft-kong-epp-bundle-mapping: Version 01 . . . . . . . 20 14.2. draft-kong-epp-bundle-mapping: Version 01 . . . . . . . 21
14.3. draft-kong-epp-bundle-mapping: Version 02 . . . . . . . 20 14.3. draft-kong-epp-bundle-mapping: Version 02 . . . . . . . 21
14.4. draft-ietf-regext-bundle-mapping: Version 00 . . . . . . 20 14.4. draft-ietf-regext-bundle-mapping: Version 00 . . . . . . 21
14.5. draft-ietf-regext-bundle-mapping: Version 01 . . . . . . 20 14.5. draft-ietf-regext-bundle-mapping: Version 01 . . . . . . 21
14.6. draft-ietf-regext-bundle-mapping: Version 02 . . . . . . 21 14.6. draft-ietf-regext-bundle-mapping: Version 02 . . . . . . 21
14.7. draft-ietf-regext-bundle-mapping: Version 03 . . . . . . 21 14.7. draft-ietf-regext-bundle-mapping: Version 03 . . . . . . 21
14.8. draft-ietf-regext-bundle-mapping: Version 04 . . . . . . 21 14.8. draft-ietf-regext-bundle-mapping: Version 04 . . . . . . 21
14.9. draft-ietf-regext-bundle-mapping: Version 05 . . . . . . 21 14.9. draft-ietf-regext-bundle-mapping: Version 05 . . . . . . 22
14.10. draft-ietf-regext-bundle-mapping: Version 06 . . . . . . 21 14.10. draft-ietf-regext-bundle-mapping: Version 06 . . . . . . 22
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 14.11. draft-ietf-regext-bundle-mapping: Version 07 . . . . . . 22
15.1. Normative References . . . . . . . . . . . . . . . . . . 21 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
15.2. Informative References . . . . . . . . . . . . . . . . . 22 15.1. Normative References . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 15.2. Informative References . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
Bundled domain names are those which 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 which 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
skipping to change at page 19, line 29 skipping to change at page 19, line 29
Registration request for the IDN XML schema: Registration request for the IDN XML schema:
o URI: urn:ietf:params:xml:schema:epp:b-dn-1.0 o URI: urn:ietf:params:xml:schema:epp:b-dn-1.0
o Registrant Contact: See the "Author's Address" section of this o Registrant Contact: See the "Author's Address" section of this
document. document.
o XML: See the "Formal Syntax" 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 11. Security Considerations
Some registries and registrars have more than 15 years of the bundled Some registries and registrars have more than 15 years of the bundled
registration of domain names (especially Chinese domain names). They registration of domain names (especially Chinese domain names). They
have not found some significant security issues. One principle that have not found some significant security issues. One principle that
the registry and registrar should let the registrants know is that the registry and registrar should let the registrants know is that
bundled registered domain names will be created, transfered, updated, bundled registered domain names will be created, transfered, updated,
and deleted together as a group. The registrants for bundled domain and deleted together as a group. The registrants for bundled domain
names should remember this principle when doing some operations to names should remember this principle when doing some operations to
these domain names. [RFC5730] also introduces some security these domain names. [RFC5730] also introduces some security
consideration. 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 12. Implementation Status
Note to RFC Editor: Please remove this section before publication. Note to RFC Editor: Please remove this section before publication.
o The Chinese Domain Name Consortium(CDNC) including CNNIC, TWNIC, o The Chinese Domain Name Consortium(CDNC) including CNNIC, TWNIC,
HKIRC, MONIC, SGNIC and more have followed the principles defined HKIRC, MONIC, SGNIC and more have followed the principles defined
in this document for many years. in this document for many years.
o CNNIC and TELEINFO have implemented this extension in their EPP o CNNIC and TELEINFO have implemented this extension in their EPP
based Chinese domain name registration system. based Chinese domain name registration system.
skipping to change at page 21, line 31 skipping to change at page 22, line 15
14.9. draft-ietf-regext-bundle-mapping: Version 05 14.9. draft-ietf-regext-bundle-mapping: Version 05
o Scope the XML namespaces to include 'epp'. o Scope the XML namespaces to include 'epp'.
14.10. draft-ietf-regext-bundle-mapping: Version 06 14.10. draft-ietf-regext-bundle-mapping: Version 06
o add some examples for the transfer, update and renew command o add some examples for the transfer, update and renew command
o add some text to security consideration o add some text to security consideration
14.11. draft-ietf-regext-bundle-mapping: Version 07
o Update IANA consideration section based on Scott's comments
o Update security consideration based on Chair and Patrick Mevzek's
comments
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,
<https://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,
skipping to change at page 22, line 20 skipping to change at page 23, line 10
[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,
<https://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,
<https://www.rfc-editor.org/info/rfc5892>. <https://www.rfc-editor.org/info/rfc5892>.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
February 2015, <https://www.rfc-editor.org/info/rfc7451>.
[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,
""XML Schema Part 1: Structures Second Edition", World ""XML Schema Part 1: Structures Second Edition", World
skipping to change at page 23, line 23 skipping to change at page 24, line 12
DOI 10.17487/RFC4290, December 2005, DOI 10.17487/RFC4290, December 2005,
<https://www.rfc-editor.org/info/rfc4290>. <https://www.rfc-editor.org/info/rfc4290>.
Authors' Addresses Authors' Addresses
Ning Kong Ning Kong
Consultant Consultant
Email: ietfing@gmail.com Email: ietfing@gmail.com
Jiankang Yao (editor) Jiankang Yao
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 3007 Phone: +86 10 5881 3007
Email: yaojk@cnnic.cn Email: yaojk@cnnic.cn
Linlin Zhou Linlin Zhou
CNNIC CNNIC
 End of changes. 13 change blocks. 
21 lines changed or deleted 61 lines changed or added

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