Re: [OPSAWG] ICMP blackhole problem ID.
joel jaeggli <joelja@bogus.com> Mon, 16 July 2012 18:07 UTC
Return-Path: <joelja@bogus.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1529A11E828D for <opsawg@ietfa.amsl.com>; Mon, 16 Jul 2012 11:07:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.33
X-Spam-Level:
X-Spam-Status: No, score=-102.33 tagged_above=-999 required=5 tests=[AWL=0.269, BAYES_00=-2.599, 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 RV6PJgePcusf for <opsawg@ietfa.amsl.com>; Mon, 16 Jul 2012 11:07:10 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 41E0B11E828C for <opsawg@ietf.org>; Mon, 16 Jul 2012 11:07:10 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q6GI7sbY002755 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 16 Jul 2012 18:07:55 GMT (envelope-from joelja@bogus.com)
Message-ID: <50045875.9040906@bogus.com>
Date: Mon, 16 Jul 2012 11:07:49 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120704 Thunderbird/14.0
MIME-Version: 1.0
To: Vincent Roca <vincent.roca@inria.fr>
References: <4FFD74A0.4010805@inria.fr> <4FFD89ED.9000906@bogus.com> <03800193-BD58-433A-B5C6-8B6D83234FC8@inria.fr>
In-Reply-To: <03800193-BD58-433A-B5C6-8B6D83234FC8@inria.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 16 Jul 2012 18:07:55 +0000 (UTC)
Cc: opsawg@ietf.org, Mohamed Ali Kaafar <mohamed-ali.kaafar@inria.fr>
Subject: Re: [OPSAWG] ICMP blackhole problem ID.
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 18:07:11 -0000
On 7/11/12 11:30 PM, Vincent Roca wrote: > Hello Joel, > > Thanks a lot for the pointer to the filtering draft, it's useful. > > This I-D discusses with a lot of details, for each and every ICMP(v4/v6) message type, why and how > a router should filter out (or rate-limit) this message, as well as the consequences of such rules. This > is very useful to understand some of the ICMP related policies that network administrators may deploy. > > In our I-D we take the opposite standpoint. We try to understand, from the end-user point of view, > what's going on when ICMP malfunctions on a given path. This end-user tries to infer as much > information as possible (by default using only his own host, without any vantage points in the core > network), for instance to localize the router/ISP(s) that produce the problems. Whether the network > administrators have good reason to apply such filtering policies is a different matter, especially as it > can also result from configuration errors. So we think that these two documents nicely complement > each other. Do you agree with us? Detecting the existence of path mtu discovery failure is important. I believe they are complementary, probably to the point of overlap. > In any case, thanks for the feedback! > > Cheers, > > The authors > > > On July 11, 2012, 16:13, joel jaeggli wrote: > >> Seems like there is substantial overlap with >> >> http://tools.ietf.org/html/draft-ietf-opsec-icmp-filtering-03 >> >> On 7/11/12 5:42 AM, Ludovic Jacquin wrote: >>> Hi, >>> >>> we have submitted an ID for the 84th IETF meeting, here is a quick summary: >>> >>> ICMP is a key protocol to exchange control and error messages over the Internet. Unfortunately it is frequent that some routers along a given path do not correctly process this protocol. This document provides a taxonomy of the problem in order to help an end user who suspects ICMP-related problems to better understand the situation, and possibly identify the faulty router(s). >>> >>> 2 usefull links if you are interested: >>> the ID: http://datatracker.ietf.org/doc/draft-jacquin-opsawg-icmp-blackhole-problem/ >>> the globecom'12 paper: http://hal.inria.fr/hal-00695746/en/ >>> >>> Feedbacks are welcome. >>> >>> Cheers, >>> Ludovic. >>> _______________________________________________ >>> OPSAWG mailing list >>> OPSAWG@ietf.org >>> https://www.ietf.org/mailman/listinfo/opsawg >>> >> _______________________________________________ >> OPSAWG mailing list >> OPSAWG@ietf.org >> https://www.ietf.org/mailman/listinfo/opsawg >
- [OPSAWG] ICMP blackhole problem ID. Ludovic Jacquin
- Re: [OPSAWG] ICMP blackhole problem ID. joel jaeggli
- Re: [OPSAWG] ICMP blackhole problem ID. Vincent Roca
- Re: [OPSAWG] ICMP blackhole problem ID. joel jaeggli