Re: [Coin] Minutes of the interim meeting and some words from thecochairs

Toerless Eckert <tte@cs.fau.de> Wed, 09 March 2022 20:57 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: coin@ietfa.amsl.com
Delivered-To: coin@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 284033A083F for <coin@ietfa.amsl.com>; Wed, 9 Mar 2022 12:57:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level:
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01] 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 YHNgPvCflXur for <coin@ietfa.amsl.com>; Wed, 9 Mar 2022 12:57:02 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE2993A0817 for <coin@irtf.org>; Wed, 9 Mar 2022 12:57:01 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 10980549F10; Wed, 9 Mar 2022 21:56:55 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id D064B4EA88C; Wed, 9 Mar 2022 21:56:54 +0100 (CET)
Date: Wed, 09 Mar 2022 21:56:54 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Colin Perkins <csp@csperkins.org>
Cc: Sharon Barkai <sharon.barkai=40getnexar.com@dmarc.ietf.org>, Eve Schooler <eve.m.schooler@intel.com>, coin <coin@irtf.org>, JEF <jefhe@foxmail.com>, coinrg-chairs <coinrg-chairs@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
Message-ID: <YikUlghyEuKt64Lg@faui48e.informatik.uni-erlangen.de>
References: <tencent_877D4D58E350C28439106A9CDF6FAAC4400A@qq.com> <SN6PR11MB31506AC8BBCDB6DF9395A196D70A9@SN6PR11MB3150.namprd11.prod.outlook.com> <EAC330CD-85E3-4764-9EE2-7247C20F7A53@getnexar.com> <Yijmpqp7hk8A/L5/@faui48e.informatik.uni-erlangen.de> <D69D8A05-DC9C-48B3-AAF5-8DD0CC1C737E@csperkins.org> <YikDDxTRtAjfbYIY@faui48e.informatik.uni-erlangen.de> <3E25CFF2-F6AE-4507-A71A-E0EBBD17883C@csperkins.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <3E25CFF2-F6AE-4507-A71A-E0EBBD17883C@csperkins.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/Zp0CL5aLzWpWBtNMWFjrbGyFJqI>
Subject: Re: [Coin] Minutes of the interim meeting and some words from thecochairs
X-BeenThere: coin@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "COIN: Computing in the Network" <coin.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/coin>, <mailto:coin-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/coin/>
List-Post: <mailto:coin@irtf.org>
List-Help: <mailto:coin-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/coin>, <mailto:coin-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Mar 2022 20:57:07 -0000

Colin,

I think everybody understands that process can be used positively to help or
negatively  to hinder specific activities. It is left up to every IETF participant 
to form their opinions as to whether or how this is happening in any instance.

I explicitly did not make any complaints about how the COIN chairs are running
the RG, i was just observing that the charter is quite inclusive and
maybe more so than what a single RG can grasp. But that is not a bad problem to
deal with, and i certainly understand that the COIN chairs are trying to find
some good interpretations about what is and what is not in scope (as Jeff did
i think speaking for all chairs in his summary).

Of course i am also yealous, because i think routing would also be a great topic
to deserve an RG with such an inclusive charter as "compute", but seemingly i am
in a minority there. Which is still baffling to me given how routing is really
one of the roots of this whole organization. 

I did make very specific observations about how i think programmability aspects
are closely tied to protocol/addressing design and how that makes it hard
and/or not very productive IMHO to try to find a strict separation between the
two. I welcome any technical thoughts you have about that technical contention.

Cheers
    Toerless

On Wed, Mar 09, 2022 at 08:13:54PM +0000, Colin Perkins wrote:
> Toerless,
> 
> The COINRG, like every other IRTF group, has a charter that defines what is, and is not, in scope. The charter was agreed with the IAB when the group was formed, and has been reviewed since. One of the roles of the research group chairs is to interpret that charter, and ensure the group remains on topic.
> 
> If you believe the chairs are interpreting that charter incorrectly, you may appeal to me, as IRTF Chair. If you disagree with my decisions, you may appeal to the IAB.
> 
> Colin
> 
> 
> 
> > On 9 Mar 2022, at 19:42, Toerless Eckert <tte@cs.fau.de> wrote:
> > 
> > On Wed, Mar 09, 2022 at 07:32:13PM +0000, Colin Perkins wrote:
> >>> Given Colins ask to the folks like Adrian focussing on semantic addressing to first go to coin, i think any such problems should maybe start using COIN at least as a dispatch, and either the discussion about a specific topic
> >> 
> >> No – that is not correct.
> >> 
> >> What I said to Adrian was that some parts of the semantic routing work fall into the scope of COINRG, some parts overlap with other IRTF groups, and some parts are outside the scope of IRTF or are better suited to other venues. 
> > 
> > Ah, thanks for reminding me. I forgot that you wanted to make any useful discusion
> > around the work we propose even more impossible by asking to go shopping around a variety
> > of existing and non-existing RGs for any individual detail that may not fit a
> > particular groups charter.
> > 
> >> COINRG is not a DISPATCH-style group. Work that does not relate to computation in the network research is out of scope and should be discussed elsewhere.
> >> If the work does not fit within the COINRG charter, it should not be raised here. 
> > 
> > The COIN charter is so broadly written that everything the COIN chairs want to claim
> > to be in charter they can, and likewise anything they don't, they can equally do.
> > 
> > Everything a network forwarding plane does is compute of how to process packets for example.
> > 
> > Cheers
> >    Toerless

-- 
---
tte@cs.fau.de