RFC 3172: Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")
In plain English — editorial summary, not part of the RFC
This memo describes the management and operational requirements for the address and routing parameter area ("arpa") domain. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC3172
- Published
- September 2001
- Authors
- G. Huston
- Status
- BEST CURRENT PRACTICE
- Stream
- IAB
- Area
- —
- Pages
- 8
- Also known as
- BCP52
- Updated by:
- RFC 9120
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 3152Delegation of IP6.ARPAObsoleted
August 2001
- RFC 3026Liaison to IETF/ISOC on ENUMCurrent
January 2001
- RFC 1982Serial Number ArithmeticCurrent
August 1996
- RFC 9199Considerations for Large Authoritative DNS Server OperatorsCurrent
March 2022
- RFC 3197Applicability Statement for DNS MIB ExtensionsCurrent
November 2001
- RFC 3130Notes from the State-Of-The-Technology: DNSSECCurrent
June 2001
- RFC 3090DNS Security Extension Clarification on Zone StatusObsoleted
March 2001
- RFC 3254Definitions for talking about directoriesCurrent
April 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?