RFC - 3226
DNSSEC and IPv6 A6 aware server/resolver message size requirements
| Updates: |
| RFC-2874exp |
DNS Extensions to Support IPv6 Address Aggregation and Renumbering (Updated by RFC-3226prop, RFC-3152, RFC-3364, RFC-3363)
|
| RFC-2535 |
Domain Name System Security Extensions (Obsoleted by RFC-4033prop, RFC-4035prop, RFC-4034prop) (Updated by RFC-3755, RFC-3757, RFC-3226prop, RFC-3658, RFC-3655, RFC-3007prop, RFC-3008, RFC-3845, RFC-3597prop, RFC-3445, RFC-3090, RFC-2931prop)
|
| Updated by: |
| RFC-4035prop |
Protocol Modifications for the DNS Security Extensions (Updated by RFC-4470prop)
|
| RFC-4034prop |
Resource Records for the DNS Security Extensions (Updated by RFC-4470prop)
|
| RFC-4033prop |
DNS Security Introduction and Requirements |
| Referred by: |
6 RFC |
| Refers to: |
8 RFC |
Status
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved.
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(-> 4035prop | 4034prop | 4033prop) and RFC 2874exp, by adding new requirements.
