RFC 8495: Allocation Token Extension for the Extensible Provisioning Protocol (EPP)
In plain English — editorial summary, not part of the RFC
This document describes an Extensible Provisioning Protocol (EPP) extension for including an Allocation Token in "query" and "transform" commands. The Allocation Token is used as a credential that authorizes a client to request the allocation of a specific object from the server using one of the EPP transform commands, including "create" and "transfer".
Document record
- Document ID
- RFC8495
- Published
- November 2018
- Authors
- J. Gould; K. Feher
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 17
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8499DNS TerminologyObsoleted
January 2019
- RFC 8490DNS Stateful OperationsCurrent
March 2019
- RFC 8501Reverse DNS in IPv6 for Internet Service ProvidersCurrent
November 2018
- RFC 8488RIPE NCC's Implementation of Resource Public Key Infrastructure (RPKI) Certificate Tree ValidationCurrent
December 2018
- RFC 8487Mtrace Version 2: Traceroute Facility for IP MulticastCurrent
October 2018
- RFC 8506Diameter Credit-Control ApplicationCurrent
March 2019
- RFC 8482Providing Minimal-Sized Responses to DNS Queries That Have QTYPE=ANYCurrent
January 2019
- RFC 8481Clarifications to BGP Origin Validation Based on Resource Public Key Infrastructure (RPKI)Updated
September 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?