[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
draft-nakibly-v6ops-tunnel-loops-03
- To: v6ops@ops.ietf.org
- Subject: draft-nakibly-v6ops-tunnel-loops-03
- From: Gabi Nakibly <gnakibly@yahoo.com>
- Date: Wed, 18 Aug 2010 12:00:03 -0700 (PDT)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=h6/XbNeKgDI4gOLueBLj0ZU6okqYFHqD1POd+/h1LZYR5CT+JrBo9HiyoPFrrind7yWo9+I+YoLnpszCfKZ4EFk3r99vv6lyVkWxG8K1UV2GIeH4GPVDNSsbwk4VPSb+JHmz3wAS0KtdcobEkD+d9Ci1ehSRzb9JMqtpcnhea3A=;
A new version of draft-nakibly-v6ops-tunnel-loops has been posted.
The new version follows the comments given on the list.
The major change is the addition of a Recommendation section
that recommends preferred mitigation measures under different conditions.
Gabi
----- Forwarded Message ----
> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> To: gnakibly@yahoo.com
> Cc: fltemplin@acm.org
> Sent: Wed, August 18, 2010 9:46:46 PM
> Subject: New Version Notification for draft-nakibly-v6ops-tunnel-loops-03
>
>
> A new version of I-D, draft-nakibly-v6ops-tunnel-loops-03.txt has been
>successfully submitted by Gabi Nakibly and posted to the IETF repository.
>
> Filename: draft-nakibly-v6ops-tunnel-loops
> Revision: 03
> Title: Routing Loop Attack using IPv6 Automatic Tunnels: Problem
>Statement and Proposed Mitigations
> Creation_date: 2010-08-18
> WG ID: Independent Submission
> Number_of_pages: 11
>
> Abstract:
> This document is concerned with security vulnerabilities in IPv6-in-
> IPv4 automatic tunnels. These vulnerabilities allow an attacker to
> take advantage of inconsistencies between a tunnel's overlay IPv6
> routing state and the native IPv6 routing state. The attack forms a
> routing loop which can be abused as a vehicle for traffic
> amplification to facilitate 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.
>
>
>
>
>
> The IETF Secretariat.
>
>
>