--- 1/draft-ietf-regext-allocation-token-00.txt 2017-04-17 06:13:20.346027374 -0700 +++ 2/draft-ietf-regext-allocation-token-01.txt 2017-04-17 06:13:20.374028035 -0700 @@ -1,20 +1,20 @@ Network Working Group J. Gould Internet-Draft VeriSign, Inc. Intended status: Standards Track S. Wodjenski -Expires: April 17, 2017 Neustar - October 14, 2016 +Expires: October 19, 2017 Neustar + April 17, 2017 Allocation Token Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-allocation-token-00 + draft-ietf-regext-allocation-token-01 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,25 +26,25 @@ 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 April 17, 2017. + This Internet-Draft will expire on October 19, 2017. Copyright Notice - Copyright (c) 2016 IETF Trust and the persons identified as the + 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -74,21 +74,22 @@ 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 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 + A.6. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 17 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 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 @@ -615,37 +616,45 @@ in these other specifications apply to this specification as well. 7. 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 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate - Requirement Levels", BCP 14, RFC 2119, March 1997. + Requirement Levels", BCP 14, RFC 2119, + DOI 10.17487/RFC2119, March 1997, + . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, - January 2004. + DOI 10.17487/RFC3688, January 2004, + . [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)", RFC 3915, - September 2004. + DOI 10.17487/RFC3915, September 2004, + . [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", - STD 69, RFC 5730, August 2009. + STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, + . [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) - Domain Name Mapping", STD 69, RFC 5731, August 2009. + Domain Name Mapping", STD 69, RFC 5731, + DOI 10.17487/RFC5731, August 2009, + . [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible - Provisioning Protocol", RFC 7451, February 2015. + 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. 2. Moved Change History to the back section as an Appendix. A.2. Change from 01 to 02 @@ -658,20 +667,24 @@ A.4. Change from 03 to 04 1. Updated the authors for the draft. 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. + Authors' Addresses James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com URI: http://www.verisigninc.com