--- 1/draft-ietf-regext-org-05.txt 2018-05-08 21:13:19.647414131 -0700 +++ 2/draft-ietf-regext-org-06.txt 2018-05-08 21:13:19.715415762 -0700 @@ -1,22 +1,22 @@ Internet Engineering Task Force L. Zhou Internet-Draft N. Kong Intended status: Standards Track G. Zhou -Expires: November 8, 2018 X. Lee +Expires: November 10, 2018 X. Lee CNNIC J. Gould Verisign, Inc. - May 7, 2018 + May 9, 2018 Extensible Provisioning Protocol (EPP) Organization Mapping - draft-ietf-regext-org-05 + draft-ietf-regext-org-06 Abstract This document describes an Extensible Provisioning Protocol (EPP) mapping for provisioning and management of organization objects stored in a shared central repository. Specified in Extensible Markup Language (XML), this extended mapping is applied to provide additional features required for the provisioning of organizations. Status of This Memo @@ -27,21 +27,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 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 @@ -76,35 +76,35 @@ 3.3. Contact and Client Identifiers . . . . . . . . . . . . . 5 3.4. Organization Status Values . . . . . . . . . . . . . . . 5 3.5. Role Status Values . . . . . . . . . . . . . . . . . . . 6 3.6. Parent Identifier . . . . . . . . . . . . . . . . . . . . 7 3.7. URL . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.8. Dates and Times . . . . . . . . . . . . . . . . . . . . . 7 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 8 4.1.2. EPP Command . . . . . . . . . . . . . . . . . 9 - 4.1.3. EPP Command . . . . . . . . . . . . . . . 15 + 4.1.3. EPP Query Command . . . . . . . . . . . . 15 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 15 4.2.1. EPP Command . . . . . . . . . . . . . . . . 15 4.2.2. EPP Command . . . . . . . . . . . . . . . . 19 4.2.3. EPP Command . . . . . . . . . . . . . . . . . 20 4.2.4. EPP Command . . . . . . . . . . . . . . . 20 4.2.5. EPP Command . . . . . . . . . . . . . . . . 21 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 25 6. Internationalization Considerations . . . . . . . . . . . . . 33 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 33 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 34 7.3. Role Values Registry . . . . . . . . . . . . . . . . . . 34 7.3.1. Registration Template . . . . . . . . . . . . . . . . 34 - 7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 35 + 7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 34 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 35 8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 36 8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 36 9. Security Considerations . . . . . . . . . . . . . . . . . . . 36 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 37 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 11.1. Normative References . . . . . . . . . . . . . . . . . . 37 11.2. Informative References . . . . . . . . . . . . . . . . . 38 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 38 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 @@ -316,21 +316,21 @@ mappings described here are specifically for use in provisioning and managing organization information via EPP. 4.1. EPP Query Commands EPP provides two commands to retrieve organization information: to determine if an organization object can be provisioned within a repository, and to retrieve detailed information associated with an organization object. This document does not define a mapping for the EPP command to retrieve - organization-object transfer status information.. + organization-object transfer status information. 4.1.1. EPP Command The EPP command is used to determine if an object can be provisioned within a repository. It provides a hint that allows a client to anticipate the success or failure of provisioning an object using the command, as object-provisioning requirements are ultimately a matter of server policy. In addition to the standard EPP command elements, the command @@ -536,21 +536,21 @@ o A element that contains the identifier of the client that last updated the organization object. This element MUST NOT be present if the organization has never been modified. o A element that contains the date and time of the most recent organization object modification. This element MUST NOT be present if the organization object has never been modified. Example response for "Example Registrar Inc." organization - object with registrar identifier "1362": + organization object with identifier "registrar1362": S: S: S: S: S: Command completed successfully S: S: S: @@ -589,21 +589,21 @@ S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: Example response for "Example Reseller Inc." organization - object of reseller type managed by registrar identifier "1362": + object of reseller type managed by identifier "registrar1362": S: S: S: S: S: Command completed successfully S: S: S: @@ -623,41 +623,41 @@ S: Suite 100 S: Dulles S: VA S: 20166-6503 S: US S: S: S: +1.7035555556 S: http://organization.example S: sh8013 - S: 1362 + S: 1362 S: ClientX S: 1999-04-03T22:00:00.0Z S: ClientX S: 1999-12-03T09:00:00.0Z S: S: S: S: ABC-12345 S: 54322-XYZ 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 The transfer semantics does not apply to organization object. No EPP - command is defined in this document. + query command is defined in this document. 4.2. EPP Transform Commands This document provides three commands to transform organization object information: to create an instance of an organization object, to delete an instance of an organization object, and to change information associated with an organization object. This document does not define a mapping for the EPP and command. @@ -1014,21 +1014,20 @@ C: C: privacyproxy C: clientLinkProhibited C: C: clientLinkProhibited C: C: C: sh8014 C: C: reseller - C: clientDeleteProhibited C: C: C: C: C: C: 124 Example Dr. C: Suite 200 C: Dulles C: VA C: 20166-6503 @@ -1466,54 +1465,49 @@ 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:org-1.0 - Registrant Contact: See the "Author's Address" section of this - document. + Registrant Contact: IESG XML: None. Namespace URIs do not represent an XML specification. Registration request for the organization XML schema: URI: urn:ietf:params:xml:ns:org-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 Object Extension - - Document status: Standards Track - - Reference: (insert reference to RFC version of this document) + Name of Extension: Extensible Provisioning Protocol (EPP) + Organization Mapping - 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 7.3. Role Values Registry The following values should be registered by the IANA in the "EPP Organization Role Values" registry. The registration policy for this registry is "Expert Review" [RFC8126]. 7.3.1. Registration Template Value: the string value being registered. @@ -1770,20 +1764,30 @@ Organization WG document-05: * Updated the description of of a role. * Removed the third paragraph of "Implementation Status". * Remove the Informative Reference to draft-ietf-regext-reseller from the draft. + Organization WG document-06: + + * Updated typos. + + * 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 @@ -1804,20 +1808,19 @@ China Phone: +86 10 5881 2692 Email: zhouguiqing@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