Skip to main content

DNS Out Of Protocol Signalling
draft-grubto-dnsop-dns-out-of-protocol-signalling-03

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Catherine Almond , Peter van Dijk , M. Groeneweg , Stefan Ubbink , Daniel Salzman , Willem Toorop
Last updated 2024-01-11 (Latest revision 2023-07-10)
RFC stream (None)
Intended RFC status (None)
Formats
Additional resources GitHub Repository
Knot-DNS version 3.1.6 has out of protocol signalling using D-Bus
Presentation at DNSOP at IETF116
Results from Port 53 RIPE DNS Hackathon on 2023-05-2[01]
html of the repo's WIP draft
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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

This document seeks to specify a method for DNS servers to signal programs outside of the server software, and which are not necessarily involved with the DNS protocol, about conditions that can arise within the server. These signals can be used to invoke actions in areas that help provide the DNS service, such as routing. Currently this document serves as a requirements document to come to a signalling mechanism that will suit the use cases best. Part of that effort is to assemble a list of conditions with potential associated out of DNS protocol actions, as well as inventory and assess existing signalling mechanisms for suitability.

Authors

Catherine Almond
Peter van Dijk
M. Groeneweg
Stefan Ubbink
Daniel Salzman
Willem Toorop

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)