Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!CCQ.BBN.COM!pogran
From: pogran@CCQ.BBN.COM.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: GOSIP
Message-ID: <8703041526.AA03414@ucbvax.Berkeley.EDU>
Date: Wed, 4-Mar-87 10:07:29 EST
Article-I.D.: ucbvax.8703041526.AA03414
Posted: Wed Mar  4 10:07:29 1987
Date-Received: Fri, 6-Mar-87 04:33:41 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 20
Approved: tcp-ip@sri-nic.arpa

Marshall,

But the document states (p. 2, sec. 1.4):

    "GOSIP is to be used by all Federal Government agencies
     when procuring ADP systems or services and communica-
     tion systems or services.  It is mandatory for all new
     network implementations ...  Specifically, this speci-
     fication is mandatory and applies to the procurement of
     all mini computers and mainframes that are to be inter-
     connected as end systems or intermediate systems."

If the framers of this document wanted to say, "Use this
specification IF you want to procure OSI stuff", it certainly
didn't come out that way!  My paraphrase of it would be, "If you
want to buy systems that communicate, you MUST use this spec." I
vote with MAP on this one (that's Michael A. Padlipsky, not
Manufacturing Automation Protocol).

Ken Pogran