Skip to main content

Recommendations for DNSSEC Resolvers Operators

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
Authors Daniel Migault , Edward Lewis , Dan York
Last updated 2020-11-22 (Latest revision 2020-05-21)
Replaces draft-mglt-dnsop-dnssec-validator-requirements
RFC stream Internet Engineering Task Force (IETF)
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
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:


The DNS Security Extensions define a process for validating received data and assert them authentic and complete as opposed to forged. This document is focused clarifying the scope and responsibilities of DNSSEC Resolver Operators (DRO) as well as operational recommendations that DNSSEC validators operators SHOULD put in place in order to implement sufficient Trust that makes DNSSEC validation output accurate. The recommendations described in this document include, provisioning mechanisms as well as monitoring and management mechanisms.


Daniel Migault
Edward Lewis
Dan York

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)