Re: draft-ietf-dnsext-axfr-clarify-05.txt

[Mark.Andrews@isc.org]

> </chair>
> <uncloak> 
> 
> <surprise>
> confession, other than djb, i have been the other wg member not in
> consensus on this document.
> 
> as i said in yokohama, i was the one personally uncomfortable with
> the axfr document mandating the zone content being maintained
> exactly as served by the primary.  i did not see why it was
> *necessary* for this to be done, and was hesitant as djb claimed
> his implementation would be adversely affected.
> </surprise>
> 
> yes dan, i was the one holding up progress of this document.
> 
> i have recently become convinced that the primary's zone content on
> axfrs needs to be preserved purely so that subsequent ixfrs may be
> applied.

	Randy, while I'm glad that you agree that the zone contents
	need to be preserved, this sounds like you discount the
	need to fix the operational problems caused as the result
	replacing data in the zone with that from another source.

	This is *not* just a IXFR problem.  It causes problems with
	servers that don't support IXFR.  I would hate to see a
	implementor say "I don't need to do this because I don't
	support IXFR".

	See <200211280030.gAS0UYgU009457@drugs.dv.isc.org> for
	a detailed example of a non IXFR related problem that is
	fixed by preserving the zones contents.
 
	Mark

> randy
> 
> 
> --
> 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/>
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org

--
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/>