]> VeriSign, Inc.

12061 Bluemont Way Reston VA 20190 US jgould@verisign.com http://www.verisigninc.com

Neustar

21575 Ridgetop Circle Sterling VA 20166 US Sharon.Wodjenski@neustar.biz http://www.neustar.biz

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.

This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP). This mapping, an extension to EPP object mappings like the EPP domain name mapping, 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.

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. 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 implementation. In examples, "C:" represents lines sent by a protocol client and "S:" represents lines returned by a protocol server. Indentation and white space in examples are provided only to illustrate element relationships and are not a REQUIRED feature of this protocol. "allocationToken-1.0" is used as an abbreviation for "urn:ietf:params:xml:ns:allocationToken-1.0". The XML namespace prefix "allocationToken" is used, but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents.

This extension adds additional elements to EPP object mappings like the EPP domain name mapping. Only those new elements are described here.

The Allocation Token is a simple XML "token" type. The exact format of the Allocation Token is up to server policy. The server MUST have the allocation token for each object to match against the allocation token passed by the client to authorize the allocation of the object. The same <allocationToken:allocationToken> element is used for all of the supported EPP transform commands as well as the info response. If an invalid allocation token is passed the server MUST return an EPP error result code of 2201.

An example <allocationToken:allocationToken> element with value of "abc123": abc123 ]]>

A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification .

EPP provides three commands to retrieve object information: <check> to determine if an object is known to the server, <info> to retrieve detailed information associated with an object, and <transfer> to retrieve object transfer status information.

This extension defines additional elements to extend the EPP <check> command of an object mapping like . This extension allow clients to check the availability of an object with an allocation token, as described in . Clients can check if an object can be created using the allocation token. The allocation token is applied to all object names included in the EPP <check> command.

Example <check> command for the example.tld domain name using the <allocationToken:allocationToken> extension with the allocation token of 'abc123': C: C: C: C: C: example.tld C: C: C: C: C: abc123 C: C: C: ABC-12345 C: C:]]>

If the query was successful, the server replies with an <check> response providing availability status of queried object.

Example <check> domain response for a <check> command using the <allocationToken:allocationToken> extension: S: S: S: S: Command completed successfully S: S: S: S: S: example.tld S: Invalid domain-token pair S: S: S: S: S: ABC-DEF-12345 S: 54321-XYZ S: S: S:]]>

Example <check> command with the <allocationToken:allocationToken> extension for the example.tld and example2.tld domain names. Availability of example.tld and example2.tld domain names are based on the allocation token 'abc123': C: C: C: C: C: example.tld C: example2.tld C: C: C: C: C: abc123 C: C: C: ABC-DEF-12345 C: C:]]>

Example <check> domain response for multiple domain names in the <check> command using the <allocationToken:allocationToken> extension: S: S: S: S: Command completed successfully S: S: S: S: S: example.tld S: Invalid domain-token pair S: S: S: example2.tld S: S: S: S: S: ABC-DEF-12345 S: 54321-XYZ S: S: S:]]>

This extension does not add any elements to the EPP <check> response described in the .

This extension defines additional elements to extend the EPP <info> command of an object mapping like . The EPP <info> command allows a client to request information on an existing object. Authorized clients MAY retrieve the allocation token along with the other object information using the <allocationToken:info> element that identifies the extension namespace. The <allocationToken:info> element is an empty element that serves as a marker to the server to return the <allocationToken:allocationToken> element, defined in , in the info response. If the client is not authorized to receive the allocation token, the server MUST return an EPP error result code of 2201. If the client is authorized to receive the allocation token, but there is no allocation token associated with the object, the server MUST return an EPP error result code of 2303 object referencing the <allocationToken:info> element.

Example <info> command with the allocationToken:info extension for the example.tld domain name: C: C: C: C: C: example.tld C: C: C: C: C: C: ABC-12345 C: C:]]>

If the query was successful, the server replies with an <allocationToken:allocationToken> element, as described in .

