A new Request for Comments is now available in online RFC libraries. RFC 4074 Title: Common Misbehavior Against DNS Queries for IPv6 Addresses Author(s): Y. Morishita, T. Jinmei Status: Informational Date: May 2005 Mailbox: yasuhiro@jprs.co.jp, jinmei@isl.rdc.toshiba.co.jp Pages: 6 Characters: 13073 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dnsop-misbehavior-against-aaaa-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4074.txt There is some known misbehavior of DNS authoritative servers when they are queried for AAAA resource records. Such behavior can block IPv4 communication that should actually be available, cause a significant delay in name resolution, or even make a denial of service attack. This memo describes details of known cases and discusses their effects. This document is a product of the Domain Name System Operations Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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. 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. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
Attachment:
2#Part.001
Description: Binary data
Content-Type: text/plain Content-ID: <050601171319.RFC@RFC-EDITOR.ORG>
Attachment:
4#Part.003
Description: Binary data
Attachment:
5#Mime.822
Description: Binary data
AdmID:F64F8983CFA4D0A9A6A131C1C8690F03
_______________________________________________ IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce