A new Request for Comments is now available from the DDN Network Information
Center in the online library at FTP.NISC.SRI.COM.

Note: This is a PostScript RFC, a secondary version is available in
ASCII.  The secondary ASCII version may lack figures and the
information encoded in typographic variation (italics, boldface,
etc.).  Since this information often provides esssential context, the
ASCII version is at best incomplete and at worst misleading.  Anyone
expecting to understand this document is strongly encouraged to obtain
the PostScript version.


	RFC 1237:

        Title:      Guidelines for OSI NSAP Allocation
                    in the Internet
       	Author:     Colella, Gardner & Callon
	Mailbox:    colella@osi3.ncsl.nist.gov, epg@gateway.mitre.org,
                    Callon@bigfut.enet.dec.com
        PS-Pages:  38           ASCII-Pages:  49
        PS-Characters: 160,478  ASCII-Characters: 116,989
	Obsoletes/Updates:  none

		pathname: rfc/rfc1237.ps


The Internet is moving towards a multi-protocol environment that
includes OSI.  To support OSI in the Internet, an OSI lower layers
infrastructure is required.  This infrastructure comprises the
connectionless network protocol (CLNP) and supporting routing
protocols.  Also required as part of this infrastructure are guidelines
for network service access point (NSAP) address assignment.  This paper
provides guidelines for allocating NSAPs in the Internet.

This document provides our current best judgment for the allocation of
NSAP addresses in the Internet.  This is intended to guide initial
deployment of OSI 8473 (Connectionless Network Layer Protocol) in the
Internet, as well as to solicit comments.  It is expected that these
guidelines may be further refined and this document updated as a
result of experience gained during this initial deployment.

This RFC specifies an IAB Proposed Standard Protocol for the Internet
community, and requests discussion and suggestions for improvements.
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.

RFCs can be obtained via FTP from FTP.NISC.SRI.COM, NIS.NSF.NET, or
NISC.JVNC.NET.

This RFC can be obtained via FTP from FTP.NISC.SRI.COM, with the pathname
rfc/rfcNNNN.ps.  Login with FTP username "anonymous" and password
"guest".

SRI also provides an automatic mail service for those sites which
cannot use FTP.  Address the request to MAIL-SERVER@NISC.SRI.COM and
in the body of the message indicate the RFC to be sent: "send rfcNNNN.ps"
where NNNN is the RFC number.  Multiple requests may be included in
the same message.

To obtain RFCs from NIS.NSF.NET via FTP, login with username
"anonymous" and password "guest"; then connect to the RFC directory
("cd RFC").  The file name is of the form RFCnnnn.PS-1 (where "nnnn"
refers to the number of the RFC).

The NIS also provides an automatic mail service for those sites which
cannot use FTP.  Address the request to NIS-INFO@NIS.NSF.NET and leave
the subject field of the message blank.  The first line of the text of
the message must be "SEND RFCnnnn.PS-1", where nnnn is replaced by
the RFC number.

RFCs can also be obtained via FTP from NISC.JVNC.NET, with the
pathname rfc/RFCnnnn.PS.v (where "nnnn" refers to the number of the RFC
and "v" refers to the version number of the RFC).  Login with FTP,
username "anonymous" and your e-mail address as your password.

JvNCnet also provides a mail service for those sites which cannot use
FTP.  Address the request to SENDRFC@JVNC.NET and in the subject field
of the message indicate the RFC number, as in "Subject: RFCnnnn.PS" where
nnnn is the RFC number.  Please note that RFCs whose number are less
than 1000 need not place a "0". (For example, RFC932 is fine.)  No
text in the body of the message is needed.

To obtain the ASCII version, substitute "TXT" for "PS" in the
preceeding instructions.

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
POSTEL@ISI.EDU.  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.

Requests to be added to or deleted from this distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.


Joyce K. Reynolds
USC/Information Sciences Institute