Browse Prior Art Database

DNS NSAP Resource Records (RFC1637)

IP.com Disclosure Number: IPCOM000002473D
Original Publication Date: 1994-Jun-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 8 page(s) / 20K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Manning: AUTHOR [+2]

Abstract

The Internet is moving towards the deployment of an OSI lower layers infrastructure. This infrastructure comprises the connectionless network protocol (CLNP) and supporting routing protocols. Also required as part of this infrastructure is support in the Domain Name System (DNS) for mapping between names and NSAP addresses.

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

Network Working Group B. Manning

Request for Comments: 1637 Rice University

Obsoletes: 1348 R. Colella

Category: Experimental NIST

June 1994

DNS NSAP Resource Records

Status of this Memo

This memo defines an Experimental Protocol for the Internet

community. This memo does not specify an Internet standard of any

kind. Discussion and suggestions for improvement are requested.

Distribution of this memo is unlimited.

Abstract

The Internet is moving towards the deployment of an OSI lower layers

infrastructure. This infrastructure comprises the connectionless

network protocol (CLNP) and supporting routing protocols. Also

required as part of this infrastructure is support in the Domain Name

System (DNS) for mapping between names and NSAP addresses.

This document defines the format of one new Resource Record (RR) for

the DNS for domain name-to-NSAP mapping. The RR may be used with any

NSAP address format. This document supercedes RFC 1348.

NSAP-to-name translation is accomplished through use of the PTR RR

(see STD 13, RFC 1035 for a description of the PTR RR). This paper

describes how PTR RRs are used to support this translation.

1. Introduction

The Internet is moving towards the deployment of an OSI lower layers

infrastructure. This infrastructure comprises the connectionless

network protocol (CLNP) [6] and supporting routing protocols. Also

required as part of this infrastructure is support in the Domain Name

System (DNS) [8] [9] for mapping between domain names and OSI Network

Service Access Point (NSAP) addresses [7] [Note: NSAP and NSAP

address are used interchangeably throughout this memo].

This document defines the format of one new Resource Record (RR) for

the DNS for domain name-to-NSAP mapping. The RR may be used with any

NSAP address format.

NSAP-to-name translation is accomplished through use of the PTR RR

(see RFC 1035 for a description of the PTR RR). This paper describes

how PTR RRs are used to support this translation.

This memo assumes that the reader is familiar with the DNS. Some

familiarity with NSAPs is useful; see [2] or [7] for additional

information.

2. Background

The reason for defining DNS mappings for NSAPs is to support CLNP in

the Internet. Debugging with CLNP ping and traceroute is becoming

more difficult with only numeric NSAPs as the scale of deployment

increases. Current debugging is supported by maintaining and

exchanging a configuration file with name/NSAP mappings similar in

function to hosts.txt. This suffers from the lack of a central

coordinator for this file and also from the perspective of scaling.

The former is the most serious short-term problem. Scaling of a

hosts.txt-like solution has well-know...