--- 1/draft-ietf-regext-org-ext-09.txt 2018-11-29 19:13:26.882247773 -0800 +++ 2/draft-ietf-regext-org-ext-10.txt 2018-11-29 19:13:26.926248837 -0800 @@ -1,47 +1,48 @@ Internet Engineering Task Force L. Zhou Internet-Draft CNNIC Intended status: Standards Track N. Kong -Expires: February 25, 2019 Consultant +Expires: June 3, 2019 Consultant J. Wei J. Yao CNNIC J. Gould Verisign, Inc. - August 24, 2018 + November 30, 2018 Organization Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-org-ext-09 + draft-ietf-regext-org-ext-10 Abstract - This document describes an extension to EPP object mappings, which is - designed to support assigning an organization to any existing object - (domain, host, contact) as well as any future objects. + This document describes an extension to Extensible Provisioning + Protocol (EPP) object mappings, which is designed to support + assigning an organization to any existing object (domain, host, + contact) as well as any future 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 February 25, 2019. + This Internet-Draft will expire on June 3, 2019. 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 @@ -62,101 +63,106 @@ 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 4 4.1.2. EPP Command . . . . . . . . . . . . . . . . . 4 4.1.3. EPP Query 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 . . . . . . . . . . . . . 17 + 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. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 19 8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 20 9. Security Considerations . . . . . . . . . . . . . . . . . . . 20 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 20 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 11.1. Normative References . . . . . . . . . . . . . . . . . . 20 - 11.2. Informative References . . . . . . . . . . . . . . . . . 21 + 11.2. Informative References . . . . . . . . . . . . . . . . . 22 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 22 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 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 be - other roles of entities involved in the domain registration process - which are not formally defined, such as resellers, DNS service - operators, privacy proxies, etc. + In the business model of domain registration, we usually have three + roles of entities: a registrant, a registrar and a registry. There + may be other roles of entities involved in the domain registration + process which are not formally defined yet, such as resellers, DNS + service operators, privacy proxies, etc. A domain reseller is an individual or a company that acts as an 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 record for the delegation. A privacy proxy is an entity used for domain registrations to protect the private information of the individuals and organizations. 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 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. + organization extension mapping for any Extensible Provisioning + Protocol (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. - 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. + Organization object identifiers defined in [ID.draft-ietf-regext-org] + MUST be known to the server before the organization object can be + associated with the EPP object. 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", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119][RFC8174] when, and only when, they appear in all capitals, as shown here. In examples, "C:" represents lines sent by a protocol client and "S:" represents lines returned by a protocol server. Indentation and white space in examples are provided only to illustrate element relationships and are not a required feature of this specification. 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. + character case. - The XML namespace prefix "orgext" is used, but implementations MUST - NOT depend on it and instead employ a proper namespace-aware XML - parser and serializer to interpret and output the XML documents. + The XML namespace prefix "orgext" is used for the namespace + "urn:ietf:params:xml:ns:epp:orgext-1.0", but implementations MUST NOT + depend on it and instead employ a proper namespace-aware XML parser + and serializer to interpret and output the XML documents. 3. Object Attributes 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. + objects are identified by a server-unique identifier. A "role" + attribute is used to represent the relationship that the organization + has to the EPP object. Any given object MUST have at most one + associated organization ID for any given role value. 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 assigning organizations to EPP objects. 4.1. EPP Query Commands @@ -174,29 +180,30 @@ 4.1.2. EPP Command This extension does not add any elements to the EPP command described in the EPP object mapping. However, additional elements are defined for the response in the EPP object mapping. 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. This element or its - ancestor element MUST identify the extension namespace if the object - has data associated with this extension and based on server policy. - The element contains the following child elements: + ancestor element MUST identify the extension namespace + "urn:ietf:params:xml:ns:epp:orgext-1.0" if the object has data + associated with this extension and based on server policy. The + element contains the following child elements: o Zero or more elements are allowed that contain 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. + identifier of the organization, as defined in Section 3.1. 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 response for an authorized client with multiple organizations: S: S: S: S: S: Command completed successfully S: @@ -218,22 +225,22 @@ S: 2015-02-06T04:01:21.0Z S: 2018-02-06T04:01:21.0Z S: S: 2fooBAR S: S: S: S: S: - S: myreseller - S: myproxy + S: reseller1523 + S: proxy2935 S: S: S: S: ngcl-IvJjzMZc S: test142AWQONJZ S: S: S: Example response for an authorized client with no @@ -299,28 +306,30 @@ This extension defines additional elements for the EPP command described in the EPP object extensions. No additional elements are defined for the EPP response. 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. This element or its ancestor element MUST - identify the extension namespace if the client wants to associate - data defined in this extension to the object. The - element contains the following child elements: + identify the extension namespace "urn:ietf:params:xml:ns:epp:orgext- + 1.0" 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 elements that contain 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. + the organization, as defined in Section 3.1. 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: C: C: example.com @@ -333,21 +342,21 @@ C: sh8013 C: sh8013 C: C: fooBAR C: C: C: C: C: - C: myreseller + C: reseller1523 C: C: C: ABC-12345 C: C: Example Command with multiple organizations: C: C: @@ -365,22 +374,22 @@ C: sh8013 C: sh8013 C: C: fooBAR C: C: C: C: C: - C: myreseller - C: myproxy + C: reseller1523 + C: proxy2935 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 @@ -409,58 +418,65 @@ This extension defines additional elements for the EPP command described in the EPP domain mapping [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733]. No additional elements are defined for the EPP response. The EPP command provides a transform operation that allows a client to modify the attributes of an object. In addition to the EPP command elements, the command MUST contain an element, and the element MUST contain a child element. This element or its ancestor element MUST - identify the extension namespace if the client wants to update the - object with data defined in this extension. The - element contains the following child elements: + identify the extension namespace "urn:ietf:params:xml:ns:epp:orgext- + 1.0" if the client wants to update the object with data defined in + this extension. The element contains the following + child elements: - o An OPTIONAL element that contains attribute values to - be added to the object. + o An OPTIONAL element that contains one or more + elements, as defined in Section 3.1, that add non- + existent organization roles to the object. The + element MUST have a non-empty organization identifier value. The + server SHOULD validate that the element role does not + exist. - o An OPTIONAL element that contains attribute values to - be removed from the object. + o An OPTIONAL element that contains one or more + elements, as defined in Section 3.1, that remove + organization roles from the object. The element MAY + have an empty organization identifier value. The server SHOULD + validate the existence of the element role and the + organization identifier if provided. - o An OPTIONAL element that contains attribute values to - be changed. + o An OPTIONAL element that contains one or more + elements, as defined in Section 3.1, that change + organization role identifiers for the object. The existing + organization identifier value will be replaced for the defined + role. The server SHOULD validate the existence of the + element role. At least one , or element MUST - be provided. The , and - elements contain the following child element: - - o One or more elements that contain 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. + be provided. Example command, adding a reseller: C: C: C: C: C: C: example.com C: C: C: C: C: - C: myreseller + C: reseller1523 C: C: C: C: ABC-12345 C: C: Example command, adding multiple organizations: C: @@ -469,29 +485,28 @@ C: C: C: example.com C: C: C: C: C: - C: myreseller - C: myproxy + C: reseller1523 + C: proxy2935 C: C: C: C: ABC-12345 C: C: - Example command, removing a reseller: C: C: C: C: C: C: example.com C: @@ -540,21 +554,21 @@ C: C: C: example.com C: C: C: C: C: - C: myreseller + C: reseller1523 C: C: C: C: ABC-12345 C: C: Example command, updating multiple organization identifiers: C: @@ -563,29 +577,28 @@ C: C: C: example.com C: C: C: C: C: - C: myreseller - C: myproxy + C: reseller1523 + C: proxy2935 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. An EPP error response MUST be returned if an command cannot be processed for any reason. An attempt to add one organization ID or multiple organization IDs with a particular role value when at least one of them already exists does not change the object at all. A server SHOULD notify clients that object relationships exist by sending a 2305 error response code. An attempt to remove an organization ID or multiple organization IDs with a particular role @@ -759,26 +771,31 @@ 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 for the Extensible Provisioning Protocol (EPP) + Document status: Standards Track + + Reference: RFCXXXX (please replace "XXXX" with the RFC number for + this document after a number is assigned by the RFC Editor) Registrant Name and Email Address: IESG, iesg@ietf.org TLDs: Any IPR Disclosure: None + Status: Active Notes: None 8. Implementation Status Note to RFC Editor: Please remove this section and the reference to [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 @@ -1026,20 +1043,32 @@ * Updated error codes of response. * Modified XML namespace and schema. Organization WG document-09: * Modified XML namespace and schema. * Changed "Exactly one" to "At least one" in section 4.2.5. + Organization WG document-10: + + * Updated the reseller id and dns proxy id in the document. + + * Updated the full xml namespace. + + * Updated the text of EPP , and + . + + * Added "Document satus" and "Reference" in section "EPP + Extension Registry". + Authors' Addresses Linlin Zhou CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing, Beijing 100190 China Email: zhoulinlin@cnnic.cn