RFC1706 on DNS NSAP RRs
"Joyce K. Reynolds" <jkrey@isi.edu> Tue, 25 October 1994 20:53 UTC
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09491; 25 Oct 94 16:53 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa18079; 25 Oct 94 16:53 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09460; 25 Oct 94 16:53 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09400; 25 Oct 94 16:50 EDT
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa18005; 25 Oct 94 16:50 EDT
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-17) id <AA29949>; Tue, 25 Oct 1994 13:50:59 -0700
Message-Id: <199410252050.AA29949@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1706 on DNS NSAP RRs
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 25 Oct 1994 13:51:43 -0700
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>
A new Request for Comments is now available in online RFC libraries. RFC 1706: Title: DNS NSAP Resource Records Author: B. Manning & R. Colella Mailbox: bmanning@isi.edu, colella@nist.gov Pages: 10 Characters: 19,721 Obsoletes: 1637 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 memo describes how PTR RRs are used to support this translation. 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. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-REQUEST@NIC.DDN.MIL. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@ISI.EDU with the message body help: ways_to_get_rfcs. For example: To: rfc-info@ISI.EDU Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to admin@DS.INTERNIC.NET. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC Authors, for further information. Joyce K. Reynolds USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC1706 on DNS NSAP RRs Joyce K. Reynolds