[v6ops] RFC 6324 on Routing Loop Attack Using IPv6 Automatic Tunnels: Problem Statement and Proposed Mitigations

rfc-editor@rfc-editor.org Tue, 23 August 2011 20:03 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 416B321F8D00; Tue, 23 Aug 2011 13:03:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level:
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sYyzJLIR0N0d; Tue, 23 Aug 2011 13:03:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 8F63A21F8CEF; Tue, 23 Aug 2011 13:03:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4EAF498C253; Tue, 23 Aug 2011 13:04:28 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110823200431.4EAF498C253@rfc-editor.org>
Date: Tue, 23 Aug 2011 13:04:28 -0700
Cc: v6ops@ietf.org, rfc-editor@rfc-editor.org
Subject: [v6ops] RFC 6324 on Routing Loop Attack Using IPv6 Automatic Tunnels: Problem Statement and Proposed Mitigations
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 20:03:29 -0000

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

        
        RFC 6324

        Title:      Routing Loop Attack Using IPv6 
                    Automatic Tunnels: Problem Statement and Proposed 
                    Mitigations 
        Author:     G. Nakibly, F. Templin
        Status:     Informational
        Stream:     IETF
        Date:       August 2011
        Mailbox:    gnakibly@yahoo.com, 
                    fltemplin@acm.org
        Pages:      19
        Characters: 47385
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-v6ops-tunnel-loops-07.txt

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

This document is concerned with security vulnerabilities in IPv6-in-
IPv4 automatic tunnels.  These vulnerabilities allow an attacker to
take advantage of inconsistencies between the IPv4 routing state and
the IPv6 routing state.  The attack forms a routing loop that can be
abused as a vehicle for traffic amplification to facilitate denial-
of-service (DoS) attacks.  The first aim of this document is to
inform on this attack and its root causes.  The second aim is to
present some possible mitigation measures.  It should be noted that
at the time of this writing there are no known reports of malicious
attacks exploiting these vulnerabilities.  Nonetheless, these
vulnerabilities can be activated by accidental misconfiguration.
This document is not an Internet Standards Track specification; it is
published for informational purposes.

This document is a product of the IPv6 Operations Working Group of the IETF.


INFORMATIONAL: 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-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
Association Management Solutions, LLC