Re: [v6ops] Limiting the size of the IPv6 header chain (draft-ietf-6man-oversized-header-chain)

Fernando Gont <fgont@si6networks.com> Tue, 11 June 2013 11:51 UTC

Return-Path: <fgont@si6networks.com>
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 5E2EA21F94E1; Tue, 11 Jun 2013 04:51:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.332
X-Spam-Level:
X-Spam-Status: No, score=-2.332 tagged_above=-999 required=5 tests=[AWL=0.267, BAYES_00=-2.599]
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 rle6kMY5z8eG; Tue, 11 Jun 2013 04:51:42 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 60FC521F942B; Tue, 11 Jun 2013 04:51:42 -0700 (PDT)
Received: from [186.134.37.222] (helo=[192.168.0.6]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UmN6y-0002lJ-2P; Tue, 11 Jun 2013 13:51:41 +0200
Message-ID: <51B70F16.4050007@si6networks.com>
Date: Tue, 11 Jun 2013 13:50:46 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Jared Mauch <jared@puck.nether.net>
References: <51B6876A.9020202@si6networks.com> <CAD6AjGRuSShUNWE=Dy_e+Y3sVAro-nwyvD8wYy11wN=MfsTXDg@mail.gmail.com> <51B69AB8.3080502@gmail.com> <CAD6AjGSf3LQjfiT-hmKdoDTGxjEQeVSRwUvRKehx=BpNASX7Ww@mail.gmail.com> <51B69FDB.1090809@gmail.com> <CAD6AjGRCKjY83-mD2EMh7bnENksE5AC5ecG5O7K_4H_7PyYW7w@mail.gmail.com> <9636419F-A126-4775-A6C9-3864F8C22323@puck.nether.net>
In-Reply-To: <9636419F-A126-4775-A6C9-3864F8C22323@puck.nether.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Cc: 6man@ietf.org, IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] Limiting the size of the IPv6 header chain (draft-ietf-6man-oversized-header-chain)
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, 11 Jun 2013 11:51:45 -0000

On 06/11/2013 11:50 AM, Jared Mauch wrote:
> 
> On Jun 11, 2013, at 12:23 AM, cb.list6 <cb.list6@gmail.com> wrote:
> 
>> I believe Warren's data hints at the idea that the packets will vanish if they don't fit a very specific profile.  
> 
> Very likely…
> 
> Anything beyond the ability of my device to filter poses a security risk.  

That's why we're considering limiting the size of the IPv6 header chain.



> Example from 2008 of operators turning off header processing:
> 
> http://www.gossamer-threads.com/lists/nsp/juniper/15066

I only skimmed through the that thread... but it seems unlreated to this
issue -- that thread seems to be about filtering RHT0, which has/had
known security issues such as being useful for amplification attacks.

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