e59d56ad
XPost: comp.os.linux.networking
From: rick.jones2@hp.com
In comp.protocols.tcp-ip karthikbalaguru wrote:
> Why TCP does not support the functionality of taking
> over of the Existing connections by the other interface ?
It isn't entirely clear what you are asking. That said:
A TCP connection is uniquely identified by the four-tuple of
local/remote IP and local/remote port number. If the four-tuple is
different, it is a different TCP connection.
Dealing with things like interface failure is handled at layer2 and
layer3 in the 7 (or 9 if you include financial and political) layer
model. When handled at layer two, you will see terms like LACP, bond,
trunk, aggregate and team in your web searches. When handled at layer
three (eg IP) it is called "routing." In the case of IP, there is
also the more fundamental question of whether an IP address belongs to
the system or to the interface - you will see terms like "weak
end-system" and "strong end-system" model when you do web searches.
So, TCP does not support dealing with link/interface failure because
it does not need to - those things are dealt with elsewhere. For TCP
to deal with it would require a TCP connection to be named via
something other than the four-tuple of local/remote IP, local/remote
port number, complicating it unnecessarily, when IP and the data-link
can deal with that to the benefit of more than just TCP. (eg UDP,
etc...)
rick jones
--
The computing industry isn't as much a game of "Follow The Leader" as
it is one of "Ring Around the Rosy" or perhaps "Duck Duck Goose."
- Rick Jones
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
