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

Jari Arkko <jari.arkko@piuha.net> Fri, 08 January 2021 19:01 UTC

Return-Path: <jari.arkko@piuha.net>
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 CD0373A0AD3; Fri, 8 Jan 2021 11:01:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 KMTHjetwypt3; Fri, 8 Jan 2021 11:01:04 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:1829::130]) by ietfa.amsl.com (Postfix) with ESMTP id 1EE5A3A09D7; Fri, 8 Jan 2021 11:01:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6DAD56601C1; Fri, 8 Jan 2021 21:01:03 +0200 (EET)
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xw0eto2cRemt; Fri, 8 Jan 2021 21:01:02 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id 3DF1E66012A; Fri, 8 Jan 2021 21:01:02 +0200 (EET)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <BF2DF408-8AF0-498B-A14D-4D117A2A9ECD@vigilsec.com>
Date: Fri, 08 Jan 2021 21:01:01 +0200
Cc: "iot-directorate@ietf.org" <iot-directorate@ietf.org>, draft-ietf-core-dev-urn.all@ietf.org, core@ietf.org, last-call@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5D1297B-A49E-43D9-8D69-6AC5FA2A80EA@piuha.net>
References: <160996930502.21827.5533521556349871834@ietfa.amsl.com> <7BE43FEF-DA33-4B40-9DA7-E646C60CB600@piuha.net> <BF2DF408-8AF0-498B-A14D-4D117A2A9ECD@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/a9uS2gMVESN-6ozhjvd-zCh2Qgg>
Subject: Re: [core] [Last-Call] Iotdir telechat review of draft-ietf-core-dev-urn-09
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: Fri, 08 Jan 2021 19:01:06 -0000

Hi Russ,

> 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.

That sounds very good. Thanks!

Updated in the draft.

Jari