<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<font face="Helvetica, Arial, sans-serif">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.<br>
<br>
And if you do, there is no reason why the server needs to maintain
*connection* state at all - connections are for long term interactions.<br>
<br>
Am I missing something here?<br>
<br>
<br>
</font><br>
On 08/12/2009 05:51 PM, William Allen Simpson wrote:
<blockquote cite="mid:4A833956.2050501@gmail.com" type="cite">With the
advent of more widespread DNSsec deployment, more UDP sessions
<br>
are likely to fallover into TCP sessions.
<br>
<br>
I've been informed that even today, with a more limited TCP activity,
<br>
busy servers cannot wait 2MSL to finish closing.
<br>
<br>
Also, busy caching servers run out of port numbers, and cycle quickly.
<br>
So there's ample opportunity for seemingly duplicate transmissions.
<br>
<br>
I've been searching my personal copy of the e2e-interest archives back
to
<br>
'98 (the previous years are only on backup somewhere), and haven't
found
<br>
anything on improved closing strategies. Ideas?
<br>
<br>
Of course, there's T/TCP, but wasn't closing one of its Achilles heels?
<br>
<br>
</blockquote>
</body>
</html>