<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-dnsop-cds-consistency" target="https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-cds-consistency-09">
   <front>
      <title>Clarifications on CDS/CDNSKEY and CSYNC Consistency</title>
      <author initials="P." surname="Thomassen" fullname="Peter Thomassen">
         <organization>SSE - Secure Systems Engineering GmbH</organization>
      </author>
      <date month="October" day="15" year="2025" />
      <abstract>
	 <t>   Maintenance of DNS delegations requires occasional changes of the DS
   and NS record sets on the parent side of the delegation.  For the
   case of DS records, &quot;Automating DNSSEC Delegation Trust Maintenance&quot;
   (RFC 7344) provides automation by allowing the child to publish CDS
   and/or CDNSKEY records holding the prospective DS parameters which
   the parent can ingest.  Similarly, &quot;Child-to-Parent Synchronization
   in DNS&quot; (RFC 7477) specifies CSYNC records to indicate a desired
   update of the delegation&#x27;s NS (and glue) records.  Parent-side
   entities (e.g., Registries and Registrars) can query these records
   from the child and, after validation, use them to update the parent-
   side Resource Record Sets (RRsets) of the delegation.

   This document specifies that when performing such queries, parent-
   side entities has to ensure that updates triggered via CDS/CDNSKEY
   and CSYNC records are consistent across the child&#x27;s authoritative
   nameservers, before taking any action based on these records.

   This document updates RFC 7344 and RFC 7477.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-dnsop-cds-consistency-09" />
   
</reference>
