On Mar 11, 2024, at 07:30, Ray Bellis <r...@bellis.me.uk> wrote: > > I think this document gives an opportunity to explicitly clarify expectations > regarding the NS records either side of the zone cut.
Wearing my co-author hat: yes, that's the purpose. > I get the impression with DELEG on the horizon that there's a shift towards > the parent side data being considered more "authoritative" even though in > protocol terms it explicitly isn't. Wearing my BoF co-chair hat: it is waaay to soon to say that. There were explicit requests for child-side declarations to be in scope for the eventual working group. > Even if that's not the case, discussion of when child-side NS records should > be purged and then re-learned by following the parent-side delegation would > be useful. Wearing my DNSOP participant hat: that's why I encouraged Shumon and PaulV to revive <https://datatracker.ietf.org/doc/draft-ietf-dnsop-ns-revalidation/>. > I also idly wonder what would happen if one were able to incorrectly put the > DS records for a zone into the child zone... Wearing my Hackathon hat: I'm working on a small testbed, using Shumon's code, that could test that. --Paul Hoffman, who rarely actually wears hats, but will in Brisbane because of the sun _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
