RFC 8145: Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC)
In plain English — editorial summary, not part of the RFC
The DNS Security Extensions (DNSSEC) were developed to provide origin authentication and integrity protection for DNS data by using digital signatures. These digital signatures can be verified by building a chain of trust starting from a trust anchor and proceeding down to a particular node in the DNS. This document specifies two different ways for validating resolvers to signal to a server which keys are referenced in their chain of trust. The data from such signaling allow zone administrators to monitor the progress of rollovers in a DNSSEC-signed zone.
Document record
- Document ID
- RFC8145
- Published
- April 2017
- Authors
- D. Wessels; W. Kumari; P. Hoffman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 13
- Also known as
- —
- Updated by:
- RFC 8553
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7344Automating DNSSEC Delegation Trust MaintenanceUpdated
September 2014
- RFC 8027DNSSEC Roadblock AvoidanceCurrent
November 2016
- RFC 7828The edns-tcp-keepalive EDNS0 OptionCurrent
April 2016
- RFC 8509A Root Key Trust Anchor Sentinel for DNSSECCurrent
December 2018
- RFC 7646Definition and Use of DNSSEC Negative Trust AnchorsCurrent
September 2015
- RFC 8749Moving DNSSEC Lookaside Validation (DLV) to Historic StatusCurrent
March 2020
- RFC 8976Message Digest for DNS ZonesCurrent
February 2021
- RFC 9276Guidance for NSEC3 Parameter SettingsCurrent
August 2022
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?