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

Toerless Eckert <tte@cs.fau.de> Wed, 09 March 2022 19:42 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 8DB633A0C41 for <coin@ietfa.amsl.com>; Wed, 9 Mar 2022 11:42:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.662
X-Spam-Level:
X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 4tthX-CUaVHZ for <coin@ietfa.amsl.com>; Wed, 9 Mar 2022 11:42:16 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.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 D3D983A0C4C for <coin@irtf.org>; Wed, 9 Mar 2022 11:42:13 -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 C6BF0549AE6; Wed, 9 Mar 2022 20:42:07 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 96C174EA88B; Wed, 9 Mar 2022 20:42:07 +0100 (CET)
Date: Wed, 09 Mar 2022 20:42:07 +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: <YikDDxTRtAjfbYIY@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>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <D69D8A05-DC9C-48B3-AAF5-8DD0CC1C737E@csperkins.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/MmztvLuxRj0Far7Ht6gRSFe9BvQ>
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 19:42:19 -0000

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