Internet Engineering Task Force L. Zhou
Internet-Draft N. Kong
Intended status: Standards Track J. Wei
Expires: November 13, 2017 X. Lee
CNNIC
J. Gould
VeriSign, Inc.
May 12, 2017
Organization Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-org-ext-00
Abstract
This mapping, an extension to EPP object mappings like the EPP domain
name mapping [RFC5731], to support assigning an organization to any
existing object (domain, host, contact) as well as any future
objects. Specified in Extensible Markup Language (XML), this
extended mapping is applied to provide additional features required
for the provisioning of organizations.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
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 http://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 November 13, 2017.
Copyright Notice
Copyright (c) 2017 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
Zhou, et al. Expires November 13, 2017 [Page 1]
Internet-Draft Organization Extension for the EPP May 2017
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 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4
4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4
4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 4
4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 4
4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 4
4.1.3. EPP <transfer> Command . . . . . . . . . . . . . . . 7
4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 7
4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 7
4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 8
4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 8
4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 9
4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 9
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 11
6. Internationalization Considerations . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 14
7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 14
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 15
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
Zhou, et al. Expires November 13, 2017 [Page 2]
Internet-Draft Organization Extension for the EPP May 2017
1. Introduction
In the business model of domain registration, we usually have 3 roles
of entities, a registrant, a registrar and a registry. There may
have some other roles of entities involved in the domain registration
process which are not formally defined, such as resellers, DNS
service operators, privacy proxy, etc.
A domain reseller is an individual or a company that acts as a agent
for accredited registrars. A third-party DNS service operator is
responsible for a zone where the operator is neither the registrant
nor the registrar of records for the delegation. And a privacy proxy
is an entity that provides with individuals or organizations domain
registration without exposing their private information. These kind
of entities are defined as "organizations" with different role types
in this document.
In order to facilitate provisioning and management of organization
information in a shared central repository, this document proposes a
organization extension mapping for any EPP object like domain names
in [RFC5731], hosts in [RFC5732] and contacts in [RFC5733]. The
examples provided in this document are used for the domain object for
illustration purpose. The host and contact object could be extended
in the same way with the domain object.
A organization mapping object defined in [ID.draft-ietf-regext-org]
SHOULD be created first. The organization information specified in
this document MUST reference the existing organization identifier.
This document is specified using the 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].
2. Conventions Used in This Document
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].
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.
Zhou, et al. Expires November 13, 2017 [Page 3]
Internet-Draft Organization Extension for the EPP May 2017
orgext-1.0 in this document is used as an abbreviation for
urn:ietf:params:xml:ns:orgext-1.0.
3. Object Attributes
This extension adds additional elements to the EPP domain name
mapping [RFC5731]. Only the new elements are described here.
3.1. Organization Identifier
Organization identifier provides the ID of an organization. Its
corresponding element is <orgext:id> which refers to the
<organization:id> element defined in [ID.draft-ietf-regext-org]. All
organization objects are identified by a server-unique identifier.
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 organization information 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 elements to the EPP <check> command
or <check> response described in the EPP domain name mapping
[RFC5731], host mapping [RFC5732] and contact mapping [RFC5733].
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], host mapping [RFC5732]
and contact mapping [RFC5733]. However, additional elements are
defined for the <info> response.
Example <info> command:
Zhou, et al. Expires November 13, 2017 [Page 4]
Internet-Draft Organization Extension for the EPP May 2017
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <info>
C: <domain:info
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.com</domain:name>
C: <domain:authInfo>
C: <domain:pw>fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:info>
C: </info>
C: <clTRID>ngcl-mIFICBNP</clTRID>
C: </command>
C:</epp>
When an <info> command has been processed successfully, the EPP
<resData> element MUST contain child elements as described in the EPP
object extensions. In addition, the EPP <extension> element SHOULD
contain a child <orgext:infData> element that identifies the
extension namespace if the object has data associated with this
extension and based on its service policy. The <orgext:infData>
element contains the following child elements:
o A <orgext:id> element that contains the identifier of the
organization. An attribute "role" associated with <orgext:id> is
used to represent the relationship an organization would have.
See Section 7.3 in [ID.draft-ietf-regext-org] for a list of
values.
Example <info> response for an authorized client:
Zhou, et al. Expires November 13, 2017 [Page 5]
Internet-Draft Organization Extension for the EPP May 2017
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 lang="en-US">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>example.com</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="ok"/>
S: <domain:registrant>jd1234</domain:registrant>
S: <domain:contact type="admin">sh8013</domain:contact>
S: <domain:contact type="billing">sh8013</domain:contact>
S: <domain:contact type="tech">sh8013</domain:contact>
S: <domain:ns>
S: <domain:hostObj>ns1.example.com</domain:hostObj>
S: </domain:ns>
S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientY</domain:crID>
S: <domain:crDate>2015-02-06T04:01:21.0Z</domain:crDate>
S: <domain:exDate>2018-02-06T04:01:21.0Z</domain:exDate>
S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo>
S: </domain:infData>
S: </resData>
S: <extension>
S: <orgext:infData
S: xmlns:orgext="urn:ietf:params:xml:ns:orgext-1.0">
S: <orgext:id role="reseller">myreseller</orgext:id>
S: <orgext:id role="privacyproxy">myproxy</orgext:id>
S: </orgext:infData>
S: </extension>
S: <trID>
S: <clTRID>ngcl-IvJjzMZc</clTRID>
S: <svTRID>test142AWQONJZ</svTRID>
S: </trID>
S: </response>
S:</epp>
An EPP error response MUST be returned if an <info> command cannot be
processed for any reason.
Zhou, et al. Expires November 13, 2017 [Page 6]
Internet-Draft Organization Extension for the EPP May 2017
4.1.3. EPP <transfer> Command
This extension does not add any elements to the EPP <transfer>
command or <transfer> response described in the EPP domain name
mapping [RFC5731], host mapping [RFC5732] and contact mapping
[RFC5733].
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 for the EPP <create>
command described in the EPP object extensions. No additional
elements are defined for the EPP <create> response.
The EPP <create> command provides a transform operation that allows a
client to create an object. In addition to the EPP command elements
described in the EPP object extensions, the command MUST contain an
<extension> element, and the <extension> element MUST contain a child
<orgext:create> element that identifies the extension namespace if
the client wants to associate data defined in this extension to the
object. The <orgext:create> element contains the following child
elements:
o A <orgext:id> element that contains the identifier of the
organization. An attribute "role" associated with <orgext:id> is
used to represent the relationship an organization would have.
See Section 7.3 in [ID.draft-ietf-regext-org] for a list of
values.
Example <create> Command:
Zhou, et al. Expires November 13, 2017 [Page 7]
Internet-Draft Organization Extension for the EPP May 2017
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <create>
C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.com</domain:name>
C: <domain:period unit="y">3</domain:period>
C: <domain:ns>
C: <domain:hostObj>ns1.example.com</domain:hostObj>
C: </domain:ns>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:contact type="billing">sh8013</domain:contact>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw roid="ddddd-dddd">fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <orgext:create
C: xmlns:orgext="urn:ietf:params:xml:ns:orgext-1.0">
C: <orgext:id role="reseller">myreseller</orgext:id>
C: </orgext:create>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
When a <create> command has been processed successfully, the EPP
response is as described in the EPP object extension.
An EPP error response MUST be returned if a <create> command cannot
be processed for any reason.
4.2.2. EPP <delete> Command
This extension does not add any elements to the EPP <delete> command
or <delete> response described in the EPP domain mapping [RFC5731],
host mapping [RFC5732] and contact mapping [RFC5733].
4.2.3. EPP <renew> Command
This extension does not add any elements to the EPP <renew> command
or <renew> response described in the EPP domain mapping [RFC5731],
host mapping [RFC5732] and contact mapping [RFC5733].
Zhou, et al. Expires November 13, 2017 [Page 8]
Internet-Draft Organization Extension for the EPP May 2017
4.2.4. EPP <transfer> Command
This extension does not add any elements to the EPP <transfer>
command or <transfer> response described in the EPP domain mapping
[RFC5731], host mapping [RFC5732] and contact mapping [RFC5733], but
after a successful transfer of an object with an assigned
organization, the handling of the assigned organization is dependent
on the organization roles and server policy.
4.2.5. EPP <update> Command
This extension defines additional elements for the EPP <update>
command described in the EPP domain mapping [RFC5731], host mapping
[RFC5732] and contact mapping [RFC5733]. No additional elements are
defined for the EPP <update> response.
The EPP <update> command provides a transform operation that allows a
client to modify the attributes of a domain object. In addition to
the EPP command elements described in the EPP domain mapping, the
command MUST contain an <extension> element, and the <extension>
element MUST contain a child <orgext:update> element that identifies
the extension namespace if the client wants to update the domain
object with data defined in this extension. The <orgext:update>
element contains the following child elements:
o An OPTIONAL <orgext:add> element that contains attribute values to
be added to the object.
o An OPTIONAL <orgext:rem> element that contains attribute values to
be removed from the object.
o An OPTIONAL <orgext:chg> element that contains attribute values to
be changed.
At least one and only one <orgext:add>, <orgext:rem> or <orgext:rem>
element MUST be provided. The <orgext:add>, <orgext:rem> and
<orgext:rem> elements contain the following child element:
o A <orgext:id> element that contains the identifier of the
organization. An attribute "role" associated with <orgext:id> is
used to represent the relationship an organization would have.
See Section 7.3 in [ID.draft-ietf-regext-org] for a list of
values.
Example <update> command, adding a reseller:
Zhou, et al. Expires November 13, 2017 [Page 9]
Internet-Draft Organization Extension for the EPP May 2017
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.com</domain:name>
C: </domain:update>
C: </update>
C: <extension>
C: <orgext:update
C: xmlns:orgext="urn:ietf:params:xml:ns:orgext-1.0">
C: <orgext:add>
C: <orgext:id role="reseller">myreseller</orgext:id>
C: </orgext:add>
C: </orgext:update>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
Example <update> command, removing a reseller:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.com</domain:name>
C: </domain:update>
C: </update>
C: <extension>
C: <orgext:update
C: xmlns:orgext="urn:ietf:params:xml:ns:orgext-1.0">
C: <orgext:rem>
C: <orgext:id role="reseller">myreseller</orgext:id>
C: </orgext:rem>
C: </orgext:update>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
Example <update> command, updating reseller identifier:
Zhou, et al. Expires November 13, 2017 [Page 10]
Internet-Draft Organization Extension for the EPP May 2017
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.com</domain:name>
C: </domain:update>
C: </update>
C: <extension>
C: <orgext:update
C: xmlns:orgext="urn:ietf:params:xml:ns:orgext-1.0">
C: <orgext:chg>
C: <orgext:id role="reseller">myreseller</orgext:id>
C: </orgext:chg>
C: </orgext:update>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
When an extended <update> command has been processed successfully,
the EPP response is as described in the EPP object extension.
5. Formal Syntax
An EPP object mapping 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:orgext-1.0"
xmlns:orgext="urn:ietf:params:xml:ns:orgext-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">
<!--
Import common element types.
-->
Zhou, et al. Expires November 13, 2017 [Page 11]
Internet-Draft Organization Extension for the EPP May 2017
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
schemaLocation="eppcom-1.0.xsd"/>
<import namespace="urn:ietf:params:xml:ns:epp-1.0"
schemaLocation="epp-1.0.xsd"/>
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
Organization Extension Schema v1.0
</documentation>
</annotation>
<!-- Child elements found in EPP commands. -->
<element name="create" type="orgext:createType"/>
<element name="update" type="orgext:updateType"/>
<!-- Child elements of the <orgext:create> command
All elements must be present at time of creation
-->
<complexType name="createType">
<sequence>
<!-- agent identifier or the organization,
e.g. registrar, reseller, privacy proxy, etc. -->
<element name="id" type="eppcom:clIDType"/>
</sequence>
<attribute name="role"
type="token" use="required"/>
</complexType>
<!--
Child elements of <orgext:update> command
-->
<complexType name="updateType">
<sequence>
<element name="add"
type="orgext:addRemChgType" minOccurs="0"/>
<element name="rem"
type="orgext:addRemChgType" minOccurs="0"/>
<element name="chg"
type="orgext:addRemChgType" minOccurs="0"/>
</sequence>
</complexType>
<complexType name="addRemChgType">
<sequence>
<!-- agent identifier the organization,
e.g. registrar, reseller, privacy proxy, etc. -->
Zhou, et al. Expires November 13, 2017 [Page 12]
Internet-Draft Organization Extension for the EPP May 2017
<element name="id" type="eppcom:clIDType" minOccurs="0"/>
</sequence>
<attribute name="role"
type="token" use="required"/>
</complexType>
<!-- Child response element -->
<element name="infData" type="orgext:infDataType"/>
<!-- <orgext:infData> response elements -->
<complexType name="infDataType">
<sequence>
<!-- agent identifier the organization,
e.g. registrar, reseller, privacy proxy, etc. -->
<element name="id"
type="eppcom:clIDType" minOccurs="0"/>
</sequence>
<attribute name="role"
type="token" use="required"/>
</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
Zhou, et al. Expires November 13, 2017 [Page 13]
Internet-Draft Organization Extension for the EPP May 2017
7.1. XML Namespace
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 URI.
Registration request for the organization namespace:
o URI: urn:ietf:params:xml:ns:orgext-1.0
o Registrant Contact: See the "Author's Address" section of this
document.
o XML: See the "Formal Syntax" section of this document.
7.2. EPP Extension Registry
The EPP extension described in this document should be registered by
the IANA in the EPP Extension Registry described in [RFC7451]. The
details of the registration are as follows:
Name of Extension: Organization Extension
Document status: Standards Track
Reference: (insert reference to RFC version of this document)
Registrant Name and Email Address: See the "Author's Address" section
of this document.
TLDs: any
IPR Disclosure: none
Status: active
Notes: none
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], [RFC5731],
[RFC5732] and [RFC5733] or those caused by the protocol layers used
by EPP.
Zhou, et al. Expires November 13, 2017 [Page 14]
Internet-Draft Organization Extension for the EPP May 2017
9. Acknowledgement
The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick
Mevzek, Antoin Verschuren and Scott Hollenbeck for their careful
review and valuable comments.
10. References
10.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,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
<http://www.rfc-editor.org/info/rfc5730>.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731,
DOI 10.17487/RFC5731, August 2009,
<http://www.rfc-editor.org/info/rfc5731>.
[RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732,
August 2009, <http://www.rfc-editor.org/info/rfc5732>.
[RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733,
August 2009, <http://www.rfc-editor.org/info/rfc5733>.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
February 2015, <http://www.rfc-editor.org/info/rfc7451>.
[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>.
Zhou, et al. Expires November 13, 2017 [Page 15]
Internet-Draft Organization Extension for the EPP May 2017
[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>.
10.2. Informative References
[ID.draft-ietf-regext-org]
Zhou, L., Kong, N., Zhou, G., Lee, X., Gould, J., and S.
Hollenbeck, "Extensible Provisioning Protocol (EPP)
Reseller Mapping", Apr 2017,
<http://tools.ietf.org/html/draft-ietf-regext-org>.
Appendix A. Change Log
Initial -00: Individual document submitted.
-01:
* Updated abstract and introduction.
* Revised typos in info response.
* Added explanations on how to process reseller extension after
successful transfer operation.
* Modified <update> explanation.
* Deleted reseller name element in <create> and <update>
commands.
* Removed some inaccurate comments from xml schema.
* Modified the element name of reseller id and reseller name.
-02:
* Changed author information.
Zhou, et al. Expires November 13, 2017 [Page 16]
Internet-Draft Organization Extension for the EPP May 2017
* Updated xml typos <reseller:infData> to <resellerext:infData>
in <info> response.
-03:
* Changed author information.
* Updated section 3.1.
* Removed reseller name element in <info> response.
* Added acknowledgement.
* Revised the typo "resellerr" to "resellerext".
WG document-00: WG document submitted
WG document-01: Keep document alive for further discussion. The
requirement of reseller information is clear for both registrar
and registry. What we should reach a consensus is whether the
extension should support only a name or ID and name.
Organization WG document-00: Change to a generic organization object
extension.
Authors' Addresses
Linlin Zhou
CNNIC
4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190
China
Phone: +86 10 5881 2677
Email: zhoulinlin@cnnic.cn
Ning Kong
CNNIC
4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190
China
Phone: +86 10 5881 3147
Email: nkong@cnnic.cn
Zhou, et al. Expires November 13, 2017 [Page 17]
Internet-Draft Organization Extension for the EPP May 2017
Junkai Wei
CNNIC
4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190
China
Phone: +86 10 5881 3494
Email: weijunkai@cnnic.cn
Xiaodong Lee
CNNIC
4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190
China
Phone: +86 10 5881 3020
Email: xl@cnnic.cn
James Gould
VeriSign, Inc.
12061 Bluemont Way
Reston, VA 20190
US
Email: jgould@verisign.com
Zhou, et al. Expires November 13, 2017 [Page 18]