Re: [core] CoRE rechartering: proposed text

Carsten Bormann <cabo@tzi.org> Sun, 17 October 2021 05:09 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 236153A0860 for <core@ietfa.amsl.com>; Sat, 16 Oct 2021 22:09:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 5ky3YNPGDDsN for <core@ietfa.amsl.com>; Sat, 16 Oct 2021 22:09:36 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E08B3A085F for <core@ietf.org>; Sat, 16 Oct 2021 22:09:34 -0700 (PDT)
Received: from smtpclient.apple (p5089a8ac.dip0.t-ipconnect.de [80.137.168.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4HX7NC0FqDz2xHt; Sun, 17 Oct 2021 07:09:31 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <13516.1634429685@localhost>
Date: Sun, 17 Oct 2021 07:09:30 +0200
Cc: "core@ietf.org WG (core@ietf.org)" <core@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <276C40A2-B053-43B4-A173-7F76EDA318B1@tzi.org>
References: <b91fb1fb-6d54-5594-2424-e1ca37d501f5@ri.se> <fe11a970-4750-1b58-eaed-1863fa0dfe48@ri.se> <AM8P190MB09799B48F4E50F7515BA60B8FDA09@AM8P190MB0979.EURP190.PROD.OUTLOOK.COM> <290101ab-0022-0ed7-424e-dc5d6c73b401@ri.se> <24137.1634425047@localhost> <17AE33BD-E8EA-4114-9D87-EB5A25A50D47@tzi.org> <13516.1634429685@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/8t3GQGVjb33XAhPcp_FM8GpBv8c>
Subject: Re: [core] CoRE rechartering: proposed text
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Oct 2021 05:09:42 -0000

On 17. Oct 2021, at 02:14, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Carsten Bormann <cabo@tzi.org> wrote:
>> I commented on the individual proposals in the GitHub repo, but I’m
>> really surprised at how bad most of them would be for getting any
>> useful work done.
> 
> There is a lot of useful work in CORE's charter which is not getting done.

Making it harder to do that work is not going to help with this.

I understand that the progress of CORECONF is frustrating.
But that is no reason to shut down other work that is proceeding at a reasonable pace.
It’s not like the OSCORE people will suddenly put time into the latest YANG problem if they can’t work on group communication any more.

>> Whether some work should be in a specific WG does not depend on some
>> abstract academic concept of how the world is structured, but on having
>> the people assembled who can do good work.  E.g., I’m having a hard
>> time believing that any useful work on using CoAP with DTLS would
>> happen in the TLS WG;
> 
> I probably have even more wounds on this than you.
> But, we won't get it done here.  Let's not say we are going to try.

A charter is meant to provide a frame for the WG to work in.
If nobody wants to move this forward, it won’t happen if we move it to a WG that isn’t interested.
(I don’t have any particular wounds with the TLS WG because I wouldn’t even try to do work there that is related to CoRE.
We did manage to pull off a DICE WG in 2013 to get RFC 7925; but that was a non-trivial effort; not sure we have anything at that level on our plates right now.)

>> the people there have quite different priorities.
>> SenML may not be useful to you, but it is out there in actual use and
>> we have done and are doing occasional maintenance (RFC 8798,
> 
> It's because I think it's useful that I think it deserves its own place.

That wouldn’t make a lot of sense, because the maintenance needed for SenML is really limited.
(The current wording about “completing” SenML may give the wrong impression.)

> When a WG has so many focuses it has no focuses.  I point to OPSAWG.

I think we have a laser-sharp focus compared to OPSAWG…
(I also think we have a relatively well-working WG going on, in particular since I stopped being involved in its management :-)

> I think that we all agree that the existing charter would never get approved today.
> That's why rechartering is scary.

If that is the diagnostic, we probably shouldn’t spend time trying to do it.

Grüße, Carsten