draft-ietf-regext-bundling-registration-00.txt   draft-ietf-regext-bundling-registration-01.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: December 9, 2016 CNNIC Expires: November 4, 2017 CNNIC
W. Tan W. Tan
Cloud Registry Cloud Registry
J. Xie J. Xie
June 7, 2016 May 3, 2017
Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for
Bundling Registration Strict Bundling Registration
draft-ietf-regext-bundling-registration-00 draft-ietf-regext-bundling-registration-01
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 bundling registration of domain names. Specified in management of strict bundling registration of domain names.
XML, this mapping extends the EPP domain name mapping to provide Specified in XML, this mapping extends the EPP domain name mapping to
additional features required for the provisioning of bundled domain provide additional features required for the provisioning of bundled
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 http://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 December 9, 2016. This Internet-Draft will expire on November 4, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 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 (http://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
skipping to change at page 2, line 28 skipping to change at page 2, line 28
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 . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6.2. BDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . 9 7.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 10
7.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 9 7.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 10
7.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 10 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 . . . . . . . . . . . . . . . . 14 7.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 14
8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 14 8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 14
9. Internationalization Considerations . . . . . . . . . . . . . 16 9. Internationalization Considerations . . . . . . . . . . . . . 16
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
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 . . . . . . . . . . . . . . . . . 19
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 who share the same TLD but whose
second level labels are variants, or those who has identical second second level labels are variants, or those who 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 with the different TLDs
(V-tld); (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.
For the name variants, some registries adopt the policy that variant For the name variants, some registries adopt the policy that variant
IDNs which are identified as equivalent are allocated or delegated to IDNs which are identified as equivalent are allocated or delegated to
the same registrant. For example, the specified registration policy the same registrant. For example, the specified registration policy
of Chinese Domain Name (CDN) is that a registrant can apply an of Chinese Domain Name (CDN) is that a registrant can apply an
original CDN in any forms: Simplified Chinese (SC) form, Traditional original CDN in any forms: Simplified Chinese (SC) form, Traditional
Chinese (TC) form, or other variant forms, then the corresponding Chinese (TC) form, or other variant forms, then the corresponding
variant CDN in SC form and that in TC form will also be delegated to variant CDN in SC form and that in TC form will also be delegated to
the same registrant. All variant names in the same TLD contain same the same registrant. All variant names in the same TLD contain same
attributes. attributes.
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 bindled names which share the same not specify how to register the strict bundled names which share many
attributes. same attributes.
In order to meet above requirements of the 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
skipping to change at page 18, line 29 skipping to change at page 18, line 29
o Refine the text, and update the examples. o Refine the text, and update the examples.
14.3. draft-kong-epp-bundle-mapping: Version 02 14.3. draft-kong-epp-bundle-mapping: Version 02
o Refine the texts. o Refine the texts.
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
o make this document to focus on the restrict bundled domain name
registration.
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>. <http://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,
 End of changes. 15 change blocks. 
19 lines changed or deleted 35 lines changed or added

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