Re: [dnsext] Slamming the TCP door, was Re: Fwd: New Version Notification for draft-ah-dnsext-rfc1995bis-ixfr-02

[Edward Lewis <[e-mail]>]

At 14:14 +0200 6/20/11, Shane Kerr wrote:

>While you will not get the entire zone, you'll likely still get a lot of
>extra data. Your operating system will be happily filling its TCP buffer
>until your application notices that it is getting a AXFR-style transfer
>and then closes the connection.

I really think there's a misunderstanding of the AXFR-style IXFR.

Even if IXFR is on TCP, it's the same protocol that runs over UDP.  I 
once tried to write up an AXFR over UDP and in writing the draft 
learned that AXFR is fundamentally unable to run over UDP.  AXFR and 
IXFR responses are different.  You don't get an AXFR response from an 
IXFR query.

If you have an open TCP connection and see a IXFR query lead to an 
AXFR response, you have to see an IXFR response and AXFR query in 
there too - and also an SOA query/response.  Of else something was 
mis-reporting the AXFR-style IXFR.  Or maybe the IXFR server was 
buggy.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at [phone]

I'm overly entertained.