Re: [Iot-directorate] [Last-Call] Iotdir telechat review of draft-ietf-core-dev-urn-09

Russ Housley <housley@vigilsec.com> Fri, 08 January 2021 16:49 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: iot-directorate@ietfa.amsl.com
Delivered-To: iot-directorate@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DFFA3A113A for <iot-directorate@ietfa.amsl.com>; Fri, 8 Jan 2021 08:49:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable 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 qAa28RJf0oXN for <iot-directorate@ietfa.amsl.com>; Fri, 8 Jan 2021 08:49:25 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 675A63A1137 for <iot-directorate@ietf.org>; Fri, 8 Jan 2021 08:49:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 12BAA300BCF for <iot-directorate@ietf.org>; Fri, 8 Jan 2021 11:44:17 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 5-SrfMAW45Tc for <iot-directorate@ietf.org>; Fri, 8 Jan 2021 11:44:14 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id EBFE4300A48; Fri, 8 Jan 2021 11:44:13 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <BF2DF408-8AF0-498B-A14D-4D117A2A9ECD@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A8B02140-027B-460E-8D81-B11045BCDD34"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Fri, 08 Jan 2021 11:44:15 -0500
In-Reply-To: <7BE43FEF-DA33-4B40-9DA7-E646C60CB600@piuha.net>
Cc: "iot-directorate@ietf.org" <iot-directorate@ietf.org>, draft-ietf-core-dev-urn.all@ietf.org, core@ietf.org, last-call@ietf.org
To: Jari Arkko <jari.arkko@piuha.net>
References: <160996930502.21827.5533521556349871834@ietfa.amsl.com> <7BE43FEF-DA33-4B40-9DA7-E646C60CB600@piuha.net>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-directorate/ngSy7t0XDYJLY-1mIdmatk55qzo>
Subject: Re: [Iot-directorate] [Last-Call] Iotdir telechat review of draft-ietf-core-dev-urn-09
X-BeenThere: iot-directorate@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for the IoT Directorate Members <iot-directorate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-directorate>, <mailto:iot-directorate-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-directorate/>
List-Post: <mailto:iot-directorate@ietf.org>
List-Help: <mailto:iot-directorate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-directorate>, <mailto:iot-directorate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2021 16:49:27 -0000

Jari:

All but one of my comments are resolved.

>> Section 6 says:
>> 
>>  ... An implementation of the DEV URN MUST NOT
>>  change these properties from what they were intended.
>> 
>> It is not clear to me the meaning of "they" in this sentence.
>> Please clarify.
> 
> I made a small change, but I’m not sure how else to express this. We are talking about whether identifiers are modifiable for instance. The whole paragraph reads now:
> 
> On most devices, the user can display device identifiers. Depending
> on circumstances, device identifiers may or may not be modified or
> tampered with by the user. An implementation of the DEV URN MUST NOT change
> such limitations or behaviour from what they were intended. In particular, a device
> identifier that is intended to be immutable should not become mutable
> as a part of implementing the DEV URN type. More generally, nothing in
> this document should be construed to override what the relevant device
> specifications have already said about the identifiers.

I am still unsure what an implementer would do to comply the MUST NOT statement.  Maybe it will helpful to turn it into a MUST statement.  Does this work for you?

On most devices, the user can display device identifiers. Depending
on circumstances, device identifiers may or may not be modified or
tampered with by the user. An implementation of the DEV URN MUST preserve
such limitations and behaviors associated with the device identifiers. In particular,
a device identifier that is intended to be immutable should not become mutable
as a part of implementing the DEV URN type. More generally, nothing in
this document should be construed to override what the relevant device
specifications have already said about the identifiers.

Russ