Re: [core] CoRE rechartering: proposed text

Carsten Bormann <cabo@tzi.org> Sat, 16 October 2021 23:16 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 14EF03A0C6F for <core@ietfa.amsl.com>; Sat, 16 Oct 2021 16:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 2K7n64FkPwsN for <core@ietfa.amsl.com>; Sat, 16 Oct 2021 16:16:12 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::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 ABB903A0C7C for <core@ietf.org>; Sat, 16 Oct 2021 16:16:11 -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 4HWzXP4PvXz2xJB; Sun, 17 Oct 2021 01:16:05 +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: <24137.1634425047@localhost>
Date: Sun, 17 Oct 2021 01:16:05 +0200
Cc: "core@ietf.org WG (core@ietf.org)" <core@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <17AE33BD-E8EA-4114-9D87-EB5A25A50D47@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>
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/hlSkpCNItjm9MRw9vANX0lEuOPw>
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: Sat, 16 Oct 2021 23:16:18 -0000

Hi Michael,

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.
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; 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, draft-ietf-core-senml-data-ct); no other WG is going to do that properly (even though, yes, it may be weird to have a WG that does both a protocol and a couple of data formats that go with that protocol; er, maybe not so unusual).

Grüße, Carsten