Operational recommendations for management of DNSSEC Validator
draft-mglt-dnsop-dnssec-validator-requirements-08
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-11-16
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
dnsop D. Migault
Internet-Draft Ericsson
Intended status: Informational E. Lewis
Expires: May 20, 2020 ICANN
D. York
ISOC
November 17, 2019
Operational recommendations for management of DNSSEC Validator
draft-mglt-dnsop-dnssec-validator-requirements-08
Abstract
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 20, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Migault, et al. Expires May 20, 2020 [Page 1]
Internet-DraftDNSSEC Validator operational recommendations November 2019
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. DNSSEC Validator Description . . . . . . . . . . . . . . . . 5
5. Recommendations Categories . . . . . . . . . . . . . . . . . 6
6. Time deviation and absence of Real Time Clock Recommendations 7
7. Trust Anchor Related Recommendations . . . . . . . . . . . . 8
7.1. Trust Anchor Configuration . . . . . . . . . . . . . . . 9
7.1.1. IANA Trust Anchor Bootstrapping . . . . . . . . . . . 10
7.2. Trust Anchor Update . . . . . . . . . . . . . . . . . . . 11
7.2.1. Automated Updates to DNSSEC Trust Anchors . . . . . . 11
7.2.2. Automated Trust Anchor Check . . . . . . . . . . . . 12
8. ZSK / KSK (non TA) Related Recommendations . . . . . . . . . 13
9. DNSKEY Related Recommendations . . . . . . . . . . . . . . . 14
9.1. Automated Reporting . . . . . . . . . . . . . . . . . . . 15
9.2. Negative Trust Anchors . . . . . . . . . . . . . . . . . 15
9.3. Interactions with the cached RRsets . . . . . . . . . . . 16
10. Cryptography Deprecation Recommendations . . . . . . . . . . 16
11. Invalid Reporting Recommendations . . . . . . . . . . . . . . 17
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
13. Security Considerations . . . . . . . . . . . . . . . . . . . 17
14. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 18
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
15.1. Normative References . . . . . . . . . . . . . . . . . . 19
15.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described BCP 14
[RFC2119] [RFC8174] when, and only when, they appear in all capitals,
Show full document text