A Sentinel for Detecting Trusted Keys in DNSSEC
draft-huston-kskroll-sentinel-04
| Document | Type | Replaced Internet-Draft (dnsop WG) | |
|---|---|---|---|
| Authors | Geoff Huston , Joao da Silva Damas , Warren "Ace" Kumari | ||
| Last updated | 2017-12-10 (Latest revision 2017-11-13) | ||
| Replaced by | RFC 8509 | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dnsop-kskroll-sentinel | |
| Consensus boilerplate | Yes | ||
| 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
The DNS Security Extensions (DNSSEC) were developed to provide origin authentication and integrity protection for DNS data by using digital signatures. These digital signatures can be verified by building a chain of trust starting from a trust anchor and proceeding down to a particular node in the DNS. This document specifies a mechanism that will allow an end user to determine the trusted key state of the resolvers that handle the user's DNS queries.
Authors
Geoff Huston
Joao da Silva Damas
Warren "Ace" Kumari
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)