--- 1/draft-ietf-regext-org-01.txt 2018-02-27 20:13:09.367664963 -0800 +++ 2/draft-ietf-regext-org-02.txt 2018-02-27 20:13:09.427666371 -0800 @@ -1,51 +1,51 @@ Internet Engineering Task Force L. Zhou Internet-Draft N. Kong Intended status: Standards Track G. Zhou -Expires: June 8, 2018 X. Lee +Expires: September 1, 2018 X. Lee CNNIC J. Gould VeriSign, Inc. - December 5, 2017 + February 28, 2018 Extensible Provisioning Protocol (EPP) Organization Mapping - draft-ietf-regext-org-01 + draft-ietf-regext-org-02 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 + mapping for provisioning and management of organization objects + 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 https://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 June 8, 2018. + This Internet-Draft will expire on September 1, 2018. Copyright Notice - Copyright (c) 2017 IETF Trust and the persons identified as the + Copyright (c) 2018 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 (https://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 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 @@ -65,58 +65,59 @@ Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 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.2.3. Example of Organization Roles . . . . . . . . . . . . 4 + 3.3. Contact and Client Identifiers . . . . . . . . . . . . . 5 + 3.4. Organization Status Values . . . . . . . . . . . . . . . 5 3.5. Role Status Values . . . . . . . . . . . . . . . . . . . 6 3.6. Parent Identifier . . . . . . . . . . . . . . . . . . . . 6 - 3.7. URL . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 + 3.7. URL . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 + 3.8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 + 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 7 4.1.2. EPP Command . . . . . . . . . . . . . . . . . 9 - 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 - - 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 31 - 8.1. CNNIC Impelementation . . . . . . . . . . . . . . . . . . 31 - 8.2. Reseller Extension . . . . . . . . . . . . . . . . . . . 32 - 9. Security Considerations . . . . . . . . . . . . . . . . . . . 32 - 10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 32 - 11. Normative References . . . . . . . . . . . . . . . . . . . . 32 - Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 33 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34 + 4.1.3. EPP Command . . . . . . . . . . . . . . . 15 + 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 15 + 4.2.1. EPP Command . . . . . . . . . . . . . . . . 15 + 4.2.2. EPP Command . . . . . . . . . . . . . . . . 19 + 4.2.3. EPP Command . . . . . . . . . . . . . . . . . 20 + 4.2.4. EPP Command . . . . . . . . . . . . . . . 20 + 4.2.5. EPP Command . . . . . . . . . . . . . . . . 21 + 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 24 + 6. Internationalization Considerations . . . . . . . . . . . . . 30 + 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 + 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 30 + 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 31 + 7.3. Role Values Registry . . . . . . . . . . . . . . . . . . 31 + 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 32 + 8.1. CNNIC Implementation . . . . . . . . . . . . . . . . . . 32 + 8.2. Reseller Extension . . . . . . . . . . . . . . . . . . . 33 + 9. Security Considerations . . . . . . . . . . . . . . . . . . . 33 + 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 33 + 11. Normative References . . . . . . . . . . . . . . . . . . . . 33 + Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 34 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 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 + There are many entities, such as registrars, resellers, DNS service + operators, or privacy proxies involved in the domain registration + business. These kind of entities have not been formally defined as + an object 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 @@ -157,29 +158,38 @@ 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 + list of values. Its corresponding element is with a "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.2.3. Example of Organization Roles + + Example of "Organization Roles" + + S: + S: registrar + S: 1362 + S: + 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 @@ -188,21 +198,21 @@ 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. o hold: Organization transform commands and new links MUST be rejected. - o terminated: The organization has been terminated MUST NOT be + o terminated: The organization which 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. @@ -268,34 +278,44 @@ 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. +3.8. + + Date and time attribute values MUST be represented in Universal + Coordinated Time (UTC) using the Gregorian calendar. The extended + date-time form using upper case "T" and "Z" characters defined in + [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time + values, as XML Schema does not support truncated date-time forms or + lower case "T" and "Z" characters. + 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. + for the EPP command to retrieve domain-object transfer + status information.. 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 @@ -419,22 +440,22 @@ 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 One or more elements 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 @@ -496,22 +517,22 @@ 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": + Example response for "Example Registrar Inc." organization + object with registrar identifier "1362": S: S: S: S: S: Command completed successfully S: S: S: @@ -546,22 +567,22 @@ S: ClientX S: 1999-12-03T09:00:00.0Z S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: - Example response for "Example Reseller Inc." reseller object - managed by registrar identifier "1362": + Example response for "Example Reseller Inc." organization + object of reseller type managed by registrar identifier "1362": S: S: S: S: S: Command completed successfully S: S: S: @@ -602,21 +623,21 @@ 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 + 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 @@ -913,22 +934,20 @@ 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. @@ -1160,21 +1179,21 @@ + type="org:statusType" default="ok" maxOccurs="9"/> @@ -1381,22 +1400,22 @@ registry or registrar). Registrant Name: IESG 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. + could help to register a domain without exposing the registrants' + private information.. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org 8. Implementation Status Note to RFC Editor: Please remove this section and the reference to [RFC6982] before publication. This section records the status of known implementations of the protocol defined by this specification @@ -1415,50 +1434,50 @@ 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". CNNIC is in the process of development research to update EPP organization mapping from reseller mapping. Verisign is also planning to implement this document. -8.1. CNNIC Impelementation +8.1. CNNIC Implementation Organization: CNNIC Name: EPP Organization Mapping - Description: CNNIC is trying to update EPP organizaiton mapping from + Description: CNNIC is trying to update EPP organization mapping from previous reseller mapping according to this document. Level of maturity: Research. Coverage: EPP organization mapping. Contact: zhouguiqing@cnnic.cn 8.2. Reseller Extension This document was updated from draft-ietf-regext-reseller. CNNIC, - Verisign and Patrick Mevzek have already implemented the reseller - mapping. + Verisign and Net::DRI (Patrick Mevzek) have already implemented the + reseller mapping. 9. 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. -10. Acknowledgement +10. Acknowledgment 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. 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, @@ -1540,44 +1559,47 @@ * Updated url definition. * Updated XML schema. -03: * Changed author information. * Updated section 3.1. - * Refactored the XSD file. Added element. + * Refactoried the XSD file. Added element. - * Added acknowledgement. + * 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 "Imeplementation Status" section. + Organization WG document-01: Added "Implementation Status" section. -Authors' Addresses + Organization WG document-02: Accepted some of the feedbacks on the + mailing list. +Authors' Addresses Linlin Zhou CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 2677 Email: zhoulinlin@cnnic.cn + Ning Kong CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 3147 Email: nkong@cnnic.cn Guiqing Zhou