Browse Prior Art Database

DNS NSAP Resource Records (RFC1706)

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

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Manning: AUTHOR [+2]

Abstract

OSI lower layer protocols, comprising the connectionless network protocol (CLNP) and supporting routing protocols, are deployed in some parts of the global Internet. Maintenance and debugging of CLNP connectivity is greatly aided by 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 16% of the total text.

Network Working Group B. Manning

Request for Comments: 1706 ISI

Obsoletes: 1637, 1348 R. Colella

Category: Informational NIST

October 1994

DNS NSAP Resource Records

Status of this Memo

This memo provides information for the Internet community. This memo

does not specify an Internet standard of any kind. Distribution of

this memo is unlimited.

Abstract

OSI lower layer protocols, comprising the connectionless network

protocol (CLNP) and supporting routing protocols, are deployed in

some parts of the global Internet. Maintenance and debugging of CLNP

connectivity is greatly aided by 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.

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.

This document obsoletes RFC 1348 and RFC 1637.

1. Introduction

OSI lower layer protocols, comprising the connectionless network

protocol (CLNP) [5] and supporting routing protocols, are deployed in

some parts of the global Internet. Maintenance and debugging of CLNP

connectivity is greatly aided by support in the Domain Name System

(DNS) [7] [8] for mapping between names and NSAP (network service

access point) addresses [6] [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 [1] or Annex A of [6] for

additional information.

2. Background

The reason for defining DNS mappings for NSAPs is to support the

existing CLNP deployment in the Internet. Debugging with CLNP ping

and traceroute has become more difficult with only numeric NSAPs as

the scale of deployment has increased. 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 describes the most serious short-term

problem. Scaling of a hosts.txt-like solution has well-known long-

term scaling difficienci...