RFC 5731: Extensible Provisioning Protocol (EPP) Domain Name Mapping
In plain English — editorial summary, not part of the RFC
This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of Internet domain names stored in a shared central repository. Specified in XML, the mapping defines EPP command syntax and semantics as applied to domain names. This document obsoletes RFC 4931. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5731
- Published
- August 2009
- Authors
- S. Hollenbeck
- Status
- INTERNET STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 44
- Also known as
- STD69
- Obsoletes:
- RFC 4931
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3731 (2004)
- RFC 4931 (2007)
- RFC 5731 (2009)
Read the full history of Extensible Provisioning Protocol (EPP) Domain Name Mapping →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5732Extensible Provisioning Protocol (EPP) Host MappingCurrent
August 2009
- RFC 5733Extensible Provisioning Protocol (EPP) Contact MappingCurrent
August 2009
- RFC 5734Extensible Provisioning Protocol (EPP) Transport over TCPUpdated
August 2009
- RFC 5910Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)Current
May 2010
- RFC 3915Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)Current
October 2004
- RFC 5854The Metalink Download Description FormatCurrent
June 2010
- RFC 6020YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)Updated
October 2010
- RFC 6022YANG Module for NETCONF MonitoringCurrent
October 2010
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?