draft-ietf-regext-org-06.txt   draft-ietf-regext-org-07.txt 
Internet Engineering Task Force L. Zhou Internet Engineering Task Force L. Zhou
Internet-Draft N. Kong Internet-Draft N. Kong
Intended status: Standards Track G. Zhou Intended status: Standards Track G. Zhou
Expires: November 10, 2018 X. Lee Expires: December 17, 2018 X. Lee
CNNIC CNNIC
J. Gould J. Gould
Verisign, Inc. Verisign, Inc.
May 9, 2018 June 15, 2018
Extensible Provisioning Protocol (EPP) Organization Mapping Extensible Provisioning Protocol (EPP) Organization Mapping
draft-ietf-regext-org-06 draft-ietf-regext-org-07
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. Specified in Extensible
Markup Language (XML), this extended mapping is applied to provide Markup Language (XML), this extended mapping is applied to provide
additional features required for the provisioning of organizations. additional features required for the provisioning of organizations.
Status of This Memo Status of This Memo
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 10, 2018. This Internet-Draft will expire on December 17, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
skipping to change at page 2, line 40 skipping to change at page 2, line 40
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 . . . . . . . . . . . . . . . . . . . 6
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 . . . . . . . . . . . . . . . . . . . . . 7
4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7
4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7
4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 8 4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 8
4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 9 4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 10
4.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 15 4.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 15
4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 15 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 15
4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 15 4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 15
4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 19 4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 19
4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 20 4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 20
4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 20 4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 20
4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 21 4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 21
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 25 4.3. Offline Review of Requested Actions . . . . . . . . . . . 25
6. Internationalization Considerations . . . . . . . . . . . . . 33 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 27
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 6. Internationalization Considerations . . . . . . . . . . . . . 36
7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 33 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 34 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 36
7.3. Role Values Registry . . . . . . . . . . . . . . . . . . 34 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 36
7.3.1. Registration Template . . . . . . . . . . . . . . . . 34 7.3. Role Type Values Registry . . . . . . . . . . . . . . . . 37
7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 34 7.3.1. Registration Template . . . . . . . . . . . . . . . . 37
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 35 7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 37
8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 36 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 38
8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 36 8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 39
9. Security Considerations . . . . . . . . . . . . . . . . . . . 36 8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 39
10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 37 9. Security Considerations . . . . . . . . . . . . . . . . . . . 39
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 40
11.1. Normative References . . . . . . . . . . . . . . . . . . 37 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 40
11.2. Informative References . . . . . . . . . . . . . . . . . 38 11.1. Normative References . . . . . . . . . . . . . . . . . . 40
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 38 11.2. Informative References . . . . . . . . . . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43
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, or privacy proxies involved in the domain registration
business. These kind of entities have not been formally defined as business. These kind of entities have not been formally defined as
an object in EPP which will be specified as "organization" in this an object in EPP which will be specified as "organization" in this
document. document.
This document describes an organization object mapping for version This document describes an organization object mapping for version
skipping to change at page 4, line 19 skipping to change at page 4, line 19
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 specific 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]. Its 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 would have. Its corresponding element is <org:role>. organization could have. Its corresponding element is <org:role>.
An organization object MUST always have at least one associated role.
Roles can be set only by the client that sponsors an organization
object. A client can change the role of an organization object using
the EPP <update> command.
3.2.1. Role Type 3.2.1. Role Type
An organization would support a list of roles. See Section 7.3 for a An organization role MUST have a type which support a list of values.
list of values. Its corresponding element is <org:type>. An organization could have multiple roles with a different role type.
See Section 7.3 for a list of values. Its corresponding element is
<org:type>.
3.2.2. Role Status 3.2.2. Role Status
A role of an organization object would have its own statuses. Its A role of an organization object MAY have its own statuses. Its
corresponding element is <org:status>. The values of the role status corresponding element is <org:status>. The values of the role status
are defined in Section 3.5. 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. Its corresponding element is <org:roleid>.
Example of organization role identifier: Example of organization role identifier:
skipping to change at page 6, line 25 skipping to change at page 6, line 25
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 only one of these exclusive statuses. Organization MUST have only 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
"clientLinkProhibited" or "serverLinkProhibited" if new links must be
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 values
MUST NOT be combined with each other. MUST NOT be combined with each other.
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
skipping to change at page 9, line 50 skipping to change at page 10, line 8
S: </trID> S: </trID>
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. It is up to the server policy to decide
elements, the <info> command MUST contain a <org:info> element that what attributes will be returned of an organization object. In
identifies the organization namespace. The <org:info> element addition to the standard EPP command elements, the <info> command
contains the following child elements: MUST contain a <org:info> element that identifies the organization
namespace. The <org:info> element contains the following child
elements:
o A <org:id> element that contains the server-unique identifier of o A <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 5 skipping to change at page 11, line 13
organization, as defined in Section 3.2. organization, as defined in Section 3.2.
* One or more <org:status> elements that contains the role * One or more <org:status> elements that contains 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
in Section 3.2.3. in Section 3.2.3.
o Zero or more <org:status> elements that contains the operational o One or more <org:status> elements that contains 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 UTF-8 that can element content MUST be represented in a subset of UTF-8 that can
be represented in the 7-bit US-ASCII character set. If a be represented in the 7-bit US-ASCII character set. If a
localized form (type="loc") is provided, element content MAY be localized form (type="loc") is provided, element content MAY be
represented in unrestricted UTF-8. The <org:postalInfo> element represented in unrestricted UTF-8. The <org:postalInfo> element
contains the following child elements: contains the following child elements:
* A <org:name> element that contains the name of the * A <org:name> element that contains the name of the
organization. organization.
* A <org:addr> element that contains address information * An OPTIONAL <org:addr> element that contains address
associated with the organization. A <org:addr> element information associated with the organization. A <org:addr>
contains the following child elements: element contains the following child elements:
+ One, two, or three OPTIONAL <org:street> elements that + One, two, or three OPTIONAL <org:street> elements that
contain the organization's street address. contain the organization's street address.
+ A <org:city> element that contains the organization's city. + A <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
skipping to change at page 16, line 36 skipping to change at page 16, line 36
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 UTF-8 that can element content MUST be represented in a subset of UTF-8 that can
be represented in the 7-bit US-ASCII character set. If a be represented in the 7-bit US-ASCII character set. If a
localized form (type="loc") is provided, element content MAY be localized form (type="loc") is provided, element content MAY be
represented in unrestricted UTF-8. The <org:postalInfo> element represented in unrestricted UTF-8. The <org:postalInfo> element
contains the following child elements: contains the following child elements:
* A <org:name> element that contains the name of the * A <org:name> element that contains the name of the
organization. organization.
* A <org:addr> element that contains address information * An OPTIONAL <org:addr> element that contains address
associated with the organization. A <org:addr> element information associated with the organization. A <org:addr>
contains the following child elements: element contains the following child elements:
+ One, two, or three OPTIONAL <org:street> elements that + One, two, or three OPTIONAL <org:street> elements that
contain the organization's street address. contain the organization's street address.
+ A <org:city> element that contains the organization's city. + A <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
skipping to change at page 21, line 40 skipping to change at page 21, line 40
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 contains the role type, role o Zero or more <org:role> elements that contains the role type, role
statuses and optional role id of the organization. statuses and optional role id of the organization.
* A <org:type> element that contains the type of the * A <org:type> element that contains the role type of the
organization, as defined in Section 3.2. organization, as defined in Section 3.2. The role type
uniquely identifies the role to update.
* Zero or more <org:status> elements that contains the role * Zero or more <org:status> elements that contains 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
in Section 3.2.3. in Section 3.2.3.
o Zero or more <org:status> element that contains the operational o Zero or more <org:status> element that contains the operational
skipping to change at page 22, line 29 skipping to change at page 22, line 32
represented in unrestricted UTF-8. The change of the postal info represented in unrestricted UTF-8. The change of the postal info
is defined as a replacement of that postal info element with the is defined as a replacement of that postal info element with the
contents of the sub-elements included in the update command. An contents of the sub-elements included in the update command. An
empty <org:postalInfo> element is supported to allow a type of empty <org:postalInfo> element is supported to allow a type of
postal info to be removed. The <org:postalInfo> element contains postal info to be removed. The <org:postalInfo> element contains
the following child elements: the following child elements:
* A <org:name> element that contains the name of the * A <org:name> element that contains the name of the
organization. organization.
* A <org:addr> element that contains address information * An OPTIONAL <org:addr> element that contains address
associated with the organization. A <org:addr> element information associated with the organization. A <org:addr>
contains the following child elements: element contains the following child elements:
+ One, two, or three OPTIONAL <org:street> elements that + One, two, or three OPTIONAL <org:street> elements that
contain the organization's street address. contain the organization's street address.
+ A <org:city> element that contains the organization's city. + A <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
skipping to change at page 25, line 21 skipping to change at page 25, line 21
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 an <update> command cannot An EPP error response MUST be returned if an <update> command cannot
be processed for any reason. be processed for any reason.
4.3. Offline Review of Requested Actions
Commands are processed by a server in the order they are received
from a client. Though an immediate response confirming receipt and
processing of the command is produced by the server, a server
operator MAY perform an offline review of requested transform
commands before completing the requested action. In such situations,
the response from the server MUST clearly note that the transform
command has been received and processed, but the requested action is
pending. The status of the corresponding object MUST clearly reflect
processing of the pending action. The server MUST notify the client
when offline processing of the action has been completed.
Examples describing a <create> command that requires offline review
are included here. Note the result code and message returned in
response to the <create> command.
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1001">
S: <msg>Command completed successfully; action pending</msg>
S: </result>
S: <resData>
S: <org:creData
S: xmlns:org="urn:ietf:params:xml:ns:org-1.0">
S: <org:id>res1523</org:id>
S: <org:crDate>1999-04-03T22:00:00.0Z</org:crDate>
S: </org:creData>
S: </resData>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
The service message MUST contain text that describes the notification
in the child <msg> element of the response <msgQ> element. In
addition, the EPP <resData> element MUST contain a child
<org:panData> element that identifies the organization namespace.
The <org:panData> element contains the following child elements:
o A <org:id> element that contains the server-unique identifier of
the organization object. The <org:id> element contains a REQUIRED
"paResult" attribute. A positive boolean value indicates that the
request has been approved and completed. A negative boolean value
indicates that the request has been denied and the requested
action has not been taken.
o A <org:paTRID> element that contains the client transaction
identifier and server transaction identifier returned with the
original response to process the command. The client transaction
identifier is OPTIONAL and will only be returned if the client
provided an identifier with the original <create> command.
o A <org:paDate> element that contains the date and time describing
when review of the requested action was completed.
Example "review completed" service message:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result>
S: <msgQ count="5" id="12345">
S: <qDate>1999-04-04T22:01:00.0Z</qDate>
S: <msg>Pending action completed successfully.</msg>
S: </msgQ>
S: <resData>
S: <org:panData
S: xmlns:org="urn:ietf:params:xml:ns:org-1.0">
S: <org:id paResult="1">res1523</org:id>
S: <org:paTRID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </org:paTRID>
S: <org:paDate>1999-04-04T22:00:00.0Z</org:paDate>
S: </org:panData>
S: </resData>
S: <trID>
S: <clTRID>BCD-23456</clTRID>
S: <svTRID>65432-WXY</svTRID>
S: </trID>
S: </response>
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
skipping to change at page 26, line 13 skipping to change at page 28, line 26
</annotation> </annotation>
<!-- <!--
Child elements found in EPP commands. Child elements found in EPP commands.
--> -->
<element name="create" type="org:createType"/> <element name="create" type="org:createType"/>
<element name="delete" type="org:sIDType"/> <element name="delete" type="org:sIDType"/>
<element name="update" type="org:updateType"/> <element name="update" type="org:updateType"/>
<element name="check" type="org:mIDType"/> <element name="check" type="org:mIDType"/>
<element name="info" type="org:infoType"/> <element name="info" type="org:infoType"/>
<element name="panData" type="org:panDataType"/>
<!-- <!--
Utility types. Utility types.
--> -->
<simpleType name="statusType"> <simpleType name="statusType">
<restriction base="token"> <restriction base="token">
<enumeration value="ok"/> <enumeration value="ok"/>
<enumeration value="hold"/> <enumeration value="hold"/>
<enumeration value="terminated"/> <enumeration value="terminated"/>
<enumeration value="clientDeleteProhibited"/> <enumeration value="clientDeleteProhibited"/>
skipping to change at page 27, line 4 skipping to change at page 29, line 17
</simpleType> </simpleType>
<complexType name="roleType"> <complexType name="roleType">
<sequence> <sequence>
<element name="type" type="token"/> <element name="type" type="token"/>
<element name="status" type="org:roleStatusType" <element name="status" type="org:roleStatusType"
minOccurs="0" maxOccurs="3"/> minOccurs="0" maxOccurs="3"/>
<element name="roleid" type="token" minOccurs="0"/> <element name="roleid" type="token" minOccurs="0"/>
</sequence> </sequence>
</complexType> </complexType>
<complexType name="postalInfoType"> <complexType name="postalInfoType">
<sequence> <sequence>
<element name="name" <element name="name"
type="org:postalLineType"/> type="org:postalLineType"/>
<element name="addr" <element name="addr"
type="org:addrType"/> type="org:addrType" minOccurs="0"/>
</sequence> </sequence>
<attribute name="type" <attribute name="type"
type="org:postalInfoEnumType" type="org:postalInfoEnumType"
use="required"/> use="required"/>
</complexType> </complexType>
<complexType name="contactType"> <complexType name="contactType">
<simpleContent> <simpleContent>
<extension base="eppcom:clIDType"> <extension base="eppcom:clIDType">
<attribute name="type" type="org:contactAttrType" <attribute name="type" type="org:contactAttrType"
skipping to change at page 29, line 19 skipping to change at page 31, line 34
<!-- <!--
Child element of commands that accept multiple identifiers. Child element of commands that accept multiple identifiers.
--> -->
<complexType name="mIDType"> <complexType name="mIDType">
<sequence> <sequence>
<element name="id" <element name="id"
type="eppcom:clIDType" maxOccurs="unbounded"/> type="eppcom:clIDType" maxOccurs="unbounded"/>
</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">
<simpleContent>
<extension base="eppcom:clIDType">
<attribute name="paResult" type="boolean"
use="required"/>
</extension>
</simpleContent>
</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>
skipping to change at page 34, line 25 skipping to change at page 37, line 14
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 Values Registry 7.3. Role Type Values Registry
The following values should be registered by the IANA in the "EPP The following values should be registered by the IANA in the "EPP
Organization Role Values" registry. The registration policy for this Organization Role Values" registry. The registration policy for this
registry is "Expert Review" [RFC8126]. registry 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.
skipping to change at page 35, line 16 skipping to change at page 38, line 4
Registrant Contact Information: 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 Name: IESG
Registrant Contact Information: 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 Contact Information: iesg@ietf.org
Value: dns-operator
Description: The entity object instance represents a third-party
DNS operator that maintains the name servers and zone data on
behalf of a registrant.
Registrant Name: IESG Registrant Name: IESG
Registrant Contact Information: iesg@ietf.org Registrant Contact Information: iesg@ietf.org
8. Implementation Status 8. Implementation Status
Note to RFC Editor: Please remove this section and the reference to Note to RFC Editor: Please remove this section and the reference to
[RFC7942] before publication. This section records the status of [RFC7942] before publication. This section records the status of
known implementations of the protocol defined by this specification known implementations of the protocol defined by this specification
skipping to change at page 40, line 22 skipping to change at page 43, line 22
Organization WG document-06: Organization WG document-06:
* Updated typos. * Updated typos.
* Added "Query" for "<Transfer> Query Command". * Added "Query" for "<Transfer> Query Command".
* Change "Registrant Contact" to IESG in section 7.1. * Change "Registrant Contact" to IESG in section 7.1.
* Modified section 7.2. * Modified section 7.2.
Organization WG document-07:
* Updated typos.
* Added dns-operator in section 7.1.
* Added "OPTIONAL" for <org:addr>
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
Phone: +86 10 5881 2677 Phone: +86 10 5881 2677
Email: zhoulinlin@cnnic.cn Email: zhoulinlin@cnnic.cn
 End of changes. 26 change blocks. 
48 lines changed or deleted 190 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/