Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Great Suggestion for the DNS problem...?

  • From: Mohacsi Janos
  • Date: Tue Jul 29 10:32:46 2008



On Tue, 29 Jul 2008, Steven M. Bellovin wrote:

On Tue, 29 Jul 2008 15:56:19 +0200
Colin Alston <karnaugh@karnaugh.za.net> wrote:

DNS uses UDP.
Ahh yes of course..

Why does it use UDP? :P

In this situation, UDP uses one query packet and one reply.  TCP uses 3
to set up the connection, a query, a reply, and three to tear down the
connection.  *Plus* the name server will have to keep state for
every client, plus TIMEWAIT state, etc.  (Exercise left to TCP geek
readers: how few packets can you do this in?  For example -- send the
query with the SYN+ACK, send client FIN with the query, send server FIN
with the answer?  Bonus points for not leaving the server's side in
TIMEWAIT.  Exercise for implementers: how sane can your stack be if
you're going to support that?)
It was advocated as T/TCP in 90s.
http://www.kohala.com/start/ttcp.html
Not accepted widely:
http://en.wikipedia.org/wiki/T/TCP
Regads,
 		Janos Mohacsi





Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.