idnits 2.17.1 draft-ietf-dnsext-message-size-04.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3226 5 Title: DNSSEC and IPv6 A6 aware server/resolver message 6 size requirements 7 Author(s): O. Gudmundsson 8 Status: Standards Track 9 Date: December 2001 10 Mailbox: ogud@ogud.com 11 Pages: 6 12 Characters: 12078 13 Updates: 2874, 2535 15 I-D Tag: draft-ietf-dnsext-message-size-04.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3226.txt 19 This document mandates support for EDNS0 (Extension Mechanisms for 20 DNS) in DNS entities claiming to support either DNS Security 21 Extensions or A6 records. This requirement is necessary because these 22 new features increase the size of DNS messages. If EDNS0 is not 23 supported fall back to TCP will happen, having a detrimental impact on 24 query latency and DNS server load. This document updates RFC 2535 25 and RFC 2874, by adding new requirements. 27 This document is a product of the DNS Extensions Working Group of the 28 IETF. 30 This is now a Proposed Standard Protocol. 32 This document specifies an Internet standards track protocol for 33 the Internet community, and requests discussion and suggestions 34 for improvements. Please refer to the current edition of the 35 "Internet Official Protocol Standards" (STD 1) for the 36 standardization state and status of this protocol. Distribution 37 of this memo is unlimited. 39 This announcement is sent to the IETF list and the RFC-DIST list. 40 Requests to be added to or deleted from the IETF distribution list 41 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 42 added to or deleted from the RFC-DIST distribution list should 43 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 45 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 46 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 47 help: ways_to_get_rfcs. For example: 49 To: rfc-info@RFC-EDITOR.ORG 50 Subject: getting rfcs 52 help: ways_to_get_rfcs 54 Requests for special distribution should be addressed to either the 55 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 56 specifically noted otherwise on the RFC itself, all RFCs are for 57 unlimited distribution.echo 58 Submissions for Requests for Comments should be sent to 59 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 60 Authors, for further information.