[dnsop] RFC 4074 on Common Misbehavior Against DNS Queries for IPv6 Addresses
rfc-editor@rfc-editor.org Thu, 02 June 2005 01:38 UTC
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27210 for <dnsop-archive@lists.ietf.org>; Wed, 1 Jun 2005 21:38:49 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1]) by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j520G9ib000937; Wed, 1 Jun 2005 17:16:09 -0700 (PDT)
Received: (from majordom@localhost) by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j520G9aq000935; Wed, 1 Jun 2005 17:16:09 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j520G803000891 for <dnsop@lists.uoregon.edu>; Wed, 1 Jun 2005 17:16:08 -0700 (PDT)
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j520EcL13676; Wed, 1 Jun 2005 17:14:38 -0700 (PDT)
Message-Id: <200506020014.j520EcL13676@boreas.isi.edu>
To: ietf-announce@ietf.org
Subject: [dnsop] RFC 4074 on Common Misbehavior Against DNS Queries for IPv6 Addresses
Cc: rfc-editor@rfc-editor.org, dnsop@lists.uoregon.edu
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 01 Jun 2005 17:14:38 -0700
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: rfc-editor@rfc-editor.org
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.