Re: [v6ops] new draft: draft-taylor-v6ops-fragdrop

Nick Hilliard <nick@inex.ie> Wed, 17 October 2012 12:52 UTC

Return-Path: <nick@inex.ie>
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 ABD6C21F87DB for <v6ops@ietfa.amsl.com>; Wed, 17 Oct 2012 05:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level:
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6z59qjyMltcK for <v6ops@ietfa.amsl.com>; Wed, 17 Oct 2012 05:52:58 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id DEE8621F8781 for <v6ops@ietf.org>; Wed, 17 Oct 2012 05:52:57 -0700 (PDT)
X-Envelope-To: v6ops@ietf.org
Received: from crumpet.internal.acquirer.com ([IPv6:2001:1bb8:2004:100:9d04:11ba:6a88:6416]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q9HCqEc8037778 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 17 Oct 2012 13:52:14 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <507EAA22.20404@inex.ie>
Date: Wed, 17 Oct 2012 13:52:50 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <201210161245.q9GCj0i26478@ftpeng-update.cisco.com> <E1829B60731D1740BB7A0626B4FAF0A65E0DEDF3A2@XCH-NW-01V.nw.nos.boeing.com> <507DA6A3.20807@inex.ie> <E1829B60731D1740BB7A0626B4FAF0A65E0DEDF3C3@XCH-NW-01V.nw.nos.boeing.com> <507DAB13.2010704@inex.ie> <E1829B60731D1740BB7A0626B4FAF0A65E0DEDF3CE@XCH-NW-01V.nw.nos.boeing.com> <507DDF8A.9010607@inex.ie> <E1829B60731D1740BB7A0626B4FAF0A65E0DEDF5AB@XCH-NW-01V.nw.nos.boeing.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65E0DEDF5AB@XCH-NW-01V.nw.nos.boeing.com>
X-Enigmail-Version: 1.4.5
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "draft-taylor-v6ops-fragdrop@tools.ietf.org" <draft-taylor-v6ops-fragdrop@tools.ietf.org>
Subject: Re: [v6ops] new draft: draft-taylor-v6ops-fragdrop
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: Wed, 17 Oct 2012 12:52:58 -0000

On 17/10/2012 00:19, Templin, Fred L wrote:
> Filtering near the edges is where we have stateful filters that
> are good at managing state. "Stateless" filtering near the middle
> has no choice but to pass the fragments always.

I understand, but this opens up an implicit DoS vector if you use iACLs on
your dumb/fast transit boxes to filter out external ipv6 traffic to core
infrastructure, because you will be forced to explicitly allow fragments.

> IPv6 nodes are required to reassemble at least 1500 bytes in
> any event. That is for packets explicitly addressed to the node,
> but also consider (temporary) fragment matching for packets
> passing through the node, e.g. as done by VRF. Plus, when the
> router gets a fragment, chances are very good that its brethren
> are hot on its heels and will arrive or not very quickly. So,
> its not a case of holding onto gobs of fragments indefinitely
> and can be managed by reasonably good hardware. At least, I
> have been informed by individuals working for major network
> equipment vendors that their implementations can handle router
> reassembly.

I'll believe this when I see it.  Not saying that this isn't the case, but
in all networking equipment I've ever dealt with, whenever I've heard about
statements like this, the list of caveats is a long as your arm.

> Dropping fragments violates the end-to end principles, and negates
> path MTU diversity. 1280 is too small of a size for us to lock into
> "the matrix" once and for always.

I agree.  All I'm saying is that most core infrastructure on the internet
does not have clever enough silicon to handle anything other than
fixed-format packet structures, and if we expect it to make sensible
decisions on TLV based packet header decoding, we're fooling ourselves.
This problem may be fixed in future if we move from dumb ASICs to smarter
silicon, but there will be a substantial core network upgrade cost
associated with this, and it will take many years to deal with.  In the
interim, operators will need to choose between passing fragments (i.e.
allowing core infrastructure DoS vectors) or dropping fragments (i.e.
breaking ipv6 in the general case).  Neither option is good.


Nick