[core] IPR considerations ahead of expected WGLC for draft-ietf-core-dns-over-coap and draft-ietf-core-coap-dtls-alpn

Carsten Bormann <cabo@tzi.org> Mon, 16 December 2024 17:03 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 E88C3C14F605 for <core@ietfa.amsl.com>; Mon, 16 Dec 2024 09:03:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fN6fBKa8_7VZ for <core@ietfa.amsl.com>; Mon, 16 Dec 2024 09:03:01 -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 ietfa.amsl.com (Postfix) with ESMTPS id 8CFBDC14F6F4 for <core@ietf.org>; Mon, 16 Dec 2024 09:03:00 -0800 (PST)
Received: from [192.168.217.145] (p548dc3ec.dip0.t-ipconnect.de [84.141.195.236]) (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 4YBmTt5gSZzDCdW; Mon, 16 Dec 2024 18:02:58 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 756061378.280448-8c6f61585e3ab5a3d651e3a742a46f62
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Mon, 16 Dec 2024 18:02:58 +0100
Message-Id: <B5E7B16F-63E0-460F-B3D3-CE7F494F75F2@tzi.org>
To: core <core@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Message-ID-Hash: EDQTXDNM62JTTYLKKBE4OM6MUOH3KO27
X-Message-ID-Hash: EDQTXDNM62JTTYLKKBE4OM6MUOH3KO27
X-MailFrom: cabo@tzi.org
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 considerations ahead of expected WGLC for draft-ietf-core-dns-over-coap and draft-ietf-core-coap-dtls-alpn
List-Id: "Constrained RESTful Environments (CoRE) Working Group list" <core.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/-8jgb0jpEOpPjfJyfkIcVcpx5F0>
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>

The CoRE WG is getting close to a Working Group Last Call (WGLC) on
draft-ietf-core-dns-over-coap and draft-ietf-core-coap-dtls-alpn.

The IETF has received at least one "IPR disclosure" on
draft-ietf-core-dns-over-coap [1].

[1]: https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-core-dns-over-coap

The existence of such an IPR disclosure adds some considerations to
the upcoming WGLC.

Note that, in the IETF, patent claims are usually called "IPR"
("Intellectual Property Rights"), independent of whether there are any
actual rights or what "IPR" may apply beyond patent claims (for
instance, there are usually copright claims or similar droit
d'auteur/Urheberrecht on the text of a draft).

So, focusing on patent claims, before answering the WGLC, PLEASE
REVIEW the IETF procedures for dealing with such claims, as recorded
in BCP 79 (currently RFC 8179 [2]).

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

In general, in the IETF it is up to a WG to consider the impact of
patent claims on a technology and to decide whether a potentially
encumbered technology should be agreed on or whether alternative
technologies should be pursued.
(IESG members may be interested in a WG's record of making this
decision, but the rules notably do not put them in a position to
second-guess that decision.
Neither are the WG chairs, which however do need to gauge the WG
consensus on a particular decision.)

Please note that one weird aspect of the patent law that governs
several of the jurisdictions under which members of the WG operate is
that plausibly having knowledge about a patent claim can create
additional liability for those WG members (as individuals or for their
companies).
We therefore generally DO NOT discuss details of patent claims on WG
mailing lists.

However, WG members will need to factor in information about patent
claims when making the decision whether to be in favor of a document
advancing after a WG call.
They may need to obtain some of the necessary input from separate
sources, such as corporate lawyers, which may require additional time
-- hence this call for attention ahead of the WGLC.
Your lawyers may be interested in whether the patent claims actually
"read" on the specification under consideration (i.e., claim patent
rights on some aspect of it) and whether that specific claim is
sufficiently likely to be enforceable to be of interest for the
decision of the organization.

Note that this is a legal decision, and as such not subject to a logic
that engineers might understand.
There is therefore little reason to fall into armchair lawyering on
the mailing list, and, as I mentioned, that would likely be
detrimental for some WG members (having caused WG members to
unsubscribe and cease their activities in a WG before).
Also, you definitely do not want to appear to give legal advice.

So this is a call for attention: please obtain enough information
off-list before the WGLC so you can contribute to an informed decision
of the individuals in the WG about whether we should continue with
advancing the document(s).

Among other considerations, the sense of this contribution may hinge
on the details of Section VI of the IPR disclosure.
When evaluating this, please play attention to RFC 8179 [2],
particularly to its Section 5.5. Letter A item (c), and, more
generally, its Section 7.

Does any of this make sense?  I don’t think so.
But it is part of the legal environment that most of use operate in.

Grüße, Carsten