Skip to main content

DNSSEC and IPv6 A6 aware server/resolver message size requirements
draft-ietf-dnsext-message-size-04

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3226.
Author Ólafur Guðmundsson
Last updated 2020-01-21 (Latest revision 2001-02-23)
RFC stream Internet Engineering Task Force (IETF)
Formats
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state RFC 3226 (Proposed Standard)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-ietf-dnsext-message-size-04
A new Request for Comments is now available in online RFC libraries.

        RFC 3226

        Title:      DNSSEC and IPv6 A6 aware server/resolver message
                    size requirements
        Author(s):  O. Gudmundsson
        Status:     Standards Track
        Date:       December 2001
        Mailbox:    ogud@ogud.com
        Pages:      6
        Characters: 12078
        Updates:    2874, 2535

        I-D Tag:    draft-ietf-dnsext-message-size-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3226.txt

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.

This document is a product of the DNS Extensions Working Group of the
IETF.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.