[e2e] [unclassified] TCP improved closing strategies?
David P. Reed
dpreed at reed.com
Wed Aug 12 18:14:54 PDT 2009
I'm not sure whether it wouldn't be better to think through a non-TCP
solution here. TCP is incredibly heavy duty for the purpose of doing a
properly "secure" DNS transaction, which ultimately involves a single
request-response in the most common case.
And if you do, there is no reason why the server needs to maintain
*connection* state at all - connections are for long term interactions.
Am I missing something here?
On 08/12/2009 05:51 PM, William Allen Simpson wrote:
> With the advent of more widespread DNSsec deployment, more UDP sessions
> are likely to fallover into TCP sessions.
> I've been informed that even today, with a more limited TCP activity,
> busy servers cannot wait 2MSL to finish closing.
> Also, busy caching servers run out of port numbers, and cycle quickly.
> So there's ample opportunity for seemingly duplicate transmissions.
> I've been searching my personal copy of the e2e-interest archives back to
> '98 (the previous years are only on backup somewhere), and haven't found
> anything on improved closing strategies. Ideas?
> Of course, there's T/TCP, but wasn't closing one of its Achilles heels?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the end2end-interest