FYI -- RFC1237.bis on NSAP Guidelines goes to Draft Standard

colella@nist.gov Tue, 08 March 1994 18:43 UTC

Date: Tue, 08 Mar 1994 13:44:30 -0500
Organization: National Institute of Standards and Technology (NIST)
Sub-Organization: Computer Systems Laboratory (CSL)
Message-Id: <9403081844.AA17564@emu.ncsl.nist.gov>
To: noop@merit.edu, tuba@lanl.gov
Subject: FYI -- RFC1237.bis on NSAP Guidelines goes to Draft Standard
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: colella@nist.gov
Reply-To: colella@nist.gov

Just in case you didn't see this.....

--Richard



----- Begin Included Message -----

>From scoya@CNRI.Reston.VA.US Fri Mar  4 18:35:17 1994
To: IETF-Announce:;@CNRI.Reston.VA.US
Cc: Jon Postel -- RFC Editor <postel@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: ietf-osi-nsap@wolf.ncsl.nist.gov
Cc: The Internet Engineering Steering Group <IESG@IETF.CNRI.Reston.VA.US>
>From: IESG Secretary <iesg-secretary@CNRI.Reston.VA.US>
Subject: Protocol Action: Guidelines for OSI NSAP Allocation in the
	 Internet to Draft Standard
Date: Fri, 04 Mar 94 16:04:59 -0500
Sender: scoya@CNRI.Reston.VA.US
Content-Length: 1969



The IESG has approved the Internet-Draft "Guidelines for OSI NSAP
Allocation in the Internet" <draft-ietf-osinsap-allocation-01.txt> as a
Draft Standard. This document is the product of the Assignment of OSI
NSAP Addresses Working Group. The IESG contact person is Dave
Piscitello.


Technical Summary

CLNP is currently being deployed in the Internet. This is useful to
support OSI and DECnet(tm) traffic.  In addition, CLNP can be used to
support TCP- and UDP-based applications as described in RFC 1347 [17].
Required as part of the CLNP infrastructure are guidelines for network
service access point (NSAP) address assignment. This paper provides
guidelines for allocating NSAP addresses in the Inter-net.

The guidelines provided in this paper have been the basis for initial
deployment of CLNP in the Internet, and have proven very valuable both
as an aid to scaling of CLNP routing, and for address administration.


Changes between RFC1237 and the I-D
-----------------------------------
The I-D has been updated with:

	- input from RARE on the RARE NSAP format,

	- information about how IDRP interacts with the allocation
		scheme (note that it does not change the allocation
		scheme), and,

	- less of an emphasis on a hierarchical set of service
		providers and more as a mesh of providers (this is
		primarily cosmetic).


Implementation Audit Trail
--------------------------
Vendors that have CLNP and associated routing protocols that implement
NSAPs according to the Guidelines include:
	3com
	cisco
	DEC
	HP
	IBM
	Proteon
	Sun
	Wellfleet

Organizations that have used the Guidelines as the basis for
allocations include:
	AlterNet
	BARRNet
	ESNet
	Europanet
	Nearnet
	NSFNet
	NSI
	SESQUINET/Texas
	SURANet
	US Department of Defense Registration Authority


Working Group Summary

This document has been in active use for over two years.  A recent
request to interested working groups (NOOP and TUBA) resulted in no
objection to it moving forward.


----- End Included Message -----

FYI -- RFC1237.bis on NSAP Guidelines goes to Dra… colella