Dismiss
The IQ application will be briefly unavailable on Sunday, March 31st, starting at 10:00am ET. Access will be restored as quickly as possible.
Browse Prior Art Database

DNS NSAP RRs (RFC1348)

IP.com Disclosure Number: IPCOM000002172D
Original Publication Date: 1992-Jul-01
Included in the Prior Art Database: 2019-Feb-11
Document File: 4 page(s) / 5K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Manning: AUTHOR

Related Documents

10.17487/RFC1348: DOI

Abstract

This RFC defines the format of two new Resource Records (RRs) for the Domain Name System (DNS), and reserves corresponding DNS type mnemonic and numerical codes. This memo defines an Experimental Protocol for the Internet community.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 50% of the total text.

Network Working Group B. Manning Request for Comments: 1348 Rice University Updates: RFCs 1034, 1035 July 1992

DNS NSAP RRs

Status of this Memo

This memo defines an Experimental Protocol for the Internet community. Discussion and suggestions for improvement are requested. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Table of Contents

Introduction ..................................................... 1 Background ....................................................... 1 NSAP RR .......................................................... 2 NSAP-PTR RR ...................................................... 2 REFERENCES and BIBLIOGRAPHY ...................................... 3 Security Considerations .......................................... 4 Author’s Address ................................................. 4

Introduction

This RFC defines the format of two new Resource Records (RRs) for the Domain Name System (DNS), and reserves corresponding DNS type mnemonic and numerical codes. This format may be used with the any proposal that has variable length addresses, but is targeted for CLNP use.

This memo assumes that the reader is familiar with the DNS [3,4].

Background

This section describes an experimental representation of NSAP addresses in the DNS. There are several reasons to take this approch. First, it provides simple documentation of the correct addresses to use in static configurations of CLNP compliant hosts and routers.

NSAP support requires that a new DNS resource record entry type ("NSAP") be defined, to store longer Internet (i.e., NSAP) addresses. This resource record allows mapping from DNS names to NSAP addresses, and will contain entries for systems which are able to run Internet applications, over TCP or UDP, over CLNP.

Manning [Page 1]

RFC 1348 DNS NSAP RRs July 1992

The backward translation (from NSAP address to DNS name) is facilitated by definition of an associated resource record. This resource record is known as "NSAP-PTR", and is used in a manner analogous to the existing "in-addr.arpa".

These RRs are intended for use in a proposal [6] by one of the members of the NOOP WG to address the next-generation internet.

The NSAP RR

The NSAP RR is defined with mnemonic NSAP and type code 22 (decimal).

An NSAP (Network Service Access Protocol) number is a unique string to OSI transport service.

The numbering plan follows RFC 1237 and associated OSI definitions for NSAP format.

NSAP has the following format:

<owner> <ttl> <class> NSAP <length> <NSAP-address>

All fields are required.

<length> identifies the number of octets in the <NSAP-address> as defined by the various national and international authorities.

<NSAP-address> enumerates the actual octet values assigned by the assigning authority. Its format in master files is a <character- string> syntactically identical to that used in TXT and HINFO.

The f...

Processing...
Loading...