--- 1/draft-ietf-regext-allocation-token-03.txt 2017-10-18 14:13:08.886111600 -0700 +++ 2/draft-ietf-regext-allocation-token-04.txt 2017-10-18 14:13:08.918112369 -0700 @@ -1,20 +1,20 @@ Network Working Group J. Gould Internet-Draft VeriSign, Inc. Intended status: Standards Track K. Feher -Expires: January 4, 2018 Neustar - July 3, 2017 +Expires: April 21, 2018 Neustar + October 18, 2017 Allocation Token Extension for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-allocation-token-03 + draft-ietf-regext-allocation-token-04 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,40 +26,40 @@ 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 January 4, 2018. + This Internet-Draft will expire on April 21, 2018. 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 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 described in the Simplified BSD License. Table of Contents - 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Allocation Token . . . . . . . . . . . . . . . . . . . . 3 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 4 3.1.1. EPP Command . . . . . . . . . . . . . . . . . 4 3.1.2. EPP Command . . . . . . . . . . . . . . . . . 8 3.1.3. EPP Command . . . . . . . . . . . . . . . 10 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 11 3.2.1. EPP Command . . . . . . . . . . . . . . . . 11 @@ -67,33 +67,36 @@ 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. 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 + 6.2. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 17 + 6.3. Neustar gTLD SRS . . . . . . . . . . . . . . . . . . . . 17 + 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.8. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 19 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 + A.8. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 20 + A.9. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 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 @@ -651,66 +655,103 @@ 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 +6.2. Neustar EPP SDK + + Organisation: Neustar Inc. + + Name: Neustar EPP SDK + + Description: The Neustar EPP SDK includes a full client + 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: kal.feher@team.neustar + + URL: http://registrytoolkit.neustar + +6.3. Neustar gTLD SRS + + Organisation: Neustar Inc. + + Name: Neustar generic Top Level Domain (gTLD) Shared Registry System + (SRS). + + Description: The Neustar gTLD SRS implements the server side of + draft-ietf-regext-allocation-token. For several Top Level Domains + + Level of maturity: Production + + Coverage: All server side aspects of the protocol are implemented. + + Licensing: Proprietary + + Contact: kal.feher@team.neustar + 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. 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. 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, - . + DOI 10.17487/RFC2119, March 1997, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, - DOI 10.17487/RFC3688, January 2004, - . + DOI 10.17487/RFC3688, January 2004, . [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)", RFC 3915, - DOI 10.17487/RFC3915, September 2004, - . + DOI 10.17487/RFC3915, September 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, - . + 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, - . + DOI 10.17487/RFC6982, July 2013, . [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, - February 2015, . + 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 @@ -735,20 +776,25 @@ 1. Ping update. A.7. Change from REGEXT 01 to REGEXT 02 1. Added the Implementation Status section. 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. + Authors' Addresses James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com URI: http://www.verisigninc.com