draft-ietf-regext-allocation-token-04.txt   draft-ietf-regext-allocation-token-05.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: April 21, 2018 Neustar Expires: July 6, 2018 Neustar
October 18, 2017 January 2, 2018
Allocation Token Extension for the Extensible Provisioning Protocol Allocation Token Extension for the Extensible Provisioning Protocol
(EPP) (EPP)
draft-ietf-regext-allocation-token-04 draft-ietf-regext-allocation-token-05
Abstract Abstract
This document describes an Extensible Provisioning Protocol (EPP) 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 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 transferred out-of-band to a client to give them authorization to
allocate an object using one of the EPP transform commands including allocate an object using one of the EPP transform commands including
create, update, and transfer. create, update, and transfer.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 April 21, 2018. This Internet-Draft will expire on July 6, 2018.
Copyright Notice 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. 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 44 skipping to change at page 2, line 44
7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 7. Security Considerations . . . . . . . . . . . . . . . . . . . 18
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
9. Normative References . . . . . . . . . . . . . . . . . . . . 18 9. Normative References . . . . . . . . . . . . . . . . . . . . 18
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 . . . . . . . . . . . . . . . 19
A.6. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 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.8. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 20
A.9. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 20 A.9. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 20
A.10. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
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], for passing an allocation token one of the EPP transform [RFC5731], for passing an allocation token to one of the EPP
commands including create, update, and transfer. The allocation transform commands including create, update, and transfer. A client
token is known to the server to authorize a client that passes a MUST pass an allocation token known to the server to be authorized to
matching allocation token with one of the supported EPP transform use one of the supported EPP transform commands. It is up to server
commands. It is up to server policy which EPP transform commands and policy which EPP transform commands and which objects support the
which objects support the allocation token. The allocation token MAY allocation token. The allocation token MAY be returned to an
be returned to an authorized client for passing out-of-band to a authorized client for passing out-of-band to a client that uses it
client that uses it with an EPP transform command. with an EPP transform command.
1.1. Conventions Used in This Document 1.1. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
XML is case sensitive. Unless stated otherwise, XML specifications XML is case sensitive. Unless stated otherwise, XML specifications
and examples provided in this document MUST be interpreted in the and examples provided in this document MUST be interpreted in the
character case presented in order to develop a conforming character case presented in order to develop a conforming
skipping to change at page 13, line 14 skipping to change at page 13, line 14
The EPP <transfer> request command provides a transform operation The EPP <transfer> request command provides a transform operation
that allows a client to request the transfer of an object. In that allows a client to request the transfer of an object. In
addition to the EPP command elements described in an object mapping addition to the EPP command elements described in an object mapping
like [RFC5731], the command MUST contain a child like [RFC5731], the command MUST contain a child
<allocationToken:allocationToken> element, as defined in Section 2.1, <allocationToken:allocationToken> element, as defined in Section 2.1,
that identifies the extension namespace for the client to be that identifies the extension namespace for the client to be
authorized to transfer and allocate the object. If the allocation authorized to transfer and allocate the object. If the allocation
token (Section 2.1) does not match the object's allocation token 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 (Section 2.1), the server MUST return an EPP error result code of
2201.: 2201.
Example <transfer> request command to allocate the domain object with Example <transfer> request command to allocate the domain object with
the allocation token: the allocation token:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <transfer op="request"> C: <transfer op="request">
C: <domain:transfer C: <domain:transfer
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
skipping to change at page 14, line 13 skipping to change at page 14, line 13
definition of the restore command within [RFC3915]. definition of the restore command within [RFC3915].
An extension of an empty EPP <update> command defines a new verb that An extension of an empty EPP <update> command defines a new verb that
transforms an object. In addition to the EPP command elements transforms an object. In addition to the EPP command elements
described in an object mapping like [RFC5731], the command MUST described in an object mapping like [RFC5731], the command MUST
contain a child <allocationToken:allocationToken> element, as defined contain a child <allocationToken:allocationToken> element, as defined
in Section 2.1, that identifies the extension namespace for the in Section 2.1, that identifies the extension namespace for the
client to be authorized to allocate the object. If the allocation client to be authorized to allocate the object. If the allocation
token (Section 2.1) does not match the object's allocation token 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 (Section 2.1), the server MUST return an EPP error result code of
2201.: 2201.
Example use an extension of an empty <update> command to release a Example use an extension of an empty <update> command to release a
domain object with an allocation token: domain object with an allocation token:
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command> C: <command>
C: <update> C: <update>
C: <domain:update C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
skipping to change at page 18, line 32 skipping to change at page 18, line 32
security services beyond those described by EPP [RFC5730] and security services beyond those described by EPP [RFC5730] and
protocol layers used by EPP. The security considerations described protocol layers used by EPP. The security considerations described
in these other specifications apply to this specification as well. in these other specifications apply to this specification as well.
8. Acknowledgements 8. Acknowledgements
The authors wish to acknowledge the original concept for this draft 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 the efforts in the initial versions of this draft by Trung Tran
and Sharon Wodjenski. and Sharon Wodjenski.
Special suggestions that have been incorporated into this document
were provided by Patrick Mevzek.
9. Normative References 9. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, <https://www.rfc- DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
editor.org/info/rfc2119>. editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, <https://www.rfc- DOI 10.17487/RFC3688, January 2004, <https://www.rfc-
editor.org/info/rfc3688>. editor.org/info/rfc3688>.
skipping to change at page 20, line 14 skipping to change at page 20, line 18
A.8. Change from REGEXT 02 to REGEXT 03 A.8. Change from REGEXT 02 to REGEXT 03
1. Changed Neustar author to Kal Feher. 1. Changed Neustar author to Kal Feher.
A.9. Change from REGEXT 03 to REGEXT 04 A.9. Change from REGEXT 03 to REGEXT 04
1. Added Neustar implementation to the Implementation Status 1. Added Neustar implementation to the Implementation Status
section. 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 <transfer> Command and
EPP <update> Command sections.
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
 End of changes. 12 change blocks. 
17 lines changed or deleted 37 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/