Re: [Int-area] FYI/Feedback for draft-bryant-arch-fwd-layer-ps-00

Toerless Eckert <tte@cs.fau.de> Tue, 24 March 2020 22:35 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C69E03A0538; Tue, 24 Mar 2020 15:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level:
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 F2or5kgG8EYS; Tue, 24 Mar 2020 15:35:38 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E726D3A0496; Tue, 24 Mar 2020 15:35:37 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id AF120548048; Tue, 24 Mar 2020 23:35:32 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id A6298440040; Tue, 24 Mar 2020 23:35:32 +0100 (CET)
Date: Tue, 24 Mar 2020 23:35:32 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Joseph Touch <touch@strayalpha.com>
Cc: Ted Lemon <mellon@fugue.com>, "int-area@ietf.org" <int-area@ietf.org>, "draft-bryant-arch-fwd-layer-ps@ietf.org" <draft-bryant-arch-fwd-layer-ps@ietf.org>
Message-ID: <20200324223532.GD49016@faui48f.informatik.uni-erlangen.de>
References: <20200324020956.GA28168@faui48f.informatik.uni-erlangen.de> <57A23F79-2686-4A4D-A175-7D33F3D8CCAB@cisco.com> <20200324175226.GB49016@faui48f.informatik.uni-erlangen.de> <78D0C85B-0D3D-4CFA-8CEB-8B8257CAAA13@fugue.com> <3FD5C322-68F9-4B5C-B12E-28DB18910AE0@strayalpha.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3FD5C322-68F9-4B5C-B12E-28DB18910AE0@strayalpha.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/v37W1RYkx9OkFkhcEyGr5_T4Xp4>
Subject: Re: [Int-area] FYI/Feedback for draft-bryant-arch-fwd-layer-ps-00
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Mar 2020 22:35:40 -0000

On Tue, Mar 24, 2020 at 11:06:53AM -0700, Joseph Touch wrote:
> 
> 
> > On Mar 24, 2020, at 10:56 AM, Ted Lemon <mellon@fugue.com> wrote:
> > 
> > On Mar 24, 2020, at 1:52 PM, Toerless Eckert <tte@cs.fau.de <mailto:tte@cs.fau.de>> wrote:
> >> But without a longer term architectural track doing work like this
> >> in parallel to current WGs, it will be difficult for the IETF to really drive
> >> innovation at the network / forwarding layer longer term.
> > 
> > Is this something we are even competent to do?
> 
> By person, sure.
> 
> By group, i.e., does INTAREA or any other area, or even (or especially) the IAB, IMO - NO.
> 
> Papers like this are great ways to start beer chats or kickstart panel discussions but don???t do much IMO to move the needle forward. What matter are targeted answers, and those aren???t often the result of group-think (see ???the Innovator???s Dilemma???*)

Agreed. But at least to me it looks quite helpfull to even start
attempting to write down the problem statemens, because they
are not necessarily trivial.

Btw: How did you folks manage to get this thread on int-area.
I specifiy had a "Reply-To: architecture-discuss@ietf.org" into
my first email, to avoid this segmentation of discussion along
IETF area  boundaries ;-))

Cheers
    Toerless