RFC 4310: Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5910.
Current version: 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 extensions (DNSSEC) 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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4310
- Published
- December 2005
- Authors
- S. Hollenbeck
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 22
- Also known as
- —
- Obsoleted by:
- RFC 5910
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4035Protocol Modifications for the DNS Security ExtensionsUpdated
March 2005
- RFC 4034Resource Records for the DNS Security ExtensionsUpdated
March 2005
- RFC 4033DNS Security Introduction and RequirementsUpdated
March 2005
- RFC 3226DNSSEC and IPv6 A6 aware server/resolver message size requirementsUpdated
December 2001
- RFC 3225Indicating Resolver Support of DNSSECUpdated
December 2001
- RFC 4255Using DNS to Securely Publish Secure Shell (SSH) Key FingerprintsCurrent
January 2006
- RFC 4471Derivation of DNS Name Predecessor and SuccessorCurrent
September 2006
- RFC 3845DNS Security (DNSSEC) NextSECure (NSEC) RDATA FormatObsoleted
August 2004
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?