--- 1/draft-ietf-regext-allocation-token-06.txt 2018-04-18 11:13:29.209260158 -0700 +++ 2/draft-ietf-regext-allocation-token-07.txt 2018-04-18 11:13:29.249261109 -0700 @@ -1,20 +1,20 @@ Network Working Group J. Gould Internet-Draft VeriSign, Inc. Intended status: Standards Track K. Feher -Expires: August 2, 2018 Neustar - January 29, 2018 +Expires: October 20, 2018 Neustar + April 18, 2018 Allocation Token Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-allocation-token-06 + draft-ietf-regext-allocation-token-07 Abstract This document describes an Extensible Provisioning Protocol (EPP) extension for including an Allocation Token in query and transform commands. The Allocation Token is used as a credential that authorizes a client to request the allocation of a specific object from the server, using one of the EPP transform commands including create and transfer. @@ -26,21 +26,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 http://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 August 2, 2018. + This Internet-Draft will expire on October 20, 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 (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -71,33 +71,37 @@ 4.1. Allocation Token Extension Schema . . . . . . . . . . . . 14 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 15 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 15 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 15 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 16 6.2. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 16 6.3. Neustar gTLD SRS . . . . . . . . . . . . . . . . . . . . 17 7. Security Considerations . . . . . . . . . . . . . . . . . . . 17 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 - 9. Normative References . . . . . . . . . . . . . . . . . . . . 18 + 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 + 9.1. Normative References . . . . . . . . . . . . . . . . . . 18 + 9.2. Informative References . . . . . . . . . . . . . . . . . 19 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 19 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 19 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 19 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 19 A.5. Change from 04 to REGEXT 00 . . . . . . . . . . . . . . . 19 A.6. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 19 A.7. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 19 A.8. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 19 A.9. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 19 A.10. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 20 A.11. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 20 + A.12. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 22 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 1. Introduction This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP) [RFC5730]. This mapping, an extension to EPP object mappings like the EPP domain name mapping [RFC5731], supports passing an Allocation Token as a credential that authorizes a client to request the allocation of a specific object from the server, using one of the EPP transform commands including @@ -602,36 +606,36 @@ IPR Disclosure: None Status: Active Notes: None 6. Implementation Status Note to RFC Editor: Please remove this section and the reference to - RFC 6982 [RFC6982] before publication. + RFC 7942 [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 RFC 6982 - [RFC6982]. The description of implementations in this section is + Internet-Draft, and is based on a proposal described in RFC 7942 + [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 listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. - According to RFC 6982 [RFC6982], "this will allow reviewers and + According to RFC 7942 [RFC7942], "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit". 6.1. Verisign EPP SDK Organization: Verisign Inc. @@ -719,44 +723,48 @@ 8. Acknowledgements The authors wish to acknowledge the original concept for this draft and the efforts in the initial versions of this draft by Trung Tran and Sharon Wodjenski. Special suggestions that have been incorporated into this document were provided by Scott Hollenbeck, Rubens Kuhl, Alexander Mayrhofer, and Patrick Mevzek. -9. Normative References +9. References + +9.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, . [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, . [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, DOI 10.17487/RFC5731, August 2009, . - [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running - Code: The Implementation Status Section", RFC 6982, - DOI 10.17487/RFC6982, July 2013, . + [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running + Code: The Implementation Status Section", BCP 205, + RFC 7942, DOI 10.17487/RFC7942, July 2016, + . + +9.2. Informative References [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, February 2015, . Appendix A. Change History A.1. Change from 00 to 01 1. Amended XML Namespace section of IANA Considerations, added EPP @@ -885,20 +893,27 @@ the confusion and lack of known applicability. 3. Updates based on feedback from Scott Hollenbeck, that include: 1. Revised XML schema to included a minimum length of 1 for the allocationTokenType. 2. Revised the "IANA Considerations" section to include the registration of the XML schema. 3. Revised the "Security Considerations" section to include considerations for the definition of the Allocation Tokens. +A.12. Change from REGEXT 06 to REGEXT 07 + + 1. Updates based on feedback from Patrick Mevzek: + + 1. Updated obsoleted RFC 7942 to RFC 7942. + 2. Moved RFC 7451 to an informational reference. + Authors' Addresses James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com URI: http://www.verisigninc.com