Allocation Token Extension for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-allocation-token-00
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (regext WG) | |
| Last updated | 2017-04-17 (latest revision 2016-10-14) | ||
| Replaces | draft-gould-allocation-token | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Reviews | |||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-regext-allocation-token-00.txt
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.
Authors
James Gould
(jgould@verisign.com)
Sharon Wodjenski
(sharon.wodjenski@neustar.biz)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)