draft-ietf-regext-bundling-registration-10.txt   draft-ietf-regext-bundling-registration-11.txt 
Internet Engineering Task Force N. Kong Internet Engineering Task Force N. Kong
Internet-Draft Consultant Internet-Draft Consultant
Intended status: Informational J. Yao Intended status: Informational J. Yao
Expires: March 23, 2020 L. Zhou Expires: April 7, 2020 L. Zhou
CNNIC CNNIC
W. Tan W. Tan
Cloud Registry Cloud Registry
J. Xie J. Xie
September 20, 2019 October 5, 2019
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-10 draft-ietf-regext-bundling-registration-11
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. This is a non-standard proprietary extension.
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 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 March 23, 2020. This Internet-Draft will expire on April 7, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
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.
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 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
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 . . . . . . . . . . . . . . . . 13
7.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 13 7.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 14
7.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 14 7.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 15
7.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 15 7.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 16
8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 16 8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 17
9. Internationalization Considerations . . . . . . . . . . . . . 18 9. Internationalization Considerations . . . . . . . . . . . . . 19
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
11. Security Considerations . . . . . . . . . . . . . . . . . . . 19 11. Security Considerations . . . . . . . . . . . . . . . . . . . 20
12. Implementation Status . . . . . . . . . . . . . . . . . . . . 20 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 21
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
14. Change History . . . . . . . . . . . . . . . . . . . . . . . 20 14. Change History . . . . . . . . . . . . . . . . . . . . . . . 21
14.1. draft-ietf-regext-bundle-registration: Version 00 . . . 20 14.1. draft-ietf-regext-bundle-registration: Version 00 . . . 21
14.2. draft-ietf-regext-bundle-registration: Version 01 . . . 20 14.2. draft-ietf-regext-bundle-registration: Version 01 . . . 21
14.3. draft-ietf-regext-bundle-registration: Version 02 . . . 21 14.3. draft-ietf-regext-bundle-registration: Version 02 . . . 22
14.4. draft-ietf-regext-bundle-registration: Version 03 . . . 21 14.4. draft-ietf-regext-bundle-registration: Version 03 . . . 22
14.5. draft-ietf-regext-bundle-registration: Version 04 . . . 21 14.5. draft-ietf-regext-bundle-registration: Version 04 . . . 22
14.6. draft-ietf-regext-bundle-registration: Version 05 . . . 21 14.6. draft-ietf-regext-bundle-registration: Version 05 . . . 22
14.7. draft-ietf-regext-bundle-registration: Version 06 . . . 21 14.7. draft-ietf-regext-bundle-registration: Version 06 . . . 22
14.8. draft-ietf-regext-bundle-registration: Version 07 . . . 21 14.8. draft-ietf-regext-bundle-registration: Version 07 . . . 22
14.9. draft-ietf-regext-bundle-registration: Version 08 . . . 21 14.9. draft-ietf-regext-bundle-registration: Version 08 . . . 22
14.10. draft-ietf-regext-bundle-registration: Version 09 . . . 21 14.10. draft-ietf-regext-bundle-registration: Version 09 . . . 22
14.11. draft-ietf-regext-bundle-registration: Version 10 . . . 21 14.11. draft-ietf-regext-bundle-registration: Version 10 . . . 22
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 14.12. draft-ietf-regext-bundle-registration: Version 11 . . . 23
15.1. Normative References . . . . . . . . . . . . . . . . . . 22
15.2. Informative References . . . . . . . . . . . . . . . . . 23 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 15.1. Normative References . . . . . . . . . . . . . . . . . . 23
15.2. Informative References . . . . . . . . . . . . . . . . . 24
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 have identical second level labels are variants, or those which have identical
second level labels for which certain parameters are shared in second level labels for which certain parameters are shared in
different TLDs. For an example, Public Interest Registry has different TLDs. For an example, Public Interest Registry has
requested to implement bundling of second level domains for .NGO and requested to implement bundling of second level domains for .NGO and
.ONG. So we have two kinds of bundled domain names. The first one .ONG. So we have two kinds of bundled domain names. The first one
is in the form of "V-label.TLD" in which the second level label is in the form of "V-label.TLD" in which the second level label
skipping to change at page 3, line 50 skipping to change at page 3, line 52
share a common set of attributes. share a common set of attributes.
The basic Extensible Provisioning Protocol (EPP) domain name mapping The basic Extensible Provisioning Protocol (EPP) domain name mapping
[RFC5731] provides the facility for single domain name registration. [RFC5731] provides the facility for single domain name registration.
It does not specify how to register the strict bundled names which It does not specify how to register the strict bundled names which
share many of the attributes. share many of the attributes.
In order to meet the above requirements of strict bundled name In order to meet the above requirements of strict bundled name
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 Extensible Markup Language names. This document describes a non-standard proprietary extension.
(XML) 1.0 as described in [W3C.REC-xml-20040204] and XML Schema
notation as described in [W3C.REC-xmlschema-1-20041028] and This extension is specially useful for registries of practising
[W3C.REC-xmlschema-2-20041028]. Chinese domain name registration. This document is specified using
Extensible Markup Language (XML) 1.0 as described in
[W3C.REC-xml-20040204] and XML Schema notation as described in
[W3C.REC-xmlschema-1-20041028] and [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 mapping described in this document. understand the extension mapping described in this document.
This document uses many IDN concepts, so a thorough understanding of This document uses many IDN concepts, so a thorough understanding of
the IDNs for Application (IDNA, described in [RFC5890], [RFC5891], the IDNs for Application (IDNA, described in [RFC5890], [RFC5891],
and [RFC5892]) and the variant approach discussed in [RFC4290] is and [RFC5892]) and the variant approach discussed in [RFC4290] is
assumed. assumed.
skipping to change at page 4, line 27 skipping to change at page 4, line 31
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119][RFC8174] when, and only when, they appear in all 14 [RFC2119][RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
uLabel in this document is used to express the U-label of an uLabel in this document is used to express the U-label of an
internationalized domain name as a series of characters where non- internationalized domain name as a series of characters where non-
ASCII characters will be represented in the format of U+XXXX where ASCII characters will be represented in the format of "&#xXXXX;"
XXXX is a UNICODE point. U-Label is defined in [RFC5890]. where XXXX is a UNICODE point by using the XML escaping mechanism.
U-Label is defined in [RFC5890].
The XML namespace prefix "b-dn" is used for the namespace The XML namespace prefix "b-dn" is used for the namespace
"urn:ietf:params:xml:ns:epp:b-dn", but implementations MUST NOT rely "urn:ietf:params:xml:ns:epp:b-dn", but implementations MUST NOT rely
on it and instead employ a proper namespace-aware XML parser and on it and instead employ a proper namespace-aware XML parser and
serializer to interpret and output the XML documents. serializer to interpret and output the XML documents.
In examples, "C:" represents lines sent by a protocol client and "S:" In examples, "C:" represents lines sent by a protocol client and "S:"
represents lines returned by a protocol server. Indentation and represents lines returned by a protocol server. Indentation and
white space in examples are provided only to illustrate element white space in examples are provided only to illustrate element
relationships and are not a required feature of this specification. relationships and are not a required feature of this specification.
skipping to change at page 6, line 42 skipping to change at page 6, line 50
domain name mapping [RFC5731]. All of these additional elements are domain name mapping [RFC5731]. All of these additional elements are
returned from <domain:info> command. returned from <domain:info> command.
6.1. RDN 6.1. RDN
The RDN is an ASCII name or an IDN with the A-label [RFC5890] form. The RDN is an ASCII name or an IDN with the A-label [RFC5890] form.
In this document, its corresponding element is <b-dn:rdn>. An In this document, its corresponding element is <b-dn:rdn>. An
optional attribute "uLabel" associated with <b-dn:rdn> is used to optional attribute "uLabel" associated with <b-dn:rdn> is used to
represent the U-label [RFC5890] form. represent the U-label [RFC5890] form.
For example: <b-dn:rdn uLabel="U+5B9E U+4F8B.example"> xn-- For example: <b-dn:rdn uLabel="&#x5B9E;&#x4F8B;.example"> xn--
fsq270a.example</b-dn:rdn> fsq270a.example</b-dn:rdn>
6.2. BDN 6.2. BDN
The BDN is an ASCII name or an IDN with the A-label [RFC5890] form The BDN is an ASCII name or an IDN with the A-label [RFC5890] form
which is converted from the corresponding BDN. In this document, its which is converted from the corresponding BDN. In this document, its
corresponding element is <b-dn:bdn>. An optional attribute "uLabel" corresponding element is <b-dn:bdn>. An optional attribute "uLabel"
associated with <b-dn:bdn> is used to represent the U-label [RFC5890] associated with <b-dn:bdn> is used to represent the U-label [RFC5890]
form. form.
For example: <b-dn:bdn uLabel="U+5BE6 U+4F8B.example"> xn-- For example: <b-dn:bdn uLabel="&#x5BE6;&#x4F8B;.example"> xn--
fsqz41a.example</b-dn:bdn> fsqz41a.example</b-dn:bdn>
7. EPP Command Mapping 7. EPP Command Mapping
A detailed description of the EPP syntax and semantics can be found A detailed description of the EPP syntax and semantics can be found
in the EPP core protocol specification [RFC5730]. The command in the EPP core protocol specification [RFC5730]. The command
mappings described here are specifically for use in provisioning and mappings described here are specifically for use in provisioning and
managing bundled names via EPP. managing bundled names via EPP.
7.1. EPP Query Commands 7.1. EPP Query Commands
skipping to change at page 8, line 44 skipping to change at page 8, line 44
S:</epp> S:</epp>
7.1.2. EPP <info> Command 7.1.2. EPP <info> Command
This extension does not add any element to the EPP <info> command This extension does not add any element to the EPP <info> command
described in the EPP domain mapping [RFC5731]. However, additional described in the EPP domain mapping [RFC5731]. However, additional
elements are defined for the <info> response. elements are defined for the <info> response.
When an <info> command has been processed successfully, the EPP When an <info> command has been processed successfully, the EPP
<resData> element MUST contain child elements as described in the EPP <resData> element MUST contain child elements as described in the EPP
domain mapping [RFC5731]. In addition, the EPP <extension> element domain mapping [RFC5731]. In addition, unless some registration
policy has some special processing, the EPP <extension> element
SHOULD contain a child <b-dn:infData> element that identifies the SHOULD contain a child <b-dn:infData> element that identifies the
extension namespace if the domain object has data associated with extension namespace if the domain object has data associated with
this extension and based on its registration policy. The this extension and based on its registration policy. The
<b-dn:infData> element contains the <b-dn:bundle> which has the <b-dn:infData> element contains the <b-dn:bundle> which has the
following child elements: following child elements:
o An <b-dn:rdn> element that contains the RDN, along with the o An <b-dn:rdn> element that contains the RDN, along with the
attribute described below. attribute described below.
o An OPTIONAL <b-dn:bdn> element that contains the BDN, along with o An OPTIONAL <b-dn:bdn> element that contains the BDN, along with
skipping to change at page 9, line 49 skipping to change at page 9, line 52
S: </domain:exDate> S: </domain:exDate>
S: <domain:authInfo> S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw> S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo> S: </domain:authInfo>
S: </domain:infData> S: </domain:infData>
S: </resData> S: </resData>
S: <extension> S: <extension>
S: <b-dn:infData S: <b-dn:infData
S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"> S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn">
S: <b-dn:bundle> S: <b-dn:bundle>
S: <b-dn:rdn uLabel="U+5B9E U+4F8B.example"> S: <b-dn:rdn uLabel="&#x5B9E;&#x4F8B;.example">
S: xn--fsq270a.example S: xn--fsq270a.example
S: </b-dn:rdn> S: </b-dn:rdn>
S: <b-dn:bdn uLabel="U+5BE6 U+4F8B.example"> S: <b-dn:bdn uLabel="&#x5BE6;&#x4F8B;.example">
S: xn--fsqz41a.example S: xn--fsqz41a.example
S: </b-dn:bdn> S: </b-dn:bdn>
S: </b-dn:bundle> S: </b-dn:bundle>
S: </b-dn:infData> S: </b-dn:infData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID> S: <svTRID>54322-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
skipping to change at page 10, line 37 skipping to change at page 10, line 40
7.2. EPP Transform Commands 7.2. EPP Transform Commands
EPP provides five commands to transform domain objects: <create> to EPP provides five commands to transform domain objects: <create> to
create an instance of a domain object, <delete> to delete an instance create an instance of a domain object, <delete> to delete an instance
of a domain object, <renew> to extend the validity period of a domain of a domain object, <renew> to extend the validity period of a domain
object, <transfer> to manage domain object sponsorship changes, and object, <transfer> to manage domain object sponsorship changes, and
<update> to change information associated with a domain object. <update> to change information associated with a domain object.
When theses commands have been processed successfully, the EPP When theses commands have been processed successfully, the EPP
<resData> element MUST contain child elements as described in the EPP <resData> element MUST contain child elements as described in the EPP
domain mapping [RFC5731]. This EPP <extension> element SHOULD domain mapping [RFC5731]. Unless some registration policy has some
contain the <b-dn:bundle> which has the following child elements: special processing, this EPP <extension> element SHOULD contain the
<b-dn:bundle> which has the following child elements:
o An <b-dn:rdn> element that contains the RDN, along with the o An <b-dn:rdn> element that contains the RDN, along with the
attribute described below. attribute described below.
o An OPTIONAL <b-dn:bdn> element that contains the BDN, along with o An OPTIONAL <b-dn:bdn> element that contains the BDN, along with
the attribute described below. the attribute described below.
The above elements contain the following attribute: The above elements contain the following attribute:
o An optional "uLabel" attribute represents the U-label of the o An optional "uLabel" attribute represents the U-label of the
element. element.
7.2.1. EPP <create> Command 7.2.1. EPP <create> Command
This extension defines additional elements to extend the EPP <create> This extension defines additional elements to extend the EPP <create>
command described in the EPP domain name mapping [RFC5731] for command described in the EPP domain name mapping [RFC5731] for
bundled names registration. bundled names registration.
In addition to the EPP command elements described in the EPP domain In addition to the EPP command elements described in the EPP domain
mapping [RFC5731], the <create> command SHALL contain an <extension> mapping [RFC5731], the <create> command SHALL contain an <extension>
element. The <extension> element SHOULD contain a child element. Unless some registration policy has some special
processing, the <extension> element SHOULD contain a child
<b-dn:create> element that identifies the bundle namespace, and a <b-dn:create> element that identifies the bundle namespace, and a
child <b-dn:rdn> element that identifies the U-Label form of the child <b-dn:rdn> element that identifies the U-Label form of the
registered domain name with the uLabel attribute. registered domain name with the uLabel attribute.
Example <create> command: Example <create> command:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <create> C: <create>
skipping to change at page 11, line 39 skipping to change at page 11, line 43
C: <domain:contact type="admin">123</domain:contact> C: <domain:contact type="admin">123</domain:contact>
C: <domain:contact type="tech">123</domain:contact> C: <domain:contact type="tech">123</domain:contact>
C: <domain:authInfo> C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw> C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo> C: </domain:authInfo>
C: </domain:create> C: </domain:create>
C: </create> C: </create>
C: <extension> C: <extension>
C: <b-dn:create C: <b-dn:create
C: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"> C: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn">
C: <b-dn:rdn uLabel="U+5B9E U+4F8B.example"> C: <b-dn:rdn uLabel="&#x5B9E;&#x4F8B;.example">
C: xn--fsq270a.example C: xn--fsq270a.example
C: </b-dn:rdn> C: </b-dn:rdn>
C: </b-dn:create> C: </b-dn:create>
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
When an <create> command has been processed successfully, the EPP When an <create> command has been processed successfully, the EPP
<creData> element MUST contain child elements as described in the EPP <creData> element MUST contain child elements as described in the EPP
domain mapping [RFC5731]. In addition, the EPP <extension> element domain mapping [RFC5731]. In addition, unless some registration
policy has some special processing, the EPP <extension> element
SHOULD contain a child <b-dn:creData> element that identifies the SHOULD contain a child <b-dn:creData> element that identifies the
extension namespace if the domain object has data associated with extension namespace if the domain object has data associated with
this extension and based on its registration policy. The this extension and based on its registration policy. The
<b-dn:creData> element contains the <b-dn:bundle> element. <b-dn:creData> element contains the <b-dn:bundle> element.
Example <create> response: Example <create> response:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
skipping to change at page 12, line 27 skipping to change at page 12, line 33
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>xn--fsq270a.example</domain:name> S: <domain:name>xn--fsq270a.example</domain:name>
S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate> S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
S: <domain:exDate>2001-04-03T22:00:00.0Z</domain:exDate> S: <domain:exDate>2001-04-03T22:00:00.0Z</domain:exDate>
S: </domain:creData> S: </domain:creData>
S: </resData> S: </resData>
S: <extension> S: <extension>
S: <b-dn:creData S: <b-dn:creData
S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"> S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn">
S: <b-dn:bundle> S: <b-dn:bundle>
S: <b-dn:rdn uLabel="U+5B9E U+4F8B.example"> S: <b-dn:rdn uLabel="&#x5B9E;&#x4F8B;.example">
S: xn--fsq270a.example S: xn--fsq270a.example
S: </b-dn:rdn> S: </b-dn:rdn>
S: <b-dn:bdn uLabel="U+5BE6 U+4F8B.example" > S: <b-dn:bdn uLabel="&#x5BE6;&#x4F8B;.example" >
S: xn--fsqz41a.example S: xn--fsqz41a.example
S: </b-dn:bdn> S: </b-dn:bdn>
S: </b-dn:bundle> S: </b-dn:bundle>
S: </b-dn:creData> S: </b-dn:creData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID> S: <svTRID>54322-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
skipping to change at page 13, line 7 skipping to change at page 13, line 13
be processed for any reason. be processed for any reason.
7.2.2. EPP <delete> Command 7.2.2. EPP <delete> Command
This extension does not add any element to the EPP <delete> command This extension does not add any element to the EPP <delete> command
described in the EPP domain mapping [RFC5731]. However, additional described in the EPP domain mapping [RFC5731]. However, additional
elements are defined for the <delete> response. elements are defined for the <delete> response.
When a <delete> command has been processed successfully, the EPP When a <delete> command has been processed successfully, the EPP
<delData> element MUST contain child elements as described in the EPP <delData> element MUST contain child elements as described in the EPP
domain mapping [RFC5731]. In addition, the EPP <extension> element domain mapping [RFC5731]. In addition, unless some registration
policy has some special processing, the EPP <extension> element
SHOULD contain a child <b-dn:delData> element that identifies the SHOULD contain a child <b-dn:delData> element that identifies the
extension namespace if the domain object has data associated with extension namespace if the domain object has data associated with
this extension and based on its registration policy. The this extension and based on its registration policy. The
<b-dn:delData> element SHOULD contain the <b-dn:bundle> element. <b-dn:delData> element SHOULD contain the <b-dn:bundle> element.
Example <delete> response: Example <delete> response:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <extension> S: <extension>
S: <b-dn:delData S: <b-dn:delData
S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"> S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn">
S: <b-dn:bundle> S: <b-dn:bundle>
S: <b-dn:rdn uLabel="U+5B9E U+4F8B.example"> S: <b-dn:rdn uLabel="&#x5B9E;&#x4F8B;.example">
S: xn--fsq270a.example S: xn--fsq270a.example
S: </b-dn:rdn> S: </b-dn:rdn>
S: <b-dn:bdn uLabel="U+5BE6 U+4F8B.example"> S: <b-dn:bdn uLabel="&#x5BE6;&#x4F8B;.example">
S: xn--fsqz41a.example S: xn--fsqz41a.example
S: </b-dn:bdn> S: </b-dn:bdn>
S: </b-dn:bundle> S: </b-dn:bundle>
S: </b-dn:delData> S: </b-dn:delData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
skipping to change at page 13, line 50 skipping to change at page 14, line 11
An EPP error response MUST be returned if a <delete> command cannot An EPP error response MUST be returned if a <delete> command cannot
be processed for any reason. be processed for any reason.
7.2.3. EPP <renew> Command 7.2.3. EPP <renew> Command
This extension does not add any element to the EPP <renew> command This extension does not add any element to the EPP <renew> command
described in the EPP domain name mapping [RFC5731]. However, when described in the EPP domain name mapping [RFC5731]. However, when
either RDN or BDN is sent for renew, response SHOULD contain both RDN either RDN or BDN is sent for renew, response SHOULD contain both RDN
and BDN information. When the command has been processed and BDN information. When the command has been processed
successfully, the EPP <extension> element SHOULD be contained in the successfully, the EPP <extension> element SHALL be contained in the
response if the domain object has data associated with bundled names. response if the domain object has data associated with bundled names.
Unless some registration policy has some special processing, this EPP
This EPP <extension> element SHOULD contain the <b-dn:renData> which <extension> element SHOULD contain the <b-dn:renData> which contains
contains <b-dn:bundle> element. <b-dn:bundle> element.
Example <renew> response: Example <renew> response:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <domain:renData S: <domain:renData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>xn--fsq270a.example</domain:name> S: <domain:name>xn--fsq270a.example</domain:name>
S: <domain:exDate>2012-04-03T22:00:00.0Z</domain:exDate> S: <domain:exDate>2012-04-03T22:00:00.0Z</domain:exDate>
S: </domain:renData> S: </domain:renData>
S: </resData> S: </resData>
S: <extension> S: <extension>
S: <b-dn:renData S: <b-dn:renData
S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"> S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn">
S: <b-dn:bundle> S: <b-dn:bundle>
S: <b-dn:rdn uLabel="U+5B9E U+4F8B.example"> S: <b-dn:rdn uLabel="&#x5B9E;&#x4F8B;.example">
S: xn--fsq270a.example S: xn--fsq270a.example
S: </b-dn:rdn> S: </b-dn:rdn>
S: <b-dn:bdn uLabel="U+5BE6 U+4F8B.example" > S: <b-dn:bdn uLabel="&#x5BE6;&#x4F8B;.example" >
S: xn--fsqz41a.example S: xn--fsqz41a.example
S: </b-dn:bdn> S: </b-dn:bdn>
S: </b-dn:bundle> S: </b-dn:bundle>
S: </b-dn:renData> S: </b-dn:renData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID> S: <svTRID>54322-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
7.2.4. EPP <transfer> Command 7.2.4. EPP <transfer> Command
This extension does not add any element to the EPP <transfer> command This extension does not add any element to the EPP <transfer> command
described in the EPP domain name mapping [RFC5731]. However, described in the EPP domain name mapping [RFC5731]. However,
additional elements are defined for the <transfer> response in the additional elements are defined for the <transfer> response in the
EPP object mapping. When the command has been processed EPP object mapping. When the command has been processed
successfully, the EPP <extension> element SHOULD be contained in the successfully, the EPP <extension> element SHALL be contained in the
response if the domain object has data associated with bundled names. response if the domain object has data associated with bundled names.
This EPP <extension> element SHOULD contain the <b-dn:trnData> which Unless some registration policy has some special processing, this EPP
contains <b-dn:bundle> element. <extension> element SHOULD contain the <b-dn:trnData> which contains
<b-dn:bundle> element.
Example <transfer> response: Example <transfer> response:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1001"> S: <result code="1001">
S: <msg>Command completed successfully; action pending</msg> S: <msg>Command completed successfully; action pending</msg>
S: </result> S: </result>
S: <resData> S: <resData>
skipping to change at page 15, line 29 skipping to change at page 16, line 29
S: <domain:reDate>2011-04-03T22:00:00.0Z</domain:reDate> S: <domain:reDate>2011-04-03T22:00:00.0Z</domain:reDate>
S: <domain:acID>ClientY</domain:acID> S: <domain:acID>ClientY</domain:acID>
S: <domain:acDate>2011-04-08T22:00:00.0Z</domain:acDate> S: <domain:acDate>2011-04-08T22:00:00.0Z</domain:acDate>
S: <domain:exDate>2012-04-03T22:00:00.0Z</domain:exDate> S: <domain:exDate>2012-04-03T22:00:00.0Z</domain:exDate>
S: </domain:trnData> S: </domain:trnData>
S: </resData> S: </resData>
S: <extension> S: <extension>
S: <b-dn:trnData S: <b-dn:trnData
S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"> S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn">
S: <b-dn:bundle> S: <b-dn:bundle>
S: <b-dn:rdn uLabel="U+5B9E U+4F8B.example"> S: <b-dn:rdn uLabel="&#x5B9E;&#x4F8B;.example">
S: xn--fsq270a.example S: xn--fsq270a.example
S: </b-dn:rdn> S: </b-dn:rdn>
S: <b-dn:bdn uLabel="U+5BE6 U+4F8B.example"> S: <b-dn:bdn uLabel="&#x5BE6;&#x4F8B;.example">
S: xn--fsqz41a.example S: xn--fsqz41a.example
S: </b-dn:bdn> S: </b-dn:bdn>
S: </b-dn:bundle> S: </b-dn:bundle>
S: </b-dn:trnData> S: </b-dn:trnData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID> S: <svTRID>54322-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
7.2.5. EPP <update> Command 7.2.5. EPP <update> Command
This extension does not add any element to the EPP <update> command This extension does not add any element to the EPP <update> command
described in the EPP domain name mapping [RFC5731]. However, described in the EPP domain name mapping [RFC5731]. However,
additional elements are defined for the <update> response in the EPP additional elements are defined for the <update> response in the EPP
object mapping. When the command has been processed successfully, object mapping. When the command has been processed successfully,
the EPP <extension> element SHOULD be contained in the response if the EPP <extension> element SHALL be contained in the response if the
the domain object has data associated with bundled names. This EPP domain object has data associated with bundled names. Unless some
<extension> element SHOULD contain the <b-dn:upData> which contains registration policy has some special processing, this EPP <extension>
<b-dn:bundle> element. element SHOULD contain the <b-dn:upData> which contains <b-dn:bundle>
element.
Example <update> response: Example <update> response:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <extension> S: <extension>
S: <b-dn:upData S: <b-dn:upData
S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"> S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn">
S: <b-dn:bundle> S: <b-dn:bundle>
S: <b-dn:rdn uLabel="U+5B9E U+4F8B.example" > S: <b-dn:rdn uLabel="&#x5B9E;&#x4F8B;.example" >
S: xn--fsq270a.example S: xn--fsq270a.example
S: </b-dn:rdn> S: </b-dn:rdn>
S: <b-dn:bdn uLabel="U+5BE6 U+4F8B.example"> S: <b-dn:bdn uLabel="&#x5BE6;&#x4F8B;.example">
S: xn--fsqz41a.example S: xn--fsqz41a.example
S: </b-dn:bdn> S: </b-dn:bdn>
S: </b-dn:bundle> S: </b-dn:bundle>
S: </b-dn:upData> S: </b-dn:upData>
S: </extension> S: </extension>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID> S: <svTRID>54322-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
skipping to change at page 19, line 44 skipping to change at page 20, line 46
o Status: Active o Status: Active
o Notes: None 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 any significant security issues. One principle that have not found any 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, transferred, updated, bundled registered domain names will be created, transferred,
and deleted together as a group. The registrants for bundled domain updated, and deleted together as a group. The registrants for
names should remember this principle when doing some operations to bundled domain names should remember this principle when doing some
these domain names. [RFC5730] also introduces some security operations to these domain names. [RFC5730] also introduces some
consideration. security consideration.
This document does not take a position regarding whether or not the This document does not take a position regarding whether or not the
bundled domain names share a DS/DNSKEY key. The DNS administrator bundled domain names share a DS/DNSKEY key. The DNS administrator
can choose whether DS/DNSKEY information can be shared or not. If a 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 DS/DNSKEY key is shared then the bundled domain names share fate if
there is a key compromise. 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.
skipping to change at page 22, line 5 skipping to change at page 23, line 5
o Refine some texts. o Refine some texts.
14.10. draft-ietf-regext-bundle-registration: Version 09 14.10. draft-ietf-regext-bundle-registration: Version 09
o Refine the texts. o Refine the texts.
14.11. draft-ietf-regext-bundle-registration: Version 10 14.11. draft-ietf-regext-bundle-registration: Version 10
o Update the texts based on IETF LC. o Update the texts based on IETF LC.
14.12. draft-ietf-regext-bundle-registration: Version 11
o Update the texts based on AD's comment.
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,
 End of changes. 38 change blocks. 
77 lines changed or deleted 93 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/