Re: [Coin] Cancelling the COINRG meeting at IETF113

Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk> Sun, 13 March 2022 09:51 UTC

Return-Path: <Jon.Crowcroft@cl.cam.ac.uk>
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 1BD153A158A; Sun, 13 Mar 2022 01:51:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cl.cam.ac.uk
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 Hn6XDCG9NHn0; Sun, 13 Mar 2022 01:51:20 -0800 (PST)
Received: from mta1.cl.cam.ac.uk (mta1.cl.cam.ac.uk [IPv6:2a05:b400:110::25:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44A3A3A1587; Sun, 13 Mar 2022 01:51:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cl.cam.ac.uk; s=mta3; h=Message-Id:Date:Content-Transfer-Encoding: Content-ID:Content-Type:MIME-Version:References:In-reply-to:Subject:cc:To: From:Sender:Reply-To:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=PHJFOy17+n8I2iNly+e5/1E86JodzLP+EfY5mxPHI7Q=; t=1647165079; x=1648029079; b=YgO1bQtVRXXhMqj2yKwNhdMjFxiNQW2JwjmyO+XZbIR2RaVFRpJhKrsGAvRTIy1kO/G+In6NUMQ r0eLKgS6gaJQgbb4P/s0lmLz6C1GaT5LucwfkONYTt6v2l2X04pVGFjYl42I5ZVeCGRbXzY+AaRss qCu/hr/BZ46UROMBCIEOifS2mXHwJNoTdC7J+LKSlcZKmZCfVTUhqa85Gp6MbBb2WH13AWdjPWxwX yHLC2jnqtNV1hO+QtK1RsSVODIk/moklwO2dCsfRmk64CACcXV9+oMJE52iF9e9Dg4VzyaPLOPIdh GCTgtpyso3vpbdtHB+ufH07Yuo9fGp+7FXjg==;
Received: from slogin-new.cl.cam.ac.uk ([2a05:b400:110::22:98] helo=svr-ssh-0.cl.cam.ac.uk) (dnseec=no) by mta1.cl.cam.ac.uk:587 [2a05:b400:110::25:1] with esmtp (Exim 4.94) id 1nTKsT-0005YX-Jb (envelope-from <Jon.Crowcroft@cl.cam.ac.uk>); Sun, 13 Mar 2022 09:51:05 +0000
From: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
To: Toerless Eckert <tte@cs.fau.de>
cc: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>, "Schooler, Eve M" <eve.m.schooler@intel.com>, Marie-Jose Montpetit <marie@mjmontpetit.com>, coinrg-chairs <coinrg-chairs@ietf.org>, Dirk Trossen <dirk.trossen=40huawei.com@dmarc.ietf.org>, coin <coin@irtf.org>
In-reply-to: <YivQcRu8K+/YP3oC@faui48e.informatik.uni-erlangen.de>
References: <CAPjWiCStyJidZnVC0f8VMy1hgYmmrt-y82jEcbeAJ4ZpMe8y1w@mail.gmail.com> <0df941ff8fcc405fb50a5eecf6823df6@huawei.com> <DM6PR11MB314820FF0F07FAE8653F64FAD70C9@DM6PR11MB3148.namprd11.prod.outlook.com> <YiuLm+zv+cn3nCle@faui48e.informatik.uni-erlangen.de> <E1nSn8T-0003xv-1g@mta1.cl.cam.ac.uk> <YivQcRu8K+/YP3oC@faui48e.informatik.uni-erlangen.de>
Comments: In-reply-to Toerless Eckert <tte@cs.fau.de> message dated "Fri, 11 Mar 2022 23:42:57 +0100."
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <761690.1647165065.1@svr-ssh-0.cl.cam.ac.uk>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 13 Mar 2022 09:51:05 +0000
Message-Id: <E1nTKsT-0005YX-Jb@mta1.cl.cam.ac.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/vAT56i49vlQcTrlrIuPShGGKCJQ>
Subject: Re: [Coin] Cancelling the COINRG meeting at IETF113
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: Sun, 13 Mar 2022 09:51:25 -0000

> On Fri, Mar 11, 2022 at 09:49:21PM +0000, Jon Crowcroft wrote:
> > sorry, but you are wrong.

> About what ?

if several people perceive divisiveness in a debate, then it is there, by definition.
if you don't perceive it, that's fine, but that doesn't make it not so.

talking about the tone or a dialog is not name calling. it is an observation.

perhaps we need an in-network moderator for this group - 

now there's an "AI in a switch" challenge, 
especially if you consider the ethical challenges of such a technology :-)
(not least privacy and key sharing with third parties)....


going back on topic, for me, the scoping problem with the semantic routing&addressing work
is that it was originated in response to soling limitations of routing and addressing, but is
clearly not rooted in what one would design for identifying and path finding to and between
distributed applications running in switches and routers as well as end systems, beyond
applications that were only concerned with the business of routing....

identifiers and locators for distributed computational objects in general would have a whole
slew of other attrbutes and characterists (I would guess) that would deal with the
requirements (e.g. from other coin type use cases than routing) of those applications...

i think t his is a post-layering type challenge - of course, one can hack up a network layer
identifier system to name/find computational stuff (especially with big ipv6 identiefiers) -
or one can do this with application layer ids (URIs etc), or one could try to design something
fit for purpose from scratch (just for example thinking about security needs of such systems,
seems different, in general, than those for the routing infrastructure)....

now t hat'd be a fun project!



> 
> > > On Fri, Mar 11, 2022 at 08:35:16AM +0000, Schooler, Eve M wrote:
> > > > As for transparency…If you are a regular reader of this list, 
> then it
> > > is painfully obvious that there has been quite a bit of divisiveness
> > > happening both on and off the list. As chairs, given the state of the
> > > agenda and the tone of the dialog, we felt the need to take a step 
> back
> > > from the vitriol and simply take a deep breath to regroup.
> > >
> > > I am sorry to hear that you feel that way. But you can imagine that
> > > anybody who might feel addressed by your "vitriol" would not be happy
> > > about that
> > > name calling either. I for once don't that anybody did spill vitriol, 
> and
> > > especially
> > > if you think i did, then i would very much appreciate if you would 
> call
> > > such
> > > a perception out, for example in private mail, before making it lead 
> to
> > > such
> > > choices for the RG.
> > >
> > > I am also not sure where there would be divisiveness in the community
> > > wrt. COIN work.
> > > As i said, with a charter as openly written, there is a lot of 
> freedom to
> > > put
> > > work items in or out of scope, and the chairs did attempt to define a 
> line
> > > what was in and out. In response, i was suggesting a technical
> > > presentation
> > > that was intended to describe the intricate dependencies between what 
> was
> > > declared to be in and what was maybe? declared out (not to dissimilar 
> to
> > > what IMHO
> > > the use-case draft has), but with use-case examples focussed on what i
> > > think
> > > we would call semantic addressing. To help continue that
> > > technical/research discussion.
> > >
> > > In any case, it would be nice to understand if/when you would make a
> > > decision
> > > whether to accept my proposal for a presentation based on the outline 
> i
> > > sent.
> > >
> > > Cheers
> > >     Toerless
> > >
> > > > We certainly have valued the continued involvement of the COIN
> > > community, which has made many of the discussions vibrant and 
> rewarding.
> > > >
> > > > Best regards,
> > > > Eve
> > > >
> > > > From: Coin <coin-bounces@irtf.org> On Behalf Of Dirk Trossen
> > > > Sent: Thursday, March 10, 2022 10:30 PM
> > > > To: Marie-Jose Montpetit <marie@mjmontpetit.com>; coin 
> <coin@irtf.org>
> > > > Cc: coinrg-chairs <coinrg-chairs@ietf.org>
> > > > Subject: Re: [Coin] Cancelling the COINRG meeting at IETF113
> > > >
> > > > Hi J/E/M, all,
> > > >
> > > > Now that’s a surprise, not just in content but also in style since
> > > the RG community lacks the transparency of this decision.
> > > >
> > > > As a COIN RG member myself for now more than 3 years (spanning two
> > > organizations), I had looked forward to discussing at least three
> > > activities in which I am involved in, namely the (i) use case advances
> > > (trying to formulate and categorize the pertinent research questions 
> in a
> > > number of COIN areas), (ii) the applicability of SDN for routing (i.e.
> > > the use of DP programmability for realizing novel routing solutions,
> > > which according to the chairs is in scope of COIN), and (iii) a
> > > discussion on how COIN could help improve on DLT realizations; all
> > > activities resulting from research on topics I see as relevant to and
> > > within COIN.
> > > >
> > > > So this gives already three agenda items from where I’m coming 
> from
> > > (depending on willingness for time allocation, between about 45 to 
> 60mins
> > > on an agenda in my mind) but yet we are told at ‘we cannot put a 
> good
> > > agenda together’. Is there nothing beyond these items, really, 
> and/or
> > > is this a judgement of those items in quality (I would expect good
> > > discussions on them but maybe it is just me)?
> > > >
> > > > So I’m disappointed but also shocked by this style of simply
> > > cancelling the RG meeting with that (too) thin ‘we cannot put a good
> > > agenda together for IETF113’ explanation. I cannot and do not see 
> the
> > > reasoning behind it albeit I may speculate but I am not a friend of 
> those
> > > second guesses.
> > > >
> > > > Hence, I would ask the community here: what discussions were we 
> looking
> > > forward to have? Are those good enough to discuss regardless of the RG
> > > meeting being cancelled? If there is no RG meeting for whatever 
> reason,
> > > maybe we can simply come together among those interested in those
> > > discussions and have them regardless, such as in a side meeting of the
> > > ‘COIN community’ (not the RG)?
> > > >
> > > > From my side, I would be highly interested in that since I have 
> valued
> > > the COIN discussions over the past years and don’t want to let go of
> > > this for reasons that are just not well enough explained below.
> > > >
> > > > Best,
> > > >
> > > > Dirk
> > > >
> > > > From: Coin [mailto:coin-bounces@irtf.org] On Behalf Of Marie-Jose
> > > Montpetit
> > > > Sent: 11 March 2022 00:45
> > > > To: coin <coin@irtf.org<mailto:coin@irtf.org>>
> > > > Cc: coinrg-chairs
> > > <coinrg-chairs@ietf.org<mailto:coinrg-chairs@ietf.org>>
> > > > Subject: [Coin] Cancelling the COINRG meeting at IETF113
> > > >
> > > > Dear all:
> > > >
> > > > Because of many converging issues, delays and (non) availability of
> > > invited researchers and papers we cannot put a good agenda together 
> for
> > > IETF113.  Hence we are cancelling the meeting.
> > > >
> > > > We plan to re-group, consult the community and plan for 114.
> > > >
> > > > Discussions on the use cases and other important COIN topics will 
> have
> > > to continue or be initiated on the list for now. Of course as the
> > > co-author of a draft that was going to be presented I am disappointed.
> > > >
> > > > The co-chairs are in full agreement that this is the right decision 
> at
> > > this point and the IRTF leadership has been kept in the loop.
> > > >
> > > > J/E/M
> > > >
> 
> --
> Coin mailing list
> Coin@irtf.org
> https://www.irtf.org/mailman/listinfo/coin
>