[Iotops] Re: WG Last Call: draft-ietf-iotops-7228bis-03 (Ends 2026-01-08)

Carsten Bormann <cabo@tzi.org> Tue, 10 February 2026 10:30 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: iotops@mail2.ietf.org
Delivered-To: iotops@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 028DCB49CF5D; Tue, 10 Feb 2026 02:30:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -3.989
X-Spam-Level:
X-Spam-Status: No, score=-3.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=tzi.org
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ii0jiegTzqb7; Tue, 10 Feb 2026 02:30:05 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id B2FE6B49CF58; Tue, 10 Feb 2026 02:30:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tzi.org; s=2019; t=1770719404; bh=th8YxOIQHJlVCqEqZQTbzDytd5bAjTSRzgpPbMDmUfM=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=bJ4BoeNOu5x4b2Bgnrt3b/hTJNrM1dA7Gg9eO01wzK9Ft76va0vCuNZ+dWtNNzf70 cit4TR68VyVK35nhi2bR6jtN5hgTT3S+ZF26LTZlbck1WrMbCjWDlSGavypwBT4QW9 AvsFTWjfPZdAl2AS/JEWtqsMqKbCGfbprIFcPU8uDo2GWrTqYIGiHmG/+K0pU1Y3tA zxwyxBU4YCqxL1JXwH9jOePn4CLlPAQIRa9f26yUiVefZpfupJNOIJvpInerS3cPrp lVxoFuMwA1PXqyjD3yt3vV0/3yU0avmDgovq9tj5Oq9i4Kykqxobk1BiNFzb3OzJ0i sIm3r63PLVVWA==
Received: from [192.168.217.132] (p548dcea3.dip0.t-ipconnect.de [84.141.206.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4f9HrC5W6LzDCbV; Tue, 10 Feb 2026 11:30:03 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <769ab80c-e75d-20fa-8559-b9c16c02cdc6@ietf.contact>
Date: Tue, 10 Feb 2026 11:30:03 +0100
X-Mao-Original-Outgoing-Id: 792412202.858026-2cc3008df6771349bc46bd3cef0c9886
Content-Transfer-Encoding: quoted-printable
Message-Id: <018F44EF-4AF9-4FEF-A982-3DB1F5EC3070@tzi.org>
References: <176547719355.1533923.9136328262647671710@dt-datatracker-5bd94c585b-wk4l4> <769ab80c-e75d-20fa-8559-b9c16c02cdc6@ietf.contact>
To: Henk Birkholz <henk.birkholz@ietf.contact>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
X-FromAuthMilter: ok
Message-ID-Hash: K6KG6DNYFT4RWTP7MEYKVUFYGOMKU46N
X-Message-ID-Hash: K6KG6DNYFT4RWTP7MEYKVUFYGOMKU46N
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-iotops-7228bis@ietf.org, iotops-chairs@ietf.org, iotops@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Iotops] Re: WG Last Call: draft-ietf-iotops-7228bis-03 (Ends 2026-01-08)
List-Id: IOT Operations <iotops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/SvV7U3py397ikHo0WiF_M3Pvv7I>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotops>
List-Help: <mailto:iotops-request@ietf.org?subject=help>
List-Owner: <mailto:iotops-owner@ietf.org>
List-Post: <mailto:iotops@ietf.org>
List-Subscribe: <mailto:iotops-join@ietf.org>
List-Unsubscribe: <mailto:iotops-leave@ietf.org>

On 2026-02-10, at 08:26, Henk Birkholz <henk.birkholz@ietf.contact> wrote:
> 
> There was a useful set of feedback during this WGLC. 

There was lots of feedback, and I need to apologize that this draft temporarily went to the back burner.
We do plan to have changes ready and discussed in a new revision before the IETF125 deadline.
Expect a set of PRs RSN...

Grüße, Carsten