IETF Logo Mail Archive

Re: [v6ops] Fwd: New Version Notification for draft-wkumari-long-headers-01.txt

Joe Touch <touch@isi.edu> Fri, 05 July 2013 13:36 UTC

Return-Path: <touch@isi.edu>
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 557C211E82F5 for <v6ops@ietfa.amsl.com>; Fri, 5 Jul 2013 06:36:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.321
X-Spam-Level:
X-Spam-Status: No, score=-106.321 tagged_above=-999 required=5 tests=[AWL=0.278, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 BD92sS+8PDxw for <v6ops@ietfa.amsl.com>; Fri, 5 Jul 2013 06:36:28 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 8E1E011E82E9 for <v6ops@ietf.org>; Fri, 5 Jul 2013 06:36:28 -0700 (PDT)
Received: from [172.35.3.4] (pc3.shinagawaphvod2-unet.ocn.ne.jp [220.110.141.59]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r65DZqsL022570 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 5 Jul 2013 06:36:03 -0700 (PDT)
Message-ID: <51D6CBB9.2060200@isi.edu>
Date: Fri, 05 Jul 2013 06:35:53 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Nick Hilliard <nick@inex.ie>
References: <20130703235521.17726.15468.idtracker@ietfa.amsl.com> <0BDA30D8-AEDC-4E18-8ACE-64A032305F07@kumari.net> <1372897534.35448.YahooMailNeo@web2802.biz.mail.ne1.yahoo.com> <CAD6AjGSGeNHPUs9+F6OOAeDOy_FZpTOGkH6viX_fENca4H8X0g@mail.gmail.com> <1372899240.80312.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <51D614F6.4030000@isi.edu> <51D6A1C9.8030208@inex.ie> <51D6C2FF.4090103@isi.edu> <51D6C509.7040806@inex.ie> <51D6C66E.5060901@isi.edu> <51D6C7D2.6020504@inex.ie>
In-Reply-To: <51D6C7D2.6020504@inex.ie>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Fwd: New Version Notification for draft-wkumari-long-headers-01.txt
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: Fri, 05 Jul 2013 13:36:34 -0000

On 7/5/2013 6:19 AM, Nick Hilliard wrote:
> On 05/07/2013 14:13, Joe Touch wrote:
>> I don't think that's possible unless you also protect "against" fragments
>> altogether, and I don't think that is the job of a router.
>
> so you're ok about the idea of having a router sitting on the Internet DFZ
> which you can take down with 20kpps of ipv6 fragments,

The router ought to be able to forward at that rate. Unless these are 
addressed *to* the router they don't cause the router a problem. If they 
are, then limiting the forwarding chain won't help because these aren't 
forwarded by that router.

Joe

v2.23.0 | Report a Bug | By Email