DNSSEC Validators Requirements
draft-mglt-dnsop-dnssec-validator-requirements-00
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Author | Daniel Migault | ||
Last updated | 2014-08-17 (Latest revision 2014-02-13) | ||
Replaced by | draft-ietf-dnsop-dnssec-validator-requirements | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
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
DNSSEC provides data integrity and authentication for DNSSEC validators. However, without valid trust anchor(s) and an acceptable value for the current time, DNSSEC validation cannot be performed. This document lists the requirements to be addressed so resolvers can have DNSSEC validation can be always-on.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)