Re: World's First Fuel Cell-Powered Train Locomotive Slated for 2008

From: Stephen Sprunk (stephen_at_sprunk.org)
Date: 08/23/04


Date: Mon, 23 Aug 2004 17:00:38 -0500


"Ian St. John" <istjohn@noemail.ca> wrote in message
news:u6tWc.10965$_H5.229014@news20.bellglobal.com...
> Stephen Sprunk wrote:
>> Not all "progress" is that. IP has its flaws, but in the end it's
>> turned out to be a much better model than anything else that's
>> appeared so far. Most of IPv4's flaws are fixed in IPv6, but some
>> remain for backwards compatibility.
>
> And look at how long it has taken to get even a start at IPv6, LOOOOONG
> after it was formally defined. I expect it to get into mainstream use
> outside of proprietary long distance backbones in no more than a decade or
> so.

The driving force behind IPv6, address space depletion, was mitigated by
CIDR; it still presents many advantages over IPv4 and several countries
(China, Japan, Korea, various parts of Africa) are moving to IPv6 now
because they can't get enough IPv4 addresses to serve their users even with
CIDR.

>> Many europeans adopted the OSI protocol as a replacement for TCP/IP
>> long before the WWW happened;
>
> ISO/OSI is a formal definition of a protocol stack, it is nothing to do
> with
> TCP/IP or equivalent. TCP/IP is an *implementation* of some of the layers
> of
> OSI.

You're referring to the OSI _model_, which is described in ISO TR 9575. The
OSI _protocol stack_ is defined in ISO 8648, 8348, 8306, 8307, 9548, 8822,
8823, etc.

See, the OSI _protocol stack_ is so dead in the market you don't even know
it existed. But it did, and Europeans drove the entire effort through
academia, the ISO, ITU, the market, and eventually into the ground.
Americans were content to stick with the simpler, more elegant IPv4 and won
in the end.

>> OSI ended up being a miserable failure
>> in the marketplace because it was slow, expensive, and difficult to
>> implement -- typical of anything designed by a committee instead of a
>> small team of highly focused experts.
>
> Nuts. You are clueless. The OSI formal specification is the basis for most
> networking stacks. http://www.techadvice.com/tech/O/OSI_protocol.htm

The OSI _model_ was developed long after the TCP/IP model, which only has
four layers. In fact, the OSI model was an attempt to fight IBM's
well-marketed seven-layer Systems Network Architecture -- which is still in
heavy use today, though mostly as tunnels across IP networks. Its use today
as applied to TCP/IP is actually confusing, since layers 5 and 6 don't exist
in modern networks, layer 2 is actually two separate layers, etc.

S

-- 
Stephen Sprunk      "Those people who think they know everything
CCIE #3723         are a great annoyance to those of us who do."
K5SSS                                             --Isaac Asimov 


Relevant Pages

  • Re: Worlds First Fuel Cell-Powered Train Locomotive Slated for 2008
    ... You're referring to the OSI _model_, which is described in ISO TR 9575. ... as applied to TCP/IP is actually confusing, since layers 5 and 6 don't exist ... in modern networks, layer 2 is actually two separate layers, etc. ... Stephen Sprunk ...
    (sci.energy)
  • Re: Network Models
    ... built on top of TCP implements the higher OSI layers itself. ... What i want is that TCP/IP model is also a model other than ...
    (microsoft.public.win32.programmer.networks)
  • Re: Whats bad in Java
    ... TCP/IP is slow because there are too much layers. ... uses a four layer model which approximates the lowest 5 OSI layers. ... TCP/IP provides no equivalent to the Presentation and Application ...
    (comp.lang.java.programmer)
  • Re: Layers and Protocols Involved
    ... Miniport NDIS driver of network adapter is OSI 2 layer and TCP/IP protocol ... driver driver is 3 & 4 layers of the OSI ...
    (microsoft.public.win32.programmer.networks)