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

Fernando Gont <fgont@si6networks.com> Tue, 11 June 2013 02:21 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 4A61721E80A2; Mon, 10 Jun 2013 19:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.018
X-Spam-Level:
X-Spam-Status: No, score=-2.018 tagged_above=-999 required=5 tests=[AWL=-0.019, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 YV6DPpvbHWum; Mon, 10 Jun 2013 19:21:54 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 6A4AE21E805A; Mon, 10 Jun 2013 19:21:45 -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 1UmEDP-0006An-Rt; Tue, 11 Jun 2013 04:21:44 +0200
Message-ID: <51B6876A.9020202@si6networks.com>
Date: Tue, 11 Jun 2013 04:11:54 +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: "6man@ietf.org" <6man@ietf.org>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: [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 02:21:55 -0000

Folks,

We're currently editing the aforementioned I-D. So far, the I-D just
required that the entire IPv6 header chain be present in the first fragment.

Based on recent/ongoing discussions on the 6man and v6ops lists, there
seems to be quite a few folks pushing the idea of limiting the size f
the IPv6 header chain to some value (typically in the order of a few
hundred bytes).

An earlier version of draft-ietf-6man-oversized-header-chain limited the
header chain to 1280 bytes, but this requirement was later removed.

However, since then a number of folks have produced real world data
which indicates that packets "won't make it to the destination node" if
the header chain is larger than a few hundred bytes, and I believe that,
overall, our understanding of the problem and situation has increased
since then.

My question to th wg is:

1) Do we want to limit the size of the IPv6 header chain?

2) If so, which limit should we pick?

Thanks!

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