--- 1/draft-ietf-regext-org-10.txt 2018-10-10 01:13:16.493334436 -0700 +++ 2/draft-ietf-regext-org-11.txt 2018-10-10 01:13:16.581336544 -0700 @@ -1,24 +1,24 @@ Internet Engineering Task Force L. Zhou Internet-Draft CNNIC Intended status: Standards Track N. Kong -Expires: February 25, 2019 Consultant +Expires: April 13, 2019 Consultant G. Zhou J. Yao CNNIC J. Gould Verisign, Inc. - August 24, 2018 + October 10, 2018 Extensible Provisioning Protocol (EPP) Organization Mapping - draft-ietf-regext-org-10 + draft-ietf-regext-org-11 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 @@ -29,21 +29,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 February 25, 2019. + This Internet-Draft will expire on April 13, 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 @@ -285,21 +285,21 @@ reseller. The parent identifier, as defined with the element, represents the parent organization identifier in a child organization. Take a reseller organization, for example, the parent identifier is not defined for the top level reseller, namely the registrar of the registry. An N-tier reseller has a parent reseller and at least one child reseller. A reseller customer has a parent reseller and no child resellers. - Loops SHOULD be prohibited. For example: if organization A has B as + Loops MUST be prohibited. For example: if organization A has B as its parent identifier, organization B should not have organization A as its parent identifier. The same is true for larger loops involving three or more organizations. 3.7. URL The URL represents the organization web home page, as defined with the element. 3.8. Dates and Times @@ -674,26 +674,20 @@ such situations, the server MUST return a 1001 response code to the client to note that the command has been received and processed but that the requested action is pending. The server MUST also manage the status of the object that is the subject of the command to reflect the initiation and completion of the requested action. Once the action has been completed, the client MUST be notified using a service message that the action has been completed and that the status of the object has changed. Other notification methods MAY be used in addition to the required service message. - Server operators SHOULD confirm that a client is authorized to - perform a transform command on a given object. Any attempt to - transform an object by an unauthorized client MUST be rejected, and - the server MUST return a 2201 response code to the client to note - that the client lacks privileges to execute the requested command. - 4.2.1. EPP Command The EPP command provides a transform operation that allows a client to create an organization object. In addition to the standard EPP command elements, the command MUST contain a element. This element or its ancestor element MUST identify the organization namespace. The element contains the following child elements: o An element that contains the desired server-unique @@ -1088,21 +1082,22 @@ when offline processing of the action has been completed. Examples describing a command that requires offline review are included here. Note the result code and message returned in response to the command. S: S: S: S: -S: Command completed successfully; action pending + S: Command completed successfully; + S: action pending S: S: S: S: res1523 S: 1999-04-03T22:00:00.0Z S: S: S: S: ABC-12345 @@ -1140,21 +1135,22 @@ o An element that contains the date and time describing when review of the requested action was completed. Example "review completed" service message: S: S: S: S: -S: Command completed successfully; ack to dequeue + S: Command completed successfully; + S: ack to dequeue S: S: S: 1999-04-04T22:01:00.0Z S: Pending action completed successfully. S: S: S: S: res1523 S: @@ -1572,21 +1568,21 @@ End of schema. --> 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 representations including UTF-8. Conformant XML processors recognize - both UTF-8 [RFC3629] and UTF-16 [RFC2718]. Though XML includes + both UTF-8 [RFC3629] and UTF-16 [RFC2781]. 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 organization object mapping, the elements and 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. @@ -1770,25 +1766,20 @@ 11. References 11.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . - [RFC2718] Masinter, L., Alvestrand, H., Zigmond, D., and R. Petke, - "Guidelines for new URL Schemes", RFC 2718, - DOI 10.17487/RFC2718, November 1999, - . - [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 2003, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, @@ -1827,20 +1818,24 @@ . [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 + [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO + 10646", RFC 2781, DOI 10.17487/RFC2781, February 2000, + . + [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, February 2015, . Appendix A. Change Log Initial -00: Individual document submitted. -01: @@ -1974,20 +1969,27 @@ * Updated writing typos. * Modified XML namespace and schema. Organization WG document-10: * Modified XML namespace and schema. * Removed the maxOccurs value of "reason" element. + Organization WG document-11: + + * Typo of RFC2781 and moved this reference in "Informative + References". + + * "Loops MUST be prohibited." in section 3.6. + Authors' Addresses Linlin Zhou CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing, Beijing 100190 China Email: zhoulinlin@cnnic.cn Ning Kong