--- 1/draft-ietf-regext-allocation-token-04.txt 2018-01-02 07:14:42.095240326 -0800 +++ 2/draft-ietf-regext-allocation-token-05.txt 2018-01-02 07:14:42.275244592 -0800 @@ -1,50 +1,50 @@ Network Working Group J. Gould Internet-Draft VeriSign, Inc. Intended status: Standards Track K. Feher -Expires: April 21, 2018 Neustar - October 18, 2017 +Expires: July 6, 2018 Neustar + January 2, 2018 Allocation Token Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-allocation-token-04 + draft-ietf-regext-allocation-token-05 Abstract This document describes an Extensible Provisioning Protocol (EPP) - extension for including an allocation token or code for allocating an + extension for including an allocation token or 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. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. 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 21, 2018. + This Internet-Draft will expire on July 6, 2018. Copyright Notice - Copyright (c) 2017 IETF Trust and the persons identified as the + 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 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 @@ -79,38 +79,39 @@ 7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 9. Normative References . . . . . . . . . . . . . . . . . . . . 18 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.7. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 20 A.8. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 20 A.9. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 20 + A.10. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 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 - commands. It is up to server policy which EPP transform commands and - which objects support the allocation token. The allocation token MAY - be returned to an authorized client for passing out-of-band to a - client that uses it with an EPP transform command. + [RFC5731], for passing an allocation token to one of the EPP + transform commands including create, update, and transfer. A client + MUST pass an allocation token known to the server to be authorized to + use one of the supported EPP transform commands. It is up to server + policy which EPP transform commands and which objects support the + allocation token. The allocation token MAY be returned to an + authorized client for passing out-of-band to a client that uses it + with an EPP transform command. 1.1. Conventions Used in This Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented in order to develop a conforming @@ -448,21 +449,21 @@ The EPP request command provides a transform operation that allows a client to request the transfer of an object. In addition to the EPP command elements described in an object mapping like [RFC5731], the command MUST contain a child element, as defined in Section 2.1, that identifies the extension namespace for the client to be authorized to transfer and allocate the object. If the allocation token (Section 2.1) does not match the object's allocation token (Section 2.1), the server MUST return an EPP error result code of - 2201.: + 2201. Example request command to allocate the domain object with the allocation token: C: C: C: C: C: @@ -495,21 +496,21 @@ definition of the restore command within [RFC3915]. An extension of an empty EPP command defines a new verb that transforms an object. In addition to the EPP command elements described in an object mapping like [RFC5731], the command MUST contain a child element, as defined in Section 2.1, that identifies the extension namespace for the client to be authorized to allocate the object. If the allocation token (Section 2.1) does not match the object's allocation token (Section 2.1), the server MUST return an EPP error result code of - 2201.: + 2201. Example use an extension of an empty command to release a domain object with an allocation token: C: C: C: C: C: @@ -705,20 +706,23 @@ 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. 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 Patrick Mevzek. + 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, . @@ -781,20 +785,36 @@ A.8. Change from REGEXT 02 to REGEXT 03 1. Changed Neustar author to Kal Feher. A.9. Change from REGEXT 03 to REGEXT 04 1. Added Neustar implementation to the Implementation Status section. +A.10. Change from REGEXT 04 to REGEXT 05 + + 1. Updates based on feedback from Patrick Mevzek, that include: + + 1. Remove "or code" from the Abstract section. + 2. Add a missing "to" in "an allocation token TO one of the + EPP..." in the Introduction section. + 3. Reword the "The allocation token is known to the server..." + sentence in the Introduction section. + 4. Modify the "The allocation token MAY be returned to an + authorized client for passing out-of-band to a client that + uses it with an EPP transform command" to clarify who the two + separate clients are. + 5. Removed an unneeded ":" from the EPP Command and + EPP Command sections. + Authors' Addresses James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com URI: http://www.verisigninc.com