Re: multiple TCP connections

[julian_satran@il.ibm.com]

Steve,

Ethernet links are fine between switches and end-points that do this
multilink.
On other media (WAN) this is not done.
Also on Ethernet when you have several NICS host Ethernet drivers have to
do
the "striping" (and most don't do it).

Regards,
Julo

"Steve Byan" <steve_byan@hotmail.com> on 02/08/2000 22:14:22

Please respond to "Steve Byan" <steve_byan@hotmail.com>

To:   ips@ece.cmu.edu
cc:    (bcc: Julian Satran/Haifa/IBM)
Subject:  Re: multiple TCP connections




Sorry, I didn't understand TCP multihoming. I've been reading RFC 1122 and
RFC 1123 and discovered that TCP binds to exactly one of the local
multihomed addresses, and that TCP applications must choose exactly one of
the multihomed addresses for the remote host. Multiple sessions starts to
make much more sense.

I noticed that there is a standard for ethernet link aggregation (IEEE
802.3ad), and that routers are available that will load-balance over a set
of links. Given these two, it seems to me that multiple TCP connections
aren't needed for speed or reliability, assuming ethernet links at the
end-points. Am I still missing something?

The argument that makes sense to me is that of parallelizing the TCP load
across multiple hardware accelerators.

Thanks.

Regards,
-Steve

Steve Byan <stephen.byan@quantum.com>

________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com