Now they use TCP/IP for the most part and run Cisco routers.

--

RFC 1149 Compliant.
Get in my head:
http://sar.dynu.com


""William Gragido""  wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Yes, thats true, we ran Banyon Vines, the USMC that is in addition to
> various Unix variants.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Priscilla Oppenheimer
> Sent: Thursday, March 28, 2002 1:12 PM
> To: [EMAIL PROTECTED]
> Subject: RE: TCP/IP and DOD [7:39657]
>
>
> And I've heard that the US side in Desert Storm used Banyan for their
> networking systems, not TCP/IP!?
>
> Priscilla
>
> At 12:05 PM 3/28/02, Howard C. Berkowitz wrote:
> > >Thats what the DoD taught in their DataCommunications Schools.  Sorry
> Dom.
> >
> >Absolutely, positively wrong, though. That's an urban legend that has
> >been disavowed by every early developer I can think of, including the
> >DARPA people. It developed out of pure DARPA sponsored research in
> >networking.
> >
> >I'm hard-pressed to think of any nuclear command & control
> >communications system, before the mid-80's or so, that used TCP/IP,
> >and at one time I knew pretty much every system that was deployed.
> >Among the ones I can talk about, they were circuit-switched or radio.
> >Some of the circuit-switched networks were computer controlled,
> >including AUTODIN I and a variety of intelligent networks.
> >
> >Without detailed research, I'd tend to say the first military TCP/IP
> >applications were in tactical, not strategic, nets.
> >
> >Actually, the first demonstration that packet switched networks were
> >resilient to massive attack came from the Iraqi air defense system in
> >Desert Storm.
> >
> > >
> > >-----Original Message-----
> > >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> > >Chuck
> > >Sent: Thursday, March 28, 2002 9:00 AM
> > >To: [EMAIL PROTECTED]
> > >Subject: Re: TCP/IP and DOD [7:39657]
> > >
> > >
> > >the real reason being.....?
> > >
> > >
> > >
> > >
> > >  wrote in message
> > >[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > >>  Sorry, the
> > >>
> > >>  "be resilient to Global Thermal Nuclear attacks"
> > >>
> > >>  is a myth.
> > >>
> > >>  Dom Stocqueler
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>  "William
> > >>                      Gragido"             To:
> > >>  [EMAIL PROTECTED]
> > >>                                    Subject:     RE: TCP/IP and DOD
> > >>  [7:39657]
> > >>                      Sent
> > >>  by:
> > >>
> > >>  nobody@groups
> > >>
> > >>  tudy.com
> > >>
> > >>
> > >>
> > >>  27/03/2002
> > >>
> > >>  20:17
> > >>
> > >>  Please
> > >>                      respond
> > >>  to
> > >>
> > >>  "William
> > >>
> > >>  Gragido"
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>  The DoD adopted TCP/IP as its native protocol for communications in
> 1983.
> > >>  DARPA lead the charge for a communications system that would be
> resilient
> > >>  to
> > >>  Global Thermal Nuclear attacks (therein allowing for continued,
> > >>  uninterrupted comm), and would allow for common connectivity of
> > >>  multi-vendor
> > >>  solutions.  This of course did yield 'ARPA NET' which, by a decision
> of
> > >the
> > >>  DCA (Defense Communications Agency), in 1983 was split in two
yielding
> a
> > >>  smaller version of 'ARPA NET' and 'MILNET'.  The evolution of the
> modern
> > >>  internet can followed done the line from 'ARPA NET' and as we all
know
> by
> > >>  virtue of adding new networks to the mix, 'ARPA NET' was
de-regulated
> in
> > >>  1991 ushering the age of the modern internet.
> > >>
> > >>  Hope that helps,
> > >>
> > >>  Will Gragido
> > >>
> > >>  -----Original Message-----
> > >>  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of
> > >>  Michael Williams
> > >>  Sent: Wednesday, March 27, 2002 1:37 PM
> > >>  To: [EMAIL PROTECTED]
> > >>  Subject: RE: TCP/IP and DOD [7:39657]
> > >>
> > >>
> > >>  It's kinda fuzzy.  I myself just got through doing a tech review of
a
> >book
> > >>  covering this topic as well as have written my own "materials" for
> > >>  training,
> > >>  etc covering this topic.  IMHO, DoD is credited with "creating the
> > >>  internet"
> > >>  even though at the time it wasn't called the internet and didn't use
> the
> > >>  same protocols we do now.  Although the DoD started the whole mess,
> from
> > >>  what I've read DoD commisioned ARPANET to research this.  I'm sure
> that
> > >>  peoples are various universities and colleges were in on the actual
> > >>  deveopment evidenced by the fact that in 1971 there were 15 nodes
> (with a
> > >>  total of 23 hosts), namely UCLA, SRI, UCSB, U of Utah, BBN, MIT,
RAND,
> > >SDC,
> > >>  Harvard, Lincoln Lab, Stanford, UIU(C), CWRU, CMU, and NASA/Ames.
> Note
> > >>  most
> > >>  of those listed are colleges/universities. I've read some about BBN,
> > >>  however
> > >>  it seems to me their main role was to supply the first "computers"
> > >>  (Honeywell 516 mini computers with 12K of memory) that acted as
> > >Information
> > >>  Message Processors (IMPs) (routers?).
> > >>
> > >>  However, I would humbly suggest that Howard B. or Priscilla O. throw
> >their
> > >>  2
> > >>  cents in here.
> > >>
> > >>  Also, since your doing a technical edit, be careful of the words you
> > >choose
> > >>  as well.  For example you use the word "written" over and over
above,
> but
> > >I
> > >>  don't think the conversation is really about "which programmers
> actually
> > >>  wrote the code" it's more about "who either spearheaded or caused
the
> > >>  evolution of the *standards* we call TCP/IP" in which case I don't
> think
> > >>  crediting the DoD is incorrect.
> > >>
> > >>  My 2 cents =)
> > >>  Mike W.
> ________________________
>
> Priscilla Oppenheimer
> http://www.priscilla.com




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=39838&t=39657
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to