[core] Late review of draft-ietf-core-target-attr-02

Christian Amsüss <christian@amsuess.com> Wed, 01 March 2023 14: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 4C5ADC151AE2 for <core@ietfa.amsl.com>; Wed, 1 Mar 2023 06:07:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 gfIuMxk0DPew for <core@ietfa.amsl.com>; Wed, 1 Mar 2023 06:07:46 -0800 (PST)
Received: from smtp.akis.at (smtp.akis.at [IPv6:2a02:b18:500:a515::f455]) (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 C3CEBC14CF1D for <core@ietf.org>; Wed, 1 Mar 2023 06:07:43 -0800 (PST)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by smtp.akis.at (8.17.1/8.17.1) with ESMTPS id 321E7fl3000193 (version=TLSv1.2 cipher=ECDHE-ECDSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <core@ietf.org>; Wed, 1 Mar 2023 15:07:41 +0100 (CET) (envelope-from christian@amsuess.com)
X-Authentication-Warning: smtp.akis.at: Host 095129206250.cust.akis.net [95.129.206.250] claimed to be poseidon-mailhub.amsuess.com
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 588531C651 for <core@ietf.org>; Wed, 1 Mar 2023 15:07:40 +0100 (CET)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010::907]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 1297C1E804 for <core@ietf.org>; Wed, 1 Mar 2023 15:07:40 +0100 (CET)
Received: (nullmailer pid 13031 invoked by uid 1000); Wed, 01 Mar 2023 14:07:39 -0000
Date: Wed, 01 Mar 2023 15:07:39 +0100
From: Christian Amsüss <christian@amsuess.com>
To: core@ietf.org
Message-ID: <Y/9cK9xeGvfFjoS4@hephaistos.amsuess.com>
References: <167767262860.20493.18340427345389487454@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="rY8viDsnhZ88Wh5d"
Content-Disposition: inline
In-Reply-To: <167767262860.20493.18340427345389487454@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/QTktWfAXFciFUzYTk2f5WpABXxg>
Subject: [core] Late review of draft-ietf-core-target-attr-02
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 01 Mar 2023 14:07:50 -0000

Hi all,

sorry for being late to the party, here's a few notes:

* Should this contain all attributes used in published RFCs with 6690?
  If so, there's some in RFC9176 Resouce Directory, and the RD
  Parameters Registry should be updated with a note that all "A"-used
  entries should also get registered over here.

* Some documents introduce target attributes for specific resource types
  or rels; example [1].

  Should we account for that?

  If so, the `base`, `et` `d` and `ep` of RFC9176 Resource Directory
  would be limited to rt=core.rd-ep.

* Why is href reserved? Is there anyone else apart from the abandoned
  links-json who uses it that way?

  (To be clear: I'm in favor of having it there, if only b/c an internal
  representation of a link can then use it there, but it might warrant a
  footnote).

Other than that: Thanks, good document, let's go. (And I may want to
hook into the registry with CoRAL).

BR
c

[1]: https://www.ietf.org/archive/id/draft-ietf-core-oscore-edhoc-02.html#name-web-linking

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom