--- 1/draft-ietf-regext-org-ext-01.txt 2018-02-27 20:13:58.832825769 -0800 +++ 2/draft-ietf-regext-org-ext-02.txt 2018-02-27 20:13:58.876826802 -0800 @@ -1,52 +1,50 @@ Internet Engineering Task Force L. Zhou Internet-Draft N. Kong Intended status: Standards Track J. Wei -Expires: June 8, 2018 X. Lee +Expires: September 1, 2018 X. Lee CNNIC J. Gould VeriSign, Inc. - December 5, 2017 + February 28, 2018 Organization Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-org-ext-01 + draft-ietf-regext-org-ext-02 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. Specified in Extensible Markup Language (XML), this - extended mapping is applied to provide additional features required - for the provisioning of organizations. + objects. 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 @@ -68,69 +66,68 @@ 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 4 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 4 4.1.2. EPP Command . . . . . . . . . . . . . . . . . 4 4.1.3. EPP Command . . . . . . . . . . . . . . . 7 - 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 7 - 4.2.1. EPP Command . . . . . . . . . . . . . . . . 7 - 4.2.2. EPP Command . . . . . . . . . . . . . . . . 8 - 4.2.3. EPP Command . . . . . . . . . . . . . . . . . 8 - 4.2.4. EPP Command . . . . . . . . . . . . . . . 9 - 4.2.5. EPP Command . . . . . . . . . . . . . . . . 9 - 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 11 - 6. Internationalization Considerations . . . . . . . . . . . . . 13 - 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 - 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 14 - 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 14 - 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 14 - 8.1. CNNIC Impelementation . . . . . . . . . . . . . . . . . . 15 - 8.2. Reseller Extension . . . . . . . . . . . . . . . . . . . 15 - 9. Security Considerations . . . . . . . . . . . . . . . . . . . 15 - 10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 16 - 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 - 11.1. Normative References . . . . . . . . . . . . . . . . . . 16 - 11.2. Informative References . . . . . . . . . . . . . . . . . 17 - - Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 17 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 + 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 + 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18 + 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 19 + 8.1. CNNIC Implementation . . . . . . . . . . . . . . . . . . 19 + 8.2. 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 + 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. A domain reseller is an individual or a company that acts as a agent for accredited registrars. A third-party DNS service operator is responsible for a zone where the operator is neither the registrant nor the registrar of records for the delegation. And a privacy proxy is an entity that provides with individuals or organizations domain registration without exposing their private information. These kind of entities are defined as "organizations" with different role types in this document. In order to facilitate provisioning and management of organization - information in a shared central repository, this document proposes a + information in a shared central repository, this document proposes an organization extension mapping for any EPP object like domain names in [RFC5731], hosts in [RFC5732] and contacts in [RFC5733]. The examples provided in this document are used for the domain object for illustration purpose. The host and contact object could be extended in the same way with the domain object. - A organization mapping object defined in [ID.draft-ietf-regext-org] + An organization mapping object defined in [ID.draft-ietf-regext-org] SHOULD be created first. The organization information specified in this document MUST reference the existing organization identifier. This document 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", @@ -180,21 +177,22 @@ This extension does not add any elements to the EPP command or response described in the EPP domain name mapping [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733]. 4.1.2. EPP Command This extension does not add any element to the EPP command described in the EPP domain mapping [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733]. However, additional elements are - defined for the response. + defined for the response in the EPP domain mapping [RFC5731], + host mapping [RFC5732] and contact mapping [RFC5733]. Example command: C: C: C: C: C: C: example.com @@ -205,30 +203,31 @@ C: C: ngcl-mIFICBNP C: C: When an command has been processed successfully, the EPP element MUST contain child elements as described in the EPP object extensions. In addition, the EPP element SHOULD contain a child element that identifies the extension namespace if the object has data associated with this - extension and based on its service policy. The + extension and based on its server policy. The element contains the following child elements: - o A element that contains the identifier of the - organization. An attribute "role" associated with is - used to represent the relationship an organization would have. - See Section 7.3 in [ID.draft-ietf-regext-org] for a list of - values. + o One or more elements are allowed that contains the + identifier of the organization. An attribute "role" associated + with is used to represent the relationship an + organization would have. See Section 7.3 in + [ID.draft-ietf-regext-org] for a list of values. - Example response for an authorized client: + Example response for an authorized client with multiple + organizations: S: S: S: S: S: Command completed successfully S: S: S: @@ -258,20 +257,62 @@ S: myproxy S: S: S: S: ngcl-IvJjzMZc S: test142AWQONJZ S: S: S: + Example response for an authorized client with no + organization: + + S: + S: + S: + S: + S: Command completed successfully + S: + S: + S: + S: example.com + S: EXAMPLE1-REP + S: + S: jd1234 + S: sh8013 + S: sh8013 + S: sh8013 + S: + S: ns1.example.com + S: + S: ClientX + S: ClientY + S: 2015-02-06T04:01:21.0Z + S: 2018-02-06T04:01:21.0Z + S: + S: 2fooBAR + S: + S: + S: + S: + S: + S: + S: + S: ngcl-IvJjzMZc + S: test142AWQONJZ + S: + S: + S: + An EPP error response MUST be returned if an command cannot be processed for any reason. 4.1.3. EPP Command This extension does not add any elements to the EPP command or response described in the EPP domain name mapping [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733]. @@ -297,21 +338,21 @@ the client wants to associate data defined in this extension to the object. The element contains the following child elements: o A element that contains the identifier of the organization. An attribute "role" associated with is used to represent the relationship an organization would have. See Section 7.3 in [ID.draft-ietf-regext-org] for a list of values. - Example Command: + Example Command with only one organization: C: C: C: C: C: C: example.com C: 3 C: @@ -329,20 +370,53 @@ C: C: C: myreseller C: C: C: ABC-12345 C: C: + Example Command with multiple organizations: + + C: + C: + C: + C: + C: + C: example.com + C: 3 + C: + C: ns1.example.com + C: + C: jd1234 + C: sh8013 + C: sh8013 + C: sh8013 + C: + C: fooBAR + C: + C: + C: + C: + C: + C: myreseller + C: myproxy + C: + C: + C: ABC-12345 + C: + C: + When a command has been processed successfully, the EPP response is as described in the EPP object extension. An EPP error response MUST be returned if a command cannot be processed for any reason. 4.2.2. EPP Command This extension does not add any elements to the EPP command or response described in the EPP domain mapping [RFC5731], @@ -414,36 +488,108 @@ C: xmlns:orgext="urn:ietf:params:xml:ns:orgext-1.0"> C: C: myreseller C: C: C: C: ABC-12345 C: C: + Example command, adding multiple organizations: + + C: + C: + C: + C: + C: + C: example.com + C: + C: + C: + C: + C: + C: myreseller + C: myproxy + C: + C: + C: + C: ABC-12345 + C: + C: + + Example command, domain with no organization: + + C: + C: + C: + C: + C: + C: example.com + C: + C: + C: + C: + C: + C: myreseller + C: myproxy + C: + C: + C: + C: ABC-12345 + C: + C: + Example command, removing a reseller: C: C: C: C: C: C: example.com C: C: C: C: C: - C: myreseller + C: + C: + C: + C: + C: ABC-12345 + C: + C: + + Example command, removing multiple organizations: + + C: + C: + C: + C: + C: + C: example.com + C: + C: + C: + C: + C: + C: + C: C: C: C: C: ABC-12345 C: C: Example command, updating reseller identifier: C: @@ -460,115 +606,158 @@ C: xmlns:orgext="urn:ietf:params:xml:ns:orgext-1.0"> C: C: myreseller C: C: C: C: ABC-12345 C: C: + Example command, updating multiple organization identifiers: + + C: + C: + C: + C: + C: + C: example.com + C: + C: + C: + C: + C: + C: myreseller + C: myproxy + C: + C: + C: + C: ABC-12345 + C: + C: + When an extended command has been processed successfully, the EPP response is as described in the EPP object extension. 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 - - - - - + elementFormDefault="qualified" + > Extensible Provisioning Protocol v1.0 Organization Extension Schema v1.0 - - + + - + + + + + + + + + - + - - - - - + + + - - + - - - + - - + - 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 @@ -621,71 +810,71 @@ 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 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 mplementations + proposal described in [RFC6982]. 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 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 organization extension from reseller extension. Verisign is also planning to implement this extension. -8.1. CNNIC Impelementation +8.1. CNNIC Implementation Organization: CNNIC Name: Organization Extension for EPP - Description: CNNIC is trying to update organizaiton extension from + Description: CNNIC is trying to update organization extension from previous reseller extension according to this document. Level of maturity: Research. Coverage: Organization extension for EPP. Contact: zhouguiqing@cnnic.cn 8.2. Reseller Extension This document was updated from draft-ietf-regext-reseller-ext. - CNNIC, Verisign and Patrick Mevzek have already implemented this - extension. + 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. -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. References 11.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate @@ -739,23 +928,23 @@ [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-org] - Zhou, L., Kong, N., Zhou, G., Lee, X., Gould, J., and S. - Hollenbeck, "Extensible Provisioning Protocol (EPP) - Reseller Mapping", Apr 2017, + Zhou, L., Kong, N., Zhou, G., Lee, X., and J. Gould, + "Extensible Provisioning Protocol (EPP) Reseller Mapping", + Feb 2018, . Appendix A. Change Log Initial -00: Individual document submitted. -01: * Updated abstract and introduction. @@ -781,35 +970,38 @@ in response. -03: * Changed author information. * Updated section 3.1. * Removed reseller name element in response. - * Added acknowledgement. + * Added acknowledgment. * Revised the typo "resellerr" to "resellerext". WG document-00: WG document submitted WG document-01: Keep document alive for further discussion. The requirement of reseller information is clear for both registrar and registry. What we should reach a consensus is whether the extension should support only a name or ID and name. Organization WG document-00: Change to a generic organization object extension. - Organization WG document-01: Added "Imeplementation Status" section. + Organization WG document-01: Added "Implementation Status" section. + + Organization WG document-02: Accepted some of the feedbacks on the + mailing list. Modified the examples in the document. Authors' Addresses Linlin Zhou CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 2677