Browse Prior Art Database

Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa") (RFC3172)

IP.com Disclosure Number: IPCOM000005402D
Original Publication Date: 2001-Sep-01
Included in the Prior Art Database: 2001-Sep-25
Document File: 9 page(s) / 18K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Huston: AUTHOR

Abstract

This memo describes the management and operational requirements for the address and routing parameter area ("arpa") domain. The "arpa" domain is used to support a class of infrastructural identifier spaces, providing a distributed database that translates elements of a structured name space derived from a protocol family to service names. The efficient and reliable operation of this DNS space is essential to the integrity of operation of various services within the Internet. The Internet Architecture Board (IAB) has the responsibility, in cooperation with the Internet Corporation for Assigned Names and Numbers (ICANN), to manage the "arpa" domain. This document describes the principles used by the IAB in undertaking this role.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 18% of the total text.

Network Working Group G. Huston, Editor Request for Comments: 3172 IAB BCP: 52 September 2001 Category: Best Current Practice

Management Guidelines Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")

Status of this Memo

This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2001). All Rights Reserved.

Abstract

This memo describes the management and operational requirements for the address and routing parameter area ("arpa") domain. The "arpa" domain is used to support a class of infrastructural identifier spaces, providing a distributed database that translates elements of a structured name space derived from a protocol family to service names. The efficient and reliable operation of this DNS space is essential to the integrity of operation of various services within the Internet. The Internet Architecture Board (IAB) has the responsibility, in cooperation with the Internet Corporation for Assigned Names and Numbers (ICANN), to manage the "arpa" domain. This document describes the principles used by the IAB in undertaking this role.

1. Introduction

The Domain Name System (DNS) [1] [2] is predominately used to translate a structured textual identifier into a protocol-specific value. It uses the structure embedded within a hierarchical identifier space to create a distributed database, where every node within the database corresponds to a node within the name structure. The most prevalent role of the DNS is to store a set of name to address translations, allowing a domain name to be translated to an IP address. The DNS is also used to store a number of other translations from hierarchically structured identifier spaces into target values of various types.

Huston Best Current Practice [Page 1]

RFC 3172 arpa Guidelines September 2001

The DNS is also capable of supporting a translation in the opposite direction, from protocol values to the names of service entities. One approach in using the DNS in this fashion has been to transform protocol values into a hierarchically structured identifier space, and then use these transformed protocol value names as a DNS lookup key into the appropriate DNS name hierarchy. A common use of this mechanism has been the reverse of the name to address lookup, allowing for an IPv4 address to be used to look up a matching domain name. For example, the IP address 128.9.160.55 can be associated with the domain name "www.iab.org." by creating the DNS entry 55.160.9.128.in-addr.arpa." and mapping this entry, via a DNS PTR record, to the value "www.iab.org.".

The resolution of protocol objects into service names is used by a number of applications to associate services with a particular protocol object. The correct and efficient operation of these applications is dependent on the correct and efficient operation of the associated...