Consistency for CDS/CDNSKEY and CSYNC is Mandatory
draft-ietf-dnsop-cds-consistency-04
| Document | Type |
Expired Internet-Draft
(dnsop WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Peter Thomassen | ||
| Last updated | 2024-04-04 (Latest revision 2023-10-02) | ||
| Replaces | draft-thomassen-dnsop-cds-consistency | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Reviews |
DNSDIR Early review
(of
-03)
by David Blacka
Ready w/issues
|
||
| Additional resources |
GitHub Repository
Mailing list discussion |
||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Maintenance of DNS delegations requires occasional changes of the DS and NS record sets on the parent side of the delegation. RFC 7344 automates this for DS records by having the child publish CDS and/or CDNSKEY records which hold the prospective DS parameters. Similarly, RFC 7477 specifies CSYNC records to indicate a desired update of the delegation's NS (and glue) records. Parent-side entities (e.g. Registries, Registrars) typically discover these records by querying them from the child, and then use them to update the parent-side RRsets of the delegation accordingly. This document specifies that when performing such queries, parent- side entities MUST ensure that updates triggered via CDS/CDNSKEY and CSYNC records are consistent across the child's authoritative nameservers, before taking any action based on these records.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)