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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 11 June 2013 03:34 UTC

Return-Path: <brian.e.carpenter@gmail.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 90E2111E80CC; Mon, 10 Jun 2013 20:34:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level:
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 18LJagf7MbwP; Mon, 10 Jun 2013 20:34:21 -0700 (PDT)
Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 6379B11E80E1; Mon, 10 Jun 2013 20:34:18 -0700 (PDT)
Received: by mail-pb0-f49.google.com with SMTP id jt11so7916869pbb.22 for <multiple recipients>; Mon, 10 Jun 2013 20:34:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8mK/BVNImZxMsESlsVGmAchtyjuBurB6v558WVZNpAg=; b=Ngh6yTjESHul58liRhpaU+UFXmU/47sEcC+GGcXpkqXcpDV+5UAt0U8SCxGfYQW72x pPeQt2qhjWr0MQG1lwLjPKCylxWxGuUsPF6Wjt8ZG57F5amTFyc2SGEdr/77eo740JXs E9eXfSW+I2J0iVB4342evKIqEUrKLDvEjcOWYBxLHisgPA6jXPYpeWs3pL9pohkAomLy cdc0TPA6j1XXd5y1Hl/+bcN9EPZf6rpcXthiZt58zZ26d4b0clxbUHqL2WaIXJOfTW/i bL72QfBnPBrhbE8N/05NIo7Uwviw1kJpROHbtNa2VeEtJQL48eR9fhAOOp0C5qrUZ70s 1hfA==
X-Received: by 10.66.164.232 with SMTP id yt8mr16758062pab.21.1370921658164; Mon, 10 Jun 2013 20:34:18 -0700 (PDT)
Received: from [192.168.1.2] (118-92-62-227.dsl.dyn.ihug.co.nz. [118.92.62.227]) by mx.google.com with ESMTPSA id fr1sm12699641pbb.26.2013.06.10.20.34.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 10 Jun 2013 20:34:17 -0700 (PDT)
Message-ID: <51B69AB8.3080502@gmail.com>
Date: Tue, 11 Jun 2013 15:34:16 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "cb.list6" <cb.list6@gmail.com>
References: <51B6876A.9020202@si6networks.com> <CAD6AjGRuSShUNWE=Dy_e+Y3sVAro-nwyvD8wYy11wN=MfsTXDg@mail.gmail.com>
In-Reply-To: <CAD6AjGRuSShUNWE=Dy_e+Y3sVAro-nwyvD8wYy11wN=MfsTXDg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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 03:34:21 -0000

On 11/06/2013 15:21, cb.list6 wrote:
> On Jun 10, 2013 7:23 PM, "Fernando Gont" <fgont@si6networks.com> wrote:
>> 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?
>>
> 
> It's not the size, it is how you use it.
> 
> I would suggest "common types" be permitted (tcp, udp, sctp, icmpv6, frag,
> esp, ah) while anything else must be behind an esp. This ensures all
> parties agree that further arbitrary headers will only be processed by the
> concenting end systems.

Truly, you won't get consensus for that; it isn't realistic. I think we're
already very near consensus on an unconstrained limit in the 128/256
area.

    Brian

> 
> CB
>> Thanks!
>>
>> Best regards,
>> --
>> Fernando Gont
>> SI6 Networks
>> e-mail: fgont@si6networks.com
>> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>>
>>
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> 
> ------------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------