RFC 3152: Delegation of IP6.ARPA
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3596.
Current document in this lineage: RFC 3596 — DNS Extensions to Support IP Version 6
In plain English — editorial summary, not part of the RFC
This document discusses the need for delegation of the IP6.ARPA DNS zone, and specifies a plan for the technical operation thereof. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC3152
- Published
- August 2001
- Authors
- R. Bush
- Status
- BEST CURRENT PRACTICE
- Stream
- Legacy
- Area
- —
- Pages
- 4
- Also known as
- BCP49
- Obsoleted by:
- RFC 3596
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1886 (1995)
- RFC 3152 (2001)
- RFC 3596 (2003) ✓
Read the full history of DNS Extensions to Support IP Version 6 →
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 3026Liaison to IETF/ISOC on ENUMCurrent
January 2001
- RFC 3254Definitions for talking about directoriesCurrent
April 2002
- RFC 2517Building Directories from DNS: Experiences from WWWSeekerCurrent
February 1999
- RFC 3172Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")Updated
September 2001
- RFC 2182Selection and Operation of Secondary DNS ServersCurrent
July 1997
- RFC 1982Serial Number ArithmeticCurrent
August 1996
- RFC 9199Considerations for Large Authoritative DNS Server OperatorsCurrent
March 2022
- RFC 3130Notes from the State-Of-The-Technology: DNSSECCurrent
June 2001
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?