Internet Engineering Task Force L. Zhou Internet-Draft N. Kong Intended status: Standards Track G. Zhou Expires: November 13, 2017 X. Lee CNNIC J. Gould VeriSign, Inc. May 12, 2017 Extensible Provisioning Protocol (EPP) Organization Mapping draft-ietf-regext-org-00 Abstract This document describes an Extensible Provisioning Protocol (EPP) mapping for provisioning and management of organization object stored in a shared central repository. Specified in Extensible Markup Language (XML), this extended mapping is applied to provide additional features required for the provisioning of organizations. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on November 13, 2017. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect Zhou, et al. Expires November 13, 2017 [Page 1] Internet-Draft EPP Organization Mapping May 2017 to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4 3.2. Organization Roles . . . . . . . . . . . . . . . . . . . 4 3.2.1. Role Type . . . . . . . . . . . . . . . . . . . . . . 4 3.2.2. Role Identifier . . . . . . . . . . . . . . . . . . . 4 3.3. Contact and Client Identifiers . . . . . . . . . . . . . 4 3.4. Organization Status Values . . . . . . . . . . . . . . . 4 3.5. Role Status Values . . . . . . . . . . . . . . . . . . . 5 3.6. Parent Identifier . . . . . . . . . . . . . . . . . . . . 6 3.7. URL . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 6 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 7 4.1.2. EPP Command . . . . . . . . . . . . . . . . . 8 4.1.3. EPP Command . . . . . . . . . . . . . . . 14 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 14 4.2.1. EPP Command . . . . . . . . . . . . . . . . 14 4.2.2. EPP Command . . . . . . . . . . . . . . . . 18 4.2.3. EPP Command . . . . . . . . . . . . . . . . . 19 4.2.4. EPP Command . . . . . . . . . . . . . . . 19 4.2.5. EPP Command . . . . . . . . . . . . . . . . 20 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 23 6. Internationalization Considerations . . . . . . . . . . . . . 29 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 29 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 30 7.3. Role Values Registry . . . . . . . . . . . . . . . . . . 30 Zhou, et al. Expires November 13, 2017 [Page 2] Internet-Draft EPP Organization Mapping May 2017 8. Security Considerations . . . . . . . . . . . . . . . . . . . 31 9. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 31 10. Normative References . . . . . . . . . . . . . . . . . . . . 31 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 32 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33 1. Introduction There are many domain entities, such as registrar, reseller, DNS service operator, or privacy proxy involved in the domain registration business. These kind of entities have not been formally defined in EPP which will be specified as "organization" in this document. This document describes an organization object mapping for version 1.0 of the Extensible Provisioning Protocol (EPP) [RFC5730]. This mapping is specified using the XML 1.0 as described in [W3C.REC-xml-20040204] and XML Schema notation as described in [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028]. 2. Conventions Used in This Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. In examples, "C:" represents lines sent by a protocol client and "S:" represents lines returned by a protocol server. Indentation and white space in examples are provided only to illustrate element relationships and are not a REQUIRED feature of this specification. XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented to develop a conforming implementation. "org-1.0" in is used as an abbreviation for "urn:ietf:params:xml:ns:org-1.0". The XML namespace prefix "org" is used, but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents. 3. Object Attributes An EPP organization object has attributes and associated values that can be viewed and modified by the sponsoring client or the server. This section describes each attribute type in detail. The formal syntax for the attribute values described here can be found in the Zhou, et al. Expires November 13, 2017 [Page 3] Internet-Draft EPP Organization Mapping May 2017 "Formal Syntax" section of this document and in the appropriate normative references. 3.1. Organization Identifier All EPP organizations are identified by a server-unique identifier. Organization identifiers are character strings with a specific minimum length, a specified maximum length, and a specified format. Organization identifiers use the "clIDType" client identifier syntax described in [RFC5730]. Its corresponding element is . 3.2. Organization Roles The organization roles are used to represent the relationship an organization would have. Its corresponding element is . 3.2.1. Role Type An organization would support a list of roles. See Section 7.3 for a list of values. Its corresponding element is with an "roleStatus" attribute. The values of role statuses are defined in Section 3.5. 3.2.2. Role Identifier A role MAY have a third party assigned identifier such as the IANA ID for registrars. Its corresponding element is . 3.3. Contact and Client Identifiers All EPP contacts are identified by a server-unique identifier. Contact identifiers are character strings with a specific minimum length, a specified maximum length, and a specified format. Contact identifiers use the "clIDType" client identifier syntax described in [RFC5730]. 3.4. Organization Status Values An organization object MUST always have at least one associated status value. The default value is "ok". Status Value Descriptions: o ok: This is the normal status value for an object that has no pending operations or prohibitions. This value is set and removed by the server as other status values are added or removed. Zhou, et al. Expires November 13, 2017 [Page 4] Internet-Draft EPP Organization Mapping May 2017 o hold: Organization transform commands and new links MUST be rejected. o terminated: The organization has been terminated MUST NOT be linked. Organization transform commands and new links MUST be rejected. o linked: The organization object has at least one active association with another object. The "linked" status is not explicitly set by the client. Servers SHOULD provide services to determine existing object associations. o clientLinkProhibited, serverLinkProhibited: Requests to add new links to the organization MUST be rejected. o clientUpdateProhibited, serverUpdateProhibited: Requests to update the object (other than to remove this status) MUST be rejected. o clientDeleteProhibited, serverDeleteProhibited: Requests to delete the object MUST be rejected. o pendingCreate, pendingUpdate, pendingDelete: A transform command has been processed for the object, but the action has not been completed by the server. Server operators can delay action completion for a variety of reasons, such as to allow for human review or third-party action. A transform command that is processed, but whose requested action is pending, is noted with response code 1001. "pendingCreate", "ok", "hold", and "terminated" are mutually exclusive statuses. Organization MUST have only one of these statuses set. "ok" status MAY only be combined with "linked" status. "pendingDelete" status MUST NOT be combined with either "clientDeleteProhibited" or "serverDeleteProhibited" status. The pendingCreate, pendingDelete, and pendingUpdate status values MUST NOT be combined with each other. 3.5. Role Status Values A role SHOULD have at least one associated status value. Valid values include "ok", "linked", "clientLinkProhibited", and "serverLinkProhibited". The default value is "ok". Status Value Descriptions: Zhou, et al. Expires November 13, 2017 [Page 5] Internet-Draft EPP Organization Mapping May 2017 o ok: This is the normal status value for an role that has no pending operations or prohibitions. This value is set and 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 association with another object. The "linked" status is not explicitly set by the client. Servers SHOULD provide services to determine existing object associations. o clientLinkProhibited, serverLinkProhibited: Requests to add new links to the role MUST be rejected. 3.6. Parent Identifier There can be more than one layer of organizations, such as a reseller. The parent identifier, as defined with the element, represents the parent organization identifier in a child organization. Take a reseller organization for example, the parent identifier is not defined for the top level reseller, namely the registrar of the registry. An N-tier reseller has a parent reseller and at least one child reseller. A reseller customer has a parent reseller and no child resellers. Loops SHOULD be prohibited. If organization A has B as parent identifier, organization B must not have organization A as parent identifier. 3.7. URL The URL represents the organization web home page, as defined with the element. 4. EPP Command Mapping A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification [RFC5730]. The command mappings described here are specifically for use in provisioning and managing organization information via EPP. 4.1. EPP Query Commands EPP provides two commands to retrieve domain information: to determine if an organization object can be provisioned within a repository, and to retrieve detailed information associated with an organization object. This document does not define a mapping for the EPP command. Zhou, et al. Expires November 13, 2017 [Page 6] Internet-Draft EPP Organization Mapping May 2017 4.1.1. EPP Command The EPP command is used to determine if an object can be provisioned within a repository. It provides a hint that allows a client to anticipate the success or failure of provisioning an object using the command, as object-provisioning requirements are ultimately a matter of server policy. In addition to the standard EPP command elements, the command MUST contain a element that identifies the organization namespace. The element contains the following child elements: o One or more elements that contain the server-unique identifier of the organization objects to be queried. Example command: C: C: C: C: C: C: res1523 C: re1523 C: 1523res C: C: C: ABC-12345 C: C: When a command has been processed successfully, the EPP element MUST contain a child element that identifies the organization namespace. The element contains one or more elements that contain the following child elements: o A element that identifies the queried object. This element MUST contain an "avail" attribute whose value indicates object availability (can it be provisioned or not) at the moment the command was completed. A value of "1" or "true" means that the object can be provisioned. A value of "0" or "false" means that the object cannot be provisioned. Zhou, et al. Expires November 13, 2017 [Page 7] Internet-Draft EPP Organization Mapping May 2017 o An OPTIONAL element that MAY be provided when an object cannot be provisioned. If present, this element contains server-specific text to help explain why the object cannot be provisioned. This text MUST be represented in the response language previously negotiated with the client; an OPTIONAL "lang" attribute MAY be present to identify the language if the negotiated value is something other than the default value of "en"(English). Example response: S: S: S: S: S: Command completed successfully S: S: S: S: S: res1523 S: S: S: re1523 S: In use S: S: S: 1523res S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. 4.1.2. EPP Command The EPP command is used to retrieve information associated with an organization object. In addition to the standard EPP command elements, the command MUST contain a element that Zhou, et al. Expires November 13, 2017 [Page 8] Internet-Draft EPP Organization Mapping May 2017 identifies the organization namespace. The element contains the following child elements: o A element that contains the server-unique identifier of the organization object to be queried. Example command: C: C: C: C: C: C: res1523 C: C: C: ABC-12345 C: C: When an command has been processed successfully, the EPP element MUST contain a child element that identifies the organization namespace. The element contains the following child elements: o A element that contains the server-unique identifier of the organization object, as defined in Section 3.1. o A element that contains the Repository Object IDentifier assigned to the organization object when the object was created. o One or more elements that contains the role type and optional role id of the organization. * A element that contains the type of the organization, as defined in Section 3.2. A "roleStatus" attribute is used to describe the status value of a role type. * An OPTIONAL element that contains a third party assigned identifier, such as IANA ID for registrars, as defined in Section 3.2.2. o A element that contains the operational status of the organization, as defined in Section 3.4. Zhou, et al. Expires November 13, 2017 [Page 9] Internet-Draft EPP Organization Mapping May 2017 o An OPTIONAL element that contains the identifier of the parent object, as defined in Section 3.6. o One or two elements that contain postal-address information. Two elements are provided so that address information can be provided in both internationalized and localized forms; a "type" attribute is used to identify the two forms. If an internationalized form (type="int") is provided, 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 localized form (type="loc") is provided, element content MAY be represented in unrestricted UTF-8. The element contains the following child elements: * A element that contains the name of the organization. * A element that contains address information associated with the organization. A element contains the following child elements: + One, two, or three OPTIONAL elements that contain the organization's street address. + A element that contains the organization's city. + An OPTIONAL element that contains the organization's state or province. + An OPTIONAL element that contains the organization's postal code. + A element that contains the organization's country code. o An OPTIONAL element that contains the organization's voice telephone number. o An OPTIONAL element that contains the organization's facsimile telephone number. o An OPTIONAL element that contains the organization's email address. o An OPTIONAL element that contains the URL to the website of the organization. Zhou, et al. Expires November 13, 2017 [Page 10] Internet-Draft EPP Organization Mapping May 2017 o Zero or more OPTIONAL elements that contain identifiers for the contact objects to be associated with the organization object. Contact object identifiers MUST be known to the server before the contact object can be associated with the organization object. The required "type" is used to represent contact types. The type values include "admin", "tech", "billing", "abuse", and "custom". The OPTIONAL "typeName" attribute is used to define the name of a "custom" type. o An OPTIONAL element that contains the organization identifier of the sponsoring client. There is no element if the organization is managed by the registry. o A element that contains the identifier of the client that created the organization object. o A element that contains the date and time of organization object creation. o A element that contains the identifier of the client that last updated the organization object. This element MUST NOT be present if the organization has never been modified. o A element that contains the date and time of the most recent organization object modification. This element MUST NOT be present if the organization object has never been modified. Example response for "Example Registrar Inc." registrar object with registrar identifier "1362": Zhou, et al. Expires November 13, 2017 [Page 11] Internet-Draft EPP Organization Mapping May 2017 S: S: S: S: S: Command completed successfully S: S: S: S: registrar1362 S: registrar1362-REP S: S: registrar S: 1362 S: S: ok S: S: Example Registrar Inc. S: S: 123 Example Dr. S: Suite 100 S: Dulles S: VA S: 20166-6503 S: US S: S: S: +1.7035555555 S: +1.7035555556 S: contact@organization.example S: http://organization.example S: sh8013 S: sh8013 S: sh8013 S: ClientX S: 1999-04-03T22:00:00.0Z S: ClientX S: 1999-12-03T09:00:00.0Z S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: Zhou, et al. Expires November 13, 2017 [Page 12] Internet-Draft EPP Organization Mapping May 2017 Example response for "Example Reseller Inc." reseller object managed by registrar identifier "1362": S: S: S: S: S: Command completed successfully S: S: S: S: reseller1523 S: reseller1523-REP S: S: reseller S: S: ok S: registrar1362 S: S: Example Reseller Inc. S: S: 123 Example Dr. S: Suite 100 S: Dulles S: VA S: 20166-6503 S: US S: S: S: +1.7035555556 S: http://organization.example S: sh8013 S: 1362 S: ClientX S: 1999-04-03T22:00:00.0Z S: ClientX S: 1999-12-03T09:00:00.0Z S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: Zhou, et al. Expires November 13, 2017 [Page 13] Internet-Draft EPP Organization Mapping May 2017 An EPP error response MUST be returned if an command cannot be processed for any reason. 4.1.3. EPP Command The transfer semantics does not apply to organization object. No EPP command is defined in this document. 4.2. EPP Transform Commands EPP provides four commands to transform organization-object information: to create an instance of an organization object, to delete an instance of an organization object, to manage organization-object sponsorship changes, and to change information associated with an organization object. This document does not define a mapping for the EPP and command. Transform commands are typically processed and completed in real time. Server operators MAY receive and process transform commands but defer completing the requested action if human or third-party review is required before the requested action can be completed. In such situations, the server MUST return a 1001 response code to the client to note that the command has been received and processed but that the requested action is pending. The server MUST also manage the status of the object that is the subject of the command to reflect the initiation and completion of the requested action. Once the action has been completed, all clients involved in the transaction MUST be notified using a service message that the action has been completed and that the status of the object has changed. Other notification methods MAY be used in addition to the required service message. Server operators SHOULD confirm that a client is authorized to perform a transform command on a given object. Any attempt to transform an object by an unauthorized client MUST be rejected, and the server MUST return a 2201 response code to the client to note that the client lacks privileges to execute the requested command. 4.2.1. EPP Command The EPP command provides a transform operation that allows a client to create an organization object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the organization namespace. The element contains the following child elements: Zhou, et al. Expires November 13, 2017 [Page 14] Internet-Draft EPP Organization Mapping May 2017 o A element that contains the desired server-unique identifier for the organization to be created, as defined in Section 3.1. o One or more elements that contains the role type and optional role id of the organization. * A element that contains the type of the organization, as defined in Section 3.2. A "roleStatus" attribute is used to describe the status value of a role type. * An OPTIONAL element that contains a third party assigned identifier, such as IANA ID for registrars, as defined in Section 3.2.2. o A element that contains the operational status of the organization, as defined in Section 3.4. o An OPTIONAL element that contains the identifier of the parent object, as defined in Section 3.6. o One or two elements that contain postal-address information. Two elements are provided so that address information can be provided in both internationalized and localized forms; a "type" attribute is used to identify the two forms. If an internationalized form (type="int") is provided, 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 localized form (type="loc") is provided, element content MAY be represented in unrestricted UTF-8. The element contains the following child elements: * A element that contains the name of the organization. * A element that contains address information associated with the organization. A element contains the following child elements: + One, two, or three OPTIONAL elements that contain the organization's street address. + A element that contains the organization's city. + An OPTIONAL element that contains the organization's state or province. Zhou, et al. Expires November 13, 2017 [Page 15] Internet-Draft EPP Organization Mapping May 2017 + An OPTIONAL element that contains the organization's postal code. + A element that contains the organization's country code. o An OPTIONAL element that contains the organization's voice telephone number. o An OPTIONAL element that contains the organization's facsimile telephone number. o An OPTIONAL element that contains the organization's email address. o An OPTIONAL element that contains the URL to the website of the organization. o Zero or more OPTIONAL elements that contain identifiers for the contact objects associated with the organization object. Example command: Zhou, et al. Expires November 13, 2017 [Page 16] Internet-Draft EPP Organization Mapping May 2017 C: C: C: C: C: C: res1523 C: C: reseller C: privacyproxy C: C: ok C: 1523res C: C: Example Organization Inc. C: C: 123 Example Dr. C: Suite 100 C: Dulles C: VA C: 20166-6503 C: US C: C: C: +1.7035555555 C: +1.7035555556 C: contact@organization.example C: http://organization.example C: sh8013 C: sh8013 C: C: C: ABC-12345 C: C: When a command has been processed successfully, the EPP element MUST contain a child element that identifies the organization namespace. The element contains the following child elements: o A element that contains the server-unique identifier for the created organization, as defined in Section 3.1. o A element that contains the date and time of organization-object creation. Example response: Zhou, et al. Expires November 13, 2017 [Page 17] Internet-Draft EPP Organization Mapping May 2017 S: S: S: S: S: Command completed successfully S: S: S: S: res1523 S: 1999-04-03T22:00:00.0Z S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. 4.2.2. EPP Command The EPP command provides a transform operation that allows a client to delete an organization object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the organization namespace. The element MUST contain the following child element: o A element that contains the server-unique identifier of the organization object to be deleted, as defined in Section 3.1. An organization object MUST NOT be deleted if it is associated with other known objects. An associated organization MUST NOT be deleted until associations with other known objects have been broken. A server MUST notify clients that object relationships exist by sending a 2305 error response code when a command is attempted and fails due to existing object relationships. Example command: Zhou, et al. Expires November 13, 2017 [Page 18] Internet-Draft EPP Organization Mapping May 2017 C: C: C: C: C: C: res1523 C: C: C: ABC-12345 C: C: When a command has been processed successfully, a server MUST respond with an EPP response with no element. Example response: S: S: S: S: S: Command completed successfully S: S: S: ABC-12345 S: 54321-XYZ S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. 4.2.3. EPP Command Renewal semantics do not apply to organization objects, so there is no mapping defined for the EPP command. 4.2.4. EPP Command Transfer semantics do not apply to organization objects, so there is no mapping defined for the EPP command. Zhou, et al. Expires November 13, 2017 [Page 19] Internet-Draft EPP Organization Mapping May 2017 4.2.5. EPP Command The EPP command provides a transform operation that allows a client to modify the attributes of an organization object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the organization namespace. The element contains the following child elements: o A element that contains the server-unique identifier of the organization object to be updated, as defined in Section 3.1. o An OPTIONAL element that contains attribute values to be added to the object. o An OPTIONAL element that contains attribute values to be removed from the object. o An OPTIONAL element that contains attribute values to be changed. At least one , or element MUST be provided if the command is not being extended. All of these elements MAY be omitted if an extension is present. The and elements contain the following child element: o Zero or more elements that contain the identifiers for contact objects to be associated with or removed from the organization object. Contact object identifiers MUST be known to the server before the contact object can be associated with the organization object. A element contains the following OPTIONAL child elements. At least one child element MUST be present: o One or more elements that contains the role type and optional role id of the organization. * A element that contains the type of the organization, as defined in Section 3.2. A "roleStatus" attribute is used to describe the status value of a role type. * An OPTIONAL element that contains a third party assigned identifier, such as IANA ID for registrars, as defined in Section 3.2.2. o A element that contains the operational status of the organization. Zhou, et al. Expires November 13, 2017 [Page 20] Internet-Draft EPP Organization Mapping May 2017 o A element that contains the identifier of the parent object. o One or two elements that contain postal-address information. Two elements are provided so that address information can be provided in both internationalized and localized forms; a "type" attribute is used to identify the two forms. If an internationalized form (type="int") is provided, 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 localized form (type="loc") is provided, element content MAY be represented in unrestricted UTF-8. The change of the postal info is defined as a replacement of that postal info element with the contents of the sub-elements included in the update command. An empty element is supported to allow a type of postal info to be removed. The element contains the following child elements: o * A element that contains the name of the organization. * A element that contains address information associated with the organization. A element contains the following child elements: + One, two, or three OPTIONAL elements that contain the organization's street address. + A element that contains the organization's city. + An OPTIONAL element that contains the organization's state or province. + An OPTIONAL element that contains the organization's postal code. + A element that contains the organization's country code. o A element that contains the organization's voice telephone number. o A element that contains the organization's facsimile telephone number. Zhou, et al. Expires November 13, 2017 [Page 21] Internet-Draft EPP Organization Mapping May 2017 o A element that contains the organization's email address. o A element that contains the URL to the website of the organization. Example command: C: C: C: C: C: C: res1523 C: C: sh8013 C: C: C: C: reseller C: privacyproxy C: C: ok C: C: C: 124 Example Dr. C: Suite 200 C: Dulles C: VA C: 20166-6503 C: US C: C: C: +1.7034444444 C: C: C: C: C: ABC-12345 C: C: When an command has been processed successfully, a server MUST respond with an EPP response with no element. Example response: Zhou, et al. Expires November 13, 2017 [Page 22] Internet-Draft EPP Organization Mapping May 2017 S: S: S: S: S: Command completed successfully S: S: S: ABC-12345 S: 54321-XYZ S: S: S: An EPP error response MUST be returned if an command cannot be processed for any reason. 5. Formal Syntax An EPP object mapping is specified in XML Schema notation. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. The BEGIN and END tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes. BEGIN Extensible Provisioning Protocol v1.0 Zhou, et al. Expires November 13, 2017 [Page 23] Internet-Draft EPP Organization Mapping May 2017 organization provisioning schema. Zhou, et al. Expires November 13, 2017 [Page 24] Internet-Draft EPP Organization Mapping May 2017 Zhou, et al. Expires November 13, 2017 [Page 25] Internet-Draft EPP Organization Mapping May 2017 Zhou, et al. Expires November 13, 2017 [Page 27] Internet-Draft EPP Organization Mapping May 2017 Zhou, et al. Expires November 13, 2017 [Page 28] Internet-Draft EPP Organization Mapping May 2017 END 6. Internationalization Considerations EPP is represented in XML, which provides native support for encoding information using the Unicode character set and its more compact representations including UTF-8. Conformant XML processors recognize both UTF-8 and UTF-16. Though XML includes provisions to identify and use other character encodings through use of an "encoding" attribute in an declaration, use of UTF-8 is RECOMMENDED. As an extension of the EPP organization object mapping, the elements and element content described in this document MUST inherit the internationalization conventions used to represent higher-layer domain and core protocol structures present in an XML instance that includes this extension. 7. IANA Considerations 7.1. XML Namespace This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. IANA is requested to assignment the following URI. Registration request for the organization namespace: o URI: urn:ietf:params:xml:ns:org-1.0 o Registrant Contact: See the "Author's Address" section of this document. o XML: See the "Formal Syntax" section of this document. Zhou, et al. Expires November 13, 2017 [Page 29] Internet-Draft EPP Organization Mapping May 2017 7.2. EPP Extension Registry The EPP extension described in this document should be registered by the IANA in the EPP Extension Registry described in [RFC7451]. The details of the registration are as follows: Name of Extension: Organization Object Extension Document status: Standards Track Reference: (insert reference to RFC version of this document) Registrant Name and Email Address: See the "Author's Address" section of this document. TLDs: any IPR Disclosure: none Status: active Notes: none 7.3. Role Values Registry The following values should be registered by the IANA in the "EPP Organization Role Values" registry: Value: registrar Type: role Description: The entity object instance represents the authority responsible for the registration in the registry. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: reseller Type: role Description: The entity object instance represents a third party through which the registration was conducted (i.e., not the registry or registrar). Registrant Name: IESG Zhou, et al. Expires November 13, 2017 [Page 30] Internet-Draft EPP Organization Mapping May 2017 Registrant Contact Information: iesg@ietf.org Value: privacyproxy Type: role Description: The entity object instance represents a third-party who could help to register a domain without exposing their private information. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org 8. Security Considerations The object mapping extension described in this document does not provide any other security services or introduce any additional considerations beyond those described by [RFC5730] or those caused by the protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well. 9. Acknowledgement The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick Mevzek, Antoin Verschuren and Scott Hollenbeck for their careful review and valuable comments. 10. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, . [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, August 2009, . Zhou, et al. Expires November 13, 2017 [Page 31] Internet-Draft EPP Organization Mapping May 2017 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, February 2015, . [W3C.REC-xml-20040204] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third Edition)", World Wide Web Consortium FirstEdition REC-xml- 20040204", February 2004, . [W3C.REC-xmlschema-1-20041028] Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, ""XML Schema Part 1: Structures Second Edition", World Wide Web Consortium Recommendation REC-xmlschema- 1-20041028", October 2004, . [W3C.REC-xmlschema-2-20041028] Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-2-20041028", October 2004, . Appendix A. Change Log 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 responses. * Deleted description of command in section 4.1 and 4.2. * Deleted whoisInfo disclose type in XML schema. * Deleted maxOccurs of addRemType. Zhou, et al. Expires November 13, 2017 [Page 32] Internet-Draft EPP Organization Mapping May 2017 * Deleted extra "OPTIONAL" in section 4.2.5. * Updated typos in response. -02: * Changed author information. * Updated url definition. * Updated XML schema. -03: * Changed author information. * Updated section 3.1. * Refactored the XSD file. Added element. * Added acknowledgement. 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. Authors' Addresses Linlin Zhou CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 2677 Email: zhoulinlin@cnnic.cn Zhou, et al. Expires November 13, 2017 [Page 33] Internet-Draft EPP Organization Mapping May 2017 Ning Kong CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 3147 Email: nkong@cnnic.cn Guiqing Zhou CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 2692 Email: zhouguiqing@cnnic.cn Xiaodong Lee CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 3020 Email: xl@cnnic.cn James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com Zhou, et al. Expires November 13, 2017 [Page 34]