DNSSEC Validator Requirements
draft-mglt-dnsop-dnssec-validator-requirements-07
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-06-01 (latest revision 2018-11-28) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-mglt-dnsop-dnssec-validator-requirements-07.txt
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
(daniel.migault@ericsson.com)
Edward Lewis
(edward.lewis@icann.org)
Dan York
(york@isoc.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)