RFC 3681: Delegation of E.F.F.3.IP6.ARPA
In plain English — editorial summary, not part of the RFC
This document discusses the need for delegation of the E.F.F.3.IP6.ARPA DNS zone in order to enable reverse lookups for 6bone addresses, and makes specific recommendations for the process needed to accomplish this.
Document record
- Document ID
- RFC3681
- Published
- January 2004
- Authors
- R. Bush; R. Fink
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 4
- Also known as
- BCP80
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3658Delegation Signer (DS) Resource Record (RR)Obsoleted
December 2003
- RFC 3646DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
December 2003
- RFC 3761The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Obsoleted
April 2004
- RFC 3597Handling of Unknown DNS Resource Record (RR) TypesUpdated
September 2003
- RFC 3596DNS Extensions to Support IP Version 6Current
October 2003
- RFC 3901DNS IPv6 Transport Operational GuidelinesObsoleted
September 2004
- RFC 3915Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)Current
October 2004
- RFC 3404Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)Current
October 2002
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?