Re: AXFR "clarify"

[Wouter Wijngaards <wouter@NLnetLabs.nl>]

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

Brian Dickson wrote:
| What the receiver does with an AXFR or IXFR is less important,
| *except* in the case where the receiver is also a sender.

Well the receiver has to be compatible with the old implementations.

| Correct me if I'm wrong, but the latest version of NSD only supports IXFR
| as a receiver, not as a sender, correct? (For AXFR it supports both.)

Yes. We could support the IXFR fallback case where the IXFR query gets
an AXFR response, and although this would give 'to the letter
conformance', it is not what you would want.

| As for storing case:
| The memory footprint cost is 1/8th, 12.5%, much better than double.
Smart idea.

Best regards,
~   Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHlagYkDLqNwOhpPgRAo7tAJ9k/kBec2g5MMpjekiwH6cOGDGZRgCgkmPN
/VNklI166mb6hDkkmE3zfBY=
=v/vr
-----END PGP SIGNATURE-----

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>