BCP 140, RFC 5358 on Preventing Use of Recursive Nameservers in Reflector Attacks

rfc-editor@rfc-editor.org Fri, 17 October 2008 22:23 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B582C28C150; Fri, 17 Oct 2008 15:23:03 -0700 (PDT)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C094928C13D; Fri, 17 Oct 2008 15:23:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.4
X-Spam-Level:
X-Spam-Status: No, score=-17.4 tagged_above=-999 required=5 tests=[AWL=0.199, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rq1kCGKA7P7E; Fri, 17 Oct 2008 15:23:01 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id EEF3428C122; Fri, 17 Oct 2008 15:23:00 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 5B68B168CAE; Fri, 17 Oct 2008 15:24:06 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 140, RFC 5358 on Preventing Use of Recursive Nameservers in Reflector Attacks
From: rfc-editor@rfc-editor.org
Message-Id: <20081017222406.5B68B168CAE@bosco.isi.edu>
Date: Fri, 17 Oct 2008 15:24:06 -0700
Cc: dnsop@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.

        BCP 140        
        RFC 5358

        Title:      Preventing Use of Recursive Nameservers 
                    in Reflector Attacks 
        Author:     J. Damas, F. Neves
        Status:     Best Current Practice
        Date:       October 2008
        Mailbox:    Joao_Damas@isc.org, 
                    fneves@registro.br
        Pages:      7
        Characters: 14957
        See Also:   BCP0140

        I-D Tag:    draft-ietf-dnsop-reflectors-are-evil-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5358.txt

This document describes ways to prevent the use of default configured
recursive nameservers as reflectors in Denial of Service (DoS)
attacks.  It provides recommended configuration as measures to
mitigate the attack.  This document specifies an Internet Best Current 
Practices for the Internet Community, and requests discussion and 
suggestions for improvements.

This document is a product of the Domain Name System Operations Working Group of the IETF.

BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce