--- 1/draft-ietf-regext-org-03.txt 2018-05-03 23:13:22.698013766 -0700 +++ 2/draft-ietf-regext-org-04.txt 2018-05-03 23:13:22.770015478 -0700 @@ -1,22 +1,22 @@ Internet Engineering Task Force L. Zhou Internet-Draft N. Kong Intended status: Standards Track G. Zhou -Expires: October 29, 2018 X. Lee +Expires: November 5, 2018 X. Lee CNNIC J. Gould - VeriSign, Inc. - April 27, 2018 + Verisign, Inc. + May 4, 2018 Extensible Provisioning Protocol (EPP) Organization Mapping - draft-ietf-regext-org-03 + draft-ietf-regext-org-04 Abstract This document describes an Extensible Provisioning Protocol (EPP) 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 @@ -27,21 +27,21 @@ 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 October 29, 2018. + This Internet-Draft will expire on November 5, 2018. Copyright Notice 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 @@ -69,50 +69,53 @@ 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 Status . . . . . . . . . . . . . . . . . . . . . 4 3.2.3. Role Identifier . . . . . . . . . . . . . . . . . . . 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.6. Parent Identifier . . . . . . . . . . . . . . . . . . . . 7 3.7. URL . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.8. Dates and Times . . . . . . . . . . . . . . . . . . . . . 7 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7 - 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 7 + 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 8 4.1.2. EPP Command . . . . . . . . . . . . . . . . . 9 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 . . . . . . . . . . . . . . . . . . . . . . . . 25 6. Internationalization Considerations . . . . . . . . . . . . . 33 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 33 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 34 7.3. Role Values Registry . . . . . . . . . . . . . . . . . . 34 7.3.1. Registration Template . . . . . . . . . . . . . . . . 34 - 7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 34 + 7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 35 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 35 - 8.1. CNNIC Implementation . . . . . . . . . . . . . . . . . . 36 - 8.2. Reseller Extension . . . . . . . . . . . . . . . . . . . 36 - 9. Security Considerations . . . . . . . . . . . . . . . . . . . 36 - 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 36 - 11. Normative References . . . . . . . . . . . . . . . . . . . . 36 + 8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 36 + 8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 36 + 8.3. Reseller Extension . . . . . . . . . . . . . . . . . . . 37 + 9. Security Considerations . . . . . . . . . . . . . . . . . . . 37 + 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 37 + 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 + 11.1. Normative References . . . . . . . . . . . . . . . . . . 37 + 11.2. Informative References . . . . . . . . . . . . . . . . . 38 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 38 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 1. Introduction 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 @@ -165,22 +168,22 @@ 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 . 3.2.2. Role Status A role of an organization object would have its own statuses. Its - corresponding element is . The values of role status are - defined in Section 3.5. + corresponding element is . The values of the role status + are defined in Section 3.5. 3.2.3. Role Identifier A role MAY have a third party assigned identifier such as the IANA ID for registrars. Its corresponding element is . Example of organization role identifier: registrar @@ -198,23 +201,23 @@ [RFC5730]. 3.4. Organization Status Values An organization object MUST always have at least one associated status value. The default value is "ok". Status values that can be added or removed by a client are prefixed with "client". Corresponding status values that can be added or removed by a server are prefixed with "server". The "hold" and - "terminated" are server-managed when the organization has no parent - identifier [Section 3.6] and otherwise MAY be client-managed based on - server policy. + "terminated" status values are server-managed when the organization + has no parent identifier [Section 3.6] and otherwise MAY be client- + managed based on server policy. 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. @@ -443,27 +446,27 @@ 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, role - status and optional role id of the organization. + statuses and optional role id of the organization. * A element that contains the type of the organization, as defined in Section 3.2. - * Zero or more elements of a role. The values of - role status are defined in Section 3.5. + * Zero or more elements that contains the role type. + The values of the role status are defined in Section 3.5. * An OPTIONAL element that contains a third party assigned identifier, such as IANA ID for registrars, as defined in Section 3.2.3. o Zero 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. @@ -644,22 +647,22 @@ 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 three commands to transform organization object - information: to create an instance of an organization + This document provides three commands to transform organization + object information: to create an instance of an organization object, to delete an instance of an organization object, 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 @@ -684,27 +687,27 @@ 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: 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, role - status and optional role id of the organization. + statuses and optional role id of the organization. * A element that contains the type of the organization, as defined in Section 3.2. - * Zero or more elements of a role. The values of - role status are defined in Section 3.5. + * Zero or more elements that contains the role type. + The values of the role status are defined in Section 3.5. * An OPTIONAL element that contains a third party assigned identifier, such as IANA ID for registrars, as defined in Section 3.2.3. o Zero of more 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. @@ -761,21 +764,20 @@ C: C: C: C: C: C: res1523 C: C: reseller - C: ok C: C: 1523res C: C: Example Organization Inc. C: C: 123 Example Dr. C: Suite 100 C: Dulles C: VA C: 20166-6503 @@ -910,52 +912,52 @@ 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: + MAY be omitted if an extension is present. The OPTIONAL + 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. o Zero or more elements that contains the role type, role - status and optional role id of the organization. + statuses and optional role id of the organization. * A element that contains the type of the organization, as defined in Section 3.2. - * Zero or more elements of a role. The values of - role status are defined in Section 3.5. + * Zero or more elements that contains the role type. + The values of the role status are defined in Section 3.5. * An OPTIONAL element that contains a third party assigned identifier, such as IANA ID for registrars, as defined in Section 3.2.3. o Zero or more element that contains the operational status of the organization. - A element contains the following OPTIONAL child elements. - At least one child element MUST be present: + A OPTIONAL element contains the following child elements, + where at least one child element MUST be present: - o A element that contains the identifier of the - parent object. + o An OPTIONAL element that contains the identifier of + the parent object. - o One or two elements that contain postal-address + o Zero to 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 @@ -977,31 +979,31 @@ + 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 An OPTIONAL element that contains the organization's + voice telephone number. - o A element that contains the organization's facsimile - telephone number. + o An OPTIONAL element that contains the organization's + facsimile telephone number. - o A element that contains the organization's email - address. + o An OPTIONAL element that contains the organization's + email address. - o A element that contains the URL to the website of the - organization. + o An OPTIONAL element that contains the URL to the website + of the organization. Example command: C: C: C: C: C: C: res1523 @@ -1126,25 +1128,27 @@ + - + + - @@ -1146,21 +1150,22 @@ type="org:addrType"/> - + @@ -1458,35 +1462,34 @@ 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 + URI: urn:ietf:params:xml:ns:org-1.0 - o Registrant Contact: See the "Author's Address" section of this + Registrant Contact: See the "Author's Address" section of this document. - o XML: None. Namespace URIs do not represent an XML specification. + XML: None. Namespace URIs do not represent an XML specification. Registration request for the organization XML schema: - o URI: urn:ietf:params:xml:ns:org-1.0 - - o Registrant Contact: See the "Author's Address" section of this + URI: urn:ietf:params:xml:ns:org-1.0 + Registrant Contact: See the "Author's Address" section of this document. - o XML: See the "Formal Syntax" section of this document. + XML: See the "Formal Syntax" section of this document. 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 @@ -1516,26 +1519,29 @@ Description: Brief description of the organization role values. Registrant Name: For Standards Track RFCs, state "IESG". For others, give the name of the responsible party. Registrant Contact Information: an email address, postal address, or some other information to be used to contact the registrant. 7.3.2. Initial Registry Contents + Followings are the initial registry contents: + Value: registrar 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 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 @@ -1536,120 +1542,134 @@ 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 Registrant Contact Information: iesg@ietf.org Value: privacyproxy - Description: The entity object instance represents a third-party who - could help to register a domain without exposing the registrants' - private information.. + Description: The entity object instance represents a third-party + who 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 + [RFC7942] before publication. This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a - proposal described in [RFC6982]. The description of implementations + proposal described in [RFC7942]. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. - According to [RFC6982], "this will allow reviewers and working groups + According to [RFC7942], "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit". - CNNIC and Net::DRI (Patrick Mevzek) are in the process of development - research to update organization extension from reseller extension. + Verisign has already implemented this object mapping. CNNIC and + Net::DRI (Patrick Mevzek) are in the process of development research + to update organization objecct from reseller object. Dns Belgium is + planning to implement it after the publication of this document. - Dns Belgium is planning to implement it after the publication of this - document. +8.1. Verisign EPP SDK -8.1. CNNIC Implementation + Organization: Verisign Inc. + + Name: Verisign EPP SDK + + Description: The Verisign EPP SDK includes both a full client + implementation and a full server stub implementation of draft-ietf- + regext-org. + + Level of maturity: Development + + Coverage: All aspects of the protocol are implemented. + + Licensing: GNU Lesser General Public License + + Contact: jgould@verisign.com + + URL: https://www.verisign.com/en_US/channel-resources/domain- + registry-products/epp-sdks + +8.2. CNNIC Implementation Organization: CNNIC Name: EPP Organization Mapping Description: CNNIC is trying to update EPP organization mapping from previous reseller mapping according to this document. - Level of maturity: Research. + Level of maturity: Development - Coverage: EPP organization mapping. + Coverage: EPP organization mapping Contact: zhouguiqing@cnnic.cn -8.2. Reseller Extension +8.3. Reseller Extension - This document was updated from draft-ietf-regext-reseller. CNNIC, - VeriSign and Net::DRI (Patrick Mevzek) have already implemented the - reseller mapping. + This document was updated from [ID.draft-ietf-regext-reseller]. + CNNIC, 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. 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 +11. References + +11.1. 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, . - - [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running - Code: The Implementation Status Section", RFC 6982, - DOI 10.17487/RFC6982, July 2013, - . - - [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible - Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, - February 2015, . + [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running + Code: The Implementation Status Section", BCP 205, + RFC 7942, DOI 10.17487/RFC7942, July 2016, + . [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 8126, DOI 10.17487/RFC8126, June 2017, . [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- @@ -1662,20 +1682,32 @@ 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, . +11.2. Informative References + + [ID.draft-ietf-regext-reseller] + Zhou, L., Kong, N., Guiqing, G., Lee, X., and J. Gould, + "Extensible Provisioning Protocol (EPP) Reseller Mapping", + Dec 2016, + . + + [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible + Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, + February 2015, . + 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. @@ -1734,20 +1767,29 @@ * Updated section 4.2.5 for the "add", "rem" and "chg" example. * Updated section 5 of formal syntax. * Updated section 7.2 for the registration template and initial values. * Updated section 8 of implementation status. + Organization WG document-04: + + * Updated section 3.2, changed the structure of organization + role. + + * Updated references. + + * Updated section 8 of implementation status. + 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 @@ -1772,16 +1814,16 @@ 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. + Verisign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com