IETF Logo Mail Archive

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

Jared Mauch <jared@puck.nether.net> Tue, 11 June 2013 09:50 UTC

Return-Path: <jared@puck.nether.net>
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 3E8EB21F962B; Tue, 11 Jun 2013 02:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 nZpcaN9llqtb; Tue, 11 Jun 2013 02:50:55 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 7E42921F962A; Tue, 11 Jun 2013 02:50:55 -0700 (PDT)
Received: from [10.0.0.129] (173-167-0-106-michigan.hfc.comcastbusiness.net [173.167.0.106]) (authenticated bits=0) by puck.nether.net (8.14.7/8.14.5) with ESMTP id r5B9olJV001342 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 11 Jun 2013 05:50:47 -0400
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset="windows-1252"
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAD6AjGRCKjY83-mD2EMh7bnENksE5AC5ecG5O7K_4H_7PyYW7w@mail.gmail.com>
Date: Tue, 11 Jun 2013 05:50:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9636419F-A126-4775-A6C9-3864F8C22323@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>
To: "cb.list6" <cb.list6@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (puck.nether.net [204.42.254.5]); Tue, 11 Jun 2013 05:50:48 -0400 (EDT)
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 Ops WG <v6ops@ietf.org>, 6man@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 09:50:56 -0000

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.  

Example from 2008 of operators turning off header processing:

http://www.gossamer-threads.com/lists/nsp/juniper/15066

- Jared

v2.23.0 | Report a Bug | By Email