DNSSEC Validator Requirements
draft-mglt-dnsop-dnssec-validator-requirements-07
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Daniel Migault , Edward Lewis , Dan York | ||
| Last updated | 2019-06-01 (Latest revision 2018-11-28) | ||
| Replaced by | draft-ietf-dnsop-dnssec-validator-requirements | ||
| RFC stream | (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
The DNS Security Extensions define a process for validating received data and assert them authentic and complete as opposed to forged. This document describes what is needed in implementations to make the validation process manageable Considerations for accurate time as well as management of the trust anchor store.
Authors
Daniel Migault
Edward Lewis
Dan York
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)