Example <info> domain response using the <allocationToken:allocationToken> extension: S: S: S: S: Command completed successfully S: S: S: S: example.tld S: EXAMPLE1-REP S: S: jd1234 S: sh8013 S: sh8013 S: ClientX S: ClientY S: 2012-04-03T22:00:00.0Z S: S: 2fooBAR S: S: S: S: S: S: abc123 S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S:]]>

This extension does not add any elements to the EPP <transfer> query command or <transfer> response described in the .

EPP provides five commands to transform objects: <create> to create an instance of an object, <delete> to delete an instance of an object, <renew> to extend the validity period of an object, <transfer> to manage object sponsorship changes, and <update> to change information associated with an object.

This extension defines additional elements to extend the EPP <create> command of an object mapping like . The EPP <create> command provides a transform operation that allows a client to create an object. In addition to the EPP command elements described in an object mapping like , the command MUST contain a child <allocationToken:allocationToken> element, as defined in , that identifies the extension namespace for the client to be authorized to create and allocate the object. If the allocation token does not match the object's allocation token, the server MUST return an EPP error result code of 2201.:

Example <create> command to create a domain object with an allocation token: C: C: C: C: C: example.tld C: jd1234 C: sh8013 C: sh8013 C: C: 2fooBAR C: C: C: C: C: C: abc123 C: C: C: ABC-12345 C: C:]]>

This extension does not add any elements to the EPP <create> response described in the .

This extension does not add any elements to the EPP <delete> command or <delete> response described in the .

This extension does not add any elements to the EPP <renew> command or <renew> response described in the .

This extension defines additional elements to extend the EPP <transfer> request command of an object mapping like . The EPP <transfer> 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 , the command MUST contain a child <allocationToken:allocationToken> element, as defined in , that identifies the extension namespace for the client to be authorized to transfer and allocate the object. If the allocation token does not match the object's allocation token, the server MUST return an EPP error result code of 2201.:

Example <transfer> request command to allocate the domain object with the allocation token: C: C: C: C: C: example1.tld C: 1 C: C: 2fooBAR C: C: C: C: C: C: abc123 C: C: C: ABC-12345 C: C:]]>

This extension does not add any elements to the EPP <transfer> response described in the .

This extension defines additional elements to extend an extension of an empty EPP <update> command of an object mapping like . An example of an extension of an empty EPP <update> command is the definition of the restore command within . An extension of an empty EPP <update> command defines a new verb that transforms an object. In addition to the EPP command elements described in an object mapping like , the command MUST contain a child <allocationToken:allocationToken> element, as defined in , that identifies the extension namespace for the client to be authorized to allocate the object. If the allocation token does not match the object's allocation token, the server MUST return an EPP error result code of 2201.:

Example use an extension of an empty <update> command to release a domain object with an allocation token: C: C: C: C: C: example1.tld C: C: C: C: C: C: abc123 C: C: C: ABC-12345-XYZ C: C:]]>

This extension does not add any elements to the EPP <update> response described in the .

One schema is presented here that is the EPP Allocation Token Extension schema. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. The BEGIN and END tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes.

Extensible Provisioning Protocol v1.0 Allocation Token Extension. END]]>

This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in . The following URI assignment is requested of IANA: URI: ietf:params:xml:ns:allocationToken-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: See the "Formal Syntax" section of this document.

The EPP extension described in this document should be registered by the IANA in the EPP Extension Registry described in . The details of the registration are as follows: Name of Extension: "Allocation Token Extension for the Extensible Provisioning Protocol (EPP)" Document status: Standards Track Reference: (insert reference to RFC version of this document) Registrant Name and Email Address: IESG, <iesg@ietf.org> TLDs: Any IPR Disclosure: None Status: Active Notes: None

The mapping extensions described in this document do not provide any security services beyond those described by EPP and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well.

The authors wish to acknowledge the original concept for this draft and the efforts in the initial versions of this draft by Trung Tran.

&RFC2119; &RFC3688; &RFC3915; &RFC5730; &RFC5731; &RFC7451;

Amended XML Namespace section of IANA Considerations, added EPP Extension Registry section. Moved Change History to the back section as an Appendix.

Ping update.

Ping update.

Updated the authors for the draft.