A Framework for DNSSEC Policies and DNSSEC Practice Statements
RFC 6841
Internet Engineering Task Force (IETF) F. Ljunggren
Request for Comments: 6841 Kirei AB
Category: Informational AM. Eklund Lowinder
ISSN: 2070-1721 .SE
T. Okubo
ICANN
January 2013
A Framework for DNSSEC Policies and DNSSEC Practice Statements
Abstract
This document presents a framework to assist writers of DNS Security
Extensions (DNSSEC) Policies and DNSSEC Practice Statements, such as
domain managers and zone operators on both the top level and
secondary level, who are managing and operating a DNS zone with
Security Extensions implemented.
In particular, the framework provides a comprehensive list of topics
that should be considered for inclusion into a DNSSEC Policy
definition and Practice Statement.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6841.
Ljunggren, et al. Informational [Page 1]
RFC 6841 DPS framework January 2013
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Background . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. DNSSEC Policy . . . . . . . . . . . . . . . . . . . . . . 6
3.2. DNSSEC Practice Statement . . . . . . . . . . . . . . . . 7
3.3. Relationship between DNSSEC Policy and Practice
Statement . . . . . . . . . . . . . . . . . . . . . . . . 7
3.4. Set of Provisions . . . . . . . . . . . . . . . . . . . . 9
4. Contents of a Set of Provisions . . . . . . . . . . . . . . . 10
4.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 10
4.2. Publication and Repositories . . . . . . . . . . . . . . . 11
4.3. Operational Requirements . . . . . . . . . . . . . . . . . 12
4.4. Facility, Management, and Operational Controls . . . . . . 13
4.5. Technical Security Controls . . . . . . . . . . . . . . . 17
4.6. Zone Signing . . . . . . . . . . . . . . . . . . . . . . . 20
4.7. Compliance Audit . . . . . . . . . . . . . . . . . . . . . 22
4.8. Legal Matters . . . . . . . . . . . . . . . . . . . . . . 23
5. Outline of a Set of Provisions . . . . . . . . . . . . . . . . 23
6. Security Considerations . . . . . . . . . . . . . . . . . . . 26
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 26
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
8.1. Normative References . . . . . . . . . . . . . . . . . . . 26
8.2. Informative References . . . . . . . . . . . . . . . . . . 26
Ljunggren, et al. Informational [Page 2]
RFC 6841 DPS framework January 2013
1. Introduction
1.1. Background
The Domain Name System (DNS) was not originally designed with strong
security mechanisms to provide integrity and authenticity of its
data. Over the years, a number of vulnerabilities have been
discovered that threaten the reliability and trustworthiness of the
Show full document text