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

Joe Touch <touch@isi.edu> Fri, 05 July 2013 12:53 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 9A53611E82CF for <v6ops@ietfa.amsl.com>; Fri, 5 Jul 2013 05:53:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.099
X-Spam-Level:
X-Spam-Status: No, score=-106.099 tagged_above=-999 required=5 tests=[AWL=0.500, 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 BX8f0KJNEmw1 for <v6ops@ietfa.amsl.com>; Fri, 5 Jul 2013 05:53:01 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 70BD211E82CA for <v6ops@ietf.org>; Fri, 5 Jul 2013 05:53:00 -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 r65CqPIk015587 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 5 Jul 2013 05:52:35 -0700 (PDT)
Message-ID: <51D6C189.9020300@isi.edu>
Date: Fri, 05 Jul 2013 05:52:25 -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: Gert Doering <gert@space.net>
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> <20130705124651.GP2706@Space.Net>
In-Reply-To: <20130705124651.GP2706@Space.Net>
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: IPv6 Ops WG <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 12:53:07 -0000

On 7/5/2013 5:46 AM, Gert Doering wrote:
> Hi,
>
> On Thu, Jul 04, 2013 at 05:36:06PM -0700, Joe Touch wrote:
>> So let's please be very clear about what _this_ draft is saying - it is
>> NOT about making routers do something that routers *need* to do.
>
> If you can build a router for me that has a control plane which is
> completely unreachable from the outside, that would be sufficient
> (but that would likely be a MPLS P router, who wouldn't need to look
> at *any* IPv6 bits).
>
> Today's routers *need* to be able to protect themselves, and that can
> only be done by L4-aware rate limiting and ACLs.

Are you referring to forwarded traffic? If so, how is that "protecting 
the router"?

If you're talking about traffic addressed to the router itself, the 
entire chain has to be parsed anyway.

> So please stop repeating this "a router doesn't need any of this" - while
> this is fairly nice for a theoretical router, it doesn't work out there,
> and *this* is what should be interesting.  Not "ivory tower beauty".

That "ivory tower" is all we have documented requirements for. If you 
want to propose other requirements for routers, please do. But until 
then I do not support changes to standards to support non-existent 
requirements.

Joe