The Routing Over Large Clouds Mailing List Archive by date

Cell Relay Retreat>List Archive>month:1996-May> msg00120



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

New ION group - history for the archives?

  • From: Dave Katz <dkatz@cisco.com>
  • Date: Tue, 28 May 1996 14:53:50 -0700
  • Cc: pferguso@cisco.com, ion@nexen.com

Overtaken by events, I suspect.  Other than in niche markets, nobody
actually believes that CLNP is going anywhere.  Back in the days when
NSF had some control over the large-scale infrastructure such a
requirement was slightly more meaningful, but now that things are
basically privatized there's nothing to gain by requiring CLNP in the
places that NSF is still funding, since the packets can't get anywhere
from there (I know of only one national ISP that is still actually
carrying CLNP.)  (This from the guy that got CLNP working in the old
T1 NSFNET backbone...)

IPv6 is the next CLNP.  (Take that any way you wish... ;-) )

   From: salo@msc.edu (Tim Salo)
   Date: Tue, 28 May 1996 16:24:07 -0500 (CDT)
   X-Info: [Un]Subscribe to ion-request@nexen.com, submissions to ion@nexen.com
   X-Info: Hypermail archive at http://netlab.ucs.indiana.edu/hypermail/ion/
   X-Info: FTP archive at ftp://ftp.nexen.com/pub/ion/
   Sender: owner-rolc@nexen.com
   Precedence: bulk
   X-Info: Please send "unsubscribe rolc" to majordomo@nexen.com
   X-Info: Please send "subscribe ion" to majordomo@nexen.com
   X-Info: You can send both requests in one message

   > Date: Tue, 28 May 1996 16:23:07 -0400
   > To: "Eric W. Gray" <gray@ctron.com>
   > From: Paul Ferguson <pferguso@cisco.com>
   > Subject: Re: New ION group - history for the archives? 
   > Cc: Albert Manfredi <manfredi@engr05.comsys.rockwell.com>, ion@nexen.com
   > 	[...]
   > ... since the last I checked, the Internet is IP only. Thank goodness.

   A number of NSF contracts and cooperative agreements specify that
   CLNP as well as IP must be routed over the infrastructure in question.

   See, for example, the NSFNET solicitation, NSF 93-52.  It includes
   language such as:

	   "NAPs must support the switching of IP (Internet Protocol) and
	   CLNP (ConnectionLess Networking Protocol) packets."

   and

	   "RA activities must support the network service providers which
	   switch IP (Internet Protocol) and CLNP (ConnectionLess
	   Networking Protocol) packets."

   and even

	   "The specific anticipated duties of the vBNS Provider are as
	   follows:

	   o	Establish and maintain a 155 Mbps or higher transit
		   network service which switches IP and CLNP packets..."

   and finally

	   "Networks attaching to NAPs must ... be able to switch both
	   Ip and CLNP packets."

   Welcome to the multi-protocol Internet.

   On the other hand, I haven't actually seen any CNLP packets...

   -tjs