draft-ietf-regext-bundling-registration-09.txt   draft-ietf-regext-bundling-registration-10.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
Expires: August 2, 2019 L. Zhou Expires: March 23, 2020 L. Zhou
CNNIC CNNIC
W. Tan W. Tan
Cloud Registry Cloud Registry
J. Xie J. Xie
January 29, 2019 September 20, 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-09 draft-ietf-regext-bundling-registration-10
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 August 2, 2019. This Internet-Draft will expire on March 23, 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
skipping to change at page 2, line 35 skipping to change at page 2, line 35
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 . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . 18
11. Security Considerations . . . . . . . . . . . . . . . . . . . 20 11. Security Considerations . . . . . . . . . . . . . . . . . . . 19
12. Implementation Status . . . . . . . . . . . . . . . . . . . . 20 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 20
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20
14. Change History . . . . . . . . . . . . . . . . . . . . . . . 21 14. Change History . . . . . . . . . . . . . . . . . . . . . . . 20
14.1. draft-kong-epp-bundle-mapping: Version 00 . . . . . . . 21 14.1. draft-ietf-regext-bundle-registration: Version 00 . . . 20
14.2. draft-kong-epp-bundle-mapping: Version 01 . . . . . . . 21 14.2. draft-ietf-regext-bundle-registration: Version 01 . . . 20
14.3. draft-kong-epp-bundle-mapping: Version 02 . . . . . . . 21 14.3. draft-ietf-regext-bundle-registration: Version 02 . . . 21
14.4. draft-ietf-regext-bundle-mapping: Version 00 . . . . . . 21 14.4. draft-ietf-regext-bundle-registration: Version 03 . . . 21
14.5. draft-ietf-regext-bundle-mapping: Version 01 . . . . . . 21 14.5. draft-ietf-regext-bundle-registration: Version 04 . . . 21
14.6. draft-ietf-regext-bundle-mapping: Version 02 . . . . . . 21 14.6. draft-ietf-regext-bundle-registration: Version 05 . . . 21
14.7. draft-ietf-regext-bundle-mapping: Version 03 . . . . . . 21 14.7. draft-ietf-regext-bundle-registration: Version 06 . . . 21
14.8. draft-ietf-regext-bundle-mapping: Version 04 . . . . . . 21 14.8. draft-ietf-regext-bundle-registration: Version 07 . . . 21
14.9. draft-ietf-regext-bundle-mapping: Version 05 . . . . . . 22 14.9. draft-ietf-regext-bundle-registration: Version 08 . . . 21
14.10. draft-ietf-regext-bundle-mapping: Version 06 . . . . . . 22 14.10. draft-ietf-regext-bundle-registration: Version 09 . . . 21
14.11. draft-ietf-regext-bundle-mapping: Version 07 . . . . . . 22 14.11. draft-ietf-regext-bundle-registration: Version 10 . . . 21
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
15.1. Normative References . . . . . . . . . . . . . . . . . . 22 15.1. Normative References . . . . . . . . . . . . . . . . . . 22
15.2. Informative References . . . . . . . . . . . . . . . . . 23 15.2. Informative References . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
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 have identical
level labels for which certain parameters are shared in different second level labels for which certain parameters are shared in
TLDs. For example, Public Interest Registry, request to implement different TLDs. For an example, Public Interest Registry has
technical bundling of second level domains for .NGO and .ONG. So we requested to implement bundling of second level domains for .NGO and
have two kinds of bundled domain names. First one is in the form of .ONG. So we have two kinds of bundled domain names. The first one
"V-label.TLD" in which the second level labels (V-label) are variants is in the form of "V-label.TLD" in which the second level label
sharing the same TLD; Second one is in the form of "LABEL.V-tld" in (V-label) is a variant sharing the same TLD; Second one is in the
which the second level labels(LABEL) are same ending with the form of "LABEL.V-tld" in which the second level label(LABEL) remains
different TLDs (V-tld); the same but ending with a different TLD (V-tld).
Bundled domain names normally share some attributes. There are three Bundled domain names normally share some attributes. Policy-wise
types of bundling. First one is strict bundling, which requires all bundling can be implemented in three ways. The first one is strict
bundled names to share many same attributes. When creating, bundling, which requires all bundled names to share many same
updating, or transferring of any of the bundled domain names, all attributes. When creating, updating, or transferring of any of the
bundled domain names will be created, updated or transferred. Second bundled domain names, all bundled domain names will be created,
one is partial bundling, which requires that at least the bundled updated or transferred atomically. The second one is partial
domain names if registered should be registered by the same bundling, which requires the bundled domain names to be registered by
registrant. Third one is relax bundling, which has not specific the same registrant. The third one is relaxed bundling, which has no
requirements to the domain registration. This document mainly focus specific requirements on the domain registration. This document
on strict bundling names registration. mainly addresses the 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, most registries offering Chinese
of Chinese Domain Name (CDN) is that a registrant can apply an Domain Name (CDN) adopt a registration policy whereby a registrant
original CDN in any forms: Simplified Chinese (SC) form, Traditional can apply for an original CDN in any forms: Simplified Chinese (SC)
Chinese (TC) form, or other variant forms, then the corresponding form, Traditional Chinese (TC) form, or other variant forms, then the
variant CDN in SC form and that in TC form will also be delegated to corresponding variant CDN in SC form and that in TC form will also be
the same registrant. All variant names in the same TLD contain same delegated to the same registrant. All variant names in the same TLD
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 domain name registration one by one. It does [RFC5731] provides the facility for single domain name registration.
not specify how to register the strict bundled names which share many It does not specify how to register the strict bundled names which
same attributes. share many of the attributes.
In order to meet above requirements of the strict bundled names 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 the Extensible Markup Language names. This document is specified using 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 mapping described in this document.
This document uses lots of the concepts of the IDN, so a thorough This document uses many IDN concepts, so a thorough understanding of
understanding of the IDNs for Application (IDNA, described in the IDNs for Application (IDNA, described in [RFC5890], [RFC5891],
[RFC5890], [RFC5891], and [RFC5892]) and a thorough understanding of and [RFC5892]) and the variant approach discussed in [RFC4290] is
variant approach discussed in [RFC4290] are both required. assumed.
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", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119][RFC8174] when, and only when, they appear in all
capitals, as shown here.
uLabel in this document is used to express U-label of the uLabel in this document is used to express the U-label of an
internationalized domain name into series of characters where non- internationalized domain name as a series of characters where non-
ASCII characters will be represented with the format of U+XXXX where ASCII characters will be represented in the format of U+XXXX where
XXXX is a UNICODE point. U-Label is defined in [RFC5890]. XXXX is a UNICODE point. U-Label is defined in [RFC5890].
"b-dn-1.0" in this document is used as an abbreviation for The XML namespace prefix "b-dn" is used for the namespace
urn:ietf:params:xml:ns:epp:b-dn-1.0. "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
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.
XML is case sensitive. Unless stated otherwise, XML specifications XML is case sensitive. Unless stated otherwise, XML specifications
and examples provided in this document MUST be interpreted in the and examples provided in this document MUST be interpreted in the
character case presented to develop a conforming implementation. character case presented to develop a conforming implementation.
3. Definitions 3. Definitions
The following definitions are used in this document: The following definitions are used in this document:
o Registered Domain Name (RDN), represents the valid domain name o Registered Domain Name (RDN), represents the valid domain name
that users submitted for registration by the first time. that users submitted for the initial registration.
o Bundled Domain Name (BDN), represents the bundled domain name o Bundled Domain Name (BDN), represents the bundled domain name
produced according to the bundled domain name registration policy. produced according to the bundled domain name registration policy.
4. Overview 4. Overview
Domain registries have traditionally adopted a registration model Domain registries have traditionally adopted a registration model
whereby metadata relating to a domain name, such as its expiration whereby metadata relating to a domain name, such as its expiration
date and sponsoring registrar, are stored as properties of the domain date and sponsoring registrar, are stored as properties of the domain
object. The domain object is then considered an atomic unit of object. The domain object is then considered an atomic unit of
registration, on which operations such as update, renewal and registration, on which operations such as update, renewal and
deletion may be performed. deletion may be performed.
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. places them in the registration package together with the RDN.
The bundled names share many same properties, such as expiration date The bundled names share many properties, such as expiration date and
and sponsoring registrar, by sharing one domain object. So when sponsoring registrar, by sharing the same 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 associated with domain names. Typically, bundled names will share
the following parameters or attributes: the following parameters or attributes:
o Registrar Ownership o Registrar Ownership
o Registration and Expiry Dates o Registration and Expiry Dates
o Registrant, Admin, Billing, and Technical Contacts o Registrant, Admin, Billing, and Technical Contacts
o Name Server Association o Name Server Association
o Domain Status o Domain Status
o Applicable grace periods (Add Grace Period, Renewal Grace Period, o Applicable grace periods (Add Grace Period, Renewal Grace Period,
Auto-Renewal Grace Period, Transfer Grace Period, and Redemption Auto-Renewal Grace Period, Transfer Grace Period, and Redemption
Grace Period) Grace Period)
skipping to change at page 5, line 50 skipping to change at page 6, line 4
o Domain Status o Domain Status
o Applicable grace periods (Add Grace Period, Renewal Grace Period, o Applicable grace periods (Add Grace Period, Renewal Grace Period,
Auto-Renewal Grace Period, Transfer Grace Period, and Redemption Auto-Renewal Grace Period, Transfer Grace Period, and Redemption
Grace Period) Grace Period)
Because the domain names are bundled and share the same parameters or Because the domain names are bundled and share the same parameters or
attributes, the EPP command should do some processing for these attributes, the EPP command should do some processing for these
requirements: requirements:
o When performing a domain check, either BDN or RDN can be queried o When performing a domain check, either BDN or RDN can be queried
for the EPP command, and will return the same response. for the EPP command, and will return the same response.
o When performing a domain info, either BDN or RDN can be queried, o When performing a domain info, either BDN or RDN can be queried,
the same response will include both BDN and RDN information with the the same response will include both BDN and RDN information with the
same attributes. same attributes.
o When performing a domain Create, either of the bundle names will be
o When performing a domain Create, either BDN or RDN will be
accepted. If the domain name is available, both BDN and RDN will be accepted. If the domain name is available, both BDN and RDN will be
registered. registered.
o When performing a domain Delete, either BDN or RDN will be o When performing a domain Delete, either BDN or RDN will be
accepted. If the domain name is available, both BDN and RDN will be accepted. If the domain name is registered, both BDN and RDN will be
deleted. deleted.
o When performing a domain renew, either BDN or RDN will be accepted. o When performing a domain renew, either BDN or RDN will be accepted.
Upon a successful domain renewal,both BDN and RDN will have their Upon a successful domain renewal, both BDN and RDN will have their
expiry date extended by the requested term. Upon a successful domain expiry date extended by the requested term. Upon a successful domain
renewal, both BDN and RDN will conform to the same renew grace renewal, both BDN and RDN will conform to the same renew grace
period. period.
o When performing a domain transfer, either BDN or RDN will be o When performing a domain transfer, either BDN or RDN will be
accepted. Upon successful completion of a domain transfer request, accepted. Upon successful completion of a domain transfer request,
both BDN and RDN will enter a pendingTransfer status. Upon approval both BDN and RDN will enter a pendingTransfer status. Upon approval
of the transfer request, both BDN and RDN will be owned and managed of the transfer request, both BDN and RDN will be owned and managed
by the same new registrant. by the same new registrant.
o When performing a domain update, either BDN or RDN will be o When performing a domain update, either BDN or RDN will be
accepted. Any modifications to contact associations, name server accepted. Any modifications to contact associations, name server
associations, domain status values and authorization information will associations, domain status values and authorization information will
be applied to both BDN and RDN. be applied to both BDN and RDN.
6. Object Attributes 6. Object Attributes
This extension defines following additional elements to the EPP This extension defines following additional elements to the EPP
domain name mapping [RFC5731]. All of these additional elements can domain name mapping [RFC5731]. All of these additional elements are
be got 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. An optional boolean represent the U-label [RFC5890] form.
"activated" attribute, with a default true value, is used to indicate
the presence of the label in the zone file.
For example: <b-dn:rdn uLabel="U+5B9E""U+4F8B".example> xn-- For example: <b-dn:rdn uLabel="U+5B9E U+4F8B.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="U+5BE6 U+4F8B.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 5 skipping to change at page 8, line 5
7.1.1. EPP <check> Command 7.1.1. EPP <check> Command
This extension does not add any element to the EPP <check> command or This extension does not add any element to the EPP <check> command or
<check> response described in the EPP domain name mapping [RFC5731]. <check> response described in the EPP domain name mapping [RFC5731].
However, when either RDN or BDN is sent for check, response SHOULD However, when either RDN or BDN is sent for check, response SHOULD
contain both RDN and BDN information, which may also give some contain both RDN and BDN information, which may also give some
explanation in the reason field to tell the user that the associated explanation in the reason field to tell the user that the associated
domain name is a produced name according to some bundle domain name domain name is a produced name according to some bundle domain name
policy. policy.
Example <check> Response for an authorized client: Example <check> 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:chkData S: <domain:chkData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:cd> S: <domain:cd>
S: <domain:name avail="1"> S: <domain:name avail="1">
xn--fsq270a.example</domain:name> S: xn--fsq270a.example</domain:name>
S: </domain:cd> S: </domain:cd>
S: <domain:cd> S: <domain:cd>
S: <domain:name avail="1"> S: <domain:name avail="1">
xn--fsqz41a.example</domain:name> S: xn--fsqz41a.example
S: <domain:reason>This associated domain name is S: </domain:name>
a produced name S: <domain:reason>This associated domain name is
based on bundle name policy.</domain:reason> S: a produced name based on bundle name policy.
S: </domain:cd> S: </domain:reason>
S: </domain:chkData> S: </domain:cd>
S: </resData> S: </domain:chkData>
S: <trID> S: </resData>
S: <clTRID>ABC-12345</clTRID> S: <trID>
S: <svTRID>54322-XYZ</svTRID> S: <clTRID>ABC-12345</clTRID>
S: </trID> S: <svTRID>54322-XYZ</svTRID>
S: </response> S: </trID>
S: </response>
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, 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 service policy. The <b-dn:infData> this extension and based on its registration policy. The
element contains the <b-dn:bundle> which has the following child <b-dn:infData> element contains the <b-dn:bundle> which has the
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
attributes 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 attributes described below. the attribute described below.
The above elements contain the following attributes: 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.
Example <info> Response for an authorized client: Example <info> response for an authorized client:
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:infData S: <domain:infData
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:roid>58812678-domain</domain:roid> S: <domain:roid>58812678-domain</domain:roid>
S: <domain:status s="ok"/> S: <domain:status s="ok"/>
S: <domain:registrant>123</domain:registrant> S: <domain:registrant>123</domain:registrant>
S: <domain:contact type="admin">123</domain:contact> S: <domain:contact type="admin">123</domain:contact>
S: <domain:contact type="tech">123</domain:contact> S: <domain:contact type="tech">123</domain:contact>
S: <domain:ns> S: <domain:ns>
S: <domain:hostObj>ns1.example.cn S: <domain:hostObj>ns1.example.cn
</domain:hostObj> S: </domain:hostObj>
S: </domain:ns> S: </domain:ns>
S: <domain:clID>ClientX</domain:clID> S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientY</domain:crID> S: <domain:crID>ClientY</domain:crID>
S: <domain:crDate>2011-04-03T22:00:00.0Z S: <domain:crDate>2011-04-03T22:00:00.0Z
</domain:crDate> S: </domain:crDate>
S: <domain:exDate>2012-04-03T22:00:00.0Z S: <domain:exDate>2012-04-03T22:00:00.0Z
</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-1.0"> 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="U+5B9E U+4F8B.example">
S: >xn--fsq270a.example</b-dn:rdn> S: xn--fsq270a.example
S: <b-dn:bdn uLabel="U+5BE6""U+4F8B".example S: </b-dn:rdn>
S: >xn--fsqz41a.example</b-dn:bdn> S: <b-dn:bdn uLabel="U+5BE6 U+4F8B.example">
S: </b-dn:bundle> S: xn--fsqz41a.example
S: </b-dn:infData> S: </b-dn:bdn>
S: </extension> S: </b-dn:bundle>
S: <trID> S: </b-dn:infData>
S: <clTRID>ABC-12345</clTRID> S: </extension>
S: <svTRID>54322-XYZ</svTRID> S: <trID>
S: </trID> S: <clTRID>ABC-12345</clTRID>
S: </response> S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp> S:</epp>
<info> Response for the unauthorized client has not been changed,see <info> Response for the unauthorized client has not been changed,see
[RFC5731] for detail. [RFC5731] for detail.
An EPP error response MUST be returned if an <info> command cannot be An EPP error response MUST be returned if an <info> command cannot be
processed for any reason. processed for any reason.
7.1.3. EPP <transfer> Query Command 7.1.3. EPP <transfer> Query 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
or <transfer> reponse described in the EPP domain mapping [RFC5731]. or <transfer> response described in the EPP domain mapping [RFC5731].
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]. This EPP <extension> element SHOULD
contain the <b-dn:bundle> which has the following child elements: 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
attributes 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 attributes 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. The <extension> element SHOULD contain a child
<b-dn:create> element that identifies the bundle namespace and the <b-dn:create> element that identifies the bundle namespace, and a
location of the bundle name schema. child <b-dn:rdn> element that identifies the U-Label form of the
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>
C: <domain:create C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>xn--fsq270a.example</domain:name> C: <domain:name>xn--fsq270a.example</domain:name>
C: <domain:period unit="y">2</domain:period> C: <domain:period unit="y">2</domain:period>
C: <domain:registrant>123</domain:registrant> C: <domain:registrant>123</domain:registrant>
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-1.0"> 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="U+5B9E U+4F8B.example">
C: xn--fsq270a.example</b-dn:rdn> C: xn--fsq270a.example
C: </b-dn:create> C: </b-dn:rdn>
C: </extension> C: </b-dn:create>
C: <clTRID>ABC-12345</clTRID> C: </extension>
C: </command> C: <clTRID>ABC-12345</clTRID>
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, 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 service policy. The <b-dn:creData> this extension and based on its registration policy. The
element contains the <b-dn:bundle> element. <b-dn:creData> element contains the <b-dn:bundle> element.
Example <create> Response for an authorized client:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> Example <create> response:
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg>Command completed successfully</msg>
S: </result>
S: <resData>
S: <domain:creData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>xn--fsq270a.example</domain:name>
S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
S: <domain:exDate>2001-04-03T22:00:00.0Z</domain:exDate>
S: </domain:creData>
S: </resData>
S: <extension>
S: <b-dn:creData
S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn-1.0">
S: <b-dn:bundle>
S: <b-dn:rdn uLabel="U+5B9E""U+4F8B".example
S: >xn--fsq270a.example</b-dn:rdn>
S: <b-dn:bdn uLabel="U+5BE6""U+4F8B".example
S: >xn--fsqz41a.example</b-dn:bdn>
S: </b-dn:bundle>
S: </b-dn:creData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
<create> Response for the unauthorized client has not been S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
changed,see [RFC5731] for detail. S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg>Command completed successfully</msg>
S: </result>
S: <resData>
S: <domain:creData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>xn--fsq270a.example</domain:name>
S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
S: <domain:exDate>2001-04-03T22:00:00.0Z</domain:exDate>
S: </domain:creData>
S: </resData>
S: <extension>
S: <b-dn:creData
S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn">
S: <b-dn:bundle>
S: <b-dn:rdn uLabel="U+5B9E U+4F8B.example">
S: xn--fsq270a.example
S: </b-dn:rdn>
S: <b-dn:bdn uLabel="U+5BE6 U+4F8B.example" >
S: xn--fsqz41a.example
S: </b-dn:bdn>
S: </b-dn:bundle>
S: </b-dn:creData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
An EPP error response MUST be returned if an <create> command cannot An EPP error response MUST be returned if an <create> command cannot
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, 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 service policy. The <b-dn:delData> this extension and based on its registration policy. The
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-1.0"> 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="U+5B9E U+4F8B.example">
xn--fsq270a.example</b-dn:rdn> S: xn--fsq270a.example
S: <b-dn:bdn uLabel="U+5BE6""U+4F8B".example> S: </b-dn:rdn>
xn--fsqz41a.example</b-dn:bdn> S: <b-dn:bdn uLabel="U+5BE6 U+4F8B.example">
S: </b-dn:bundle> S: xn--fsqz41a.example
S: </b-dn:delData> S: </b-dn:bdn>
S: </extension> S: </b-dn:bundle>
S: <trID> S: </b-dn:delData>
S: <clTRID>ABC-12345</clTRID> S: </extension>
S: <svTRID>54321-XYZ</svTRID> S: <trID>
S: </trID> S: <clTRID>ABC-12345</clTRID>
S: </response> S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp> S:</epp>
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 SHOULD be contained in the
resoponse if the domain object has data associated with bundled response if the domain object has data associated with bundled names.
names. This EPP <extension> element SHOULD contain the
<b-dn:renData> which contains <b-dn:bundle> element.
Example <renew> Response for an authorized client: This EPP <extension> element SHOULD contain the <b-dn:renData> which
contains <b-dn:bundle> element.
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> Example <renew> response:
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S: <result code="1000"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <msg>Command completed successfully</msg> S: <response>
S: </result> S: <result code="1000">
S: <resData> S: <msg>Command completed successfully</msg>
S: <domain:renData S: </result>
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: <resData>
S: <domain:name>xn--fsq270a.example</domain:name> S: <domain:renData
S: <domain:exDate>2012-04-03T22:00:00.0Z</domain:exDate> S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: </domain:renData> S: <domain:name>xn--fsq270a.example</domain:name>
S: </resData> S: <domain:exDate>2012-04-03T22:00:00.0Z</domain:exDate>
S: <extension> S: </domain:renData>
S: <b-dn:renData S: </resData>
S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn-1.0"> S: <extension>
S: <b-dn:bundle> S: <b-dn:renData
S: <b-dn:rdn uLabel="U+5B9E""U+4F8B".example S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn">
S: >xn--fsq270a.example</b-dn:rdn> S: <b-dn:bundle>
S: <b-dn:bdn uLabel="U+5BE6""U+4F8B".example S: <b-dn:rdn uLabel="U+5B9E U+4F8B.example">
S: >xn--fsqz41a.example</b-dn:bdn> S: xn--fsq270a.example
S: </b-dn:bundle> S: </b-dn:rdn>
S: </b-dn:renData> S: <b-dn:bdn uLabel="U+5BE6 U+4F8B.example" >
S: </extension> S: xn--fsqz41a.example
S: <trID> S: </b-dn:bdn>
S: <clTRID>ABC-12345</clTRID> S: </b-dn:bundle>
S: <svTRID>54322-XYZ</svTRID> S: </b-dn:renData>
S: </trID> S: </extension>
S: </response> S: <trID>
S:</epp> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
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 SHOULD be contained in the
resoponse if the domain object has data associated with bundled response if the domain object has data associated with bundled names.
names. This EPP <extension> element SHOULD contain the This EPP <extension> element SHOULD contain the <b-dn:trnData> which
<b-dn:trnData> which contains <b-dn:bundle> element. contains <b-dn:bundle> element.
Example <transfer> Response for an authorized client: 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>
S: <domain:trnData S: <domain:trnData
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:trStatus>pending</domain:trStatus> S: <domain:trStatus>pending</domain:trStatus>
S: <domain:reID>ClientX</domain:reID> S: <domain:reID>ClientX</domain:reID>
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-1.0"> 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="U+5B9E U+4F8B.example">
S: >xn--fsq270a.example</b-dn:rdn> S: xn--fsq270a.example
S: <b-dn:bdn uLabel="U+5BE6""U+4F8B".example S: </b-dn:rdn>
S: >xn--fsqz41a.example</b-dn:bdn> S: <b-dn:bdn uLabel="U+5BE6 U+4F8B.example">
S: </b-dn:bundle> S: xn--fsqz41a.example
S: </b-dn:trnData> S: </b-dn:bdn>
S: </extension> S: </b-dn:bundle>
S: <trID> S: </b-dn:trnData>
S: <clTRID>ABC-12345</clTRID> S: </extension>
S: <svTRID>54322-XYZ</svTRID> S: <trID>
S: </trID> S: <clTRID>ABC-12345</clTRID>
S: </response> S: <svTRID>54322-XYZ</svTRID>
S:</epp> S: </trID>
S: </response>
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 resoponse if the EPP <extension> element SHOULD be contained in the response if
the domain object has data associated with bundled names. This EPP the domain object has data associated with bundled names. This EPP
<extension> element SHOULD contain the <b-dn:upData> which contains <extension> element SHOULD contain the <b-dn:upData> which contains
<b-dn:bundle> element. <b-dn:bundle> element.
Example <update> Response for an authorized client: 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-1.0"> 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="U+5B9E U+4F8B.example" >
S: >xn--fsq270a.example</b-dn:rdn> S: xn--fsq270a.example
S: <b-dn:bdn uLabel="U+5BE6""U+4F8B".example S: </b-dn:rdn>
S: >xn--fsqz41a.example</b-dn:bdn> S: <b-dn:bdn uLabel="U+5BE6 U+4F8B.example">
S: </b-dn:bundle> S: xn--fsqz41a.example
S: </b-dn:upData> S: </b-dn:bdn>
S: </extension> S: </b-dn:bundle>
S: <trID> S: </b-dn:upData>
S: <clTRID>ABC-12345</clTRID> S: </extension>
S: <svTRID>54322-XYZ</svTRID> S: <trID>
S: </trID> S: <clTRID>ABC-12345</clTRID>
S: </response> S: <svTRID>54322-XYZ</svTRID>
S:</epp> S: </trID>
S: </response>
S:</epp>
8. Formal Syntax 8. Formal Syntax
An EPP object name mapping extension for bundled names is specified An EPP object name mapping extension for bundled names is specified
in XML Schema notation. The formal syntax presented here is a in XML Schema notation. The formal syntax presented here is a
complete schema representation of the object mapping suitable for complete schema representation of the object mapping suitable for
automated validation of EPP XML instances. The BEGIN and END tags automated validation of EPP XML instances. The BEGIN and END tags
are not part of the schema; they are used to note the beginning and are not part of the schema; they are used to note the beginning and
ending of the schema for URI registration purposes. ending of the schema for URI registration purposes.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:epp:b-dn-1.0"
xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!-- <schema targetNamespace="urn:ietf:params:xml:ns:epp:b-dn"
Import common element types. xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"
--> xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
<import namespace="urn:iana:xml:ns:eppcom-1.0" xmlns="http://www.w3.org/2001/XMLSchema"
schemaLocation="eppcom-1.0.xsd"/> elementFormDefault="qualified">
<import namespace="urn:iana:xml:ns:epp-1.0"
schemaLocation="epp-1.0.xsd"/>
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
Bundle Domain Extension Schema v1.0
</documentation>
</annotation>
<!-- <!--
Child elements found in EPP commands. Import common element types.
--> -->
<element name="create" type="b-dn:createDataType"/> <import namespace="urn:iana:xml:ns:eppcom-1.0"
schemaLocation="eppcom-1.0.xsd"/>
<!-- <annotation>
Child elements of the <b-dn:create> command <documentation>
All elements must be present at time of creation Extensible Provisioning Protocol v1.0
--> Bundle Domain Extension Schema v1.0
<complexType name="createDataType"> </documentation>
<sequence> </annotation>
<element name="rdn" type="b-dn:rdnType"
minOccurs="0" maxOccurs="unbounded" />
</sequence>
</complexType>
<!-- <!--
Child elements of the <b-dn:update> command Child elements found in EPP commands.
All elements must be present at time of creation -->
--> <element name="create" type="b-dn:createDataType"/>
<!-- <!--
Child elements found in EPP commands. Child elements of the <b-dn:create> command.
--> All elements must be present at time of creation
<element name="infData" type="b-dn:trnDataType"/> -->
<element name="delData" type="b-dn:trnDataType"/> <complexType name="createDataType">
<element name="creData" type="b-dn:trnDataType"/> <sequence>
<element name="renData" type="b-dn:trnDataType"/> <element name="rdn" type="b-dn:rdnType"
<element name="trnData" type="b-dn:trnDataType"/> minOccurs="0"/>
<element name="upData" type="b-dn:trnDataType"/> </sequence>
</complexType>
<complexType name="trnDataType"> <!--
<sequence> Child response elements in <b-dn:infData>, <b-dn:delData>,
<element name="bundle" type="b-dn:bundleType" /> <b-dn:creData>, <b-dn:renData>, <b-dn:trnData> and <b-dn:upData>.
</sequence> -->
</complexType> <element name="infData" type="b-dn:bundleDataType"/>
<!-- <element name="delData" type="b-dn:bundleDataType"/>
<transfer> response elements. <element name="creData" type="b-dn:bundleDataType"/>
All elements must be present at time of poll query <element name="renData" type="b-dn:bundleDataType"/>
--> <element name="trnData" type="b-dn:bundleDataType"/>
<complexType name="bundleType"> <element name="upData" type="b-dn:bundleDataType"/>
<sequence>
<element name="rdn" type="b-dn:rdnType" />
<element name="bdn" type="b-dn:rdnType"
minOccurs="0" maxOccurs="unbounded" />
</sequence> <complexType name="bundleDataType">
</complexType> <sequence>
<element name="bundle" type="b-dn:bundleType" />
</sequence>
</complexType>
<complexType name="rdnType"> <complexType name="bundleType">
<simpleContent> <sequence>
<extension base="eppcom:labelType"> <element name="rdn" type="b-dn:rdnType" />
<attribute name="uLabel" type="eppcom:labelType"/> <element name="bdn" type="b-dn:rdnType"
minOccurs="0" maxOccurs="unbounded" />
</sequence>
</complexType>
</extension> <complexType name="rdnType">
</simpleContent> <simpleContent>
</complexType> <extension base="eppcom:labelType">
<attribute name="uLabel" type="eppcom:labelType"/>
</extension>
</simpleContent>
</complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9. Internationalization Considerations 9. Internationalization Considerations
EPP is represented in XML, which provides native support for encoding EPP is represented in XML, which provides native support for encoding
information using the Unicode character set and its more compact information using the Unicode character set and its more compact
representations including UTF-8. Conformant XML processors recognize representations including UTF-8. Conformant XML processors recognize
both UTF-8 and UTF-16. Though XML includes provisions to identify both UTF-8 and UTF-16. Though XML includes provisions to identify
and use other character encodings through use of an "encoding" and use other character encodings through use of an "encoding"
skipping to change at page 19, line 13 skipping to change at page 18, line 48
includes this extension. includes this extension.
10. IANA Considerations 10. IANA Considerations
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. IANA is conforming to a registry mechanism described in [RFC3688]. IANA is
requested to assignment the following two URIs. requested to assignment the following two URIs.
Registration request for the IDN namespace: Registration request for the IDN namespace:
o URI: urn:ietf:params:xml:ns:epp:b-dn-1.0 o URI: urn:ietf:params:xml:ns:epp:b-dn
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: None. Namespace URI does not represent an XML specification. o XML: None. Namespace URI does not represent an XML specification.
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
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 The EPP extension described in this document should be registered by
IANA in the "Extensions for the Extensible Provisioning Protocol IANA in the "Extensions for the Extensible Provisioning Protocol
(EPP)" registry described in [RFC7451]. The details of the (EPP)" registry described in [RFC7451]. The details of the
registration are as follows: registration are as follows:
skipping to change at page 20, line 9 skipping to change at page 19, line 42
o IPR Disclosure: https://datatracker.ietf.org/ipr/ o IPR Disclosure: https://datatracker.ietf.org/ipr/
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 some 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, transfered, updated, bundled registered domain names will be created, transferred, 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 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.
skipping to change at page 20, line 37 skipping to change at page 20, line 21
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.
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 an example, the NGO registrant is also registering and purchasing
corresponding name in the .ong TLD (and vice-versa for the 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 o Patrick Mevzek has released a new version of Net::DRI, an EPP
client (Perl library, free software) implementing this extension. 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. and the following ones of CNNIC: Weiping Yang, Chao Qi.
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.
14. Change History 14. Change History
RFC Editor: Please remove this section. RFC Editor: Please remove this section.
14.1. draft-kong-epp-bundle-mapping: Version 00 14.1. draft-ietf-regext-bundle-registration: Version 00
o EPP extensiton for bundled domain name registrations.
14.2. draft-kong-epp-bundle-mapping: Version 01
o Change the proposed category from EXP to STD.
o Add the section of Implementation Status.
o Refine the text, and update the examples.
14.3. draft-kong-epp-bundle-mapping: Version 02
o Refine the texts.
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.2. draft-ietf-regext-bundle-registration: 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 14.3. draft-ietf-regext-bundle-registration: 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.4. draft-ietf-regext-bundle-registration: 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 14.5. draft-ietf-regext-bundle-registration: Version 04
o Update the implementation section. o Update the implementation section.
o Refine the text. o Refine the text.
14.9. draft-ietf-regext-bundle-mapping: Version 05 14.6. draft-ietf-regext-bundle-registration: 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.7. draft-ietf-regext-bundle-registration: 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 14.8. draft-ietf-regext-bundle-registration: Version 07
o Update IANA consideration section based on Scott's comments o Update IANA consideration section based on Scott's comments
o Update security consideration based on Chair and Patrick Mevzek's o Update security consideration based on Chair and Patrick Mevzek's
comments comments
14.9. draft-ietf-regext-bundle-registration: Version 08
o Refine some texts.
14.10. draft-ietf-regext-bundle-registration: Version 09
o Refine the texts.
14.11. draft-ietf-regext-bundle-registration: Version 10
o Update the texts based on IETF LC.
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 23, line 14 skipping to change at page 22, line 46
[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 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
February 2015, <https://www.rfc-editor.org/info/rfc7451>. February 2015, <https://www.rfc-editor.org/info/rfc7451>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[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 36 skipping to change at page 23, line 27
<http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>. <http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.
[W3C.REC-xmlschema-2-20041028] [W3C.REC-xmlschema-2-20041028]
Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes
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]
ICANN, "Registry Services Technical Evaluation Panel
(RSTEP) Report on Public Interest Registry's Request to
Implement Technical Bundling in .NGO and .ONG", July 2014,
<https://www.icann.org/public-comments/
rstep-technical-bundling-2014-07-29-en>.
[Final.Integrated.Issues.Report]
ICANN, "The IDN Variant Issues Project: A Study of Issues
Related to the Management of IDN Variant TLDs", February
2012, <http://www.icann.org/en/topics/idn/
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
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
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 2677 Phone: +86 10 5881 2677
Email: zhoulinlin@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
 End of changes. 91 change blocks. 
467 lines changed or deleted 456 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/