--- 1/draft-ietf-regext-org-ext-03.txt 2018-05-03 23:13:09.229693404 -0700 +++ 2/draft-ietf-regext-org-ext-04.txt 2018-05-03 23:13:09.269694354 -0700 @@ -1,22 +1,22 @@ Internet Engineering Task Force L. Zhou Internet-Draft N. Kong Intended status: Standards Track J. Wei -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 Organization Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-org-ext-03 + draft-ietf-regext-org-ext-04 Abstract This mapping, an extension to EPP object mappings like the EPP domain name mapping [RFC5731], to support assigning an organization to any existing object (domain, host, contact) as well as any future objects. Status of This Memo @@ -26,21 +26,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 @@ -73,33 +73,34 @@ 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 4 4.1.2. EPP Command . . . . . . . . . . . . . . . . . 4 4.1.3. EPP Command . . . . . . . . . . . . . . . 7 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8 4.2.1. EPP Command . . . . . . . . . . . . . . . . 8 4.2.2. EPP Command . . . . . . . . . . . . . . . . 10 4.2.3. EPP Command . . . . . . . . . . . . . . . . . 10 4.2.4. EPP Command . . . . . . . . . . . . . . . 11 4.2.5. EPP Command . . . . . . . . . . . . . . . . 11 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 15 - 6. Internationalization Considerations . . . . . . . . . . . . . 18 - 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 - 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 18 + 6. Internationalization Considerations . . . . . . . . . . . . . 17 + 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 + 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18 - 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 19 - 8.1. CNNIC Implementation . . . . . . . . . . . . . . . . . . 19 - 8.2. Reseller Extension . . . . . . . . . . . . . . . . . . . 20 + 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 18 + 8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 19 + 8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 19 + 8.3. Reseller Extension . . . . . . . . . . . . . . . . . . . 20 9. Security Considerations . . . . . . . . . . . . . . . . . . . 20 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 20 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 11.1. Normative References . . . . . . . . . . . . . . . . . . 20 11.2. Informative References . . . . . . . . . . . . . . . . . 21 - Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 21 + Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 1. Introduction In the business model of domain registration, we usually have 3 roles of entities, a registrant, a registrar and a registry. There may have some other roles of entities involved in the domain registration process which are not formally defined, such as resellers, DNS service operators, privacy proxy, etc. @@ -141,22 +142,23 @@ 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. orgext-1.0 in this document is used as an abbreviation for urn:ietf:params:xml:ns:orgext-1.0. 3. Object Attributes - This extension adds additional elements to the EPP domain name - mapping [RFC5731]. Only the new elements are described here. + This extension adds additional elements to EPP object mappings like + the EPP domain name mapping [RFC5731]. Only the new elements are + described here. 3.1. Organization Identifier Organization identifier provides the ID of an organization. Its corresponding element is which refers to the element defined in [ID.draft-ietf-regext-org]. All organization objects are identified by a server-unique identifier. 4. EPP Command Mapping @@ -314,21 +316,21 @@ The EPP command provides a transform operation that allows a client to create an object. In addition to the EPP command elements described in the EPP object extensions, the command MUST contain an element, and the element MUST contain a child element that identifies the extension namespace if the client wants to associate data defined in this extension to the object. The element contains the following child elements: - o One or more element that contains the identifier of + o One or more elements that contains the identifier of the organization. The "role" attribute is used to represent the relationship that the organization has to the object. See Section 7.3 in [ID.draft-ietf-regext-org] for a list of values. Example Command with only one organization: C: C: C: C: @@ -492,42 +494,20 @@ C: C: myreseller C: myproxy C: C: C: C: ABC-12345 C: C: - Example command, domain with no organization: - - - - - - - example.com - - - - - - - - ABC-12345 - - - C: - Example command, removing a reseller: C: C: C: C: C: C: example.com C: @@ -682,41 +661,46 @@ + @@ -752,26 +736,26 @@ 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:orgext-1.0 + URI: urn:ietf:params:xml:ns:orgext-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: 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 Extension Document status: Standards Track @@ -774,73 +758,95 @@ Name of Extension: Organization Extension Document status: Standards Track Reference: (insert reference to RFC version of this document) Registrant Name and Email Address: IESG TLDs: any + IPR Disclosure: none Status: active Notes: none 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". - VeriSign has already implemented this extension. CNNIC and Net::DRI + Verisign has already implemented this extension. CNNIC and Net::DRI (Patrick Mevzek) are in the process of development research to update organization extension from reseller extension. Dns Belgium is planning to implement it after the publication of this document. -8.1. CNNIC Implementation +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-ext. + + 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: Organization Extension for EPP Description: CNNIC is trying to update organization extension from previous reseller extension according to this document. - Level of maturity: Research. + Level of maturity: Development - Coverage: Organization extension for EPP. + Coverage: Organization extension for EPP Contact: zhouguiqing@cnnic.cn -8.2. Reseller Extension +8.3. Reseller Extension - This document was updated from draft-ietf-regext-reseller-ext. - CNNIC, VeriSign and Net::DRI (Patrick Mevzek) have already + This document was updated from [ID.draft-ietf-regext-reseller-ext]. + CNNIC, Verisign and Net::DRI (Patrick Mevzek) have already implemented this extension. 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], [RFC5731], [RFC5732] and [RFC5733] or those caused by the protocol layers used by EPP. @@ -873,28 +879,24 @@ . [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 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, + . [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, @@ -907,23 +909,33 @@ 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-org] Zhou, L., Kong, N., Zhou, G., Lee, X., and J. Gould, "Extensible Provisioning Protocol (EPP) Reseller Mapping", - Feb 2018, + Apr 2018, . + [ID.draft-ietf-regext-reseller-ext] + Zhou, L., Kong, N., Wei, J., 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 and introduction. * Revised typos in info response. @@ -974,21 +986,32 @@ mailing list. Modified the examples in the document. Organization WG document-03: * Updated typos. * Changed some descriptions about and role attribute. * Modified the example of "domain with no organization". - * Updated section 8, adding implementation status of VeriSign. + * Updated section 8, adding implementation status of Verisign. + + Organization WG document-04: + + * Updated typos. + + * Removed the example of command, domain with no + organization. + + * 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 @@ -1014,16 +1037,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