Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!utcsri!utegc!utai!garfield!dalcs!mnetor!uunet!seismo!gatech!hao!ames!ucbcad!ucbvax!CC5.BBN.COM!malis
From: malis@CC5.BBN.COM.UUCP
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Internet Uselessness
Message-ID: <8707211635.AA08210@ucbvax.Berkeley.EDU>
Date: Tue, 21-Jul-87 12:38:24 EDT
Article-I.D.: ucbvax.8707211635.AA08210
Posted: Tue Jul 21 12:38:24 1987
Date-Received: Thu, 23-Jul-87 01:34:08 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 19

Mike,

Your impression is correct: many X.25 networks (e.g. TELENET) set
up a path at call setup time and then force all packets along
that fixed path, just using the VC number for identification.

Your inference is also correct: in BBNCC networks, the same
underlying packet format (and dynamic adaptive routing) is used
for both AHIP and X.25 traffic.

If you are interested in the workings of the backbone subnet, you
might like to read my RFC 979.  It is the functional
specification for the PSN's new End-to-End protocol, which is
being implemented in PSN 7.0 (PSN 6.0 is now running in the
subnet).  My statement above concerning packet formats and
routing is true for both the existing and the new EEs.

Cheers,
Andy