RFC 5910: Domain Name System (DNS) Security Extensions Mapping 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 mapping for the provisioning and management of Domain Name System security (DNSSEC) extensions for domain names stored in a shared central repository. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for the provisioning of DNS security extensions. This document obsoletes RFC 4310. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5910
- Published
- May 2010
- Authors
- J. Gould; S. Hollenbeck
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 36
- Also known as
- —
- Obsoletes:
- RFC 4310
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5734Extensible Provisioning Protocol (EPP) Transport over TCPUpdated
August 2009
- RFC 5733Extensible Provisioning Protocol (EPP) Contact MappingCurrent
August 2009
- RFC 5732Extensible Provisioning Protocol (EPP) Host MappingCurrent
August 2009
- RFC 5731Extensible Provisioning Protocol (EPP) Domain Name MappingCurrent
August 2009
- RFC 3915Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)Current
October 2004
- RFC 8509A Root Key Trust Anchor Sentinel for DNSSECCurrent
December 2018
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 6604xNAME RCODE and Status Bits ClarificationCurrent
April 2012
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?