draft-ietf-regext-bundling-registration-04.txt | draft-ietf-regext-bundling-registration-05.txt | |||
---|---|---|---|---|
Internet Engineering Task Force N. Kong | Internet Engineering Task Force N. Kong | |||
Internet-Draft Consultant | Internet-Draft Consultant | |||
Intended status: Informational J. Yao, Ed. | Intended status: Informational J. Yao, Ed. | |||
Expires: February 15, 2019 L. Zhou | Expires: March 3, 2019 L. Zhou | |||
CNNIC | CNNIC | |||
W. Tan | W. Tan | |||
Cloud Registry | Cloud Registry | |||
J. Xie | J. Xie | |||
August 14, 2018 | August 30, 2018 | |||
Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for | Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for | |||
Strict Bundling Registration | Strict Bundling Registration | |||
draft-ietf-regext-bundling-registration-04 | draft-ietf-regext-bundling-registration-05 | |||
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 February 15, 2019. | This Internet-Draft will expire on March 3, 2019. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2018 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
skipping to change at page 3, line 12 ¶ | skipping to change at page 3, line 12 ¶ | |||
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 | 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 | |||
14. Change History . . . . . . . . . . . . . . . . . . . . . . . 18 | 14. Change History . . . . . . . . . . . . . . . . . . . . . . . 18 | |||
14.1. draft-kong-epp-bundle-mapping: Version 00 . . . . . . . 18 | 14.1. draft-kong-epp-bundle-mapping: Version 00 . . . . . . . 18 | |||
14.2. draft-kong-epp-bundle-mapping: Version 01 . . . . . . . 18 | 14.2. draft-kong-epp-bundle-mapping: Version 01 . . . . . . . 18 | |||
14.3. draft-kong-epp-bundle-mapping: Version 02 . . . . . . . 18 | 14.3. draft-kong-epp-bundle-mapping: Version 02 . . . . . . . 18 | |||
14.4. draft-ietf-regext-bundle-mapping: Version 00 . . . . . . 18 | 14.4. draft-ietf-regext-bundle-mapping: Version 00 . . . . . . 18 | |||
14.5. draft-ietf-regext-bundle-mapping: Version 01 . . . . . . 18 | 14.5. draft-ietf-regext-bundle-mapping: Version 01 . . . . . . 18 | |||
14.6. draft-ietf-regext-bundle-mapping: Version 02 . . . . . . 18 | 14.6. draft-ietf-regext-bundle-mapping: Version 02 . . . . . . 18 | |||
14.7. draft-ietf-regext-bundle-mapping: Version 03 . . . . . . 18 | 14.7. draft-ietf-regext-bundle-mapping: Version 03 . . . . . . 18 | |||
14.8. draft-ietf-regext-bundle-mapping: Version 04 . . . . . . 18 | 14.8. draft-ietf-regext-bundle-mapping: Version 04 . . . . . . 18 | |||
14.9. draft-ietf-regext-bundle-mapping: Version 05 . . . . . . 19 | ||||
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 | 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 | |||
15.1. Normative References . . . . . . . . . . . . . . . . . . 19 | 15.1. Normative References . . . . . . . . . . . . . . . . . . 19 | |||
15.2. Informative References . . . . . . . . . . . . . . . . . 20 | 15.2. Informative References . . . . . . . . . . . . . . . . . 20 | |||
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 | |||
1. Introduction | 1. Introduction | |||
Bundled domain names are those which share the same TLD but whose | Bundled domain names are those which share the same TLD but whose | |||
second level labels are variants, or those which has identical second | second level labels are variants, or those which has identical second | |||
level labels for which certain parameters are shared in different | level labels for which certain parameters are shared in different | |||
skipping to change at page 4, line 39 ¶ | skipping to change at page 4, line 39 ¶ | |||
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", "MAY", and "OPTIONAL" in this | |||
document are to be interpreted as described in [RFC2119]. | document are to be interpreted as described in [RFC2119]. | |||
uLable is defined in [RFC 5890]. uLabel is expressed in this document | uLable is defined in [RFC 5890]. uLabel is expressed in this document | |||
as a number of characters with the format of U+XXXX where XXXX is a | as a number of characters with the format of U+XXXX where XXXX is a | |||
UNICODE point. | UNICODE point. | |||
"b-dn-1.0" in this document is used as an abbreviation for | "b-dn-1.0" in this document is used as an abbreviation for | |||
urn:ietf:params:xml:ns:b-dn-1.0. | urn:ietf:params:xml:ns:epp:b-dn-1.0. | |||
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. | |||
skipping to change at page 9, line 47 ¶ | skipping to change at page 9, line 47 ¶ | |||
</domain:crDate> | </domain:crDate> | |||
S: <domain:exDate>2012-04-03T22:00:00.0Z | S: <domain:exDate>2012-04-03T22:00:00.0Z | |||
</domain:exDate> | </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:b-dn-1.0"> | S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn-1.0"> | |||
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</b-dn:rdn> | |||
S: <b-dn:bdn uLabel="U+5BE6""U+4F8B".example | S: <b-dn:bdn uLabel="U+5BE6""U+4F8B".example | |||
S: >xn--fsqz41a.example</b-dn:bdn> | S: >xn--fsqz41a.example</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> | |||
skipping to change at page 11, line 37 ¶ | skipping to change at page 11, line 37 ¶ | |||
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:b-dn-1.0"> | C: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn-1.0"> | |||
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</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 | |||
skipping to change at page 12, line 23 ¶ | skipping to change at page 12, line 23 ¶ | |||
S: <resData> | S: <resData> | |||
S: <domain:creData | S: <domain:creData | |||
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:b-dn-1.0"> | S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn-1.0"> | |||
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</b-dn:rdn> | |||
S: <b-dn:bdn uLabel="U+5BE6""U+4F8B".example | S: <b-dn:bdn uLabel="U+5BE6""U+4F8B".example | |||
S: >xn--fsqz41a.example</b-dn:bdn> | S: >xn--fsqz41a.example</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> | |||
skipping to change at page 13, line 20 ¶ | skipping to change at page 13, line 20 ¶ | |||
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:b-dn-1.0"> | S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn-1.0"> | |||
S: <b-dn:bundle> | S: <b-dn:bundle> | |||
S: <b-dn:rdn uLabel="U+5B9E""U+4F8B".example>xn--fsq270a.example</b-dn:rdn> | S: <b-dn:rdn uLabel="U+5B9E""U+4F8B".example>xn--fsq270a.example</b-dn:rdn> | |||
S: <b-dn:bdn uLabel="U+5BE6""U+4F8B".example>xn--fsqz41a.example</b-dn:bdn> | S: <b-dn:bdn uLabel="U+5BE6""U+4F8B".example>xn--fsqz41a.example</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> | |||
skipping to change at page 14, line 35 ¶ | skipping to change at page 14, line 35 ¶ | |||
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:b-dn-1.0" | <schema targetNamespace="urn:ietf:params:xml:ns:epp:b-dn-1.0" | |||
xmlns:b-dn="urn:ietf:params:xml:ns: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:epp="urn:ietf:params:xml:ns:epp-1.0" | |||
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" | xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" | |||
xmlns="http://www.w3.org/2001/XMLSchema" | xmlns="http://www.w3.org/2001/XMLSchema" | |||
elementFormDefault="qualified"> | elementFormDefault="qualified"> | |||
<!-- | <!-- | |||
Import common element types. | Import common element types. | |||
--> | --> | |||
<import namespace="urn:iana:xml:ns:eppcom-1.0" | <import namespace="urn:iana:xml:ns:eppcom-1.0" | |||
schemaLocation="eppcom-1.0.xsd"/> | schemaLocation="eppcom-1.0.xsd"/> | |||
skipping to change at page 16, line 49 ¶ | skipping to change at page 16, line 49 ¶ | |||
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:b-dn-1.0 | o URI: urn:ietf:params:xml:ns:epp:b-dn-1.0 | |||
o Registrant Contact: See the "Author's Address" section of this | o Registrant Contact: See the "Author's Address" section of this | |||
document. | document. | |||
o XML: 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:b-dn-1.0 | o URI: urn:ietf:params:xml:schema:epp:b-dn-1.0 | |||
o Registrant Contact: See the "Author's Address" section of this | o Registrant Contact: See the "Author's Address" section of this | |||
document. | document. | |||
o XML: See the "Formal Syntax" section of this document. | o XML: See the "Formal Syntax" section of this document. | |||
11. Security Considerations | 11. Security Considerations | |||
The object mapping extension described in this document does not | The object mapping extension described in this document does not | |||
provide any other security services or introduce any additional | provide any other security services or introduce any additional | |||
skipping to change at page 19, line 5 ¶ | skipping to change at page 19, line 5 ¶ | |||
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.8. draft-ietf-regext-bundle-mapping: 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 | ||||
o Scope the XML namespaces to include 'epp'. | ||||
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. 15 change blocks. | ||||
14 lines changed or deleted | 19 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/ |