--- 1/draft-ietf-regext-org-ext-06.txt 2018-06-14 18:13:08.093259868 -0700 +++ 2/draft-ietf-regext-org-ext-07.txt 2018-06-14 18:13:08.133260843 -0700 @@ -1,45 +1,45 @@ Internet Engineering Task Force L. Zhou Internet-Draft N. Kong Intended status: Standards Track J. Wei -Expires: November 10, 2018 X. Lee +Expires: December 17, 2018 X. Lee CNNIC J. Gould Verisign, Inc. - May 9, 2018 + June 15, 2018 Organization Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-org-ext-06 + draft-ietf-regext-org-ext-07 Abstract - This mapping which is an extension to EPP object mappings, is + 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. 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 November 10, 2018. + This Internet-Draft will expire on December 17, 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 @@ -136,63 +136,63 @@ 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. orgext-1.0 in this document is used as an abbreviation for - urn:ietf:params:xml:ns:orgext-1.0. + urn:ietf:params:xml:ns:orgext-1.0. 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. 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. + 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 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 use in provisioning and - managing organization information via EPP. + mappings described here are specifically for assigning organizations + to EPP objects. 4.1. EPP Query Commands - EPP provides three commands to retrieve domain information: - to determine if a domain object can be provisioned within a - repository, to retrieve detailed information associated with a - domain object, and to retrieve domain-object transfer - status information. + EPP provides three commands to retrieve EPP object information: + to determine if an object can be provisioned within a + repository, to retrieve detailed information associated with + an object, and to retrieve object transfer status + information. 4.1.1. 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]. + or response described in the EPP object mapping. 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 in the EPP domain mapping [RFC5731], - host mapping [RFC5732] and contact mapping [RFC5733]. + 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 that identifies the extension namespace 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 contains the @@ -287,31 +287,30 @@ S: S: S: An EPP error response MUST be returned if an command cannot be processed for any reason. 4.1.3. EPP Query Command This extension does not add any elements to the EPP query - command or query response described in the EPP domain name - mapping [RFC5731], host mapping [RFC5732] and contact mapping - [RFC5733]. + command or query response described in the EPP object + mapping. 4.2. EPP Transform Commands - EPP provides five commands to transform domain objects: to - create an instance of a domain object, to delete an instance - of a domain object, to extend the validity period of a domain - object, to manage domain object sponsorship changes, and - to change information associated with a domain object. + EPP provides five commands to transform EPP objects: to + create an instance of an object, to delete an instance of an + object, to extend the validity period of an object, + to manage the object sponsorship changes, and to + change information associated with an object. 4.2.1. EPP Command 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 @@ -393,47 +392,44 @@ 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], - host mapping [RFC5732] and contact mapping [RFC5733]. + or response described in the EPP object mapping. 4.2.3. EPP Command This extension does not add any elements to the EPP command - or response described in the EPP domain mapping [RFC5731], - host mapping [RFC5732] and contact mapping [RFC5733]. + or response described in the EPP object mapping. 4.2.4. EPP Command This extension does not add any elements to the EPP - command or response described in the EPP domain mapping - [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733], but - after a successful transfer of an object with an assigned + command or response described in the EPP object mapping, + but after a successful transfer of an object with an assigned organization, the handling of the assigned organization is dependent on the organization roles and server policy. 4.2.5. EPP Command 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 attribute of an object. In addition to the EPP + 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 that identifies the extension namespace 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. @@ -715,21 +711,21 @@ 6. Internationalization Considerations EPP is represented in XML, which provides native support for encoding information using the Unicode character set and its more compact representations including UTF-8. Conformant XML processors recognize both UTF-8 and UTF-16. Though XML includes provisions to identify and use other character encodings through use of an "encoding" attribute in an declaration, use of UTF-8 is RECOMMENDED. - As an extension of the EPP domain name mapping, the elements, element + As an extension of the EPP object mapping, the elements, element content described in this document MUST inherit the internationalization conventions used to represent higher-layer domain and core protocol structures present in an XML instance that includes this extension. 7. IANA Considerations 7.1. XML Namespace This document uses URNs to describe XML namespaces and XML schemas @@ -992,20 +988,24 @@ Organization WG document-06: * Updated "Abstraction". * Added "Query" for " Query Command". * Change "Registrant Contact" to IESG in section 7.1. * Modified section 7.2. + Organization WG document-07: + + * Updated "Abstraction". + 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