--- 1/draft-ietf-regext-org-04.txt 2018-05-07 02:13:26.293719370 -0700 +++ 2/draft-ietf-regext-org-05.txt 2018-05-07 02:13:26.361720979 -0700 @@ -1,22 +1,22 @@ Internet Engineering Task Force L. Zhou Internet-Draft N. Kong Intended status: Standards Track G. Zhou -Expires: November 5, 2018 X. Lee +Expires: November 8, 2018 X. Lee CNNIC J. Gould Verisign, Inc. - May 4, 2018 + May 7, 2018 Extensible Provisioning Protocol (EPP) Organization Mapping - draft-ietf-regext-org-04 + draft-ietf-regext-org-05 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 November 5, 2018. + This Internet-Draft will expire on November 8, 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 @@ -94,22 +94,21 @@ 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 . . . . . . . . . . . . . . 35 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 35 8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 36 8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 36 - 8.3. Reseller Extension . . . . . . . . . . . . . . . . . . . 37 - 9. Security Considerations . . . . . . . . . . . . . . . . . . . 37 + 9. Security Considerations . . . . . . . . . . . . . . . . . . . 36 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 37 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 11.1. Normative References . . . . . . . . . . . . . . . . . . 37 11.2. Informative References . . . . . . . . . . . . . . . . . 38 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 38 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 1. Introduction There are many entities, such as registrars, resellers, DNS service @@ -451,22 +450,23 @@ 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 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 that contains the role type. - The values of the role status are defined in Section 3.5. + * One or more elements that contains the role + statuses. 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. @@ -692,22 +692,23 @@ 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 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 that contains the role type. - The values of the role status are defined in Section 3.5. + * Zero or more elements that contains the role + statuses. 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. @@ -927,31 +928,32 @@ 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 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 that contains the role type. - The values of the role status are defined in Section 3.5. + * Zero or more elements that contains the role + statuses. 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 OPTIONAL element contains the following child elements, + An OPTIONAL element contains the following child elements, where at least one child element MUST be present: o An OPTIONAL element that contains the identifier of the parent object. 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, @@ -1573,25 +1575,20 @@ be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to [RFC7942], "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit". - 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. - 8.1. Verisign EPP SDK Organization: Verisign Inc. Name: Verisign EPP SDK Description: The Verisign EPP SDK includes both a full client implementation and a full server stub implementation of draft-ietf- regext-org. @@ -1614,26 +1611,20 @@ Description: CNNIC is trying to update EPP organization mapping from previous reseller mapping according to this document. Level of maturity: Development Coverage: EPP organization mapping Contact: zhouguiqing@cnnic.cn -8.3. Reseller Extension - - 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 @@ -1684,26 +1675,20 @@ . [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: @@ -1776,20 +1761,29 @@ Organization WG document-04: * Updated section 3.2, changed the structure of organization role. * Updated references. * Updated section 8 of implementation status. + Organization WG document-05: + + * Updated the description of of a role. + + * Removed the third paragraph of "Implementation Status". + + * Remove the Informative Reference to draft-ietf-regext-reseller + from the draft. + 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