draft-ietf-regext-allocation-token-07.txt   draft-ietf-regext-allocation-token-08.txt 
Network Working Group J. Gould Network Working Group J. Gould
Internet-Draft VeriSign, Inc. Internet-Draft VeriSign, Inc.
Intended status: Standards Track K. Feher Intended status: Standards Track K. Feher
Expires: October 20, 2018 Neustar Expires: November 17, 2018 Neustar
April 18, 2018 May 16, 2018
Allocation Token Extension for the Extensible Provisioning Protocol Allocation Token Extension for the Extensible Provisioning Protocol
(EPP) (EPP)
draft-ietf-regext-allocation-token-07 draft-ietf-regext-allocation-token-08
Abstract Abstract
This document describes an Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP)
extension for including an Allocation Token in query and transform extension for including an Allocation Token in query and transform
commands. The Allocation Token is used as a credential that commands. The Allocation Token is used as a credential that
authorizes a client to request the allocation of a specific object authorizes a client to request the allocation of a specific object
from the server, using one of the EPP transform commands including from the server, using one of the EPP transform commands including
create and transfer. create and transfer.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 20, 2018. This Internet-Draft will expire on November 17, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 34 skipping to change at page 2, line 34
3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 13 3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 13
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 14 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1. Allocation Token Extension Schema . . . . . . . . . . . . 14 4.1. Allocation Token Extension Schema . . . . . . . . . . . . 14
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 15 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 15
5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 15 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 15
6. Implementation Status . . . . . . . . . . . . . . . . . . . . 15 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 15
6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 16 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 16
6.2. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 16 6.2. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 16
6.3. Neustar gTLD SRS . . . . . . . . . . . . . . . . . . . . 17 6.3. Neustar gTLD SRS . . . . . . . . . . . . . . . . . . . . 17
7. Security Considerations . . . . . . . . . . . . . . . . . . . 17 6.4. Net::DRI . . . . . . . . . . . . . . . . . . . . . . . . 17
7. Security Considerations . . . . . . . . . . . . . . . . . . . 18
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
9.1. Normative References . . . . . . . . . . . . . . . . . . 18 9.1. Normative References . . . . . . . . . . . . . . . . . . 18
9.2. Informative References . . . . . . . . . . . . . . . . . 19 9.2. Informative References . . . . . . . . . . . . . . . . . 19
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 19 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 19
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 19 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 19
A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 19 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 19
A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 19 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 19
A.5. Change from 04 to REGEXT 00 . . . . . . . . . . . . . . . 19 A.5. Change from 04 to REGEXT 00 . . . . . . . . . . . . . . . 20
A.6. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 19 A.6. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 20
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 . . . . . . . . . . . 19 A.8. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 20
A.9. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 19 A.9. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 20
A.10. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 20 A.10. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 20
A.11. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 20 A.11. Change from REGEXT 05 to REGEXT 06 . . . . . . . . . . . 20
A.12. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 22 A.12. Change from REGEXT 06 to REGEXT 07 . . . . . . . . . . . 22
A.13. Change from REGEXT 07 to REGEXT 08 . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
This document describes an extension mapping for version 1.0 of the This document describes an extension mapping for version 1.0 of the
Extensible Provisioning Protocol (EPP) [RFC5730]. This mapping, an Extensible Provisioning Protocol (EPP) [RFC5730]. This mapping, an
extension to EPP object mappings like the EPP domain name mapping extension to EPP object mappings like the EPP domain name mapping
[RFC5731], supports passing an Allocation Token as a credential that [RFC5731], supports passing an Allocation Token as a credential that
authorizes a client to request the allocation of a specific object authorizes a client to request the allocation of a specific object
from the server, using one of the EPP transform commands including from the server, using one of the EPP transform commands including
skipping to change at page 17, line 13 skipping to change at page 17, line 13
Name: Neustar EPP SDK Name: Neustar EPP SDK
Description: The Neustar EPP SDK includes a full client Description: The Neustar EPP SDK includes a full client
implementation of draft-ietf-regext-allocation-token. implementation of draft-ietf-regext-allocation-token.
Level of maturity: Production Level of maturity: Production
Coverage: All aspects of the protocol are implemented. Coverage: All aspects of the protocol are implemented.
Licensing: GNU Lesser General Public License Licensing: GNU Lesser General Public License
Contact: kal.feher@team.neustar Contact: quoc-anh.np@team.neustar
URL: http://registrytoolkit.neustar URL: http://registrytoolkit.neustar
6.3. Neustar gTLD SRS 6.3. Neustar gTLD SRS
Organisation: Neustar Inc. Organisation: Neustar Inc.
Name: Neustar generic Top Level Domain (gTLD) Shared Registry System Name: Neustar generic Top Level Domain (gTLD) Shared Registry System
(SRS). (SRS).
Description: The Neustar gTLD SRS implements the server side of Description: The Neustar gTLD SRS implements the server side of
draft-ietf-regext-allocation-token for several Top Level Domains. draft-ietf-regext-allocation-token for several Top Level Domains.
Level of maturity: Production Level of maturity: Production
Coverage: All server side aspects of the protocol are implemented. Coverage: All server side aspects of the protocol are implemented.
Licensing: Proprietary Licensing: Proprietary
Contact: kal.feher@team.neustar Contact: quoc-anh.np@team.neustar
6.4. Net::DRI
Organization: Dot and Co
Name: Net::DRI
Description: Net::DRI implements the client-side of draft-ietf-
regext-allocation-token.
Level of maturity: Production
Coverage: All client-side aspects of the protocol are implemented.
Licensing: GNU Lesser General Public License
Contact: netdri@dotandco.com
7. Security Considerations 7. Security Considerations
The mapping described in this document does not provide any security The mapping described in this document does not provide any security
services beyond those described by EPP [RFC5730] and protocol layers services beyond those described by EPP [RFC5730] and protocol layers
used by EPP. The security considerations described in these other used by EPP. The security considerations described in these other
specifications apply to this specification as well. specifications apply to this specification as well.
The mapping acts as a conduit for the passing of Allocation Tokens The mapping acts as a conduit for the passing of Allocation Tokens
between a client and a server. The definition of the Allocation between a client and a server. The definition of the Allocation
skipping to change at page 22, line 12 skipping to change at page 22, line 33
3. Revised the "Security Considerations" section to include 3. Revised the "Security Considerations" section to include
considerations for the definition of the Allocation Tokens. considerations for the definition of the Allocation Tokens.
A.12. Change from REGEXT 06 to REGEXT 07 A.12. Change from REGEXT 06 to REGEXT 07
1. Updates based on feedback from Patrick Mevzek: 1. Updates based on feedback from Patrick Mevzek:
1. Updated obsoleted RFC 7942 to RFC 7942. 1. Updated obsoleted RFC 7942 to RFC 7942.
2. Moved RFC 7451 to an informational reference. 2. Moved RFC 7451 to an informational reference.
A.13. Change from REGEXT 07 to REGEXT 08
1. Changed Kal Feher's contact e-mail address.
2. Changed Neustar's Implementation Status contact e-mail address.
3. Added the Net::DRI sub-section to the Implementation Status
section.
Authors' Addresses Authors' Addresses
James Gould James Gould
VeriSign, Inc. VeriSign, Inc.
12061 Bluemont Way 12061 Bluemont Way
Reston, VA 20190 Reston, VA 20190
US US
Email: jgould@verisign.com Email: jgould@verisign.com
URI: http://www.verisigninc.com URI: http://www.verisigninc.com
skipping to change at page 22, line 22 skipping to change at page 23, line 4
Authors' Addresses Authors' Addresses
James Gould James Gould
VeriSign, Inc. VeriSign, Inc.
12061 Bluemont Way 12061 Bluemont Way
Reston, VA 20190 Reston, VA 20190
US US
Email: jgould@verisign.com Email: jgould@verisign.com
URI: http://www.verisigninc.com URI: http://www.verisigninc.com
Kal Feher Kal Feher
Neustar Neustar
lvl 8/10 Queens Road lvl 8/10 Queens Road
Melbourne, VIC 3004 Melbourne, VIC 3004
AU AU
Email: kal.feher@team.neustar Email: ietf@feherfamily.org
URI: http://www.neustar.biz URI: http://www.neustar.biz
 End of changes. 11 change blocks. 
15 lines changed or deleted 39 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/