Handling IPR disclosures through draft reorganizations

Carsten Bormann <cabo@tzi.org> Mon, 19 June 2023 07:50 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: ipr-wg@ietfa.amsl.com
Delivered-To: ipr-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8445C151980; Mon, 19 Jun 2023 00:50:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 UXCFzVPKurWy; Mon, 19 Jun 2023 00:50:10 -0700 (PDT)
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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D183C15198E; Mon, 19 Jun 2023 00:50:10 -0700 (PDT)
Received: from [192.168.217.124] (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (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 4Ql2404jx2zDCfB; Mon, 19 Jun 2023 09:50:08 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 708853808.17972-0b32807ce5c3f4eb147d631d222d9270
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Mon, 19 Jun 2023 09:50:08 +0200
Subject: Handling IPR disclosures through draft reorganizations
Message-Id: <4B64CBB8-E002-4562-836E-0D6F63629837@tzi.org>
To: "ipr-wg@ietf.org" <ipr-wg@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipr-wg/Vr13La4lbl5Ck61ISlPC20V1Hmo>
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipr-wg/>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jun 2023 07:50:13 -0000

In July 2021, the CoRE WG split the draft-ietf-core-dynlink into two parts, draft-ietf-core-dynlink proper (about dynamic link bindings), and the separately progressed draft-ietf-core-conditional-attributes.
It has been slow going, but we now have mostly completed work on the latter, and would like to take up finishing the former.

One situation that is a bit weird after the split is that the original dynlink (that was including both what is now dynlink and a previous version of the conditional attributes specification) came out of an individual draft that has IPR disclosures on it:

https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-core-dynlink

IANAL, but it very much seems the disclosure might be related to the part of the specification that went into conditional-attributes.
So, after the split, these disclosures are now associated in our database with the wrong draft.

The then holder of the patent claims in the disclosures apparently has since decided to abandon those claims.  It does not seem easy to obtain a formal statement from them to that effect (the abandonment, however, appears to be easy to ascertain from the patent databases; IANAL though); after all, there no longer is any patent claim that needs to be disclosed.

So it seems I have two questions:

(1) How do we handle IPR disclosures that stick to the wrong draft after a reorganization like the split we did?

(2) How do we handle the absence of negative IPR disclosures?

Grüße, Carsten


(This could also be discussed in the more general context of updating IPR disclosures, e.g., <https://mailarchive.ietf.org/arch/msg/ipr-wg/IHlcUZmeyanJ1f_hXKqu9yvSy_8>.)