draft-ietf-regext-org-12.txt   rfc8543.txt 
Internet Engineering Task Force L. Zhou Internet Engineering Task Force (IETF) L. Zhou
Internet-Draft CNNIC Request for Comments: 8543 CNNIC
Intended status: Standards Track N. Kong Category: Standards Track N. Kong
Expires: June 3, 2019 Consultant ISSN: 2070-1721 Consultant
G. Zhou
J. Yao J. Yao
CNNIC CNNIC
J. Gould J. Gould
Verisign, Inc. VeriSign, Inc.
November 30, 2018 G. Zhou
March 2019
Extensible Provisioning Protocol (EPP) Organization Mapping Extensible Provisioning Protocol (EPP) Organization Mapping
draft-ietf-regext-org-12
Abstract Abstract
This document describes an Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP)
mapping for provisioning and management of organization objects mapping for provisioning and management of organization objects
stored in a shared central repository. Specified in Extensible stored in a shared central repository.
Markup Language (XML), this extended mapping is applied to provide
additional features required for the provisioning of organizations.
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 3, 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/rfc8543.
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
skipping to change at page 2, line 23 skipping to change at page 2, line 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions Used in This Document . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4 3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4
3.2. Organization Roles . . . . . . . . . . . . . . . . . . . 4 3.2. Organization Roles . . . . . . . . . . . . . . . . . . . 4
3.2.1. Role Type . . . . . . . . . . . . . . . . . . . . . . 4 3.2.1. Role Type . . . . . . . . . . . . . . . . . . . . . . 4
3.2.2. Role Status . . . . . . . . . . . . . . . . . . . . . 4 3.2.2. Role Status . . . . . . . . . . . . . . . . . . . . . 4
3.2.3. Role Identifier . . . . . . . . . . . . . . . . . . . 4 3.2.3. Role Identifier . . . . . . . . . . . . . . . . . . . 4
3.3. Contact and Client Identifiers . . . . . . . . . . . . . 5 3.3. Contact and Client Identifiers . . . . . . . . . . . . . 5
3.4. Organization Status Values . . . . . . . . . . . . . . . 5 3.4. Organization Status Values . . . . . . . . . . . . . . . 5
3.5. Role Status Values . . . . . . . . . . . . . . . . . . . 6 3.5. Role Status Values . . . . . . . . . . . . . . . . . . . 7
3.6. Parent Identifier . . . . . . . . . . . . . . . . . . . . 7 3.6. Parent Identifier . . . . . . . . . . . . . . . . . . . . 7
3.7. URL . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.7. URL . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.8. Dates and Times . . . . . . . . . . . . . . . . . . . . . 7 3.8. Dates and Times . . . . . . . . . . . . . . . . . . . . . 8
4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 8 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 8
4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 8 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 8
4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 8 4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 8
4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 10 4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 10
4.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 16 4.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 15
4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 16 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 16
4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 16 4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 16
4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 20 4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 20
4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 21 4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 21
4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 21 4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 21
4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 22 4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 21
4.3. Offline Review of Requested Actions . . . . . . . . . . . 26 4.3. Offline Review of Requested Actions . . . . . . . . . . . 25
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 28 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 27
6. Internationalization Considerations . . . . . . . . . . . . . 37 6. Internationalization Considerations . . . . . . . . . . . . . 36
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 37 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 36
7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 38 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 37
7.3. Role Type Values Registry . . . . . . . . . . . . . . . . 38 7.3. Role Type Values Registry . . . . . . . . . . . . . . . . 37
7.3.1. Registration Template . . . . . . . . . . . . . . . . 38 7.3.1. Registration Template . . . . . . . . . . . . . . . . 37
7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 38 7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 38
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 39 8. Security Considerations . . . . . . . . . . . . . . . . . . . 38
8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 40 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 39
8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 40 9.1. Normative References . . . . . . . . . . . . . . . . . . 39
9. Security Considerations . . . . . . . . . . . . . . . . . . . 41 9.2. Informative References . . . . . . . . . . . . . . . . . 40
10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 41 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 41
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 41 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 41
11.1. Normative References . . . . . . . . . . . . . . . . . . 41
11.2. Informative References . . . . . . . . . . . . . . . . . 42
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 43
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46
1. Introduction 1. Introduction
There are many entities, such as registrars, resellers, DNS service There are many entities, such as registrars, resellers, DNS service
operators, or privacy proxies involved in the domain registration operators, and privacy proxies, involved in the domain registration
business. These kind of entities have not been formally defined as business. These kinds of entities have not been formally defined as
having an object in Extensible Provisioning Protocol (EPP). This having an object in Extensible Provisioning Protocol (EPP). This
document provides a way to specify them as "organization" entities. document provides a way to specify them as "organization" entities.
This document describes an organization object mapping for version This document describes an organization object mapping for version
1.0 of the EPP [RFC5730]. This mapping is specified using the XML 1.0 of the EPP [RFC5730]. This mapping is specified using XML 1.0 as
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 described in [W3C.REC-xmlschema-1-20041028] and
[W3C.REC-xmlschema-2-20041028]. [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 presented. character case presented.
The XML namespace prefix "org" is used for the namespace The XML namespace prefix "org" is used for the namespace
"urn:ietf:params:xml:ns:epp:org-1.0", but implementations MUST NOT "urn:ietf:params:xml:ns:epp:org-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
An EPP organization object has attributes and associated values that An EPP organization object has attributes and associated values that
can be viewed and modified by the sponsoring client or the server. can be viewed and modified by the sponsoring client or the server.
This section describes each attribute type in detail. The formal This section describes each attribute type in detail. The formal
syntax for the attribute values described here can be found in the syntax for the attribute values described here can be found in the
"Formal Syntax" section of this document and in the appropriate "Formal Syntax" section of this document and in the appropriate
normative references. normative references.
3.1. Organization Identifier 3.1. Organization Identifier
All EPP organizations are identified by a server-unique identifier. All EPP organizations are identified by a server-unique identifier.
Organization identifiers are character strings with a specified Organization identifiers are character strings with a specified
minimum length, a specified maximum length, and a specified format. minimum length, a specified maximum length, and a specified format.
Organization identifiers use the "clIDType" client identifier syntax Organization identifiers use the "clIDType" client identifier syntax
described in [RFC5730]. Its corresponding element is <org:id>. described in [RFC5730]. The corresponding element is <org:id>.
3.2. Organization Roles 3.2. Organization Roles
The organization roles are used to represent the relationship an The organization roles are used to represent the relationship an
organization could have. Its corresponding element is <org:role>. organization could have. The corresponding element is <org:role>.
An organization object MUST always have at least one associated role. An organization object MUST always have at least one associated role.
Roles can be set only by the client that sponsors an organization Roles can be set only by the client that sponsors an organization
object. A client can change the role of an organization object using object. A client can change the role of an organization object using
the EPP <update> command. the EPP <update> command (see Section 4.2.5).
3.2.1. Role Type 3.2.1. Role Type
An organization role MUST have a type field. This may have any of An organization role MUST have a type field, which may have any of
the values listed in Section 7.3. An organization could have the values listed in Section 7.3. The corresponding element is
multiple roles with different role types. Its corresponding element <org:type>. An organization could have multiple roles with different
is <org:type>. role types.
3.2.2. Role Status 3.2.2. Role Status
A role of an organization object MAY have its own statuses. Its A role of an organization object MAY have its own statuses. The
corresponding element is <org:status>. The values of the role status corresponding element is <org:status>. The possible values for the
are defined in Section 3.5. role status are defined in Section 3.5.
3.2.3. Role Identifier 3.2.3. Role Identifier
A role MAY have a third-party-assigned identifier such as the IANA ID A role MAY have a third-party-assigned identifier such as the IANA ID
for registrars. Its corresponding element is <org:roleID>. for registrars. The corresponding element is <org:roleID>.
Example of organization role identifier: Example of organization role identifier:
<org:role> <org:role>
<org:type>registrar</org:type> <org:type>registrar</org:type>
<org:status>ok</org:status> <org:status>ok</org:status>
<org:status>linked</org:status> <org:status>linked</org:status>
<org:roleID>1362</org:roleID> <org:roleID>1362</org:roleID>
</org:role> </org:role>
skipping to change at page 5, line 32 skipping to change at page 5, line 32
A client MUST NOT alter server status values set by the server. A A client MUST NOT alter server status values set by the server. A
server MAY alter or override status values set by a client, subject server MAY alter or override status values set by a client, subject
to local server policies. The status of an object MAY change as a to local server policies. The status of an object MAY change as a
result of either a client-initiated transform command or an action result of either a client-initiated transform command or an action
performed by a server operator. performed by a server operator.
Status values that can be added or removed by a client are prefixed Status values that can be added or removed by a client are prefixed
with "client". Corresponding server status values that can be added with "client". Corresponding server status values that can be added
or removed by a server are prefixed with "server". The "hold" and or removed by a server are prefixed with "server". The "hold" and
"terminated" status values are server-managed when the organization "terminated" status values are server managed when the organization
has no parent identifier [Section 3.6] and otherwise MAY be client- has no parent identifier (Section 3.6) and otherwise MAY be client
managed based on server policy. Other status values that do not managed based on server policy. Other status values that do not
begin with either "client" or "server" are server-managed. begin with either "client" or "server" are server managed.
Status Value Descriptions: Status Value Descriptions:
o ok: This is the normal status value for an object that has no o ok: This is the normal status value for an object that has no
operations pending or active prohibitions. This value is set and operations pending or active prohibitions. This value is set and
removed by the server as other status values are added or removed. removed by the server as other status values are added or removed.
o hold: Organization transform commands and new links MUST be o hold: Organization transform commands and new links MUST be
rejected. rejected.
o terminated: The organization which has been terminated MUST NOT be o terminated: The organization that has been terminated MUST NOT be
linked. Organization transform commands and new links MUST be linked. Organization transform commands and new links MUST be
rejected. rejected.
o linked: The organization object has at least one active o linked: The organization object has at least one active
association with another object. The "linked" status is not association with another object. The "linked" status is not
explicitly set by the client. Servers should provide services to explicitly set by the client. Servers should provide services to
determine existing object associations. determine existing object associations.
o clientLinkProhibited, serverLinkProhibited: Requests to add new o clientLinkProhibited, serverLinkProhibited: Requests to add new
links to the organization MUST be rejected. links to the organization MUST be rejected.
skipping to change at page 6, line 25 skipping to change at page 6, line 28
o pendingCreate, pendingUpdate, pendingDelete: A transform command o pendingCreate, pendingUpdate, pendingDelete: A transform command
has been processed for the object, but the action has not been has been processed for the object, but the action has not been
completed by the server. Server operators can delay action completed by the server. Server operators can delay action
completion for a variety of reasons, such as to allow for human completion for a variety of reasons, such as to allow for human
review or third-party action. A transform command that is review or third-party action. A transform command that is
processed, but whose requested action is pending, is noted with processed, but whose requested action is pending, is noted with
response code 1001. response code 1001.
"pendingCreate", "ok", "hold", and "terminated" are mutually "pendingCreate", "ok", "hold", and "terminated" are mutually
exclusive statuses. Organization MUST have exactly one of these exclusive statuses. An organization MUST have exactly one of these
statuses set. statuses set.
"ok" status MAY only be combined with "linked" status. "ok" status MAY only be combined with "linked" status.
A client or server MAY combine "linked" with either A client or server MAY combine "linked" with either
"clientLinkProhibited" or "serverLinkProhibited" if new links must be "clientLinkProhibited" or "serverLinkProhibited" if new links must be
prohibited. prohibited.
"pendingDelete" status MUST NOT be combined with either "pendingDelete" status MUST NOT be combined with either
"clientDeleteProhibited" or "serverDeleteProhibited" status. "clientDeleteProhibited" or "serverDeleteProhibited" status.
The pendingCreate, pendingDelete, and pendingUpdate status values The "pendingCreate", "pendingDelete", and "pendingUpdate" status
MUST NOT be combined with each other. values MUST NOT be combined with each other.
If "clientUpdateProhibited" or "serverUpdateProhibited" is set, the If "clientUpdateProhibited" or "serverUpdateProhibited" is set, the
client will not be able to update the object. For client will not be able to update the object. For
"clientUpdateProhibited", the client will first need to remove "clientUpdateProhibited", the client will first need to remove
"clientUpdateProhibited" prior to attempting to update the object. "clientUpdateProhibited" prior to attempting to update the object.
The server can modify the object at any time. The server can modify the object at any time.
3.5. Role Status Values 3.5. Role Status Values
A role SHOULD have at least one associated status value. Valid A role SHOULD have at least one associated status value. Valid
values include "ok", "linked", "clientLinkProhibited", and values include "ok", "linked", "clientLinkProhibited", and
"serverLinkProhibited". "serverLinkProhibited".
Status Value Descriptions: Status Value Descriptions:
o ok: This is the normal status value for an role that has no o ok: This is the normal status value for a role that has no
operations pending or active prohibitions. This value is set and operations pending or active prohibitions. This value is set and
removed by the server as other status values are added or removed. removed by the server as other status values are added or removed.
o linked: The role of an organization object has at least one active o linked: The role of an organization object has at least one active
association with another object. The "linked" status is not association with another object. The "linked" status is not
explicitly set by the client. Servers SHOULD provide services to explicitly set by the client. Servers SHOULD provide services to
determine existing object associations. determine existing object associations.
o clientLinkProhibited, serverLinkProhibited: Requests to add new o clientLinkProhibited, serverLinkProhibited: Requests to add new
links to the role MUST be rejected. links to the role MUST be rejected.
3.6. Parent Identifier 3.6. Parent Identifier
There can be more than one layer of organizations, such as a Organizations can have more than one layer. The parent identifier,
reseller. The parent identifier, as defined with the <org:parentId> as defined with the <org:parentId> element, represents the parent
element, represents the parent organization identifier in a child organization identifier in a child organization.
organization.
The case of reseller organizations provides an example. The parent The case of reseller organizations provides an example. The parent
identifier is not defined for the top level reseller, namely the identifier is not defined for the top-level reseller, namely the
registrar of the registry. An N-tier reseller has a parent reseller registrar of the registry. An N-tier reseller has a parent reseller
and at least one child reseller. A reseller customer has a parent and at least one child reseller. A reseller customer has a parent
reseller and no child resellers. reseller and no child resellers.
Loops MUST be prohibited. For example: if organization A has B as Loops MUST be prohibited. For example: if organization A has
its parent identifier, organization B cannot have organization A as organization B as its parent identifier, organization B cannot have
its parent identifier. The same is true for larger loops involving organization A as its parent identifier. The same is true for larger
three or more organizations. loops involving three or more organizations.
3.7. URL 3.7. URL
The URL represents the organization web home page, as defined with The URL represents the organization web home page, as defined with
the <org:url> element. the <org:url> element.
3.8. Dates and Times 3.8. Dates and Times
Date and time attribute values MUST be represented in Universal Date and time attribute values MUST be represented in Coordinated
Coordinated Time (UTC) using the Gregorian calendar. The extended Universal Time (UTC) using the Gregorian calendar. The extended
date-time form using upper case "T" and "Z" characters defined in date-time form using uppercase "T" and "Z" characters defined in
[W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time
values, as XML Schema does not support truncated date-time forms or values, as XML Schema does not support truncated date-time forms or
lower case "T" and "Z" characters. lowercase "T" and "Z" characters.
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 use in provisioning and mappings described here are specifically for use in provisioning and
managing organization information via EPP. managing organization information via EPP.
4.1. EPP Query Commands 4.1. EPP Query Commands
EPP provides two commands to retrieve organization information: EPP provides two commands to retrieve organization information:
<check> to determine if an organization object can be provisioned <check> to determine if an organization object can be provisioned
within a repository, and <info> to retrieve detailed information within a repository and <info> to retrieve detailed information
associated with an organization object. This document does not associated with an organization object. This document does not
define a mapping for the EPP <transfer> command to retrieve define a mapping for the EPP <transfer> command to retrieve
organization-object transfer status information. organization-object transfer status information.
4.1.1. EPP <check> Command 4.1.1. EPP <check> Command
The EPP <check> command is used to determine if an object can be The EPP <check> command is used to determine if an object can be
provisioned within a repository. It provides a hint that allows a provisioned within a repository. It provides a hint that allows a
client to anticipate the success or failure of provisioning an object client to anticipate the success or failure of provisioning an object
using the <create> command, as object-provisioning requirements are using the <create> command, as object-provisioning requirements are
skipping to change at page 10, line 40 skipping to change at page 10, line 42
S: </response> S: </response>
S:</epp> S:</epp>
An EPP error response MUST be returned if a <check> command cannot be An EPP error response MUST be returned if a <check> command cannot be
processed for any reason. processed for any reason.
4.1.2. EPP <info> Command 4.1.2. EPP <info> Command
The EPP <info> command is used to retrieve information associated The EPP <info> command is used to retrieve information associated
with an organization object. In addition to the standard EPP command with an organization object. In addition to the standard EPP command
elements, the <info> command MUST contain a <org:info> element. This elements, the <info> command MUST contain an <org:info> element.
element or its ancestor element MUST identify the organization This element or its ancestor element MUST identify the organization
namespace "urn:ietf:params:xml:ns:epp:org-1.0". The <org:info> namespace "urn:ietf:params:xml:ns:epp:org-1.0". The <org:info>
element contains the following child elements: element contains the following child element:
o An <org:id> element that contains the server-unique identifier of o An <org:id> element that contains the server-unique identifier of
the organization object to be queried. the organization object to be queried.
Example <info> command: Example <info> command:
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: <info> C: <info>
skipping to change at page 11, line 28 skipping to change at page 11, line 30
When an <info> command has been processed successfully, the EPP When an <info> command has been processed successfully, the EPP
<resData> element MUST contain a child <org:infData> element. This <resData> element MUST contain a child <org:infData> element. This
element or its ancestor element MUST identify the organization element or its ancestor element MUST identify the organization
namespace "urn:ietf:params:xml:ns:epp:org-1.0". The <org:infData> namespace "urn:ietf:params:xml:ns:epp:org-1.0". The <org:infData>
element contains the following child elements: element contains the following child elements:
o An <org:id> element that contains the server-unique identifier of o An <org:id> element that contains the server-unique identifier of
the organization object, as defined in Section 3.1. the organization object, as defined in Section 3.1.
o An <org:roid> element that contains the Repository Object o An <org:roid> element that contains the Repository Object
IDentifier assigned to the organization object when the object was Identifier assigned to the organization object when the object was
created. created.
o One or more <org:role> elements that contain the role type, role o One or more <org:role> elements that contain the role type, role
statuses and optional role id of the organization. statuses, and optional role ID of the organization.
* An <org:type> element that contains the type of the * An <org:type> element that contains the type of the
organization, as defined in Section 3.2. organization, as defined in Section 3.2.
* One or more <org:status> elements that contain the role * One or more <org:status> elements that contain the role
statuses. The values of the role status are defined in statuses. The values of the role status are defined in
Section 3.5. Section 3.5.
* An OPTIONAL <org:roleID> element that contains a third-party- * An OPTIONAL <org:roleID> element that contains a third-party-
assigned identifier, such as IANA ID for registrars, as defined assigned identifier, such as IANA ID for registrars, as defined
skipping to change at page 12, line 7 skipping to change at page 12, line 10
status of the organization, as defined in Section 3.4. status of the organization, as defined in Section 3.4.
o An OPTIONAL <org:parentId> element that contains the identifier of o An OPTIONAL <org:parentId> element that contains the identifier of
the parent object, as defined in Section 3.6. the parent object, as defined in Section 3.6.
o Zero to two <org:postalInfo> elements that contain postal-address o Zero to two <org:postalInfo> elements that contain postal-address
information. Two elements are provided so that address information. Two elements are provided so that address
information can be provided in both internationalized and information can be provided in both internationalized and
localized forms; a "type" attribute is used to identify the two localized forms; a "type" attribute is used to identify the two
forms. If an internationalized form (type="int") is provided, forms. If an internationalized form (type="int") is provided,
element content MUST be represented in a subset of Unicode in the element content MUST be represented in a subset of Unicode
range U+0020 - U+007E. If a localized form (type="loc") is [UNICODE] in the range U+0020 - U+007E. If a localized form
provided, element content MAY be represented in unrestricted UTF- (type="loc") is provided, element content MAY be represented in
8. The <org:postalInfo> element contains the following child unrestricted UTF-8. The <org:postalInfo> element contains the
elements: following child elements:
* An <org:name> element that contains the name of the * An <org:name> element that contains the name of the
organization. organization.
* An OPTIONAL <org:addr> element that contains address * An OPTIONAL <org:addr> element that contains address
information associated with the organization. A <org:addr> information associated with the organization. An <org:addr>
element contains the following child elements: element contains the following child elements:
+ One, two, or three <org:street> elements that contain the + One, two, or three <org:street> elements that contain the
organization's street address. organization's street address.
+ An <org:city> element that contains the organization's city. + An <org:city> element that contains the organization's city.
+ An OPTIONAL <org:sp> element that contains the + An OPTIONAL <org:sp> element that contains the
organization's state or province. organization's state or province.
+ An OPTIONAL <org:pc> element that contains the + An OPTIONAL <org:pc> element that contains the
organization's postal code. organization's postal code.
+ An <org:cc> element that contains the alpha-2 organization's + An <org:cc> element that contains the alpha-2 organization's
country code. The detailed format of this element is country code. The detailed format of this element is
described in section 2.4.3 of [RFC5733]. described in Section 2.4.3 of [RFC5733].
o An OPTIONAL <org:voice> element that contains the organization's o An OPTIONAL <org:voice> element that contains the organization's
voice telephone number. The detailed format of this element is voice telephone number. The detailed format of this element is
described in Section 2.5 of [RFC5733]. described in Section 2.5 of [RFC5733].
o An OPTIONAL <org:fax> element that contains the organization's o An OPTIONAL <org:fax> element that contains the organization's
facsimile telephone number. facsimile telephone number. The detailed format of this element
is described in Section 2.5 of [RFC5733].
o An OPTIONAL <org:email> element that contains the organization's o An OPTIONAL <org:email> element that contains the organization's
email address. The detailed format of this element is described email address. The detailed format of this element is described
in section 2.6 of [RFC5733]. in [RFC5322].
o An OPTIONAL <org:url> element that contains the URL to the website o An OPTIONAL <org:url> element that contains the URL to the website
of the organization. The detailed format of this element is of the organization. The detailed format of this element is
described in [RFC3986]. described in [RFC3986].
o Zero or more <org:contact> elements that contain identifiers for o Zero or more <org:contact> elements that contain identifiers for
the contact objects to be associated with the organization object. the contact objects to be associated with the organization object.
Contact object identifiers MUST be known to the server before the Contact object identifiers MUST be known to the server before the
contact object can be associated with the organization object. contact object can be associated with the organization object.
The required "type" is used to represent contact types. The type The required "type" is used to represent contact types. The type
values include "admin", "tech", "billing", "abuse", and "custom". values include "admin", "tech", "billing", "abuse", and "custom".
The OPTIONAL "typeName" attribute is used to define the name of a The OPTIONAL "typeName" attribute is used to define the name of a
"custom" type. "custom" type.
o An OPTIONAL <org:clID> element that contains the organization o An OPTIONAL <org:clID> element that contains the organization
identifier of the sponsoring client. There is no <org:clID> identifier of the sponsoring client. There is no <org:clID>
element if the organization is managed by the registry. element if the organization is managed by the registry.
skipping to change at page 13, line 31 skipping to change at page 13, line 33
o An <org:upID> element that contains the identifier of the client o An <org:upID> element that contains the identifier of the client
that last updated the organization object. This element MUST NOT that last updated the organization object. This element MUST NOT
be present if the organization has never been modified. be present if the organization has never been modified.
o An <org:upDate> element that contains the date and time of the o An <org:upDate> element that contains the date and time of the
most recent organization object modification. This element MUST most recent organization object modification. This element MUST
NOT be present if the organization object has never been modified. NOT be present if the organization object has never been modified.
Example <info> response for "Example Registrar Inc." organization Example <info> response for "Example Registrar Inc." organization
organization object with identifier "registrar1362": object with identifier "registrar1362":
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">Command completed successfully</msg> S: <msg lang="en">Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <org:infData S: <org:infData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0"> S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
skipping to change at page 14, line 23 skipping to change at page 14, line 24
S: </org:postalInfo> S: </org:postalInfo>
S: <org:voice x="1234">+1.7035555555</org:voice> S: <org:voice x="1234">+1.7035555555</org:voice>
S: <org:fax>+1.7035555556</org:fax> S: <org:fax>+1.7035555556</org:fax>
S: <org:email>contact@organization.example</org:email> S: <org:email>contact@organization.example</org:email>
S: <org:url>https://organization.example</org:url> S: <org:url>https://organization.example</org:url>
S: <org:contact type="admin">sh8013</org:contact> S: <org:contact type="admin">sh8013</org:contact>
S: <org:contact type="billing">sh8013</org:contact> S: <org:contact type="billing">sh8013</org:contact>
S: <org:contact type="custom" S: <org:contact type="custom"
S: typeName="legal">sh8013</org:contact> S: typeName="legal">sh8013</org:contact>
S: <org:crID>ClientX</org:crID> S: <org:crID>ClientX</org:crID>
S: <org:crDate>1999-04-03T22:00:00.0Z</org:crDate> S: <org:crDate>2018-04-03T22:00:00.0Z</org:crDate>
S: <org:upID>ClientX</org:upID> S: <org:upID>ClientX</org:upID>
S: <org:upDate>1999-12-03T09:00:00.0Z</org:upDate> S: <org:upDate>2018-12-03T09:00:00.0Z</org:upDate>
S: </org:infData> S: </org:infData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID> S: <svTRID>54322-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
Example <info> response for "Example Reseller Inc." organization Example <info> response for "Example Reseller Inc." organization
skipping to change at page 15, line 39 skipping to change at page 15, line 25
S: <org:sp>VA</org:sp> S: <org:sp>VA</org:sp>
S: <org:pc>20166-6503</org:pc> S: <org:pc>20166-6503</org:pc>
S: <org:cc>US</org:cc> S: <org:cc>US</org:cc>
S: </org:addr> S: </org:addr>
S: </org:postalInfo> S: </org:postalInfo>
S: <org:fax>+1.7035555556</org:fax> S: <org:fax>+1.7035555556</org:fax>
S: <org:url>https://organization.example</org:url> S: <org:url>https://organization.example</org:url>
S: <org:contact type="admin">sh8013</org:contact> S: <org:contact type="admin">sh8013</org:contact>
S: <org:clID>1362</org:clID> S: <org:clID>1362</org:clID>
S: <org:crID>ClientX</org:crID> S: <org:crID>ClientX</org:crID>
S: <org:crDate>1999-04-03T22:00:00.0Z</org:crDate> S: <org:crDate>2018-04-03T22:00:00.0Z</org:crDate>
S: <org:upID>ClientX</org:upID> S: <org:upID>ClientX</org:upID>
S: <org:upDate>1999-12-03T09:00:00.0Z</org:upDate> S: <org:upDate>2018-12-03T09:00:00.0Z</org:upDate>
S: </org:infData> S: </org:infData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID> S: <svTRID>54322-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
An EPP error response MUST be returned if an <info> command cannot be An EPP error response MUST be returned if an <info> command cannot be
processed for any reason. processed for any reason.
4.1.3. EPP <transfer> Query Command 4.1.3. EPP <transfer> Query Command
The transfer semantics does not apply to organization object. No EPP The transfer semantics do not apply to organization objects. No EPP
<transfer> query command is defined in this document. <transfer> query command is defined in this document.
4.2. EPP Transform Commands 4.2. EPP Transform Commands
This document provides three commands to transform organization This document provides three commands to transform organization
object information: <create> to create an instance of an organization object information: <create> to create an instance of an organization
object, <delete> to delete an instance of an organization object, and object, <delete> to delete an instance of an organization object, and
<update> to change information associated with an organization <update> to change information associated with an organization
object. This document does not define a mapping for the EPP object. This document does not define a mapping for the EPP
<transfer> and <renew> command. <transfer> and <renew> command.
skipping to change at page 16, line 29 skipping to change at page 16, line 24
Transform commands are typically processed and completed in real Transform commands are typically processed and completed in real
time. Server operators MAY receive and process transform commands time. Server operators MAY receive and process transform commands
but defer completing the requested action if human or third-party but defer completing the requested action if human or third-party
review is required before the requested action can be completed. In review is required before the requested action can be completed. In
such situations, the server MUST return a 1001 response code to the such situations, the server MUST return a 1001 response code to the
client to note that the command has been received and processed but client to note that the command has been received and processed but
that the requested action is pending. The server MUST also manage that the requested action is pending. The server MUST also manage
the status of the object that is the subject of the command to the status of the object that is the subject of the command to
reflect the initiation and completion of the requested action. Once reflect the initiation and completion of the requested action. Once
the action has been completed, the client MUST be notified using a the action has been completed, the client MUST be notified using a
service message that the action has been completed and that the service message that the action has been completed and the status of
status of the object has changed. Other notification methods MAY be the object has changed. Other notification methods MAY be used in
used in addition to the required service message. addition to the required service message.
4.2.1. EPP <create> Command 4.2.1. EPP <create> Command
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 organization object. In addition to the standard client to create an organization object. In addition to the standard
EPP command elements, the <create> command MUST contain a EPP command elements, the <create> command MUST contain an
<org:create> element. This element or its ancestor element MUST <org:create> element. This element or its ancestor element MUST
identify the organization namespace "urn:ietf:params:xml:ns:epp:org- identify the organization namespace "urn:ietf:params:xml:ns:epp:org-
1.0". The <org:create> element contains the following child 1.0". The <org:create> element contains the following child
elements: elements:
o An <org:id> element that contains the desired server-unique o An <org:id> element that contains the desired server-unique
identifier for the organization to be created, as defined in identifier for the organization to be created, as defined in
Section 3.1. Section 3.1.
o One or more <org:role> elements that contain the role type, role o One or more <org:role> elements that contain the role type, role
statuses and optional role id of the organization. statuses, and optional role ID of the organization.
* An <org:type> element that contains the type of the * An <org:type> element that contains the type of the
organization, as defined in Section 3.2. organization, as defined in Section 3.2.
* Zero or more <org:status> elements that contain the role * Zero or more <org:status> elements that contain the role
statuses. The values of the role status are defined in statuses. The possible values of the role statuses are defined
Section 3.5. in Section 3.5.
* An OPTIONAL <org:roleID> element that contains a third-party- * An OPTIONAL <org:roleID> element that contains a third-party-
assigned identifier, such as IANA ID for registrars, as defined assigned identifier, such as IANA ID for registrars, as defined
in Section 3.2.3. in Section 3.2.3.
o Zero or more <org:status> elements that contain the operational o Zero or more <org:status> elements that contain the operational
status of the organization, as defined in Section 3.4. status of the organization, as defined in Section 3.4.
o An OPTIONAL <org:parentId> element that contains the identifier of o An OPTIONAL <org:parentId> element that contains the identifier of
the parent object, as defined in Section 3.6. the parent object, as defined in Section 3.6.
o Zero to two <org:postalInfo> elements that contain postal-address o Zero to two <org:postalInfo> elements that contain postal-address
information. Two elements are provided so that address information. Two elements are provided so that address
information can be provided in both internationalized and information can be provided in both internationalized and
localized forms; a "type" attribute is used to identify the two localized forms; a "type" attribute is used to identify the two
forms. If an internationalized form (type="int") is provided, forms. If an internationalized form (type="int") is provided,
element content MUST be represented in a subset of Unicode in the element content MUST be represented in a subset of Unicode
range U+0020 - U+007E. If a localized form (type="loc") is [UNICODE] in the range U+0020 - U+007E. If a localized form
provided, element content MAY be represented in unrestricted UTF- (type="loc") is provided, element content MAY be represented in
8. The <org:postalInfo> element contains the following child unrestricted UTF-8. The <org:postalInfo> element contains the
elements: following child elements:
* An <org:name> element that contains the name of the * An <org:name> element that contains the name of the
organization. organization.
* An OPTIONAL <org:addr> element that contains address * An OPTIONAL <org:addr> element that contains address
information associated with the organization. A <org:addr> information associated with the organization. An <org:addr>
element contains the following child elements: element contains the following child elements:
+ One, two, or three <org:street> elements that contain the + One, two, or three <org:street> elements that contain the
organization's street address. organization's street address.
+ An <org:city> element that contains the organization's city. + An <org:city> element that contains the organization's city.
+ An OPTIONAL <org:sp> element that contains the + An OPTIONAL <org:sp> element that contains the
organization's state or province. organization's state or province.
+ An OPTIONAL <org:pc> element that contains the + An OPTIONAL <org:pc> element that contains the
organization's postal code. organization's postal code.
+ An <org:cc> element that contains the alpha-2 organization's + An <org:cc> element that contains the alpha-2 organization's
country code. The detailed format of this element is country code. The detailed format of this element is
described in section 2.4.3 of [RFC5733]. described in Section 2.4.3 of [RFC5733].
o An OPTIONAL <org:voice> element that contains the organization's o An OPTIONAL <org:voice> element that contains the organization's
voice telephone number. The detailed format of this element is voice telephone number. The detailed format of this element is
described in Section 2.5 of [RFC5733] described in Section 2.5 of [RFC5733].
o An OPTIONAL <org:fax> element that contains the organization's o An OPTIONAL <org:fax> element that contains the organization's
facsimile telephone number. facsimile telephone number. The detailed format of this element
is described in Section 2.5 of [RFC5733].
o An OPTIONAL <org:email> element that contains the organization's o An OPTIONAL <org:email> element that contains the organization's
email address. The detailed format of this element is described email address. The detailed format of this element is described
in section 2.6 of [RFC5733]. of [RFC5322].
o An OPTIONAL <org:url> element that contains the URL to the website o An OPTIONAL <org:url> element that contains the URL to the website
of the organization. The detailed format of this element is of the organization. The detailed format of this element is
described in [RFC3986]. described in [RFC3986].
o Zero or more <org:contact> elements that contain identifiers for o Zero or more <org:contact> elements that contain identifiers for
the contact objects associated with the organization object. the contact objects associated with the organization object.
Example <create> command: Example <create> command:
skipping to change at page 20, line 15 skipping to change at page 19, line 31
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">Command completed successfully</msg> S: <msg lang="en">Command completed successfully</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <org:creData S: <org:creData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0"> S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id>res1523</org:id> S: <org:id>res1523</org:id>
S: <org:crDate>1999-04-03T22:00:00.0Z</org:crDate> S: <org:crDate>2018-04-03T22:00:00.0Z</org:crDate>
S: </org:creData> S: </org:creData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
An EPP error response MUST be returned if a <create> command cannot An EPP error response MUST be returned if a <create> command cannot
skipping to change at page 22, line 10 skipping to change at page 21, line 38
4.2.4. EPP <transfer> Command 4.2.4. EPP <transfer> Command
Transfer semantics do not apply to organization objects, so there is Transfer semantics do not apply to organization objects, so there is
no mapping defined for the EPP <transfer> command. no mapping defined for the EPP <transfer> command.
4.2.5. EPP <update> Command 4.2.5. EPP <update> Command
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 organization object. In client to modify the attributes of an organization object. In
addition to the standard EPP command elements, the <update> command addition to the standard EPP command elements, the <update> command
MUST contain a <org:update> element. This element or its ancestor MUST contain an <org:update> element. This element or its ancestor
element MUST identify the organization namespace element MUST identify the organization namespace
"urn:ietf:params:xml:ns:epp:org-1.0". The <org:update> element "urn:ietf:params:xml:ns:epp:org-1.0". The <org:update> element
contains the following child elements: contains the following child elements:
o An <org:id> element that contains the server-unique identifier of o An <org:id> element that contains the server-unique identifier of
the organization object to be updated, as defined in Section 3.1. the organization object to be updated, as defined in Section 3.1.
o An OPTIONAL <org:add> element that contains attribute values to be o An OPTIONAL <org:add> element that contains attribute values to be
added to the object. added to the object.
o An OPTIONAL <org:rem> element that contains attribute values to be o An OPTIONAL <org:rem> element that contains attribute values to be
removed from the object. removed from the object.
o An OPTIONAL <org:chg> element that contains attribute values to be o An OPTIONAL <org:chg> element that contains attribute values to be
changed. changed.
At least one <org:add>, <org:rem> or <org:chg> element MUST be At least one <org:add>, <org:rem>, or <org:chg> element MUST be
provided if the command is not being extended. All of these elements provided if the command is not being extended. All of these elements
MAY be omitted if an <update> extension is present. The OPTIONAL MAY be omitted if an <update> extension is present. The OPTIONAL
<org:add> and <org:rem> elements contain the following child <org:add> and <org:rem> elements contain the following child
elements: elements:
o Zero or more <org:contact> elements that contain the identifiers o Zero or more <org:contact> elements that contain the identifiers
for contact objects to be associated with or removed from the for contact objects to be associated with or removed from the
organization object. Contact object identifiers MUST be known to organization object. Contact object identifiers MUST be known to
the server before the contact object can be associated with the the server before the contact object can be associated with the
organization object. organization object.
o Zero or more <org:role> elements that contain the role type, role o Zero or more <org:role> elements that contain the role type, role
statuses and optional role id of the organization. statuses, and optional role ID of the organization.
* An <org:type> element that contains the role type of the * An <org:type> element that contains the role type of the
organization, as defined in Section 3.2. The role type organization, as defined in Section 3.2. The role type
uniquely identifies the role to update. uniquely identifies the role to update.
* Zero or more <org:status> elements that contain the role * Zero or more <org:status> elements that contain the role
statuses. The values of the role status are defined in statuses. The values of the role status are defined in
Section 3.5. Section 3.5.
* An OPTIONAL <org:roleID> element that contains a third-party- * An OPTIONAL <org:roleID> element that contains a third-party-
skipping to change at page 23, line 19 skipping to change at page 22, line 49
where at least one child element MUST be present: where at least one child element MUST be present:
o An OPTIONAL <org:parentId> element that contains the identifier of o An OPTIONAL <org:parentId> element that contains the identifier of
the parent object. the parent object.
o Zero to two <org:postalInfo> elements that contain postal-address o Zero to two <org:postalInfo> elements that contain postal-address
information. Two elements are provided so that address information. Two elements are provided so that address
information can be provided in both internationalized and information can be provided in both internationalized and
localized forms; a "type" attribute is used to identify the two localized forms; a "type" attribute is used to identify the two
forms. If an internationalized form (type="int") is provided, forms. If an internationalized form (type="int") is provided,
element content MUST be represented in a subset of Unicode in the element content MUST be represented in a subset of Unicode
range U+0020 - U+007E. If a localized form (type="loc") is [UNICODE] in the range U+0020 - U+007E. If a localized form
provided, element content MAY be represented in unrestricted UTF- (type="loc") is provided, element content MAY be represented in
8. The change of the postal info is defined as a replacement of unrestricted UTF-8. The change of the postal info is defined as a
that postal info element with the contents of the sub-elements replacement of that postal info element with the contents of the
included in the update command. An empty <org:postalInfo> element sub-elements included in the <update> command. An empty
is supported to allow a type of postal info to be removed. The <org:postalInfo> element is supported to allow a type of postal
<org:postalInfo> element contains the following child elements: info to be removed. The <org:postalInfo> element contains the
following child elements:
* An <org:name> element that contains the name of the * An <org:name> element that contains the name of the
organization. organization.
* An OPTIONAL <org:addr> element that contains address * An OPTIONAL <org:addr> element that contains address
information associated with the organization. A <org:addr> information associated with the organization. An <org:addr>
element contains the following child elements: element contains the following child elements:
+ One, two, or three <org:street> elements that contain the + One, two, or three <org:street> elements that contain the
organization's street address. organization's street address.
+ An <org:city> element that contains the organization's city. + An <org:city> element that contains the organization's city.
+ An OPTIONAL <org:sp> element that contains the + An OPTIONAL <org:sp> element that contains the
organization's state or province. organization's state or province.
+ An OPTIONAL <org:pc> element that contains the + An OPTIONAL <org:pc> element that contains the
organization's postal code. organization's postal code.
+ An <org:cc> element that contains the alpha-2 organization's + An <org:cc> element that contains the alpha-2 organization's
country code. The detailed format of this element is country code. The detailed format of this element is
described in section 2.4.3 of [RFC5733]. described in Section 2.4.3 of [RFC5733].
o An OPTIONAL <org:voice> element that contains the organization's o An OPTIONAL <org:voice> element that contains the organization's
voice telephone number. The detailed format of this element is voice telephone number. The detailed format of this element is
described in Section 2.5 of [RFC5733] described in Section 2.5 of [RFC5733].
o An OPTIONAL <org:fax> element that contains the organization's o An OPTIONAL <org:fax> element that contains the organization's
facsimile telephone number. facsimile telephone number. The detailed format of this element
is described in Section 2.5 of [RFC5733].
o An OPTIONAL <org:email> element that contains the organization's o An OPTIONAL <org:email> element that contains the organization's
email address. The detailed format of this element is described email address. The detailed format of this element is described
in section 2.6 of [RFC5733]. in [RFC5322].
o An OPTIONAL <org:url> element that contains the URL to the website o An OPTIONAL <org:url> element that contains the URL to the website
of the organization. The detailed format of this element is of the organization. The detailed format of this element is
described in [RFC3986] described in [RFC3986].
Example <update> command: Example <update> command:
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: <org:update C: <org:update
C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0"> C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id> C: <org:id>res1523</org:id>
skipping to change at page 27, line 16 skipping to change at page 25, line 52
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="1001"> S: <result code="1001">
S: <msg lang="en">Command completed successfully; S: <msg lang="en">Command completed successfully;
S: action pending</msg> S: action pending</msg>
S: </result> S: </result>
S: <resData> S: <resData>
S: <org:creData S: <org:creData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0"> S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id>res1523</org:id> S: <org:id>res1523</org:id>
S: <org:crDate>1999-04-03T22:00:00.0Z</org:crDate> S: <org:crDate>2018-04-03T22:00:00.0Z</org:crDate>
S: </org:creData> S: </org:creData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
The status of the organization object after returning this response The status of the organization object after returning this response
MUST include "pendingCreate". The server operator reviews the MUST include "pendingCreate". The server operator reviews the
request offline, and informs the client of the outcome of the review request offline and informs the client of the outcome of the review
by queuing a service message for retrieval via the <poll> command; it by queuing a service message for retrieval via the <poll> command; it
MAY additionally use an out-of-band mechanism to inform the client of MAY additionally use an out-of-band mechanism to inform the client of
the outcome. the outcome.
The service message MUST contain text that describes the notification The service message MUST contain text that describes the notification
in the child <msg> element of the response <msgQ> element. In in the child <msg> element of the response <msgQ> element. In
addition, the EPP <resData> element MUST contain a child addition, the EPP <resData> element MUST contain a child
<org:panData> element. This element or its ancestor element MUST <org:panData> element. This element or its ancestor element MUST
identify the organization namespace "urn:ietf:params:xml:ns:epp:org- identify the organization namespace "urn:ietf:params:xml:ns:epp:org-
1.0". The <org:panData> element contains the following child 1.0". The <org:panData> element contains the following child
skipping to change at page 28, line 20 skipping to change at page 27, line 6
Example "review completed" service message: Example "review completed" service message:
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="1301"> S: <result code="1301">
S: <msg lang="en">Command completed successfully; S: <msg lang="en">Command completed successfully;
S: ack to dequeue</msg> S: ack to dequeue</msg>
S: </result> S: </result>
S: <msgQ count="5" id="12345"> S: <msgQ count="5" id="12345">
S: <qDate>1999-04-04T22:01:00.0Z</qDate> S: <qDate>2018-04-04T22:01:00.0Z</qDate>
S: <msg>Pending action completed successfully.</msg> S: <msg>Pending action completed successfully.</msg>
S: </msgQ> S: </msgQ>
S: <resData> S: <resData>
S: <org:panData S: <org:panData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0"> S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id paResult="1">res1523</org:id> S: <org:id paResult="1">res1523</org:id>
S: <org:paTRID> S: <org:paTRID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID> S: <svTRID>54321-XYZ</svTRID>
S: </org:paTRID> S: </org:paTRID>
S: <org:paDate>1999-04-04T22:00:00.0Z</org:paDate> S: <org:paDate>2018-04-04T22:00:00.0Z</org:paDate>
S: </org:panData> S: </org:panData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>BCD-23456</clTRID> S: <clTRID>BCD-23456</clTRID>
S: <svTRID>65432-WXY</svTRID> S: <svTRID>65432-WXY</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
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
registration purposes. registration purposes.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:epp:org-1.0"
xmlns:org="urn:ietf:params:xml:ns:epp:org-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.
-->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<import namespace="urn:ietf:params:xml:ns:epp-1.0"/>
<annotation> <schema targetNamespace="urn:ietf:params:xml:ns:epp:org-1.0"
<documentation> xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0"
Extensible Provisioning Protocol v1.0 xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
organization provisioning schema. xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
</documentation> xmlns="http://www.w3.org/2001/XMLSchema"
</annotation> elementFormDefault="qualified">
<!-- <!--
Child elements found in EPP commands. Import common element types.
--> -->
<element name="create" type="org:createType"/> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<element name="delete" type="org:sIDType"/> <import namespace="urn:ietf:params:xml:ns:epp-1.0"/>
<element name="update" type="org:updateType"/> <annotation>
<element name="check" type="org:mIDType"/> <documentation>
<element name="info" type="org:infoType"/> Extensible Provisioning Protocol v1.0
<element name="panData" type="org:panDataType"/> organization provisioning schema.
</documentation>
</annotation>
<!-- <!--
Utility types. Child elements found in EPP commands.
--> -->
<simpleType name="statusType"> <element name="create" type="org:createType"/>
<restriction base="token"> <element name="delete" type="org:sIDType"/>
<enumeration value="ok"/> <element name="update" type="org:updateType"/>
<enumeration value="hold"/> <element name="check" type="org:mIDType"/>
<enumeration value="terminated"/> <element name="info" type="org:infoType"/>
<enumeration value="clientDeleteProhibited"/> <element name="panData" type="org:panDataType"/>
<enumeration value="clientUpdateProhibited"/>
<enumeration value="clientLinkProhibited"/>
<enumeration value="linked"/>
<enumeration value="pendingCreate"/>
<enumeration value="pendingUpdate"/>
<enumeration value="pendingDelete"/>
<enumeration value="serverDeleteProhibited"/>
<enumeration value="serverUpdateProhibited"/>
<enumeration value="serverLinkProhibited"/>
</restriction>
</simpleType>
<simpleType name="roleStatusType"> <!--
<restriction base="token"> Utility types.
<enumeration value="ok"/> -->
<enumeration value="clientLinkProhibited"/> <simpleType name="statusType">
<enumeration value="linked"/> <restriction base="token">
<enumeration value="serverLinkProhibited"/> <enumeration value="ok"/>
</restriction> <enumeration value="hold"/>
</simpleType> <enumeration value="terminated"/>
<enumeration value="clientDeleteProhibited"/>
<enumeration value="clientUpdateProhibited"/>
<enumeration value="clientLinkProhibited"/>
<enumeration value="linked"/>
<enumeration value="pendingCreate"/>
<enumeration value="pendingUpdate"/>
<enumeration value="pendingDelete"/>
<enumeration value="serverDeleteProhibited"/>
<enumeration value="serverUpdateProhibited"/>
<enumeration value="serverLinkProhibited"/>
</restriction>
</simpleType>
<complexType name="roleType"> <simpleType name="roleStatusType">
<sequence> <restriction base="token">
<element name="type" type="token"/> <enumeration value="ok"/>
<element name="status" type="org:roleStatusType" <enumeration value="clientLinkProhibited"/>
minOccurs="0" maxOccurs="3"/> <enumeration value="linked"/>
<element name="roleID" type="token" minOccurs="0"/> <enumeration value="serverLinkProhibited"/>
</sequence> </restriction>
</complexType> </simpleType>
<complexType name="postalInfoType"> <complexType name="roleType">
<sequence> <sequence>
<element name="name" <element name="type" type="token"/>
type="org:postalLineType"/> <element name="status" type="org:roleStatusType"
<element name="addr" minOccurs="0" maxOccurs="3"/>
type="org:addrType" minOccurs="0"/> <element name="roleID" type="token" minOccurs="0"/>
</sequence> </sequence>
<attribute name="type" </complexType>
type="org:postalInfoEnumType"
use="required"/>
</complexType>
<complexType name="contactType"> <complexType name="postalInfoType">
<simpleContent> <sequence>
<extension base="eppcom:clIDType"> <element name="name"
<attribute name="type" type="org:contactAttrType" type="org:postalLineType"/>
use="required"/> <element name="addr"
<attribute name="typeName" type="token"/> type="org:addrType" minOccurs="0"/>
</extension> </sequence>
</simpleContent> <attribute name="type"
</complexType> type="org:postalInfoEnumType"
use="required"/>
</complexType>
<simpleType name="contactAttrType"> <complexType name="contactType">
<restriction base="token"> <simpleContent>
<enumeration value="admin"/> <extension base="eppcom:clIDType">
<enumeration value="billing"/> <attribute name="type" type="org:contactAttrType"
<enumeration value="tech"/> use="required"/>
<enumeration value="abuse"/> <attribute name="typeName" type="token"/>
<enumeration value="custom"/> </extension>
</restriction> </simpleContent>
</simpleType> </complexType>
<complexType name="e164Type"> <simpleType name="contactAttrType">
<simpleContent> <restriction base="token">
<extension base="org:e164StringType"> <enumeration value="admin"/>
<attribute name="x" type="token" /> <enumeration value="billing"/>
</extension> <enumeration value="tech"/>
</simpleContent> <enumeration value="abuse"/>
</complexType> <enumeration value="custom"/>
</restriction>
</simpleType>
<simpleType name="e164StringType"> <complexType name="e164Type">
<restriction base="token"> <simpleContent>
<pattern value="(\+[0-9]{1,3}\.[0-9]{1,14})?" /> <extension base="org:e164StringType">
<maxLength value="17" /> <attribute name="x" type="token"/>
</restriction> </extension>
</simpleType> </simpleContent>
</complexType>
<simpleType name="e164StringType">
<restriction base="token">
<pattern value="(\+[0-9]{1,3}\.[0-9]{1,14})?"/>
<maxLength value="17"/>
</restriction>
</simpleType>
<simpleType name="postalLineType"> <simpleType name="postalLineType">
<restriction base="normalizedString"> <restriction base="normalizedString">
<minLength value="1" /> <minLength value="1"/>
<maxLength value="255" /> <maxLength value="255"/>
</restriction> </restriction>
</simpleType> </simpleType>
<simpleType name="optPostalLineType"> <simpleType name="optPostalLineType">
<restriction base="normalizedString"> <restriction base="normalizedString">
<maxLength value="255" /> <maxLength value="255"/>
</restriction> </restriction>
</simpleType> </simpleType>
<simpleType name="pcType"> <simpleType name="pcType">
<restriction base="token"> <restriction base="token">
<maxLength value="16" /> <maxLength value="16"/>
</restriction> </restriction>
</simpleType> </simpleType>
<simpleType name="ccType"> <simpleType name="ccType">
<restriction base="token"> <restriction base="token">
<length value="2" /> <length value="2"/>
</restriction> </restriction>
</simpleType> </simpleType>
<complexType name="addrType">
<sequence>
<element name="street" type="org:optPostalLineType"
minOccurs="0" maxOccurs="3" />
<element name="city" type="org:postalLineType" />
<element name="sp" type="org:optPostalLineType"
minOccurs="0" />
<element name="pc" type="org:pcType"
minOccurs="0" />
<element name="cc" type="org:ccType" />
</sequence>
</complexType>
<simpleType name="postalInfoEnumType"> <complexType name="addrType">
<restriction base="token"> <sequence>
<enumeration value="loc" /> <element name="street" type="org:optPostalLineType"
<enumeration value="int" /> minOccurs="0" maxOccurs="3"/>
</restriction> <element name="city" type="org:postalLineType"/>
</simpleType> <element name="sp" type="org:optPostalLineType"
minOccurs="0"/>
<element name="pc" type="org:pcType"
minOccurs="0"/>
<element name="cc" type="org:ccType"/>
</sequence>
</complexType>
<!-- <simpleType name="postalInfoEnumType">
Child element of commands that require only an identifier. <restriction base="token">
--> <enumeration value="loc"/>
<complexType name="sIDType"> <enumeration value="int"/>
<sequence> </restriction>
<element name="id" type="eppcom:clIDType"/> </simpleType>
</sequence>
</complexType>
<!-- <!--
Child element of commands that accept multiple identifiers. Child element of commands that require only an identifier.
--> -->
<complexType name="mIDType"> <complexType name="sIDType">
<sequence> <sequence>
<element name="id" <element name="id" type="eppcom:clIDType"/>
type="eppcom:clIDType" maxOccurs="unbounded"/> </sequence>
</sequence> </complexType>
</complexType>
<!-- <!--
Pending action notification response elements. Child element of commands that accept multiple identifiers.
--> -->
<complexType name="panDataType"> <complexType name="mIDType">
<sequence> <sequence>
<element name="id" type="org:paCLIDType"/> <element name="id"
<element name="paTRID" type="epp:trIDType"/> type="eppcom:clIDType" maxOccurs="unbounded"/>
<element name="paDate" type="dateTime"/> </sequence>
</sequence> </complexType>
</complexType> <!--
Pending action notification response elements.
-->
<complexType name="panDataType">
<sequence>
<element name="id" type="org:paCLIDType"/>
<element name="paTRID" type="epp:trIDType"/>
<element name="paDate" type="dateTime"/>
</sequence>
</complexType>
<complexType name="paCLIDType"> <complexType name="paCLIDType">
<simpleContent> <simpleContent>
<extension base="eppcom:clIDType"> <extension base="eppcom:clIDType">
<attribute name="paResult" type="boolean" <attribute name="paResult" type="boolean"
use="required"/> use="required"/>
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
<!-- <!--
Child elements of the <info> commands. Child elements of the <info> commands.
--> -->
<complexType name="infoType"> <complexType name="infoType">
<sequence> <sequence>
<element name="id" <element name="id"
type="eppcom:clIDType"/> type="eppcom:clIDType"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- <!--
Child elements of the <create> command. Child elements of the <create> command.
--> -->
<complexType name="createType"> <complexType name="createType">
<sequence> <sequence>
<element name="id" <element name="id"
type="eppcom:clIDType"/> type="eppcom:clIDType"/>
<element name="role" <element name="role"
type="org:roleType" maxOccurs="unbounded"/> type="org:roleType" maxOccurs="unbounded"/>
<element name="status" <element name="status"
type="org:statusType" minOccurs="0" maxOccurs="4"/> type="org:statusType" minOccurs="0" maxOccurs="4"/>
<element name="parentId" <element name="parentId"
type="eppcom:clIDType" minOccurs="0"/> type="eppcom:clIDType" minOccurs="0"/>
<element name="postalInfo" <element name="postalInfo"
type="org:postalInfoType" minOccurs="0" maxOccurs="2"/> type="org:postalInfoType" minOccurs="0" maxOccurs="2"/>
<element name="voice" <element name="voice"
type="org:e164Type" minOccurs="0"/> type="org:e164Type" minOccurs="0"/>
<element name="fax" <element name="fax"
type="org:e164Type" minOccurs="0"/> type="org:e164Type" minOccurs="0"/>
<element name="email" <element name="email"
type="eppcom:minTokenType" minOccurs="0"/> type="eppcom:minTokenType" minOccurs="0"/>
<element name="url" <element name="url"
type="anyURI" minOccurs="0"/> type="anyURI" minOccurs="0"/>
<element name="contact" <element name="contact"
type="org:contactType" type="org:contactType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</sequence> </sequence>
</complexType>
</complexType> <!--
Child elements of the <update> command.
-->
<complexType name="updateType">
<sequence>
<element name="id"
type="eppcom:clIDType"/>
<element name="add"
type="org:addRemType" minOccurs="0"/>
<element name="rem"
type="org:addRemType" minOccurs="0"/>
<element name="chg"
type="org:chgType" minOccurs="0"/>
</sequence>
<!-- </complexType>
Child elements of the <update> command.
-->
<complexType name="updateType">
<sequence>
<element name="id"
type="eppcom:clIDType"/>
<element name="add"
type="org:addRemType" minOccurs="0"/>
<element name="rem"
type="org:addRemType" minOccurs="0"/>
<element name="chg"
type="org:chgType" minOccurs="0"/>
</sequence>
</complexType>
<!-- <!--
Data elements that can be added or removed. Data elements that can be added or removed.
--> -->
<complexType name="addRemType"> <complexType name="addRemType">
<sequence> <sequence>
<element name="contact" <element name="contact"
type="org:contactType" minOccurs="0" maxOccurs="unbounded"/> type="org:contactType" minOccurs="0"
<element name="role" type="org:roleType" maxOccurs="unbounded"/>
minOccurs="0" maxOccurs="unbounded"/> <element name="role" type="org:roleType"
<element name="status" type="org:statusType" minOccurs="0" maxOccurs="unbounded"/>
minOccurs="0" maxOccurs="9"/> <element name="status" type="org:statusType"
</sequence> minOccurs="0" maxOccurs="9"/>
</complexType> </sequence>
</complexType>
<!-- <!--
Data elements that can be changed. Data elements that can be changed.
--> -->
<complexType name="chgType"> <complexType name="chgType">
<sequence> <sequence>
<element name="parentId" <element name="parentId"
type="eppcom:clIDType" minOccurs="0"/> type="eppcom:clIDType" minOccurs="0"/>
<element name="postalInfo" <element name="postalInfo"
type="org:chgPostalInfoType" type="org:chgPostalInfoType"
minOccurs="0" maxOccurs="2"/> minOccurs="0" maxOccurs="2"/>
<element name="voice" <element name="voice"
type="org:e164Type" minOccurs="0"/> type="org:e164Type" minOccurs="0"/>
<element name="fax" <element name="fax"
type="org:e164Type" minOccurs="0"/> type="org:e164Type" minOccurs="0"/>
<element name="email" <element name="email"
type="eppcom:minTokenType" minOccurs="0"/> type="eppcom:minTokenType" minOccurs="0"/>
<element name="url"
type="anyURI" minOccurs="0"/>
</sequence>
</complexType>
<element name="url" <complexType name="chgPostalInfoType">
type="anyURI" minOccurs="0"/> <sequence>
</sequence> <element name="name"
</complexType> type="org:postalLineType" minOccurs="0"/>
<element name="addr"
type="org:addrType" minOccurs="0"/>
</sequence>
<attribute name="type"
type="org:postalInfoEnumType" use="required"/>
</complexType>
<complexType name="chgPostalInfoType"> <!--
<sequence> Child response elements.
<element name="name" -->
type="org:postalLineType" minOccurs="0"/> <element name="chkData" type="org:chkDataType"/>
<element name="addr" <element name="creData" type="org:creDataType"/>
type="org:addrType" minOccurs="0"/> <element name="infData" type="org:infDataType"/>
</sequence>
<attribute name="type"
type="org:postalInfoEnumType" use="required"/>
</complexType>
<!-- <!--
Child response elements. <check> response elements.
--> -->
<element name="chkData" type="org:chkDataType"/> <complexType name="chkDataType">
<element name="creData" type="org:creDataType"/> <sequence>
<element name="infData" type="org:infDataType"/> <element name="cd" type="org:checkType"
maxOccurs="unbounded" />
</sequence>
</complexType>
<!-- <complexType name="checkType">
<check> response elements. <sequence>
--> <element name="id" type="org:checkIDType"/>
<complexType name="chkDataType"> <element name="reason" type="eppcom:reasonType"
<sequence> minOccurs="0"/>
<element name="cd" type="org:checkType" </sequence>
maxOccurs="unbounded" /> </complexType>
</sequence>
</complexType>
<complexType name="checkType"> <complexType name="checkIDType">
<sequence> <simpleContent>
<element name="id" type="org:checkIDType" /> <extension base="eppcom:clIDType">
<element name="reason" type="eppcom:reasonType" <attribute name="avail" type="boolean"
minOccurs="0" /> use="required"/>
</sequence> </extension>
</complexType> </simpleContent>
</complexType>
<complexType name="checkIDType"> <!--
<simpleContent> <info> response elements.
<extension base="eppcom:clIDType"> -->
<attribute name="avail" type="boolean"
use="required" />
</extension>
</simpleContent>
</complexType> <complexType name="infDataType">
<sequence>
<element name="id"
type="eppcom:clIDType"/>
<element name="roid"
type="eppcom:roidType"/>
<element name="role"
type="org:roleType" maxOccurs="unbounded"/>
<element name="status"
type="org:statusType" maxOccurs="9"/>
<!-- <element name="parentId"
<info> response elements. type="eppcom:clIDType" minOccurs="0"/>
--> <element name="postalInfo"
<complexType name="infDataType"> type="org:postalInfoType" minOccurs="0" maxOccurs="2"/>
<sequence> <element name="voice"
<element name="id" type="org:e164Type" minOccurs="0"/>
type="eppcom:clIDType"/> <element name="fax"
<element name="roid" type="org:e164Type" minOccurs="0"/>
type="eppcom:roidType"/> <element name="email"
<element name="role" type="eppcom:minTokenType" minOccurs="0"/>
type="org:roleType" maxOccurs="unbounded"/> <element name="url"
<element name="status" type="anyURI" minOccurs="0"/>
type="org:statusType" maxOccurs="9"/> <element name="contact"
<element name="parentId" type="org:contactType" minOccurs="0"
type="eppcom:clIDType" minOccurs="0"/> maxOccurs="unbounded"/>
<element name="postalInfo" <element name="clID"
type="org:postalInfoType" minOccurs="0" maxOccurs="2"/> type="eppcom:clIDType" minOccurs="0"/>
<element name="voice" <element name="crID"
type="org:e164Type" minOccurs="0"/> type="eppcom:clIDType"/>
<element name="fax" <element name="crDate"
type="org:e164Type" minOccurs="0"/> type="dateTime"/>
<element name="email" <element name="upID"
type="eppcom:minTokenType" minOccurs="0"/> type="eppcom:clIDType" minOccurs="0"/>
<element name="url" <element name="upDate"
type="anyURI" minOccurs="0"/> type="dateTime" minOccurs="0"/>
<element name="contact" </sequence>
type="org:contactType" minOccurs="0" maxOccurs="unbounded"/> </complexType>
<element name="clID" <!--
type="eppcom:clIDType" minOccurs="0"/> <create> response elements.
<element name="crID" -->
type="eppcom:clIDType"/> <complexType name="creDataType">
<element name="crDate" <sequence>
type="dateTime"/> <element name="id" type="eppcom:clIDType"/>
<element name="upID" <element name="crDate" type="dateTime"/>
type="eppcom:clIDType" minOccurs="0"/> </sequence>
<element name="upDate" </complexType>
type="dateTime" minOccurs="0"/>
</sequence>
</complexType>
<!--
<create> response elements.
-->
<complexType name="creDataType">
<sequence>
<element name="id" type="eppcom:clIDType" />
<element name="crDate" type="dateTime" />
</sequence> <!--
</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 [RFC3629] and UTF-16 [RFC2781]. Though XML includes recognize both UTF-8 [RFC3629] and UTF-16 [RFC2781]. Though XML
provisions to identify and use other character encodings through use includes provisions to identify and use other character encodings
of an "encoding" attribute in an <?xml?> declaration, use of UTF-8 is through use of an "encoding" attribute in an <?xml?> declaration, use
RECOMMENDED. of UTF-8 is RECOMMENDED.
As an extension of the EPP organization object mapping, the elements As an extension of the EPP organization object mapping, the elements
and element content described in this document MUST inherit the and element 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 namespace: The organization namespace:
URI: urn:ietf:params:xml:ns:epp:org-1.0 URI: urn:ietf:params:xml:ns:epp:org-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:org-1.0 URI: urn:ietf:params:xml:schema:epp:org-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 8543 (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: Extensible Provisioning Protocol (EPP) Name of Extension: Extensible Provisioning Protocol (EPP)
Organization Mapping Organization Mapping
Document status: Standards Track Document status: Standards Track
Reference: RFCXXXX (please replace "XXXX" with the RFC number for Reference: RFC 8543
this document after a number is assigned by the RFC Editor)
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
7.3. Role Type Values Registry 7.3. Role Type Values Registry
IANA has created a new category of protocol registry for values of IANA has created a new category of protocol registry for values of
the organization roles. The name of this registry is "EPP the organization roles. The name of this registry is "EPP
Organization Role Values". The registration policy for this registry Organization Role Values". The registration policy for this registry
is "Expert Review" [RFC8126]. is "Expert Review" [RFC8126].
7.3.1. Registration Template 7.3.1. Registration Template
Value: the string value being registered. Value: The string value being registered.
Description: Brief description of the organization role values. Description: Brief description of the organization role values.
Registrant Name: For IETF RFCs, state "IESG". For others, give the Registrant Name: For RFC specifications, state "IESG". For other
name of the responsible party. specifications, give the name of the responsible party.
Registrant Contact Information: an email address, postal address, or Registrant Contact Information: An email address, postal address, or
some other information to be used to contact the registrant. some other information to be used to contact the registrant.
7.3.2. Initial Registry Contents 7.3.2. Initial Registry Contents
Followings are the initial registry contents: The following are the initial registry contents:
Value: registrar Value: registrar
Description: The entity object instance represents the authority Description: The entity object instance represents the authority
responsible for the registration in the registry. responsible for the registration in the registry.
Registrant Name: IESG Registrant: IESG, iesg@ietf.org
Registrant Contact Information: iesg@ietf.org
Value: reseller Value: reseller
Description: The entity object instance represents a third party Description: The entity object instance represents a third party
through which the registration was conducted (i.e., not the through which the registration was conducted (i.e., not the
registry or registrar). registry or registrar).
Registrant Name: IESG Registrant: IESG, iesg@ietf.org
Registrant Contact Information: iesg@ietf.org
Value: privacyproxy Value: privacyproxy
Description: The entity object instance represents a third-party Description: The entity object instance represents a third party
who could help to register a domain without exposing the who could help to register a domain without exposing the
registrants' private information. registrants' private information.
Registrant Name: IESG Registrant: IESG, iesg@ietf.org
Registrant Contact Information: iesg@ietf.org
Value: dns-operator Value: dns-operator
Description: The entity object instance represents a third-party Description: The entity object instance represents a third-party
DNS operator that maintains the name servers and zone data on DNS operator that maintains the name servers and zone data on
behalf of a registrant. behalf of a registrant.
Registrant Name: IESG Registrant: IESG, iesg@ietf.org
Registrant Contact Information: iesg@ietf.org
8. Implementation Status
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.
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: EPP Organization Mapping
Description: CNNIC is trying to update EPP organization mapping from
previous reseller mapping according to this document.
Level of maturity: Development
Coverage: EPP organization mapping
Contact: zhouguiqing@cnnic.cn
9. Security Considerations 8. Security Considerations
The organization object may have personally identifiable information, The organization object may have personally identifiable information,
such as <org:contact>. This information is not a required element in such as <org:contact>. This information is not a required element in
this document which can be provided on a voluntary basis. If it is this document that can be provided on a voluntary basis. If it is
provided, both client and server MUST ensure that authorization provided, both client and server MUST ensure that authorization
information is stored and exchanged with high-grade encryption information is stored and exchanged with high-grade encryption
mechanisms to provide privacy services, which is specified in mechanisms to provide privacy services, which are specified in
[RFC5733]. The security considerations described in [RFC5730] or [RFC5733]. The security considerations described in [RFC5730] or
those caused by the protocol layers used by EPP will apply to this those caused by the protocol layers used by EPP will apply to this
specification as well. specification as well.
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 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November
2003, <https://www.rfc-editor.org/info/rfc3629>. 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>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005, RFC 3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>. <https://www.rfc-editor.org/info/rfc3986>.
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322,
DOI 10.17487/RFC5322, October 2008,
<https://www.rfc-editor.org/info/rfc5322>.
[RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646,
September 2009, <https://www.rfc-editor.org/info/rfc5646>. September 2009, <https://www.rfc-editor.org/info/rfc5646>.
[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>.
[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>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
[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
[RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO
10646", RFC 2781, DOI 10.17487/RFC2781, February 2000, 10646", RFC 2781, DOI 10.17487/RFC2781, February 2000,
<https://www.rfc-editor.org/info/rfc2781>. <https://www.rfc-editor.org/info/rfc2781>.
[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 Acknowledgments
Initial -00: Individual document submitted.
-01:
* Updated abstract text.
* Added sentences to avoid loop of parent identifiers in section
3.4.
* Revised typos in section 3.6.
* Added explanation of contact type attribute in section 4.1.2.
* Updated <info> responses.
* Deleted description of <transfer> command in section 4.1 and
4.2.
* Deleted whoisInfo disclose type in XML schema.
* Deleted maxOccurs of addRemType.
* Deleted extra "OPTIONAL" in section 4.2.5.
* Updated typos in <update> response.
-02:
* Changed author information.
* Updated url definition.
* Updated XML schema.
-03:
* Changed author information.
* Updated section 3.1.
* Refactoried the XSD file. Added <chgPostalInfoType> element.
* Added acknowledgment.
WG document-00: WG document submitted
WG document-01: Keep document alive for further discussion.
Reseller object or entity object with multiple roles?
Organization WG document-00: Change to a generic organization object
mapping.
Organization WG document-01: Added "Implementation Status" section.
Organization WG document-02: Accepted some of the feedbacks on the
mailing list.
Organization WG document-03:
* Updated section 3.2, changed the structure of organization
role.
* Updated section 4.2.5 for the "add", "rem" and "chg" example.
* Updated section 5 of formal syntax.
* Updated section 7.2 for the registration template and initial
values.
* Updated section 8 of implementation status.
Organization WG document-04:
* Updated section 3.2, changed the structure of organization
role.
* Updated references.
* Updated section 8 of implementation status.
Organization WG document-05:
* Updated the description of <org:status> of a role.
* Removed the third paragraph of "Implementation Status".
* Remove the Informative Reference to draft-ietf-regext-reseller
from the draft.
Organization WG document-06:
* Updated typos.
* Added "Query" for "<Transfer> Query Command".
* Change "Registrant Contact" to IESG in section 7.1.
* Modified section 7.2.
Organization WG document-07:
* Updated typos.
* Added dns-operator in section 7.1.
* Added "OPTIONAL" for <org:addr>
Organization WG document-08:
* Updated "Offline Review of Requested Actions".
Organization WG document-09:
* Updated "This element or its ancestor element MUST identify the
organization namespace." in section 4.1.1 and other parts of
this document.
* Updated text in section 2 match RFC 8174.
* Modified "roleid" to "roleID".
* Updated text about loops in section 3.6.
* Referred section 2.5 of RFC5733 for voice format.
* Updated XML schema for the maxOccurs value of "reason" element.
* Updated section 7.3.
* Replaced "http" with "https" in the examples.
* Updated writing typos.
* Modified XML namespace and schema.
Organization WG document-10:
* Modified XML namespace and schema.
* Removed the maxOccurs value of "reason" element.
Organization WG document-11:
* Typo of RFC2781 and moved this reference in "Informative
References".
* "Loops MUST be prohibited." in section 3.6.
Organization WG document-12:
* Removed "OPTIONAL" when "zero or more" or "zero to two"
appears.
* Updated the "Organization Status Values" text.
* Updated the full xml namespace.
* Updated the text in "Offline review".
* Updated the text in "Security Considerations".
* Added "Document satus" and "Reference" in section "EPP
Extension Registry".
* Added references of RFC3688,RFC3986 and RFC5646. 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
Ning Kong Ning Kong
Consultant Consultant
Email: ietfing@gmail.com Email: ietfing@gmail.com
Guiqing Zhou
CNNIC
4 South 4th Street, Zhongguancun, Haidian District
Beijing, Beijing 100190
China
Email: zhouguiqing@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
Guiqing Zhou
Email: qing.joe@gmail.com
 End of changes. 150 change blocks. 
805 lines changed or deleted 559 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/