RFC 5158: 6to4 Reverse DNS Delegation Specification
In plain English — editorial summary, not part of the RFC
This memo describes the service mechanism for entering a delegation of DNS servers that provide reverse lookup of 6to4 IPv6 addresses into the 6to4 reverse zone file. The mechanism is based on a conventional DNS delegation service interface, allowing the service client to enter the details of a number of DNS servers for the delegated domain. In the context of a 6to4 reverse delegation, the client is primarily authenticated by its source address used in the delegation request, and is authorized to use the function if its IPv6 address prefix corresponds to an address from within the requested 6to4 delegation address block. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5158
- Published
- March 2008
- Authors
- G. Huston
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 12
- Also known as
- —
- Updated by:
- RFC 8996
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 5205Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionsObsoleted
April 2008
- RFC 4509Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)Current
May 2006
- RFC 4159Deprecation of "ip6.int"Current
August 2005
- RFC 6168Requirements for Management of Name Servers for the DNSCurrent
May 2011
- RFC 4143Facsimile Using Internet Mail (IFAX) Service of ENUMUpdated
November 2005
- RFC 3915Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)Current
October 2004
- RFC 3901DNS IPv6 Transport Operational GuidelinesObsoleted
September 2004
- RFC 3761The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Obsoleted
April 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?