RFC 8056: Extensible Provisioning Protocol (EPP) and Registration Data Access Protocol (RDAP) Status Mapping
In plain English — editorial summary, not part of the RFC
This document describes the mapping of the Extensible Provisioning Protocol (EPP) statuses with the statuses registered for use in the Registration Data Access Protocol (RDAP). This document identifies gaps in the mapping, and registers RDAP statuses to fill those gaps to ensure that all of the EPP statuses specified in RFCs are supported in RDAP.
Document record
- Document ID
- RFC8056
- Published
- January 2017
- Authors
- J. Gould
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8050Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format with BGP Additional Path ExtensionsCurrent
May 2017
- RFC 8049YANG Data Model for L3VPN Service DeliveryObsoleted
February 2017
- RFC 8063Key Relay Mapping for the Extensible Provisioning ProtocolCurrent
February 2017
- RFC 8071NETCONF Call Home and RESTCONF Call HomeCurrent
February 2017
- RFC 8040RESTCONF ProtocolUpdated
January 2017
- RFC 8072YANG Patch Media TypeCurrent
February 2017
- RFC 8078Managing DS Records from the Parent via CDS/CDNSKEYUpdated
March 2017
- RFC 8027DNSSEC Roadblock AvoidanceCurrent
November 2016
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?