--- 1/draft-ietf-regext-allocation-token-01.txt 2017-06-23 12:13:08.666032108 -0700 +++ 2/draft-ietf-regext-allocation-token-02.txt 2017-06-23 12:13:08.706033069 -0700 @@ -1,20 +1,20 @@ Network Working Group J. Gould Internet-Draft VeriSign, Inc. Intended status: Standards Track S. Wodjenski -Expires: October 19, 2017 Neustar - April 17, 2017 +Expires: December 25, 2017 Neustar + June 23, 2017 Allocation Token Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-allocation-token-01 + draft-ietf-regext-allocation-token-02 Abstract This document describes an Extensible Provisioning Protocol (EPP) extension for including an allocation token or code for allocating an object like a domain name to the client. The allocation token MAY be transferred out-of-band to a client to give them authorization to allocate an object using one of the EPP transform commands including create, update, 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 October 19, 2017. + This Internet-Draft will expire on December 25, 2017. Copyright Notice Copyright (c) 2017 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 @@ -65,31 +65,34 @@ 3.2.1. EPP Command . . . . . . . . . . . . . . . . 11 3.2.2. EPP Command . . . . . . . . . . . . . . . . 12 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 12 3.2.4. EPP Command . . . . . . . . . . . . . . . 12 3.2.5. EPP Command . . . . . . . . . . . . . . . . 13 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 14 4.1. Allocation Token Extension Schema . . . . . . . . . . . . 15 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 15 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 16 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 16 - 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16 - 8. Normative References . . . . . . . . . . . . . . . . . . . . 16 - Appendix A. Change History . . . . . . . . . . . . . . . . . . . 17 - A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 17 - A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 17 - A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 17 - A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 17 - A.5. Change from 04 to REGEXT 00 . . . . . . . . . . . . . . . 17 - A.6. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 17 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 + 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 16 + 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 17 + 7. Security Considerations . . . . . . . . . . . . . . . . . . . 17 + 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 + 9. Normative References . . . . . . . . . . . . . . . . . . . . 17 + Appendix A. Change History . . . . . . . . . . . . . . . . . . . 18 + A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 18 + A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 18 + A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 18 + A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 18 + A.5. Change from 04 to REGEXT 00 . . . . . . . . . . . . . . . 18 + A.6. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 19 + A.7. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 19 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 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], for passing an allocation token one of the EPP transform commands including create, update, and transfer. The allocation token is known to the server to authorize a client that passes a matching allocation token with one of the supported EPP transform @@ -601,33 +604,79 @@ Registrant Name and Email Address: IESG, TLDs: Any IPR Disclosure: None Status: Active Notes: None -6. Security Considerations +6. Implementation Status + + Note to RFC Editor: Please remove this section and the reference to + RFC 6982 [RFC6982] 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 + 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 + 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. + + Name: Verisign EPP SDK + + Description: The Verisign EPP SDK includes both a full client + implementation and a full server stub implementation of draft-ietf- + regext-allocation-token. + + Level of maturity: Production + + Coverage: All aspects of the protocol are implemented. + + Licensing: GNU Lesser General Public License + + Contact: jgould@verisign.com + + URL: https://www.verisign.com/en_US/channel-resources/domain- + registry-products/epp-sdks + +7. Security Considerations The mapping extensions described in this document do not provide any security services beyond those described by EPP [RFC5730] and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well. -7. Acknowledgements +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. -8. Normative References +9. 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, . @@ -638,20 +687,25 @@ [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, + . + [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 Extension Registry section. @@ -671,20 +725,24 @@ A.5. Change from 04 to REGEXT 00 1. Changed to regext working group draft by changing draft-gould- allocation-token to draft-ietf-regext-allocation-token. A.6. Change from REGEXT 00 to REGEXT 01 1. Ping update. +A.7. Change from REGEXT 01 to REGEXT 02 + + 1. Added the Implementation Status section. + Authors' Addresses James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com URI: http://www.verisigninc.com