draft-ietf-regext-org-ext-11.txt   rfc8544.txt 
Internet Engineering Task Force L. Zhou Internet Engineering Task Force (IETF) L. Zhou
Internet-Draft CNNIC Request for Comments: 8544 CNNIC
Intended status: Standards Track N. Kong Category: Standards Track N. Kong
Expires: June 8, 2019 Consultant ISSN: 2070-1721 Consultant
J. Wei J. Wei
J. Yao J. Yao
CNNIC CNNIC
J. Gould J. Gould
Verisign, Inc. VeriSign, Inc.
December 5, 2018 April 2019
Organization Extension for the Extensible Provisioning Protocol (EPP) Organization Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-org-ext-11
Abstract Abstract
This document describes an extension to Extensible Provisioning This document describes an extension to Extensible Provisioning
Protocol (EPP) object mappings, which is designed to support Protocol (EPP) object mappings that is designed to support assigning
assigning an organization to any existing object (domain, host, an organization to any existing object (domain, host, contact) as
contact) as well as any future objects. well as any future objects.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
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 https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on June 8, 2019. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8544.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions Used in This Document . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4 3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4
4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4
4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 4 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 4
4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 4 4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 4
4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 4 4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 4
4.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 7 4.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 8
4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8
4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 8 4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 8
4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 10 4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 10
4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 10 4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 10
4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 11 4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 11
4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 11 4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 11
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 15 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 15
6. Internationalization Considerations . . . . . . . . . . . . . 18 6. Internationalization Considerations . . . . . . . . . . . . . 18
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 18 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 18
7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 19
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 19 8. Security Considerations . . . . . . . . . . . . . . . . . . . 19
8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 19 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 20 9.1. Normative References . . . . . . . . . . . . . . . . . . 19
9. Security Considerations . . . . . . . . . . . . . . . . . . . 20 9.2. Informative References . . . . . . . . . . . . . . . . . 21
10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 20 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 21
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
11.1. Normative References . . . . . . . . . . . . . . . . . . 20
11.2. Informative References . . . . . . . . . . . . . . . . . 22
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25
1. Introduction 1. Introduction
In the business model of domain registration, we usually have three There are many entities, such as registrars, resellers, DNS service
roles of entities: a registrant, a registrar and a registry, as operators, and privacy proxies, involved in the domain registration
defined in section 9 of [ID.draft-ietf-dnsop-terminology-bis]. There business. These kinds of entities are supported in the Extensible
may be other roles of entities involved in the domain registration Provisioning Protocol (EPP) by the "organization" entities in
process, such as resellers, DNS operators in section 9 of [RFC8543]. This document provides a way to associate any EPP object
[ID.draft-ietf-dnsop-terminology-bis], privacy proxies, etc. such as domain names in [RFC5731], hosts in [RFC5732], and contacts
in [RFC5733] to "organization" entities in [RFC8543]. The examples
A domain reseller is an individual or a company that acts as an agent provided in this document are used for the domain object for
for accredited registrars. DNS operator is defined in section 9 of illustration purposes. The host and contact object could be extended
[ID.draft-ietf-dnsop-terminology-bis]. A privacy proxy is an entity in the same way as the domain object.
used for domain registrations to protect the private information of
the individuals and organizations. 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 an
organization extension mapping for any Extensible Provisioning
Protocol (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.
Organization object identifiers defined in [ID.draft-ietf-regext-org] Organization object identifiers, defined in [RFC8543], MUST be known
MUST be known to the server before the organization object can be to the server before the organization object can be associated with
associated with the EPP object. the EPP object.
This document is specified using the XML 1.0 as described in This document is specified using XML 1.0 as described in
[W3C.REC-xml-20040204] and XML Schema notation as described in [W3C.REC-xml-20081126] and XML Schema notation as described in
[W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028]. [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028].
2. Conventions Used in This Document 2. Conventions Used in This Document
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 BCP 14 "OPTIONAL" in this document are to be interpreted as described in
[RFC2119][RFC8174] when, and only when, they appear in all capitals, BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
as shown here. capitals, as shown here.
In examples, "C:" represents lines sent by a protocol client and "S:" In examples, "C:" represents lines sent by a protocol client, and
represents lines returned by a protocol server. Indentation and "S:" 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. character case presented.
The XML namespace prefix "orgext" is used for the namespace The XML namespace prefix "orgext" is used for the namespace
"urn:ietf:params:xml:ns:epp:orgext-1.0", but implementations MUST NOT "urn:ietf:params:xml:ns:epp:orgext-1.0", but implementations MUST NOT
depend on it and instead employ a proper namespace-aware XML parser depend on it; instead, they should employ a proper namespace-aware
and serializer to interpret and output the XML documents. XML parser and serializer to interpret and output the XML documents.
3. Object Attributes 3. Object Attributes
This extension adds additional elements to EPP object mappings like This extension adds additional elements to EPP object mappings such
the EPP domain name mapping [RFC5731]. Only the new elements are as the EPP domain name mapping [RFC5731]. Only the new elements are
described here. described here.
3.1. Organization Identifier 3.1. Organization Identifier
Organization identifier provides the ID of an organization. Its The organization identifier provides the ID of an organization. Its
corresponding element is <orgext:id> which refers to the <org:id> corresponding element is <orgext:id>, which refers to the <org:id>
element defined in [ID.draft-ietf-regext-org]. All organization element defined in [RFC8543]. All organization objects are
objects are identified by a server-unique identifier. A "role" identified by a server-unique identifier. A "role" attribute is used
attribute is used to represent the relationship that the organization to represent the relationship that the organization has to the EPP
has to the EPP object. Any given object MUST have at most one object. Any given object MUST have at most one associated
associated organization ID for any given role value. organization ID for any given role value.
4. EPP Command Mapping 4. 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 assigning organizations mappings described here are specifically for assigning organizations
to EPP objects. to EPP objects.
4.1. EPP Query Commands 4.1. EPP Query Commands
skipping to change at page 4, line 50 skipping to change at page 4, line 44
4.1.2. EPP <info> Command 4.1.2. EPP <info> Command
This extension does not add any elements to the EPP <info> command This extension does not add any elements to the EPP <info> command
described in the EPP object mapping. However, additional elements described in the EPP object mapping. However, additional elements
are defined for the <info> response in the EPP object mapping. are defined for the <info> response in the EPP object mapping.
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
object extensions. In addition, the EPP <extension> element SHOULD object extensions. In addition, the EPP <extension> element SHOULD
contain a child <orgext:infData> element. This element or its contain a child <orgext:infData> element. This element is returned
ancestor element MUST identify the extension namespace if the object has data that is associated with this extension and
"urn:ietf:params:xml:ns:epp:orgext-1.0" if the object has data that is based on server policy. This element or its ancestor element
associated with this extension and based on server policy. The MUST identify the extension namespace
<orgext:infData> element contains the following child elements: "urn:ietf:params:xml:ns:epp:orgext-1.0". The <orgext:infData>
element contains the following child elements:
o Zero or more <orgext:id> elements are allowed that contain the o Zero or more <orgext:id> elements are allowed that contain the
identifier of the organization, as defined in Section 3.1. The identifier of the organization, as defined in Section 3.1. The
"role" attribute is used to represent the relationship that the "role" attribute is used to represent the relationship that the
organization has to the object. See Section 7.3 in organization has to the object. See Section 7.3 of [RFC8543] for
[ID.draft-ietf-regext-org] for a list of values. a list of values.
Example <info> response for an authorized client with multiple Example <info> response for an authorized client with multiple
organizations: organizations:
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 lang="en-US">Command completed successfully</msg> S: <msg lang="en-US">Command completed successfully</msg>
S: </result> S: </result>
skipping to change at page 8, line 23 skipping to change at page 8, line 29
4.2.1. EPP <create> Command 4.2.1. EPP <create> Command
This extension defines additional elements for the EPP <create> This extension defines additional elements for the EPP <create>
command described in the EPP object extensions. No additional command described in the EPP object extensions. No additional
elements are defined for the EPP <create> response. elements are defined for the EPP <create> response.
The EPP <create> command provides a transform operation that allows a The EPP <create> command provides a transform operation that allows a
client to create an object. In addition to the EPP command elements client to create an object. In addition to the EPP command elements
described in the EPP object extensions, the command MUST contain an described in the EPP object extensions, the command MUST contain an
<extension> element, and the <extension> element MUST contain a child <extension> element, and the <extension> element MUST contain a child
<orgext:create> element. This element or its ancestor element MUST <orgext:create> element. This element is used if the client wants to
identify the extension namespace "urn:ietf:params:xml:ns:epp:orgext- associate data defined in this extension to the object. This element
1.0" if the client wants to associate data defined in this extension or its ancestor element MUST identify the extension namespace
to the object. The <orgext:create> element contains the following "urn:ietf:params:xml:ns:epp:orgext-1.0". The <orgext:create> element
child elements: contains the following child elements:
o One or more <orgext:id> elements that contain the identifier of o One or more <orgext:id> elements that contain the identifier of
the organization, as defined in Section 3.1. The "role" attribute the organization, as defined in Section 3.1. The "role" attribute
is used to represent the relationship that the organization has to is used to represent the relationship that the organization has to
the object. See Section 7.3 in [ID.draft-ietf-regext-org] for a the object. See Section 7.3 of [RFC8543] for a list of values.
list of values.
Example <create> Command with only one organization: Example <create> command with only one organization:
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>example.com</domain:name> C: <domain:name>example.com</domain:name>
C: <domain:period unit="y">3</domain:period> C: <domain:period unit="y">3</domain:period>
C: <domain:ns> C: <domain:ns>
skipping to change at page 9, line 34 skipping to change at page 10, line 4
C: </create> C: </create>
C: <extension> C: <extension>
C: <orgext:create C: <orgext:create
C: xmlns:orgext="urn:ietf:params:xml:ns:epp:orgext-1.0"> C: xmlns:orgext="urn:ietf:params:xml:ns:epp:orgext-1.0">
C: <orgext:id role="reseller">reseller1523</orgext:id> C: <orgext:id role="reseller">reseller1523</orgext:id>
C: </orgext:create> C: </orgext:create>
C: </extension> C: </extension>
C: <clTRID>ABC-12345</clTRID> C: <clTRID>ABC-12345</clTRID>
C: </command> C: </command>
C:</epp> C:</epp>
Example <create> command with multiple organizations:
Example <create> Command with multiple organizations:
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>example.com</domain:name> C: <domain:name>example.com</domain:name>
C: <domain:period unit="y">3</domain:period> C: <domain:period unit="y">3</domain:period>
C: <domain:ns> C: <domain:ns>
skipping to change at page 11, line 17 skipping to change at page 11, line 17
This extension does not add any elements to the EPP <transfer> This extension does not add any elements to the EPP <transfer>
command or <transfer> response described in the EPP object mapping, command or <transfer> response described in the EPP object mapping,
but after a successful transfer of an object with an assigned but after a successful transfer of an object with an assigned
organization, the handling of the assigned organization is dependent organization, the handling of the assigned organization is dependent
on the organization roles and server policy. on the organization roles and server policy.
4.2.5. EPP <update> Command 4.2.5. EPP <update> Command
This extension defines additional elements for the EPP <update> This extension defines additional elements for the EPP <update>
command described in the EPP domain mapping [RFC5731], host mapping command described in the EPP domain mapping [RFC5731], host mapping
[RFC5732] and contact mapping [RFC5733]. No additional elements are [RFC5732], and contact mapping [RFC5733]. No additional elements are
defined for the EPP <update> response. defined for the EPP <update> response.
The EPP <update> command provides a transform operation that allows a The EPP <update> command provides a transform operation that allows a
client to modify the attributes of an object. In addition to the EPP client to modify the attributes of an object. In addition to the EPP
<update> command elements, the command MUST contain an <extension> <update> command elements, the command MUST contain an <extension>
element, and the <extension> element MUST contain a child element, and the <extension> element MUST contain a child
<orgext:update> element. This element or its ancestor element MUST <orgext:update> element. This element is used if the client wants to
identify the extension namespace "urn:ietf:params:xml:ns:epp:orgext- update the object with data defined in this extension. This element
1.0" if the client wants to update the object with data defined in or its ancestor element MUST identify the extension namespace
this extension. The <orgext:update> element contains the following "urn:ietf:params:xml:ns:epp:orgext-1.0". The <orgext:update> element
child elements: contains the following child elements:
o An OPTIONAL <orgext:add> element that contains one or more o An OPTIONAL <orgext:add> element that contains one or more
<orgext:id> elements, as defined in Section 3.1, that add non- <orgext:id> elements, as defined in Section 3.1, that add
existent organization roles to the object. The <orgext:id> nonexistent organization roles to the object. The <orgext:id>
element MUST have a non-empty organization identifier value. The element MUST have a non-empty organization identifier value. The
server SHOULD validate that the <orgext:id> element role does not server SHOULD validate that the <orgext:id> element role does not
exist. exist.
o An OPTIONAL <orgext:rem> element that contains one or more o An OPTIONAL <orgext:rem> element that contains one or more
<orgext:id> elements, as defined in Section 3.1, that remove <orgext:id> elements, as defined in Section 3.1, that remove
organization roles from the object. The <orgext:id> element MAY organization roles from the object. The <orgext:id> element MAY
have an empty organization identifier value. The server SHOULD have an empty organization identifier value. The server SHOULD
validate the existence of the <orgext:id> element role and the validate the existence of the <orgext:id> element role and the
organization identifier if provided. organization identifier if provided.
o An OPTIONAL <orgext:chg> element that contains one or more o An OPTIONAL <orgext:chg> element that contains one or more
<orgext:id> elements, as defined in Section 3.1, that change <orgext:id> elements, as defined in Section 3.1, that change
organization role identifiers for the object. The existing organization role identifiers for the object. The existing
organization identifier value will be replaced for the defined organization identifier value will be replaced for the defined
role. The server SHOULD validate the existence of the <orgext:id> role. The server SHOULD validate the existence of the <orgext:id>
element role. element role.
At least one <orgext:add>, <orgext:rem> or <orgext:chg> element MUST At least one <orgext:add>, <orgext:rem>, or <orgext:chg> element MUST
be provided. be provided.
Example <update> command, adding a reseller: Example <update> command, adding a reseller:
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: <update> C: <update>
C: <domain:update C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
skipping to change at page 15, line 16 skipping to change at page 15, line 16
An EPP error response MUST be returned if an <update> command cannot An EPP error response MUST be returned if an <update> command cannot
be processed for any reason. An attempt to add one organization ID be processed for any reason. An attempt to add one organization ID
or multiple organization IDs with a particular role value when at or multiple organization IDs with a particular role value when at
least one of them already exists does not change the object at all. least one of them already exists does not change the object at all.
A server SHOULD notify clients that object relationships exist by A server SHOULD notify clients that object relationships exist by
sending a 2305 error response code. An attempt to remove an sending a 2305 error response code. An attempt to remove an
organization ID or multiple organization IDs with a particular role organization ID or multiple organization IDs with a particular role
value when at least one of them does not exist does not change the value when at least one of them does not exist does not change the
object at all. A server SHOULD notify clients that object object at all. A server SHOULD notify clients that object
relationships does not exist by sending a 2305 error response code. relationships do not exist by sending a 2305 error response code. An
An attempt to change an organization ID or multiple organization IDs attempt to change an organization ID or multiple organization IDs
with a particular role value when at least one of them does not exist with a particular role value when at least one of them does not exist
does not change the object at all. A server SHOULD notify clients does not change the object at all. A server SHOULD notify clients
that object relationships does not exist by sending a 2305 error that object relationships do not exist by sending a 2305 error
response code. Response format with error value elements is defined response code. Response format with error value elements is defined
in Section 2.6 of [RFC5730]. in Section 2.6 of [RFC5730].
5. Formal Syntax 5. Formal Syntax
An EPP object mapping is specified in XML Schema notation. The An EPP object mapping is specified in XML Schema notation. The
formal syntax presented here is a complete schema representation of formal syntax presented here is a complete schema representation of
the object mapping suitable for automated validation of EPP XML the object mapping suitable for automated validation of EPP XML
instances. The BEGIN and END tags are not part of the schema; they 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 are used to note the beginning and ending of the schema for URI
skipping to change at page 15, line 49 skipping to change at page 16, line 4
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" elementFormDefault="qualified"
> >
<annotation> <annotation>
<documentation> <documentation>
Extensible Provisioning Protocol v1.0 Extensible Provisioning Protocol v1.0
Organization Extension Schema v1.0 Organization Extension Schema v1.0
</documentation> </documentation>
</annotation> </annotation>
<!-- Child elements found in EPP commands -->
<!-- Child elements found in EPP commands. -->
<element <element
name="create" name="create"
type="orgext:createType"/> type="orgext:createType"/>
<element <element
name="update" name="update"
type="orgext:updateType"/> type="orgext:updateType"/>
<!-- <!--
Organization identifier with required role Organization identifier with required role
--> -->
skipping to change at page 16, line 26 skipping to change at page 16, line 27
<extension base="token"> <extension base="token">
<attribute <attribute
name="role" name="role"
type="token" type="token"
use="required"/> use="required"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
<!-- <!--
Child elements of the <orgext:create> command Child elements of the <orgext:create> command.
All elements must be present at time of creation All elements must be present at time of creation.
--> -->
<complexType name="createType"> <complexType name="createType">
<sequence> <sequence>
<!-- agent identifier or the organization, <!-- Agent identifier or the organization,
e.g. registrar, reseller, privacy proxy, etc. --> e.g., registrar, reseller, privacy proxy, etc. -->
<element <element
name="id" name="id"
type="orgext:orgIdType" type="orgext:orgIdType"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
Child elements of <orgext:update> command Child elements of <orgext:update> command
--> -->
skipping to change at page 17, line 17 skipping to change at page 17, line 19
<element <element
name="chg" name="chg"
type="orgext:addRemChgType" type="orgext:addRemChgType"
minOccurs="0" minOccurs="0"
/> />
</sequence> </sequence>
</complexType> </complexType>
<complexType name="addRemChgType"> <complexType name="addRemChgType">
<sequence> <sequence>
<!-- agent identifier of the organization, <!-- Agent identifier of the organization,
e.g. registrar, reseller, privacy proxy, etc. --> e.g., registrar, reseller, privacy proxy, etc. -->
<element <element
name="id" name="id"
type="orgext:orgIdType" type="orgext:orgIdType"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- Child response element --> <!-- Child response element -->
<element <element
name="infData" name="infData"
type="orgext:infDataType"/> type="orgext:infDataType"/>
<!-- <orgext:infData> response elements --> <!-- <orgext:infData> response elements -->
<complexType name="infDataType"> <complexType name="infDataType">
<sequence> <sequence>
<!-- agent identifier the organization, <!-- Agent identifier the organization,
e.g. registrar, reseller, privacy proxy, etc. --> e.g., registrar, reseller, privacy proxy, etc. -->
<element <element
name="id" name="id"
type="orgext:orgIdType" type="orgext:orgIdType"
minOccurs="0" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- End of schema. --> <!-- End of schema -->
</schema> </schema>
END END
6. Internationalization Considerations 6. 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 [UNICODE] and its more
representations including UTF-8. Conformant XML processors recognize compact representations, including UTF-8. Conformant XML processors
both UTF-8 and UTF-16. Though XML includes provisions to identify recognize both UTF-8 [RFC3629] and UTF-16 [RFC2781]. Though XML
and use other character encodings through use of an "encoding" includes provisions to identify and use other character encodings
attribute in an <?xml?> declaration, use of UTF-8 is RECOMMENDED. through use of an "encoding" attribute in an <?xml?> declaration, use
of UTF-8 is RECOMMENDED.
As an extension of the EPP object mapping, the elements, element As an extension of the EPP object mapping, the elements and element
content described in this document MUST inherit the content described in this document MUST inherit the
internationalization conventions used to represent higher-layer internationalization conventions used to represent higher-layer
domain and core protocol structures present in an XML instance that domain and core protocol structures present in an XML instance that
includes this extension. includes this extension.
7. IANA Considerations 7. IANA Considerations
7.1. XML Namespace 7.1. XML Namespace
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 has
requested to assignment the following URI. assigned the following URI.
Registration request for the organization extension namespace: The organization extension namespace:
URI: urn:ietf:params:xml:ns:epp:orgext-1.0 URI: urn:ietf:params:xml:ns:epp:orgext-1.0
Registrant Contact: IESG Registrant Contact: IESG
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the organization XML schema: The organization XML schema:
URI: urn:ietf:params:xml:schema:epp:orgext-1.0 URI: urn:ietf:params:xml:schema:epp:orgext-1.0
Registrant Contact: IESG Registrant Contact: IESG
XML: See the "Formal Syntax" section of this document. XML: See the "Formal Syntax" section of RFC 8544 (this document).
7.2. EPP Extension Registry 7.2. EPP Extension Registry
The EPP extension described in this document should be registered by The EPP extension described in this document has been registered by
the IANA in the EPP Extension Registry described in [RFC7451]. The IANA in the "Extensions for the Extensible Provisioning Protocol
details of the registration are as follows: (EPP)" registry described in [RFC7451]. The details of the
registration are as follows:
Name of Extension: Organization Extension for the Extensible Name of Extension: Organization Extension for the Extensible
Provisioning Protocol (EPP) Provisioning Protocol (EPP)
Document status: Standards Track
Reference: RFCXXXX (please replace "XXXX" with the RFC number for Document Status: Standards Track
this document after a number is assigned by the RFC Editor)
Reference: RFC 8544
Registrant Name and Email Address: IESG, iesg@ietf.org Registrant Name and Email Address: IESG, iesg@ietf.org
TLDs: Any TLDs: Any
IPR Disclosure: None IPR Disclosure: None
Status: Active Status: Active
Notes: None Notes: None
8. Implementation Status 8. Security Considerations
Note to RFC Editor: Please remove this section and the reference to
[RFC7942] before publication. This section records the status of
known implementations of the protocol defined by this specification
at the time of posting of this Internet-Draft, and is based on a
proposal described in [RFC7942]. The description of implementations
in this section is intended to assist the IETF in its decision
processes in progressing drafts to RFCs. Please note that the
listing of any individual implementation here does not imply
endorsement by the IETF. Furthermore, no effort has been spent to
verify the information presented here that was supplied by IETF
contributors. This is not intended as, and must not be construed to
be, a catalog of available implementations or their features.
Readers are advised to note that other implementations may exist.
According to [RFC7942], "this will allow reviewers and working groups
to assign due consideration to documents that have the benefit of
running code, which may serve as evidence of valuable experimentation
and feedback that have made the implemented protocols more mature.
It is up to the individual working groups to use this information as
they see fit".
8.1. Verisign EPP SDK
Organization: Verisign Inc.
Name: Verisign EPP SDK
Description: The Verisign EPP SDK includes both a full client
implementation and a full server stub implementation of draft-ietf-
regext-org-ext.
Level of maturity: Development
Coverage: All aspects of the protocol are implemented.
Licensing: GNU Lesser General Public License
Contact: jgould@verisign.com
URL: https://www.verisign.com/en_US/channel-resources/domain-
registry-products/epp-sdks
8.2. CNNIC Implementation
Organization: CNNIC
Name: Organization Extension for EPP
Description: CNNIC is trying to update organization extension from
previous reseller extension according to this document.
Level of maturity: Development
Coverage: Organization extension for EPP
Contact: zhouguiqing@cnnic.cn
9. 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
considerations beyond those described by [RFC5730], [RFC5731], considerations beyond those described by [RFC5730], [RFC5731],
[RFC5732] and [RFC5733] or those caused by the protocol layers used [RFC5732], and [RFC5733] or those caused by the protocol layers used
by EPP. by EPP.
10. Acknowledgment 9. References
The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick
Mevzek, Antoin Verschuren and Scott Hollenbeck for their careful
review and valuable comments.
11. References
11.1. Normative References 9.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>.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November
2003, <https://www.rfc-editor.org/info/rfc3629>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
<https://www.rfc-editor.org/info/rfc5730>. <https://www.rfc-editor.org/info/rfc5730>.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731, Domain Name Mapping", STD 69, RFC 5731,
skipping to change at page 21, line 26 skipping to change at page 20, line 22
<https://www.rfc-editor.org/info/rfc5731>. <https://www.rfc-editor.org/info/rfc5731>.
[RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732,
August 2009, <https://www.rfc-editor.org/info/rfc5732>. August 2009, <https://www.rfc-editor.org/info/rfc5732>.
[RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733,
August 2009, <https://www.rfc-editor.org/info/rfc5733>. August 2009, <https://www.rfc-editor.org/info/rfc5733>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016,
<https://www.rfc-editor.org/info/rfc7942>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[W3C.REC-xml-20040204] [UNICODE] The Unicode Consortium, "The Unicode Standard",
<http://www.unicode.org/versions/latest/>.
[W3C.REC-xml-20081126]
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 (Fifth
Edition)", World Wide Web Consortium FirstEdition REC-xml- Edition)", World Wide Web Consortium Recommendation
20040204", February 2004, REC-xml-20081126, November 2008,
<http://www.w3.org/TR/2004/REC-xml-20040204>. <https://www.w3.org/TR/xml/>.
[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 Wide
Wide Web Consortium Recommendation REC-xmlschema- Web Consortium Recommendation REC-xmlschema-1-20041028,
1-20041028", October 2004, October 2004,
<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>.
11.2. Informative References 9.2. Informative References
[ID.draft-ietf-dnsop-terminology-bis]
Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
Terminology", September 2018, <http://tools.ietf.org/html/
draft-ietf-dnsop-terminology-bis>.
[ID.draft-ietf-regext-org] [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO
Zhou, L., Kong, N., Zhou, G., Yao, J., and J. Gould, 10646", RFC 2781, DOI 10.17487/RFC2781, February 2000,
"Extensible Provisioning Protocol (EPP) Reseller Mapping", <https://www.rfc-editor.org/info/rfc2781>.
November 2018,
<http://tools.ietf.org/html/draft-ietf-regext-org>.
[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>.
Appendix A. Change Log [RFC8543] Zhou, L., Kong, N., Yao, J., Gould, J., and G. Zhou,
"Extensible Provisioning Protocol (EPP) Organization
Initial -00: Individual document submitted. Mapping", RFC 8543, DOI 10.17487/RFC8543, March 2019,
<https://www.rfc-editor.org/info/rfc8543>.
-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.
* 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 acknowledgment.
* 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.
Organization WG document-01: Added "Implementation Status" section.
Organization WG document-02: Accepted some of the feedbacks on the
mailing list. Modified the examples in the document.
Organization WG document-03:
* Updated typos.
* Changed some descriptions about <orgext:id> and role attribute.
* Modified the example of "domain with no organization".
* Updated section 8, adding implementation status of Verisign.
Organization WG document-04:
* Updated typos.
* Removed the example of <update> command, domain with no
organization.
* Updated references.
* Updated section 8 of implementation status.
Organization WG document-05:
* Removed the minOccurs="0" from the addRemChgType type of the
XML schema
* Removed the third paragraph of "Implementation Status".
* Remove the Informative Reference to draft-ietf-regext-reseller-
ext from the draft.
Organization WG document-06:
* Updated "Abstraction".
* Added "Query" for "<Transfer> Query Command".
* Change "Registrant Contact" to IESG in section 7.1.
* Modified section 7.2.
Organization WG document-07:
* Updated "Abstraction".
Organization WG document-08:
* Updated error codes of <update> response.
* Modified XML namespace and schema.
Organization WG document-09:
* Modified XML namespace and schema.
* Changed "Exactly one" to "At least one" in section 4.2.5.
Organization WG document-10:
* Updated the reseller id and dns proxy id in the document.
* Updated the full xml namespace.
* Updated the text of EPP <orgext:add>, <orgext:rem> and
<orgext:chg>.
* Added "Document satus" and "Reference" in section "EPP
Extension Registry".
Organization WG document-11: Acknowledgments
* Added the reference of draft-ietf-dnsop-terminology-bis. The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick
Mevzek, Antoin Verschuren, and Scott Hollenbeck for their careful
review and valuable comments.
Authors' Addresses Authors' Addresses
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
Email: zhoulinlin@cnnic.cn Email: zhoulinlin@cnnic.cn
skipping to change at page 26, line 4 skipping to change at page 22, line 35
Email: weijunkai@cnnic.cn Email: weijunkai@cnnic.cn
Jiankang Yao 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
Email: yaojk@cnnic.cn Email: yaojk@cnnic.cn
James Gould James Gould
Verisign, Inc. VeriSign, Inc.
12061 Bluemont Way 12061 Bluemont Way
Reston, VA 20190 Reston, VA 20190
US United States of America
Email: jgould@verisign.com Email: jgould@verisign.com
URI: http://www.verisign.com
 End of changes. 68 change blocks. 
363 lines changed or deleted 155 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/