metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 3225: Indicating Resolver Support of DNSSEC

Still current, but amended. Parts of this document are changed or extended by RFC 4033, RFC 4034, RFC 4035. Read both.

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

In order to deploy DNSSEC (Domain Name System Security Extensions) operationally, DNSSEC aware servers should only perform automatic inclusion of DNSSEC RRs when there is an explicit indication that the resolver can understand those RRs. This document proposes the use of a bit in the EDNS0 header to provide that explicit indication and describes the necessary protocol changes to implement that notification. [STANDARDS-TRACK]

Document record

Document ID
RFC3225
Published
December 2001
Authors
D. Conrad
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
6
Also known as
—
Updated by:
RFC 4033, RFC 4034, RFC 4035

Topics

Referenced by

3 later RFCs formally update or obsolete part of this document.

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/3225-indicating-resolver-support-of-dnssec