IETF Logo Mail Archive

Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)

Fernando Gont <fgont@si6networks.com> Mon, 08 February 2016 23:51 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5B181B3D9F for <ipv6@ietfa.amsl.com>; Mon, 8 Feb 2016 15:51:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9xzLJNthgBhp for <ipv6@ietfa.amsl.com>; Mon, 8 Feb 2016 15:51:47 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 253371B3D9D for <ipv6@ietf.org>; Mon, 8 Feb 2016 15:51:45 -0800 (PST)
Received: from [192.168.1.66] (unknown [186.56.164.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 515A7206AA8; Tue, 9 Feb 2016 00:51:38 +0100 (CET)
Subject: Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "Fred Baker (fred)" <fred@cisco.com>
References: <2134F8430051B64F815C691A62D983183395EF42@XCH-BLV-105.nw.nos.boeing.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <56B90D2B.4000204@si6networks.com>
Date: Mon, 08 Feb 2016 18:48:27 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <2134F8430051B64F815C691A62D983183395EF42@XCH-BLV-105.nw.nos.boeing.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/gS0lV60bIaiKzjVtkltTcNbF-Lk>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 23:51:49 -0000

On 02/05/2016 02:46 PM, Templin, Fred L wrote:
> 
>> As far as I know, RFC 4821 is a response to the latter issue.
> 
> RFC4821 is a response to both issues: 1) Loss of accurate ICMP PTBs, and
> 2) Receipt of inaccurate ICMP PTBs.

FWIW, RFC4821 is rather orthogonal to ICMP-based attacks, since, in
principle, it can be implemented along RFC1918 or in replacement of it.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

v2.23.0 | Report a Bug | By Email