On Jul 24 2012, Joe Abley wrote:
[...]
In this context, "the same" refers to the steady state: i.e. a mechanism
which standardised the promotion of an updated, signed apex NS set to form
a replacement delegation set in the parent would be one that enforced that
steady-state similarity.
Even if the intent is for the sets to converge, it isn't obvious that
upward propagation ("promotion") is always the best way to do things.
In theory, at least, I try to make changes in this order:
Adding an NS: 1. Set up the slaving arrangement.
2. Add to the in-zone NS RRset.
3. Add to the delegation NS RRset.
Dropping an NS: 1. Delete from the delegation NS RRset.
2. Delete from in-zone NS RRset.
3. Tear down the slaving arrangement.
It's true, though, that I wouldn't much care about the order of the first
two actions in the latter case if I could be sure that the updating of the
delegation could always be done in a timely fashion.
--
Chris Thompson University of Cambridge Computing Service,
Email: c...@ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QH,
Phone: +44 1223 334715 United Kingdom.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
