[core] IPR confusion between dynlink and conditional-attributes

Christian Amsüss <christian@amsuess.com> Mon, 26 July 2021 09:07 UTC

Return-Path: <christian@amsuess.com>
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 4DFFD3A21EF; Mon, 26 Jul 2021 02:07:31 -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 QrbNSK1ucNsw; Mon, 26 Jul 2021 02:07:28 -0700 (PDT)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [5.9.147.112]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56E613A21EA; Mon, 26 Jul 2021 02:07:24 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by prometheus.amsuess.com (Postfix) with ESMTPS id B7E65401B5; Mon, 26 Jul 2021 11:07:21 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (poseidon-mailbox.amsuess.com [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bf]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 6DB83D0; Mon, 26 Jul 2021 11:07:20 +0200 (CEST)
Received: from hephaistos.amsuess.com (77.119.209.226.wireless.dyn.drei.com [77.119.209.226]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 041BB46; Mon, 26 Jul 2021 11:07:19 +0200 (CEST)
Received: (nullmailer pid 2919482 invoked by uid 1000); Mon, 26 Jul 2021 09:07:19 -0000
Date: Mon, 26 Jul 2021 11:07:19 +0200
From: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
To: draft-ietf-core-dynlink@ietf.org, draft-ietf-core-dynlink.chairs@ietf.org
Cc: core@ietf.org
Message-ID: <YP57R1M1A81dKsJH@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="GJjHwlEUH2Vr1C1e"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/pEE41DmlPrOyw8U33LKuILU1kNw>
Subject: [core] IPR confusion between dynlink and conditional-attributes
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: Mon, 26 Jul 2021 09:07:31 -0000

Hello conditional-attributes and dynlink authors and chairs,

the data tracker shows 3 IPR items on dynlink and none for
conditional-attriutes. Judging from the statement titles on the former
("to govern measurement evaluation when in Power-Save-Mode"), I think
it'd stand to reason to reassess their applicability, and probably move
the statements over to conditional-attributes where they probably
belong.

BR
c

-- 
Build a man a fire, and he'll be warm for a day. Set a man on fire, and
he'll be warm for the rest of his life.
  -- Terry Pratchett (attributed)