Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-spam!nike!ucbcad!ucbvax!UMich-MTS.MAILNET!Hans-Werner_Braun
From: Hans-Werner_Braun@UMich-MTS.MAILNET
Newsgroups: mod.protocols.tcp-ip
Subject: re: X.25 Standard service on ARPANET
Message-ID: <1575748@UMich-MTS.Mailnet>
Date: Fri, 31-Oct-86 09:00:52 EST
Article-I.D.: UMich-MT.1575748
Posted: Fri Oct 31 09:00:52 1986
Date-Received: Sat, 1-Nov-86 04:56:50 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 12
Approved: tcp-ip@sri-nic.arpa

Yes, one of them is the operational gateway between the NSFnet and the
Arpanet, because of which I had asked the question in the first place.
Packets between the NSfnet and the Arpanet are now flowing in a more
operational sense than before, even though there are some (non-IMP
related) problems left, i.e., the IMP at PSC/CMU gets only the outgoing
packets at this point of time, while the incoming packets are still
traversing the slower DCNet/UMICH/USAN path. This will be fixed shortly,
but as said, it's not IMP or X.25 interface related. The Standard-X.25
interface appears to be behaving fine, as it's getting packets almost all
week already.

         -- Hans-Werner