[DNSOP] WG Last Call: draft-ietf-dnsop-delegation-mgmt-via-d dns-02 (Ends 2026-09-07)

Peter Thomassen via Datatracker <[email protected]>
Newsgroups gmane.ietf.dnsop
Message-ID <178722067194.864736.14347194058965603773@dt-datatracker-7c6ddbc678-86d5j>
This message starts a WG Last Call for:
draft-ietf-dnsop-delegation-mgmt-via-ddns-02

This Working Group Last Call ends on 2026-09-07

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 catastrophic 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 based on DNS Dynamic Updates
   (DDNS) secured with SIG(0) signatures, sent from the child to the
   parent across the zone cut.  The target of the update is discovered
   via the DSYNC record defined in [RFC9859].

   TO BE REMOVED: This document is being collaborated on in Github at:
   https://github.com/johanix/draft-ietf-dnsop-delegation-mgmt-via-ddns
   (https://github.com/johanix/draft-ietf-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.

File can be retrieved from:
https://www.ietf.org/archive/id/draft-ietf-dnsop-delegation-mgmt-via-ddns-02.txt

Please review and indicate your support or objection to proceed with the
publication of this document by replying to this email keeping [email protected]
in copy. Objections should be explained and suggestions to resolve them are
highly appreciated.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [1].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.

[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-delegation-mgmt-via-ddns/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-delegation-mgmt-via-ddns-02

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-dnsop-delegation-mgmt-via-ddns-02

_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.