[e2e] TCP improved closing strategies?

[Joe Touch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



William Allen Simpson wrote:
...
> With several hundred thousand clients per minute using 65,000 ports.

The TCP state is supposed to be per socket pair (src/dst IP, src/dst
port). So unless you're running those clients behind a single NAT - or
keep track of only part of the state, this isn't an issue of port reuse.
The issue is more likely consumption of kernel space.

> Through NAT boxen that pass *only* TCP and UDP, and don't randomize the
> Source port, and don't properly handle returning IP fragments.  Etc.
> 
> Back in the real world, that means TCP semantics, such as retransmission
> of lost segments.
> 
> Or reinventing the wheel (segmentation and retransmission over UDP).

A protocol that breaks a request into a 4-5 packets and does even a
simple bit-mask NACK retransmission until they all get there isn't
anywhere near as complex as TCP.

Some wheels don't need to be reinvented. Just dusted off and used where
needed.

Joe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqLm88ACgkQE5f5cImnZrvNegCfcm3tJ5NX3WxmhXbrWxIC1laR
F3sAoKKZeqOdfFP2lm0mkQ3rg92DpZqq
=oJuq
-----END PGP SIGNATURE-----