Internet DRAFT - draft-wang-epp-cdn-mapping
draft-wang-epp-cdn-mapping
Internet Engineering Task Force Z. Wang
Internet Draft CONAC
Intended status: Informational Mar 25, 2013
Expires: Sep 25, 2013
Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension
for Chinese Domain Names
draft-wang-epp-cdn-mapping-00.txt
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. This document may not be modified,
and derivative works of it may not be created, and it may not be
published except as an Internet-Draft.
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. This document may not be modified,
and derivative works of it may not be created, except to publish it
as an RFC and to translate it into languages other than English.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November 10,
2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-Drafts.
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."
Wang Expires Sep 25, 2013 [Page 1]
Internet-Draft draft-wang-epp-cdn-mapping-00.txt Mar 25, 2013
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on Fail 27, 2013.
Copyright Notice
Copyright (c) 2013 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
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents carefully,
as they describe your rights and restrictions with respect to this
document. Code Components extracted from this document must include
Simplified BSD License text as described in Section 4.e of the Trust
Legal Provisions and are provided without warranty as described in
the Simplified BSD License.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents carefully,
as they describe your rights and restrictions with respect to this
document.
Abstract
This document describes an extension of Extensible Provisioning
Protocol (EPP) domain name mapping for the provisioning and
management of Chinese Domain Names (CDNs). Specified in XML, this
extended mapping is applied to provide additional features required
by CDNs Registration.
Table of Contents
1. Introduction ................................................ 3
2. Terminology ................................................. 4
3. Object Attributes ........................................... 4
4. EPP Command Mapping ......................................... 4
4.1. EPP Query Commands...................................... 4
4.1.1. EPP<check> Command................................. 4
Wang Expires Sep 25, 2013 [Page 2]
Internet-Draft draft-wang-epp-cdn-mapping-00.txt Mar 25, 2013
4.1.2. EPP<info> Command.................................. 5
4.1.3. EPP<transfer> Query Command ....................... 6
4.2. EPP Transform Commands.................................. 6
4.2.1. EPP<create> Command................................ 6
4.2.2. EPP<delete> Command................................ 7
4.2.3. EPP<renew> Command................................. 7
4.2.4. EPP<transfer> Command.............................. 7
4.2.5. EPP<update> Command................................ 7
5. Formal Syntax ............................................... 7
6. Internationalization Considerations ......................... 8
7. IANA Considerations ......................................... 8
8. Security considerations ..................................... 9
9. References .................................................. 9
1. Introduction
Many Chinese characters in common use have variants in Simplified
Chinese (SC) form, Traditional Chinese (TC) form or other variant
forms. For example, the Chinese character "U+5B81" has 5 variants:
"U+5B81" (SC form), "U+5BE7" (TC form), "U+21A34", "U+5BDC" and
"U+5BCD" (other variant forms). For Chinese users, the variants of a
Chinese character in SC form, TC form and other variant forms are
regarded as the same.
To simplify the EPP implementations with support for CDN, Chinese
Domain Names (CDNs) containing different variant forms (SC form, TC
form, and other variant forms) are regarded as separated ones in this
extension, whereas the association between variant forms are ensured
by registration management which is out of scope of this
specification.
In order to meet above requirements of the CDNs registration, this
document describes an extension of the Extensible Provisioning
Protocol (EPP) domain name mapping [RFC5731] for the provisioning and
management of CDNs. This document is specified using the Extensible
Markup Language (XML) 1.0 as described in [W3C.REC-xml-20040204] and
XML Schema notation as described in [W3C.REC-xmlschema-1-20041028]
and [W3C.REC-xmlschema-2-20041028].
The EPP core protocol specification [RFC5730] provides a complete
description of EPP command and response structures. A thorough
understanding of the base protocol specification is necessary to
understand the extension of mapping described in this document.
Wang Expires Sep 25, 2013 [Page 3]
Internet-Draft draft-wang-epp-cdn-mapping-00.txt Mar 25, 2013
2. Terminology
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].
"conac-cdn-1.0" in this document is used as an abbreviation for
urn:ietf:params:xml:ns:conac-cdn-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.
3. Object Attributes
This extension defines one additional element to the EPP domain name
mapping [RFC5731]. It can be got from <domain:info> command.
The CDN Unicode domain name is a domain name in Unicode which is
converted from the corresponding CDNpunycode. In this document, its
corresponding element is <cdn:CDNUnicode>.
4. EPP Command Mapping
A detailed description of the EPP syntax and semantics can be found
in the EPP core protocol specification [RFC5730]. The command
mappings described here are specifically for use in provisioning and
managing CDNs via EPP.
4.1. EPP Query Commands
EPP provides three commands to retrieve domain information: <check>
to determine if a domain object can be provisioned within a
repository, <info> to retrieve detailed information associated with a
domain object, and <transfer> to retrieve domain-object transfer
status information.
4.1.1. EPP<check> Command
This extension does not add any element to the EPP <check> command or
<check> response described in the EPP domain name mapping [RFC5731].
When a domain name has not been registered, but the domain which the
Wang Expires Sep 25, 2013 [Page 4]
Internet-Draft draft-wang-epp-cdn-mapping-00.txt Mar 25, 2013
user submitted for check is in the CDN list of a registered domain
name, <check> response must contain explanation in the reason field
to tell the user that this domain name is a CDN of a registered
domain name, and can be activitated by the registrant by <create>
command.
4.1.2. EPP<info> Command
This extension does not add any element to the EPP <info> command
described in the EPP domain mapping [RFC5731]. However, additional
elements are defined for the <info> response.
This extension does not add any element to the EPP <info> command
described in the EPP domain mapping [RFC5731]. However, additional
elements are defined for the <info> response. When an <info> command
has been processed successfully, the EPP <resData> element MUST
contain child elements as described in the EPP domain mapping
[RFC5731]. In addition, the EPP <extension> element SHOULD contain a
child <cdn:infData> element that identifies the extension namespace
if the domain object has data associated with this extension and
based on server policy. The <cdn:infData> element contains one child
element:
o An OPTIONAL <cdn:CDNUnicode> element that contains the Unicode of
the CDN.
Example <info> Response for an authorized client:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
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:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>
S: xn--1lq90i.xn--55qw42g</domain:name>
S: <domain:roid>58812678-domain</domain:roid>
S: <domain:status s="ok"/>
S: <domain:registrant>123</domain:registrant>
S: <domain:contact type="admin">123</domain:contact>
S: <domain:contact type="tech">123</domain:contact>
S: <domain:ns>
S: <domain:hostObj>ns1.example.cn</domain:hostObj>
S: </domain:ns>
Wang Expires Sep 25, 2013 [Page 5]
Internet-Draft draft-wang-epp-cdn-mapping-00.txt Mar 25, 2013
S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientY</domain:crID>
S: <domain:crDate>2013-04-03T22:00:00.0Z</domain:crDate>
S: <domain:exDate>2012-04-03T22:00:00.0Z</domain:exDate>
S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo>
S: </domain:infData>
S: </resData>
S: <extension>
S: <cdn:infData
S: xmlns:cdn="urn:ietf:params:xml:ns:conac-cdn-1.0">
S: <cdn:CDNUnicode>
S: "U+5317""U+4eac"."U+516c""U+76ca"</cdn:CDNUnicode>
S: </cdn:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
<info> Response for the unauthorized client has not been changed,see
[RFC5731] for detail.
An EPP error response MUST be returned if an <info> command cannot be
processed for any reason.
4.1.3. EPP<transfer> Query Command
This extension does not add any element to the EPP <transfer> command
described in the EPP domain mapping [RFC5731].
4.2. EPP Transform Commands
EPP provides five commands to transform domain objects: <create> to
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
object, <transfer> to manage domain object sponsorship changes, and
<update> to change information associated with a domain object.
4.2.1. EPP<create> Command
This extension defines additional elements to extend the EPP <create>
command described in the EPP domain name mapping [RFC5731] for CDN
registration.
Wang Expires Sep 25, 2013 [Page 6]
Internet-Draft draft-wang-epp-cdn-mapping-00.txt Mar 25, 2013
4.2.2. EPP<delete> Command
This extension does not add any element to the EPP <delete> command
described in the EPP domain mapping [RFC5731].
4.2.3. EPP<renew> Command
This extension does not add any element to the EPP <renew> command
described in the EPP domain mapping [RFC5731].
4.2.4. EPP<transfer> Command
This extension does not add any element to the EPP <transfer> command
described in the EPP domain mapping [RFC5731].
4.2.5. EPP<update> Command
This extension does not add any element to the EPP <update> command
described in the EPP domain mapping [RFC5731].
5. Formal Syntax
An EPP object name mapping extension for CDN 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
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:conac-cdn-1.0"
xmlns:cdn="urn:ietf:params:xml:ns:conac-cdn-1.0"
xmlns:epp="urn:iana:xml:ns:epp-1.0"
xmlns:eppcom="urn:iana:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!--
Import common element types.
-->
<import namespace="urn:iana:xml:ns:eppcom-1.0"
schemaLocation="eppcom-1.0.xsd"/>
<import namespace="urn:iana:xml:ns:epp-1.0"
schemaLocation="epp-1.0.xsd"/>
<annotation>
Wang Expires Sep 25, 2013 [Page 7]
Internet-Draft draft-wang-epp-cdn-mapping-00.txt Mar 25, 2013
<documentation>
Extensible Provisioning Protocol v1.0
CONAC Domain Extension Schema v1.0
</documentation>
</annotation>
<!--
Child elements found in EPP commands.
-->
<element name="infData" type="cdn:infDataType"/>
<!--
Child elements of the <cdn:infData> command
All elements must be present at time of creation
-->
<complexType name="infDataType">
<sequence>
<element name="CDNUnicode" type="eppcom:labelType"
minOccurs="0" />
</sequence>
</complexType>
<!--
End of schema.
-->
</schema>
END
6. Internationalization Considerations
EPP is represented in XML, which provides native support for encoding
information using the Unicode character set and its more compact
representations including UTF-8. Conformant XML processors recognize
both UTF-8 and UTF-16. Though XML includes provisions to identify
and use other character encodings through use of an "encoding"
attribute in an <?xml?> declaration, use of UTF-8 is RECOMMENDED.
As an extension of the EPP domain name mapping, the elements, element
content described in this document MUST inherit the
internationalization conventions used to represent higher-layer
domain and core protocol structures present in an XML instance that
includes this extension.
7. 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 URI.
Registration request for the CDN namespace:
Wang Expires Sep 25, 2013 [Page 8]
Internet-Draft draft-wang-epp-cdn-mapping-00.txt Mar 25, 2013
o URI: urn:ietf:params:xml:ns:conac-cdn-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 CDN XML schema:
o URI: urn:ietf:params:xml:schema: conac-cdn-1.0
o Registrant Contact: See the "Author's Address" section of this
document.
o XML: See the "Formal Syntax" section of this document.
8. Security considerations
The object mapping extension described in this document does not
provide any other security services or introduce any additional
considerations beyond those described by [RFC5730] or those caused by
the protocol layers used by EPP.
9. References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, August 2009.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731, August 2009.
[W3C.REC-xml-20040204] Bray, T., Paoli, J., Sperberg-McQueen, C.,
Maler, E., and F. Yergeau, ""Extensible
Markup Language (XML) 1.0 (Third Edition)",
World Wide Web Consortium FirstEdition REC-
xml-20040204", February 2004,
<http://www.w3.org/TR/2004/REC-xml-20040204>.
Wang Expires Sep 25, 2013 [Page 9]
Internet-Draft draft-wang-epp-cdn-mapping-00.txt Mar 25, 2013
[W3C.REC-xmlschema-1-20041028] Thompson, H., Beech, D., Maloney, M.,
and N. Mendelsohn,""XML Schema Part 1:
Structures Second Edition", World Wide
Web Consortium Recommendation REC-
xmlschema-1-20041028", October
2004,<http://www.w3.org/TR/2004/REC-
xmlschema-1-20041028>.
[W3C.REC-xmlschema-2-20041028] Biron, P. and A. Malhotra, ""XML
Schema Part 2: Datatypes Second
Edition", World Wide Web Consortium
Recommendation REC-xmlschema-2-
20041028", October
2004,<http://www.w3.org/TR/2004/REC-
xmlschema-2-20041028>.
Authors' Addresses
Zheng Wang
CONAC
JIA 31,NorthGuangximen, Xibahe, Chaoyang District
Beijing 100028
China
Phone: +86 10 5203 5185
Email: wangzheng@conac.cn
Wang Expires Sep 25, 2013 [Page 10]
