|
![](/i/fill.gif) |
Am 20.08.2011 16:56, schrieb Darren New:
> Yep. How much of your networking isn't connection oriented? Here's a
> hint: all networking is connection oriented. IP layers
> non-connection-oriented networking on top of that, and then layers TCP
> to turn it back into connection-oriented, poorly. If IP wasn't
> connection oriented, you wouldn't need routing tables on each machine.
Nonsense. There's no connection-oriented networking in the classic
Ethernet, for instance - and IP ran fine on it. It's only the newer
Ethernet incarnations that installed connection-oriented principles
below IP, due to operating on point-to-point connections on the physical
layer. (Which again shows that, as you already mentioned, having
connection-oriented principles rooted pretty deep in the network stack
seems to have /some/ benefits.)
You /might/ consider the current route through the internet a kind of
IP-layer connection, but given that it can change even from packet to
packet, and the packets can reach the receiver in arbitrary order, I'd
call that pretty far-fetched.
Post a reply to this message
|
![](/i/fill.gif) |