--- 1/draft-ietf-regext-bundling-registration-04.txt 2018-08-30 03:13:07.533151234 -0700
+++ 2/draft-ietf-regext-bundling-registration-05.txt 2018-08-30 03:13:07.573152203 -0700
@@ -1,24 +1,24 @@
Internet Engineering Task Force N. Kong
Internet-Draft Consultant
Intended status: Informational J. Yao, Ed.
-Expires: February 15, 2019 L. Zhou
+Expires: March 3, 2019 L. Zhou
CNNIC
W. Tan
Cloud Registry
J. Xie
- August 14, 2018
+ August 30, 2018
Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for
Strict Bundling Registration
- draft-ietf-regext-bundling-registration-04
+ draft-ietf-regext-bundling-registration-05
Abstract
This document describes an extension of Extensible Provisioning
Protocol (EPP) domain name mapping for the provisioning and
management of strict bundling registration of domain names.
Specified in XML, this mapping extends the EPP domain name mapping to
provide additional features required for the provisioning of bundled
domain names.
@@ -30,21 +30,21 @@
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
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 (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
@@ -95,20 +95,21 @@
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17
14. Change History . . . . . . . . . . . . . . . . . . . . . . . 18
14.1. draft-kong-epp-bundle-mapping: Version 00 . . . . . . . 18
14.2. draft-kong-epp-bundle-mapping: Version 01 . . . . . . . 18
14.3. draft-kong-epp-bundle-mapping: Version 02 . . . . . . . 18
14.4. draft-ietf-regext-bundle-mapping: Version 00 . . . . . . 18
14.5. draft-ietf-regext-bundle-mapping: Version 01 . . . . . . 18
14.6. draft-ietf-regext-bundle-mapping: Version 02 . . . . . . 18
14.7. draft-ietf-regext-bundle-mapping: Version 03 . . . . . . 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.1. Normative References . . . . . . . . . . . . . . . . . . 19
15.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction
Bundled domain names are those which share the same TLD but whose
second level labels are variants, or those which has identical second
level labels for which certain parameters are shared in different
@@ -168,21 +169,21 @@
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
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
UNICODE point.
"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:"
represents lines returned by a protocol server. Indentation and
white space in examples are provided only to illustrate element
relationships and are not a REQUIRED feature of this specification.
XML is case sensitive. Unless stated otherwise, XML specifications
and examples provided in this document MUST be interpreted in the
character case presented to develop a conforming implementation.
@@ -403,21 +404,21 @@
S: 2012-04-03T22:00:00.0Z
S:
S: 2fooBAR
S:
S:
S:
S:
S:
+ S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn-1.0">
S:
S: xn--fsq270a.example
S: xn--fsqz41a.example
S:
S:
S:
S:
S: ABC-12345
@@ -486,21 +487,21 @@
C: 123
C: 123
C: 123
C:
C: 2fooBAR
C:
C:
C:
C:
C:
+ C: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn-1.0">
C:
C: xn--fsq270a.example
C:
C:
C: ABC-12345
C:
C:
When an command has been processed successfully, the EPP
element MUST contain child elements as described in the EPP
@@ -521,21 +522,21 @@
S:
S:
S: xn--fsq270a.example
S: 1999-04-03T22:00:00.0Z
S: 2001-04-03T22:00:00.0Z
S:
S:
S:
S:
+ S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn-1.0">
S:
S: xn--fsq270a.example
S: xn--fsqz41a.example
S:
S:
S:
S:
S: ABC-12345
@@ -567,21 +568,21 @@
Example response:
S:
S:
S:
S:
S: Command completed successfully
S:
S:
S:
+S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn-1.0">
S:
S: xn--fsq270a.example
S: xn--fsqz41a.example
S:
S:
S:
S:
S: ABC-12345
S: 54321-XYZ
S:
@@ -625,22 +626,22 @@
An EPP object name mapping extension for bundled names is specified
in XML Schema notation. The formal syntax presented here is a
complete schema representation of the object mapping suitable for
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
ending of the schema for URI registration purposes.
BEGIN
-
@@ -736,29 +737,29 @@
includes this extension.
10. IANA Considerations
This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. IANA is
requested to assignment the following two URIs.
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
document.
o XML: None. Namespace URI does not represent an XML specification.
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
document.
o XML: See the "Formal Syntax" section of this document.
11. Security Considerations
The object mapping extension described in this document does not
provide any other security services or introduce any additional
@@ -834,20 +835,24 @@
o This document is changed to informational category.
o Refine the text.
14.8. draft-ietf-regext-bundle-mapping: Version 04
o Update the implementation section.
o Refine the text.
+14.9. draft-ietf-regext-bundle-mapping: Version 05
+
+ o Scope the XML namespaces to include 'epp'.
+
15. References
15.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,