metasystema.org
CurrentINFORMATIONALIETF stream

RFC 4986: Requirements Related to DNS Security (DNSSEC) Trust Anchor Rollover

In plain English — editorial summary, not part of the RFC

Every DNS security-aware resolver must have at least one Trust Anchor to use as the basis for validating responses from DNS signed zones. For various reasons, most DNS security-aware resolvers are expected to have several Trust Anchors. For some operations, manual monitoring and updating of Trust Anchors may be feasible, but many operations will require automated methods for updating Trust Anchors in their security-aware resolvers. This document identifies the requirements that must be met by an automated DNS Trust Anchor rollover solution for security-aware DNS resolvers. This memo provides information for the Internet community.

Document record

Document ID
RFC4986
Published
August 2007
Authors
H. Eland; R. Mundy; S. Crocker; S. Krishnaswamy
Status
INFORMATIONAL
Stream
IETF
Area
int
Pages
11
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/4986-requirements-related-to-dns-security-dnssec-trust-anchor-rollover