Re: [v6ops] draft-gont-v6ops-ipv6-ehs-in-real-world: clarification text

Joe Touch <touch@isi.edu> Tue, 21 April 2015 15:46 UTC

Return-Path: <touch@isi.edu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 323621ACEA9 for <v6ops@ietfa.amsl.com>; Tue, 21 Apr 2015 08:46:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54-0QPwPnPki for <v6ops@ietfa.amsl.com>; Tue, 21 Apr 2015 08:46:38 -0700 (PDT)
Received: from mail-b.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3B231ACE7E for <v6ops@ietf.org>; Tue, 21 Apr 2015 08:46:38 -0700 (PDT)
Received: from [192.168.1.3] (pool-71-103-148-202.lsanca.dsl-w.verizon.net [71.103.148.202]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id t3LFjWLP026245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 21 Apr 2015 08:45:41 -0700 (PDT)
Message-ID: <5536709B.1050001@isi.edu>
Date: Tue, 21 Apr 2015 08:45:31 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Gert Doering <gert@space.net>
References: <D157BDE1.44CEE%evyncke@cisco.com> <55351EA0.2010700@isi.edu> <20150420212125.GE54385@Space.Net> <55356F68.1020605@isi.edu> <20150421064811.GG54385@Space.Net>
In-Reply-To: <20150421064811.GG54385@Space.Net>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/xekc6CkPA6HUix5peWqYgl6I3fg>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, Merike Kaeo <merike@doubleshotsecurity.com>, "draft-gont-v6ops-ipv6-ehs-in-real-world@tools.ietf.org" <draft-gont-v6ops-ipv6-ehs-in-real-world@tools.ietf.org>, Fernando Gont <fgont@si6networks.com>
Subject: Re: [v6ops] draft-gont-v6ops-ipv6-ehs-in-real-world: clarification text
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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, 21 Apr 2015 15:46:40 -0000


On 4/20/2015 11:48 PM, Gert Doering wrote:
> Hi,
> 
> On Mon, Apr 20, 2015 at 02:28:08PM -0700, Joe Touch wrote:
>> On 4/20/2015 2:21 PM, Gert Doering wrote:
>>> On Mon, Apr 20, 2015 at 08:43:28AM -0700, Joe Touch wrote:
>>>>> If for some reasons, a router in the middle needs access to layer-4
>>>>                                               ^^^^^
>>>>> information (IPFIX? DDoS mitigation? ... ?), then the EH chain must be
>>>>> parsed which can cause a performance impact.
>>> [..]
>>>> 	1) this is the router vendor's decision, not a requirement
>>>> 	of Internet routers
>>>
>>> So, please tell me how you build an Internet router that is able to
>>> defend itself against control plane abuse and does not need to look into
>>> L4 to do so?
>>
>> A router can protect its own control plane by looking at the packet
>> contents, but then it is acting as a host at that point and should be
>> looking there only for packets addressed to interfaces of that router.
>> That's not a forwarding function and thus doesn't limit the forwarding
>> plane.
> 
> Of course, but real world requires that this filter function needs to be
> implemented in the forwarding plane, because otherwise packets would just
> saturate the link between forwarding and control plane if you would only 
> filter on "the other side".

DDOS filtering is a feature, not a requirement.

If you want to offer that as a feature, please stop complaining that
customers should expect that it runs at rate with packets that conform
to existing standards.

> From a purely academic point of view, I totally agree with you.  
> 
> Unfortunately, the Internet is not.

The Internet is also not designed to optimize your profit margins either.

Joe