[comp.protocols.tcp-ip] MILNET<->ARPANET woes

trn@warper.jhuapl.edu (Tony Nardo) (02/13/89)

Does anyone know if the latest DDN essage (regarding conversion to standard
packet formats) is a roundabout explaination for why MILNET<->ARPANET
connectivity has been rather erratic over the past two weeks?

For that matter, has anyone else noticed any connectivity problems?  I seem
to be able to reach *West Coast* sites fairly reliably.  Sites closer to
home, however, have been another matter entirely.

								Tony

P.S.	To whom it concerns: warper routes thru 26.1.0.102 (aplvax.jhuapl.edu).
-------				----------------			-------
ARPA,	trn@aplcomm.jhuapl.edu,		UUCP:	{backbone!}mimsy!aplcomm!trn
BITNET:	trn@warper.jhuapl.edu

leading edge (adj.): used to describe technology that is five years out of date
and therefore mature enough to be used in a product.

malis@BBN.COM (Andy Malis) (02/14/89)

Tony,

The DDN bulletin has nothing to do with Arpanet-MILNET
connectivity, but rather with X.25 hosts requiring non-standard
default flow control parameters and the intra-MILNET
interroperability (and MILNET management) problems that result.

The connectivity problems are the result of a problem in the
Butterfly mailbridge software that was fixed late last week.  New
disks were being sent out on Friday.

Regards,
Andy Malis <malis@bbn.com>    UUCP: {harvard,rutgers,uunet}!bbn!malis