metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 3226: DNSSEC and IPv6 A6 aware server/resolver message size requirements

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

This document mandates support for EDNS0 (Extension Mechanisms for DNS) in DNS entities claiming to support either DNS Security Extensions or A6 records. This requirement is necessary because these new features increase the size of DNS messages. If EDNS0 is not supported fall back to TCP will happen, having a detrimental impact on query latency and DNS server load. This document updates RFC 2535 and RFC 2874, by adding new requirements. [STANDARDS-TRACK]

Document record

Document ID
RFC3226
Published
December 2001
Authors
O. Gudmundsson
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
6
Also known as
—
Updates:
RFC 2535, RFC 2874
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/3226-dnssec-and-ipv6-a6-aware-server-resolver-message-size-requirements