<?xml version='1.0'?>

<reference anchor='RFC1706'>

<front>
<title abbrev='DNS NSAP RRs'>DNS NSAP Resource Records</title>
<author initials='B.' surname='Manning' fullname='Bill Manning'>
<organization>USC/Information Sciences Institute</organization>
<address>
<postal>
<street>4676 Admiralty Way</street>
<city>Marina del Rey</city>
<region>CA</region>
<code>90292</code>
<country>US</country></postal>
<phone>+1 310 822 1511</phone>
<email>bmanning@isi.edu</email></address></author>
<author initials='R.' surname='Colella' fullname='Richard Colella'>
<organization>National Institute of Standards and Technology, Technology/B217</organization>
<address>
<postal>
<street />
<city>Gaithersburg</city>
<region>MD</region>
<code>20899</code>
<country>US</country></postal>
<phone>+1 301 975 3627</phone>
<facsimile>+1 301 590 0932</facsimile>
<email>colella@nist.gov</email></address></author>
<date month='October' year='1994' />
<abstract>
<t>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.</t>
<t>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.</t>
<t>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.</t>
<t>This document obsoletes RFC 1348 and RFC 1637.</t></abstract></front>

<seriesInfo name='RFC' value='1706' />
</reference>
