RFC1348 on DNS NSAP RRs

Joyce Reynolds <jkrey@isi.edu> Thu, 02 July 1992 04:51 UTC

Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa10917; 2 Jul 92 0:51 EDT
Received: from venera.isi.edu by NRI.Reston.VA.US id aa15013; 2 Jul 92 0:52 EDT
Received: by venera.isi.edu (5.65c/5.65+local-6) id <AA12891>; Wed, 1 Jul 1992 10:25:09 -0700
From: Joyce Reynolds <jkrey@isi.edu>
Received: from akamai.isi.edu by venera.isi.edu (5.65c/5.65+local-6) id <AA12867>; Wed, 1 Jul 1992 10:25:02 -0700
Date: Wed, 01 Jul 1992 10:23:22 -0700
Posted-Date: Wed, 1 Jul 1992 10:23:22 -0700
Message-Id: <199207011723.AA02180@akamai.isi.edu>
Received: by akamai.isi.edu (5.65c/4.0.3-4) id <AA02180>; Wed, 1 Jul 1992 10:23:22 -0700
To: ietf@isi.edu, rfc-dist@nic.ddn.mil
Subject: RFC1348 on DNS NSAP RRs
Cc: jkrey@isi.edu




A new Request for Comments is now available in online RFC libraries.


        RFC 1348:

        Title:      DNS NSAP RRs
        Author:     B. Manning
        Mailbox:    bmanning@rice.edu
        Pages:      4
        Characters: 6,871
        Updates:    RFCs 1034, 1035


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.

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.

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@NRI.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.

RFCs can be obtained via FTP from FTP.NISC.SRI.COM, NIS.NSF.NET,
NISC.JVNC.NET, VENERA.ISI.EDU, WUARCHIVE.WUSTL.EDU, SRC.DOC.IC.AC.UK,
FTP.CONCERT.NET, or 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 NIC@NIC.DDN.MIL.  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 1111, "Instructions to RFC
Authors", for further information.


Joyce K. Reynolds
USC/Information Sciences Institute

======================================================================