Operational Recommendations for DS Automation
draft-shetho-dnsop-ds-automation-02
| Document | Type |
Replaced Internet-Draft
(dnsop WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Steve Sheng , Peter Thomassen | ||
| Last updated | 2025-09-05 (Latest revision 2025-08-07) | ||
| Replaced by | draft-ietf-dnsop-ds-automation | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dnsop-ds-automation | |
| 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
Enabling support for automatic acceptance of DS parameters from the Child DNS operator (via RFCs 7344, 8078, 9615) requires the parent operator, often a registry or registrar, to make a number of technical decisions. This document describes recommendations for new deployments of such DS automation.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)