draft-ietf-regext-bundling-registration-03.txt   draft-ietf-regext-bundling-registration-04.txt 
Internet Engineering Task Force N. Kong
Internet-Draft J. Yao, Ed. Internet Engineering Task Force N. Kong
Intended status: Informational X. Li Internet-Draft Consultant
Expires: October 30, 2018 CNNIC Intended status: Informational J. Yao, Ed.
Expires: February 15, 2019 L. Zhou
CNNIC
W. Tan W. Tan
Cloud Registry Cloud Registry
J. Xie J. Xie
April 28, 2018 August 14, 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-03 draft-ietf-regext-bundling-registration-04
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 39 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 October 30, 2018. This Internet-Draft will expire on February 15, 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 27 skipping to change at page 2, line 28
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Requirement for Bundling Registration of Names . . . . . . . 5 5. Requirement for Bundling Registration of Names . . . . . . . 5
6. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 6 6. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 6
6.1. RDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6.1. RDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.2. BDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 6.2. BDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7 7. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7
7.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7 7.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7
7.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 7 7.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 7
7.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 8 7.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 8
7.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 10 7.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 10
skipping to change at page 3, line 10 skipping to change at page 3, line 11
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 14.6. draft-ietf-regext-bundle-mapping: Version 02 . . . . . . 18
14.7. draft-ietf-regext-bundle-mapping: Version 03 . . . . . . 18 14.7. draft-ietf-regext-bundle-mapping: Version 03 . . . . . . 18
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 14.8. draft-ietf-regext-bundle-mapping: Version 04 . . . . . . 18
15.1. Normative References . . . . . . . . . . . . . . . . . . 18 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
15.1. Normative References . . . . . . . . . . . . . . . . . . 19
15.2. Informative References . . . . . . . . . . . . . . . . . 20 15.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
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
skipping to change at page 4, line 11 skipping to change at page 4, line 14
The basic Extensible Provisioning Protocol (EPP) domain name mapping The basic Extensible Provisioning Protocol (EPP) domain name mapping
[RFC5731] provides the domain name registration one by one. It does [RFC5731] provides the domain name registration one by one. It does
not specify how to register the strict bundled names which share many not specify how to register the strict bundled names which share many
same attributes. same attributes.
In order to meet above requirements of the strict bundled names In order to meet above requirements of the strict bundled names
registration, this document describes an extension of the EPP domain registration, this document describes an extension of the EPP domain
name mapping [RFC5731] for the provisioning and management of bundled name mapping [RFC5731] for the provisioning and management of bundled
names.This document is specified using the Extensible Markup Language names.This document is specified using the Extensible Markup Language
(XML) 1.0 as described in [W3C.REC-xml-20040204] and XML Schema (XML) 1.0 as described in [W3C.REC-xml-20040204] and XML Schema
notation as described in [W3C.REC-xmlschema-1-20041028] and notation as described in [W3C.REC-xmlschema-1-20041028] and
[W3C.REC-xmlschema-2-20041028]. [W3C.REC-xmlschema-2-20041028].
The EPP core protocol specification [RFC5730] provides a complete The EPP core protocol specification [RFC5730] provides a complete
description of EPP command and response structures. A thorough description of EPP command and response structures. A thorough
understanding of the base protocol specification is necessary to understanding of the base protocol specification is necessary to
understand the extension of mapping described in this document. understand the extension of mapping described in this document.
This document uses lots of the concepts of the IDN, so a thorough This document uses lots of the concepts of the IDN, so a thorough
understanding of the IDNs for Application (IDNA, described in understanding of the IDNs for Application (IDNA, described in
[RFC5890], [RFC5891], and [RFC5892]) and a thorough understanding of [RFC5890], [RFC5891], and [RFC5892]) and a thorough understanding of
skipping to change at page 17, line 43 skipping to change at page 17, line 43
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.
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).
o Patrick Mevzek has released a new version of Net::DRI, an EPP
client (Perl library, free software) implementing this extension.
13. Acknowledgements 13. Acknowledgements
The authors especially thank the authors of [RFC5730] and [RFC5731] The authors especially thank the authors of [RFC5730] and [RFC5731]
and the following ones of CNNIC: Weiping Yang, Chao Qi. This draft and the following ones of CNNIC: Weiping Yang, Chao Qi. This draft
extends the draft draft-kong-epp-idn-variants-mapping to support both extends the draft draft-kong-epp-idn-variants-mapping to support both
forms of bundled names: V-label.TLD and LABEL.V-tld. forms of bundled names: V-label.TLD and LABEL.V-tld.
Useful comments were made by John Klensin, Scott Hollenbeck, Patrick Useful comments were made by John Klensin, Scott Hollenbeck, Patrick
Mevzek and Edward Lewis. Mevzek and Edward Lewis.
skipping to change at page 18, line 44 skipping to change at page 18, line 47
14.6. draft-ietf-regext-bundle-mapping: Version 02 14.6. draft-ietf-regext-bundle-mapping: Version 02
o Update the section of implementation status. o Update the section of implementation status.
14.7. draft-ietf-regext-bundle-mapping: Version 03 14.7. draft-ietf-regext-bundle-mapping: Version 03
o This document is changed to informational category. o This document is changed to informational category.
o Refine the text. o Refine the text.
14.8. draft-ietf-regext-bundle-mapping: Version 04
o Update the implementation section.
o Refine the text.
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 20, line 28 skipping to change at page 20, line 41
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,
<https://www.rfc-editor.org/info/rfc4290>. <https://www.rfc-editor.org/info/rfc4290>.
Authors' Addresses Authors' Addresses
Ning Kong Ning Kong
CNNIC Consultant
4 South 4th Street,Zhongguancun,Haidian District
Beijing, Beijing 100190
China
Phone: +86 10 5881 3147
Email: nkong@cnnic.cn
Email: ietfing@gmail.com
Jiankang Yao (editor) Jiankang Yao (editor)
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
Xiaodong Li
Linlin Zhou
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 3020 Phone: +86 10 5881 2677
Email: xl@cnnic.cn Email: zhoulinlin@cnnic.cn
Wil Tan Wil Tan
Cloud Registry Cloud Registry
Suite 32 Seabridge House, 377 Kent St Suite 32 Seabridge House, 377 Kent St
Sydney, NSW 2000 Sydney, NSW 2000
Australia Australia
Phone: +61 414 710899 Phone: +61 414 710899
Email: wil@cloudregistry.net Email: wil@cloudregistry.net
 End of changes. 13 change blocks. 
22 lines changed or deleted 30 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/