Paul Vixie wrote:
> my proposal at the time IXFR was being worked on back in DNSEXT was to use the
> UPDATE encoding, which allows RRset deletion or replacement without
> transmitting
> the old RRset. i still think that's a good plan, and if...
As conditions to update a zone supported by UPDATE is limited, my
proposal at that time is:
1) a client gets the current serial number from the primary
of the zone.
2) the client check the current zone content satisfies
certain conditions for update, including those which
are not supported by UPDATE (e.g. some RR does not exist)
the conditions can be arbitrary complex.
3) the client gets the serial number again, to confirm
that other clients haven't changed the zone content
4) the client send IXFR style update and if it fails,
it should be because of race condition with other clients
so, try again
which is still a good thing to do.
Then, IXFR syntax may be extended with wildcard styles of UPDATE,
if bandwidth consumed by DNS administration is a so severe problem.
Masataka Ohta
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
