Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ucbvax!CCV.BBN.COM!brescia
From: brescia@CCV.BBN.COM (Mike Brescia)
Newsgroups: mod.protocols.tcp-ip
Subject: Re: IP source routing questions
Message-ID: <8610100147.AA20932@ucbvax.Berkeley.EDU>
Date: Thu, 9-Oct-86 15:55:07 EDT
Article-I.D.: ucbvax.8610100147.AA20932
Posted: Thu Oct  9 15:55:07 1986
Date-Received: Fri, 10-Oct-86 07:20:25 EDT
References: <8610091539.AA16270@mitre-gateway.arpa>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 12
Approved: tcp-ip@sri-nic.arpa

(from bmogart@mitre)
     All of the problems are caused by the differences between RFC791, The
     DARPA Internet Protocol Specification, and MILSTD-1777, The DoD Military
     Standard Internet Protocol.

My understanding of mil-std-1777 was that it recast the darpa IP spec in
mil-std terminology.  I thought that there was no intent to change the spec,
or cause disinteroperability.  I would be interested in hearing if anyone has
implemented the mil-std spec /in vacuo/ and expected that implementation to
talk to any existing host, or pass packets through any existing gateway.

Mike