--- 1/draft-ietf-regext-org-ext-05.txt 2018-05-08 21:13:18.306315621 -0700 +++ 2/draft-ietf-regext-org-ext-06.txt 2018-05-08 21:13:18.350316890 -0700 @@ -1,46 +1,45 @@ Internet Engineering Task Force L. Zhou Internet-Draft N. Kong Intended status: Standards Track J. Wei -Expires: November 8, 2018 X. Lee +Expires: November 10, 2018 X. Lee CNNIC J. Gould Verisign, Inc. - May 7, 2018 + May 9, 2018 Organization Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-org-ext-05 + draft-ietf-regext-org-ext-06 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. + This mapping which is an extension to EPP object mappings, 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 8, 2018. + This Internet-Draft will expire on November 10, 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 @@ -65,21 +64,21 @@ Table of Contents 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.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 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17 @@ -91,33 +90,33 @@ 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. + 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 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. + 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. An organization mapping object defined in [ID.draft-ietf-regext-org] @@ -285,24 +284,24 @@ 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 +4.1.3. EPP Query Command - This extension does not add any elements to the EPP - command or response described in the EPP domain name + 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]. 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. @@ -733,46 +732,42 @@ 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: URI: urn:ietf:params:xml:ns:orgext-1.0 - Registrant Contact: See the "Author's Address" section of this - document. + Registrant Contact: IESG 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 - - Reference: (insert reference to RFC version of this document) + Name of Extension: Organization Extension for the Extensible + Provisioning Protocol (EPP) - Registrant Name and Email Address: IESG + Registrant Name and Email Address: IESG, iesg@ietf.org - TLDs: any + TLDs: Any - IPR Disclosure: none + IPR Disclosure: None - Status: active + Status: Active - Notes: none + 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 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 @@ -988,20 +982,30 @@ Organization WG document-05: * Removed the minOccurs="0" from the addRemChgType type of the XML schema * Removed the third paragraph of "Implementation Status". * Remove the Informative Reference to draft-ietf-regext-reseller- ext from the draft. + Organization WG document-06: + + * Updated "Abstraction". + + * Added "Query" for " Query Command". + + * Change "Registrant Contact" to IESG in section 7.1. + + * Modified section 7.2. + 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 @@ -1007,35 +1011,34 @@ Email: zhoulinlin@cnnic.cn Ning Kong CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 3147 Email: nkong@cnnic.cn - Junkai Wei CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing, Beijing 100190 China Phone: +86 10 5881 3494 Email: weijunkai@cnnic.cn + 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. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com