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

Nick Hilliard <nick@inex.ie> Wed, 17 October 2012 21:43 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 BB24F21F873D for <v6ops@ietfa.amsl.com>; Wed, 17 Oct 2012 14:43:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level:
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.050, 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 vkxFunwZf4Xi for <v6ops@ietfa.amsl.com>; Wed, 17 Oct 2012 14:43:06 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 09F6321F8726 for <v6ops@ietf.org>; Wed, 17 Oct 2012 14:43:05 -0700 (PDT)
X-Envelope-To: v6ops@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100:9031:7f05:47f2:b06a]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q9HLgHxH043805 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 17 Oct 2012 22:42:23 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <507F265E.6030000@inex.ie>
Date: Wed, 17 Oct 2012 22:42:54 +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> <BB219517-B488-4777-AE9C-35C57BE91263@kumari.net> <E1829B60731D1740BB7A0626B4FAF0A65E0DEDF778@XCH-NW-01V.nw.nos.boeing.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65E0DEDF778@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 21:43:06 -0000

On 17/10/2012 16:39, Templin, Fred L wrote:
> You know, all of this discussion is moot. RFC2460, Section 5 says:
[...]
> the law until someone writes a different one. Middleboxes therefore
> have no basis for dropping fragments, unless they can through some
> means be determined as malicious (e.g., VFR).

We're all agreed that legitimate fragments should get through.  But there
is a large body of installed hardware out there in the core of the Internet
which has exactly the following options for dealing with ipv6 fragments:

> 1. forward them to the RP for software processing, which will cause a
> management plane DoS

> 2. drop them unilaterally, implicitly overriding all v6 ACLs, breaking
> IPv6 fragmentation

> 3. forward them unilaterally, implicitly overriding all ACLs, opening up
> an infrastructure DoS vector

None of these are pleasant options.

It's not a moot point: it's just a matter of the equipment not matching up
with the requirements of the RFCs and is a serious practical problem for
operators which use older equipment.  So how do we deal with it?  Does it
deserve a mention in the draft, with recommendations on what to do, or
would it be better to ignore the problem as it's a vendor/device specific
issue?

Nick