aprm%gd@SHAFTER-EMH2.ARMY.MIL (Gary Dunn) (06/03/91)
Text:
The Army Small Multiuser Computer (SMC) contract, awarded to EDS,
uses TP4 for the transport layer and supports Intel's OpenNET and the
new GOSIP protocols. TCP/IP is not on the contract, but DDN
connectivity hardware and software are.
Is DoD making a move to change DDN from TCP/IP to GOSIP? If so, what is
the timetable?
--Gary Dunn
U.S. Army USARPAC DCSRM IMO
--- End of Message -----------barns@GATEWAY.MITRE.ORG (06/06/91)
There is a document "Army Open Systems Interconnection (OSI) Interoperability and Transition Plan" that you should probably try to get through Army channels. I imagine it came from USAISC at Ft Huachuca. The people who did this would also have access to various other DOD OSI transition information. As for the DDN I would just briefly (and unofficially, but I think accurately) state that the capability to support connectivity through the PSN backbone between OSI systems has existed for some time already. There is really nothing to "switch" about the PSN backbone, though some enhancements might be done for performance reasons or to add features, should that seem to be necessary (this is an open topic now), and appendages such as mailbridges, NIC, etc., do have to have OSI capabilities added eventually in order to make those functions accessible to OSI users. If you have boxes with GOSIP-compliant protocol stacks that include X.25, you can connect them to the PSNs now, configure them to know about each other and proceed to talk OSI between them. The port must have Basic service enabled (either basic only or basic+standard, whatever you require). The lack of GOSIP routing protocols has some effects on what you can do (or more precisely, on how you can make it happen and whether you will be glad you did) but the only real functional limitation that comes to mind is that you can't talk pure OSI to the non-DOD part of the Internet at the moment. Bill Barns / MITRE-Washington / barns@gateway.mitre.org
Jswisher@HUACHUCA-EMH8.ARMY.MIL (06/06/91)
Gary,
You are incorrect when you stated that TCP/IP is NOT on the SMC contract.
TCP/IP IS ON THE SMC Contract.
CLIN DESCRIPTION VENDOR PRODUCT
0906CA SMC DDN Host SW Prime EXL X.25 TCP/IP
It provides access to DDN and TCP/IP hosts.
By providing GOSIP, OpenNET, and TCP/IP products, the Prime EXL can
be used as a bridge between these different LAN architectures.
_________________________________
* *
* CPT JOEL V. SWISHER *
* U.S. ARMY *
* COMPUTER ENGINEERING CENTER *
* jswisher@huachuca-emh8.army.mil *
* DSN:821-2865 COMM:(602)533-2865 *
*_________________________________*
Received: from alamo by cochise.huachuca-emh8.army.mil id aa13838;
5 Jun 91 18:54 MDT
Received: from alamo.huachuca-emh8.army.mil by alamo.huachuca-emh8.army.mil
id aa13391; 5 Jun 91 18:32 MDT
Received: from nic.ddn.mil by alamo.huachuca-emh8.army.mil id aa13339;
5 Jun 91 18:22 MDT
Received: from shafter-emh2.army.mil by NIC.DDN.MIL with TCP; Tue, 4 Jun 91 12:40:42 PDT
Received: by shafter-emh2.army.mil (sendmail(4.12)/R3-6.3(SMS))
id AA12423; Tue, 4 Jun 91 09:44:49 hst
Received: by aprm (smail2.5)
id AA18505; 4 Jun 91 09:42:41 HST (Tue)
To: tcp-ip@NIC.DDN.MIL
Subject: When will DDN switch to GOSIP?
Date: Tue Jun 4 09:42:39 1991
Message-Id: <9106040942.AA18505@aprm>
From: Gary Dunn <aprm%gd@SHAFTER-EMH2.ARMY.MIL>
Text:
The Army Small Multiuser Computer (SMC) contract, awarded to EDS,
uses TP4 for the transport layer and supports Intel's OpenNET and the
new GOSIP protocols. TCP/IP is not on the contract, but DDN
connectivity hardware and software are.
Is DoD making a move to change DDN from TCP/IP to GOSIP? If so, what is
the timetable?
--Gary Dunn
U.S. Army USARPAC DCSRM IMO
--- End of Message -----------