DNSSEC and IPv6 A6 aware server/resolver message size requirements
RFC 3226, “DNSSEC and IPv6 A6 aware server/resolver message size requirements”, is a Proposed Standard document published in December 2001 by O. Gudmundsson. It updates RFC 2535, RFC 2874. It has since been updated by RFC 4033, RFC 4034, RFC 4035. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3226 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3225 Indicating Resolver Support of DNSSEC
- RFC 3222 Terminology for Forwarding Information Base based Router Performance
- RFC 3221 Commentary on Inter-Domain Routing in the Internet
- RFC 3217 Triple-DES and RC2 Key Wrapping
- RFC 3216 SMIng Objectives
- RFC 3211 Password-based Encryption for CMS
- RFC 3210 Applicability Statement for Extensions to RSVP for LSP-Tunnels
- RFC 3209 RSVP-TE: Extensions to RSVP for LSP Tunnels