Common Features for Encrypted Recursive to Authoritative DNS
draft-pp-dprive-common-features-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Peter van Dijk , Paul E. Hoffman | ||
Last updated | 2021-12-18 (Latest revision 2021-06-16) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
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
Encryption between recursive and authoritative DNS servers is currently being defined in two modes: unauthenticated and fully- authenticated. These two modes have some features in common, and this document defines those common features so that the documents defining the modes do not need to point to each other.
Authors
Peter van Dijk
Paul E. Hoffman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)