IETF Logo Mail Archive

Re: [core] I-D Action: draft-ietf-core-dev-urn-07.txt

Henk Birkholz <henk.birkholz@sit.fraunhofer.de> Thu, 02 July 2020 19:05 UTC

Return-Path: <henk.birkholz@sit.fraunhofer.de>
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 75C023A003E for <core@ietfa.amsl.com>; Thu, 2 Jul 2020 12:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 yhYIo5iz4QZS for <core@ietfa.amsl.com>; Thu, 2 Jul 2020 12:04:59 -0700 (PDT)
Received: from mail-edgeS23.fraunhofer.de (mail-edges23.fraunhofer.de [153.97.7.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D93E3A0035 for <core@ietf.org>; Thu, 2 Jul 2020 12:04:57 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2EFAwD9Lv5e/xmnZsBfHAEBAQEBAQcBARIBAQQEAQFAgUqETAqEJ5ETnAQLAQEBAQEBAQEBBgEBLQIEAQGERwKCHgEkOBMCEAEBBgEBAQEBBgQCAoZQhkgBBSMPAQU6BxAJAg4KAgImAgJHEAYNAQUCAQGDIoJ9BI5Em3qBMoVRg2iBQIEOKoxoD4FMP4E4D4JaPodTgmAEj1OCY6IsKAeBWYEGgQcEC5goBQodgnOJMIR1Bo1/sDkCBAIJAhWBaoF5TSSDOFAXAg2OKheOJnICNQIGAQcBAQMJfI1QAYEQAQE
X-IPAS-Result: A2EFAwD9Lv5e/xmnZsBfHAEBAQEBAQcBARIBAQQEAQFAgUqETAqEJ5ETnAQLAQEBAQEBAQEBBgEBLQIEAQGERwKCHgEkOBMCEAEBBgEBAQEBBgQCAoZQhkgBBSMPAQU6BxAJAg4KAgImAgJHEAYNAQUCAQGDIoJ9BI5Em3qBMoVRg2iBQIEOKoxoD4FMP4E4D4JaPodTgmAEj1OCY6IsKAeBWYEGgQcEC5goBQodgnOJMIR1Bo1/sDkCBAIJAhWBaoF5TSSDOFAXAg2OKheOJnICNQIGAQcBAQMJfI1QAYEQAQE
X-IronPort-AV: E=Sophos;i="5.75,305,1589234400"; d="scan'208";a="18832265"
Received: from mail-mtadd25.fraunhofer.de ([192.102.167.25]) by mail-edgeS23.fraunhofer.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jul 2020 21:04:55 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DYAwCMLv5e/1lIDI1fHAEBAQEBAQcBARIBAQQEAQFAgUqCKnJUMCwKhCeRFJwECwEDAQEBAQEGAQEtAgQBAYRHAoIcAiQ4EwIQAQEFAQEBAgEGBG2FZ4VvAQUjDwEFOgcQCQIOCgICJgICRxAGDQEFAgEBgyKDAY4/m3qBMoVRg2aBQIEOKoxoD4FMP4E4D4JaPodTgmAEj1OCY6IsKAeBWYEGgQcEC5goBQodgnOJMIR1Bo1/sDkCBAIJAhWBaiKBVk0kgzhQFwINjioXjiZBMQI1AgYBBwEBAwl8jVABgRABAQ
X-IronPort-AV: E=Sophos;i="5.75,305,1589234400"; d="scan'208";a="85432437"
Received: from mailext.sit.fraunhofer.de ([141.12.72.89]) by mail-mtaDD25.fraunhofer.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jul 2020 21:04:52 +0200
Received: from mail.sit.fraunhofer.de (mail.sit.fraunhofer.de [141.12.84.171]) by mailext.sit.fraunhofer.de (8.15.2/8.15.2/Debian-10) with ESMTPS id 062J4osA013761 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA256 bits=128 verify=NOT); Thu, 2 Jul 2020 21:04:50 +0200
Received: from [192.168.16.50] (79.206.156.41) by mail.sit.fraunhofer.de (141.12.84.171) with Microsoft SMTP Server (TLS) id 14.3.487.0; Thu, 2 Jul 2020 21:04:45 +0200
To: Carsten Bormann <cabo@tzi.org>
CC: Michael Richardson <mcr+ietf@sandelman.ca>, "core@ietf.org" <core@ietf.org>
References: <159367707352.18882.7029018895298940774@ietfa.amsl.com> <EABE9193-E927-44C4-B04D-A352B4D20E06@arm.com> <12185.1593707940@localhost> <5c67a0ac-5f2c-6f84-2ced-b368488455d2@sit.fraunhofer.de> <DFD4B879-A3F1-410D-ACCA-EB7A2DA402F1@tzi.org>
From: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
Message-ID: <965be580-b470-bfff-b2cc-70ecdcef1519@sit.fraunhofer.de>
Date: Thu, 02 Jul 2020 21:04:37 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <DFD4B879-A3F1-410D-ACCA-EB7A2DA402F1@tzi.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [79.206.156.41]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/-Z80fQVd9yjhgDJFvapv0Xp-aDE>
Subject: Re: [core] I-D Action: draft-ietf-core-dev-urn-07.txt
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: Thu, 02 Jul 2020 19:05:03 -0000

I am fine with vice versa. Having said that, I am not pulling this from 
thin air. The "relations to devid" question is pretty much always the 
first question I encounter when floating this I-D (next to application 
in production today, of course).

Viele Grüße,

Henk

On 02.07.20 20:24, Carsten Bormann wrote:
> On 2020-07-02, at 18:44, Henk Birkholz <henk.birkholz@sit.fraunhofer.de> wrote:
>>
>> While not mission critical, I'd +1 some expositional text on how hardware device identifier URNs relate to secure device identifier DevIDs.
> 
> Rathole alert.  We have so far avoided dev-urn getting stuck in the stable identifier debate.  Adding more relationships to things some of us don’t think are acceptable for privacy reasons is not going to help.
> 
> (I wouldn’t mind the idevid people writing up how they could use dev-urns.  Once these are an RFC, please…)
> 
> Grüße, Carsten
>

v2.23.0 | Report a Bug | By Email