[core] IPR poll for draft-ietf-core-coap-pubsub

Esko Dijk <esko.dijk@iotconsultancy.nl> Thu, 25 June 2026 09:31 UTC

Return-Path: <esko.dijk@iotconsultancy.nl>
X-Original-To: core@mail2.ietf.org
Delivered-To: core@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 46A1510722A0E; Thu, 25 Jun 2026 02:31:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782379874; bh=+BBhdulj6KxpnHBMAS9ap+rATlj3dwy5AWeKV9g78rY=; h=Date:From:To:Subject; b=UpQlRV15ekWfr4IxP1DIRW2Bg1K8hfLf5z0jVxRY++tUJQ5HIsXbKCNquFmMjDUn6 UUUxSt2tLm1y425/wPEd9whYzV+qDWJNMITpYElxd4SdsfF4ILpU02YWNwhNRHMENt /mtxd3UjuvxMgFsndDwwbC7ysHgI87PnXlYwXyg4=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=iotconsultancy.nl
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 Zoq4blZqamWs; Thu, 25 Jun 2026 02:31:13 -0700 (PDT)
Received: from dane.soverin.net (dane.soverin.net [185.233.34.41]) (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 8A21E1072299A; Thu, 25 Jun 2026 02:31:04 -0700 (PDT)
Received: from smtp.soverin.net (unknown [10.10.4.99]) (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 dane.soverin.net (Postfix) with ESMTPS id 4gmD7j4Y5Fz27jF; Thu, 25 Jun 2026 09:30:57 +0000 (UTC)
Received: from smtp.soverin.net (smtp.soverin.net [10.10.4.99]) by soverin.net (Postfix) with ESMTPSA id 4gmD7j16v8z7Y; Thu, 25 Jun 2026 09:30:57 +0000 (UTC)
Authentication-Results: smtp.soverin.net; dkim=pass (2048-bit key; unprotected) header.d=iotconsultancy.nl header.i=@iotconsultancy.nl header.a=rsa-sha256 header.s=soverin1 header.b=oc7K/UQV; dkim-atps=neutral
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iotconsultancy.nl; s=soverin1; t=1782379857; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=q01+dW5jUXj/0a4I1yH7omwDt3P/r8Nu1sFUMEA4QWc=; b=oc7K/UQVmZqNaVrsC4O1ZKLDqiqJm5ZAwe/1OhSUZyE6zgih2S64esw5JLEBSQCJ8hLw7u 0pbnL9dx+KKatR3epVdgAd/5IqNXq1GelX2RvpwX6dOTUU/Y/CcvFlDWe8t0u6yNir5kYL qBmiJObMQzEuOnGOljwxqJFJDSN0LtXpClzGPiEWJYEZ0GTJEgmrotyWgbYaEEFle2+PJD 224S6Ou9UExPu6s4cBm5+AhYSeC9acAHqv4IHOw/OMSp9EOXWe/uEJs84VoDFHoYFRlRND kFnEDVDDYXrMLHkNFX5hEjK55xXU61x52pjIHBaYVZzMdDvrivicpj+hl8hQGg==
X-CM-Envelope: MS4xfHcWg+Xgct12+pr3IObnbVYhuRps5iqbtvJ1ocPoK4Bm2WD7HxhSFVmDrLKD0Rjy0MIdurGuZC/VAfNopOdgXb/w+IrGGxLSrPIqX/BsqCBLHAuvoFZE VIUhtSBmwYBL2Ty2eeODDdvhhUeZK1GxK3UslmTBi6EE3DIbEhuhGug9JCdGQSFTyWjeSV5x5y4YzPVjOWPF6MPwWSkgutS5h29IeRfCibbqrnlsudNPCBDx wXOgv+Q5dEPkO+SbV00cMEOGDvxV3FpO2hd3bzwHHukW7aP3jJb/K/2fUFTbNgJOzSQhTXJJBIzDLcuHZTE2afhpw8VEsfusgzKKvSafatrxxAHq0/ovVEJK MUIe+dBlkKTetqh+9EwhJnBtq8rBXN4IbZICU7rW3fcHivT9b/k=
X-Soverin-Id: 019efe1e-4468-7e8c-9497-cf544485a3cd
Content-Type: multipart/alternative; boundary="------------00s1rj0uE0dml0HKQ90mkAl5"
Message-ID: <4e3e7e50-5494-466d-b207-b07f3a98c120@iotconsultancy.nl>
Date: Thu, 25 Jun 2026 11:30:56 +0200
MIME-Version: 1.0
Content-Language: en-US
From: Esko Dijk <esko.dijk@iotconsultancy.nl>
Organization: IoTconsultancy.nl
To: core <core@ietf.org>, draft-ietf-core-coap-pubsub@ietf.org, core-chairs@ietf.org
X-Spampanel-Class: ham
Message-ID-Hash: HJMAPBZ4R4BBBQE6A3XVKYRSDHDEOTMA
X-Message-ID-Hash: HJMAPBZ4R4BBBQE6A3XVKYRSDHDEOTMA
X-MailFrom: esko.dijk@iotconsultancy.nl
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-core.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [core] IPR poll for draft-ietf-core-coap-pubsub
List-Id: "Constrained RESTful Environments (CoRE) Working Group list" <core.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/XRqcUYE0wvL0dYi17Seuw6s8OFw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Owner: <mailto:core-owner@ietf.org>
List-Post: <mailto:core@ietf.org>
List-Subscribe: <mailto:core-join@ietf.org>
List-Unsubscribe: <mailto:core-leave@ietf.org>

(Note: this message is reusing text from an earlier poll from Marco - 
I'll take the liberty to reuse, thanks. I might even have a license from 
IETF Trust to do so :)  )
Dear all,

I am sending this message as an IPR poll for the document 
draft-ietf-core-coap-pubsub of which I am the Shepherd.

https://datatracker.ietf.org/doc/html/draft-ietf-core-coap-pubsub

As you all know, there are certain requirements about declaring patent 
claims (called "IPR" in IETF lingo) that you are personally aware of and 
that apply to a contribution (another IETF term) you make to the IETF.

These requirements do not change with IESG submission of a document, but 
that milestone provides a convenient check point, particularly for all 
authors and contributors listed, to indicate that such "IPR 
declarations" have been made as required, or possibly an assertion that 
you are not personally aware of patent claims that would "read" on that 
document. Note that this is about what you personally know, not about 
needing to consult your employer's corporate lawyers to state a legal 
opinion.

So: If you are **personally aware of any patent claims** that might 
apply to systems that implement this draft, please review BCP 78 [1] and 
BCP 79 [2] and make any appropriate IPR declaration now. If you are not 
sure whether you need to make a declaration or not, please talk to the 
chairs (core-chairs@ietf.org)

**If you are an author or listed contributor** and do not know about a 
pertinent patent claim (granted or in processing), please simply do a 
wide reply to this message and state:

"I am not personally aware of any patent claims that would read on this 
specification."

(Creating the Shepherd write-up is blocking on the authors' responses.)

Best regards,
Esko Dijk

[1] https://www.rfc-editor.org/rfc/rfc5378.html

[2] https://www.rfc-editor.org/rfc/rfc8179.html