Hi,
On 04/12/2025 13:48, Peter Thomassen via Datatracker wrote:
Subject: Call for adoption: draft-johani-dnsop-delegation-mgmt-via-ddns-06
(Ends 2025-12-18)
This message starts a 2-week Call for Adoption for this document.
Abstract:
Delegation information (i.e. the NS RRset, possible glue, possible DS
records) should always be kept in sync between child zone and parent
zone. However, in practice that is not always the case.
When the delegation information is not in sync the child zone is
usually working fine, but without the amount of redundancy that the
zone owner likely expects to have. Hence, should any further
problems ensue it could have catastropic consequences.
The DNS name space has lived with this problem for decades and it
never goes away. Or, rather, it will never go away until a fully
automated mechanism for how to keep the information in sync
automatically is deployed.
This document proposes such a mechanism.
TO BE REMOVED: This document is being collaborated on in Github at:
https://github.com/johanix/draft-johani-dnsop-delegation-mgmt-via-
ddns (https://github.com/johanix/draft-johani-dnsop-delegation-mgmt-
via-ddns). The most recent working version of the document, open
issues, etc, should all be available there. The authors (gratefully)
accept pull requests.
I support adoption of this draft and I am willing to review.
The draft ties together prior technology (SIG(0), CDS/CSYNC) to
introduce a push model for automatically updating delegation information
in the parent zone. Which could be proven to be more efficient and
easier to operate than the current pull model with scanners.
Best regards,
-- Yorgos
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
