[Rats] Re: [IANA #1441242] expert review for draft-ietf-rats-eat-measured-component (core-parameters)

Esko Dijk <esko.dijk@iotconsultancy.nl> Wed, 14 January 2026 11:28 UTC

Return-Path: <esko.dijk@iotconsultancy.nl>
X-Original-To: rats@mail2.ietf.org
Delivered-To: rats@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 71453A783EC2 for <rats@mail2.ietf.org>; Wed, 14 Jan 2026 03:28:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.224
X-Spam-Level:
X-Spam-Status: No, score=-2.224 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_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URG_BIZ=0.573] 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 B7tpFHKcxjof for <rats@mail2.ietf.org>; Wed, 14 Jan 2026 03:28:44 -0800 (PST)
Received: from dane.soverin.net (dane.soverin.net [185.233.34.30]) (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 D4001A783EBB for <rats@ietf.org>; Wed, 14 Jan 2026 03:28:44 -0800 (PST)
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 4drkQG0DwczG2; Wed, 14 Jan 2026 11:28:38 +0000 (UTC)
Received: from smtp.soverin.net (smtp.soverin.net [10.10.4.99]) by soverin.net (Postfix) with ESMTPSA id 4drkQF4mVcz4kB; Wed, 14 Jan 2026 11:28:37 +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=ng7cwGAC; dkim-atps=neutral
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iotconsultancy.nl; s=soverin1; t=1768390117; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=V4sMJW1G9B5g0jRr3mHo1niF8B1s2gwwdY1YCCKQY3o=; b=ng7cwGAC4Ilo+FjoH+F3vkUReAAt57x93jkOiINfmW3UBol+8kLD6iuVa/RDlj/I/Pos6/ cc8WcJRyi346wutpGv6rG57fZ1QPob2t+r1uE2xCCPjFCtpvHoJtfehu5Jcwc1Bs3UZUk9 7cqJiQpru2BijD4/f+Bfg7wI5BTTX6racfWVgBdeL36f9iKYg31Ov9D/Sl8Podknr9Cp5N bQ+aEQifrEgT+cceNTfFaIsLMJVFnAoukZ6B5xrKQIJhVFqThskZ+W/BB/XUaCij4L64Cv HMrC+z0BfOeE4CFbrx+VQA8JKIxBLduWdOKOeObh53mGIyGN2UYmASHRvzjZZA==
X-CM-Envelope: MS4xfO/K27KXHHjEI5H/7F7gMXIPtqHxTd4reWNPdETDT92c0IMxBG+hjx7yilgk5ZN1L+WslOAGcf533sEtTvT0gEs6APE0isZ/3UqMeJBFcG0Bxf/vxaCd OiSlS6D8KsEaWbkOiHRdIttaMfZrkDu6wHvtKlsSo7F/LhH0Hr0d33feGnawofvbVUh1YQsuMfN7z/7+/XFA2g++JwnQUwyjk9/F7YE1qGHPbkzbQOyXYxs/ P1geN2EDcVosC009rt76Pg==
X-Soverin-Id: 019bbc43-c688-7c95-9840-dcaa684fa88d
Content-Type: multipart/alternative; boundary="------------riZkgLSV9zcIjHcyS50OAC5n"
Message-ID: <64c6bd5b-3142-400f-a912-a906bf015087@iotconsultancy.nl>
Date: Wed, 14 Jan 2026 12:28:37 +0100
MIME-Version: 1.0
To: drafts-expert-review-comment@iana.org
References: <RT-Ticket-1441242@icann.org> <rt-5.0.3-656136-1768262296-1564.1441242-9-0@icann.org> <rt-5.0.3-84234-1768332377-189.1441242-9-0@icann.org>
Content-Language: en-US
From: Esko Dijk <esko.dijk@iotconsultancy.nl>
Organization: IoTconsultancy.nl
In-Reply-To: <rt-5.0.3-84234-1768332377-189.1441242-9-0@icann.org>
X-Spampanel-Class: ham
Message-ID-Hash: QXSHYFJZ4LAZG2MQLRIRZE6RZM3N7Q44
X-Message-ID-Hash: QXSHYFJZ4LAZG2MQLRIRZE6RZM3N7Q44
X-MailFrom: esko.dijk@iotconsultancy.nl
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rats.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rats@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Rats] Re: [IANA #1441242] expert review for draft-ietf-rats-eat-measured-component (core-parameters)
List-Id: Remote ATtestation procedureS <rats.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/GZybcnSHd7e9XlA8DcJ3Twq3WXE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Owner: <mailto:rats-owner@ietf.org>
List-Post: <mailto:rats@ietf.org>
List-Subscribe: <mailto:rats-join@ietf.org>
List-Unsubscribe: <mailto:rats-leave@ietf.org>

Hi David,

This registration is approved, provided that the related media type 
registrations are approved. Numbers in the range 295-309 are suggested.

Note that the media type registrations table in Section 7.1 can be 
confusing in current form, since it has a column "Name" (first column).
This seems to be a locally used name within the scope of the draft, not 
related to the Type name or Subtype name of the actual template or the 
"Name" that would appear finally in the Media Types registry.

So these local names will not show in the end in the Media Types 
registry column 1 , which uses a "Name" column that contains only the 
Subtype name, but it doesn't allow for any other string or any aliasing. 
Or at least I haven't found any item so far the deviates from the 
Subtype name.
Since the table 4 re-uses the exact same column names from the Media 
Types registry, this becomes extra confusing!

So it may appear to a read like a different "Name" is desired to be 
registered other than the Subtype name, for the Media Types registry;  
which I think is impossible.

If you're all confused by the above explanation, so am I - so this is an 
urgent request to do either one of these things to resolve the 
inconsistency:

1) Use the full registered "Subtype name" in the fields in the "Name" 
column cells in Table 4.   (Then the table would match what we see in 
the Media Types registry.)
2) Remove column "Name" in Table 4 entirely.
3) Rename the column header in Table 4 from "Name" to "Local identifier" 
or so.
4) Do as 3) and also insert a new column between current column 1 and 2, 
that has "Subtype name". So that we both have the local alias "mc+cbor" 
and the official Subtype name "measured-component+cbor", for example.

I'm not the media types expert of course, but if I were, I wouldn't 
approve the current formulated registration.

best regards,
Esko

On 13-1-2026 20:26, David Dong via RT wrote:
> Dear Esko Dijk (cc: rats WG),
>
> As the designated expert for the CoAP Content-Formats registry, can you review the proposed registrations in draft-ietf-rats-eat-measured-component-10 for us? Please see:
>
> https://datatracker.ietf.org/doc/draft-ietf-rats-eat-measured-component/
>
> The due date is January 27th.
>
> If this is OK, when the IESG approves the document for publication, we'll make the registration at:
>
> https://www.iana.org/assignments/core-parameters/
>
> With thanks,
>
> David Dong
> IANA Services Sr. Specialist

-- 
*IoTconsultancy.nl* | Email/Teams: esko.dijk@iotconsultancy.nl | +31 6 
2385 8339