Re: [Secdispatch] [lamps] IDevID considerations document to secdispatch

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 23 July 2020 17:33 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79EC93A0C63; Thu, 23 Jul 2020 10:33:24 -0700 (PDT)
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, RCVD_IN_DNSWL_BLOCKED=0.001, 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 ocA71TTpg8CT; Thu, 23 Jul 2020 10:33:22 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CB9A3A0C64; Thu, 23 Jul 2020 10:33:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 231F838A30; Thu, 23 Jul 2020 13:12:51 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id dY7-hBsZd7gp; Thu, 23 Jul 2020 13:12:50 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 40B1E389AA; Thu, 23 Jul 2020 13:12:50 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 640939A; Thu, 23 Jul 2020 13:33:17 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Brockhaus\, Hendrik" <hendrik.brockhaus@siemens.com>
cc: "spasm\@ietf.org" <spasm@ietf.org>, "secdispatch\@ietf.org" <secdispatch@ietf.org>, Tomas Gustavsson <tomas.gustavsson@primekey.com>
In-Reply-To: <AM0PR10MB315388224916907E62839AE1FE790@AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM>
References: <159176190855.9169.7350787463977998504@ietfa.amsl.com> <10463.1591763623@localhost> <13107.1591804306@localhost> <f7cdd360-7ab7-28f6-86b9-9f8c4ae04aaf@primekey.com> <5843.1591897975@localhost> <092308c1-dc44-4989-e3a5-1a248a3c361e@primekey.com> <20595.1593377487@localhost> <841240ae-f610-dcf8-1e29-c73371ae976b@primekey.com> <22303.1595374300@localhost> <AM0PR10MB315388224916907E62839AE1FE790@AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Thu, 23 Jul 2020 13:33:17 -0400
Message-ID: <16964.1595525597@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/bxYil8NRzwxXVqFGCKu1TxQF5_8>
Subject: Re: [Secdispatch] [lamps] IDevID considerations document to secdispatch
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jul 2020 17:33:25 -0000

Brockhaus, Hendrik <hendrik.brockhaus@siemens.com> wrote:
    > I use the image of the "birth certificate" to better explain the attributes of an IDevID certificate.
    > - Issued at manufacturing time (in Germany the birth certificate is a
    > simple sheet stamped and signed by the local register office)

    > - The enrollment process requires some organizational/physical
    > security, as there is nothing to derive trust from at that point in
    > time (in Germany the father or mother have to request the birth
    > certificate personally. They need to define the name of the child in
    > front of the register officer and need present a conformation letter
    > from the hospital or midwife about the date of birth)

In Canada, I think the birth certificate is signed by doctor or midwife.

    > - It lasts as long as the device is used (in Germany a birth
    > certificate has no validity and it is difficult to get a new one, if
    > you lost yours)

Thus IDevID never expire.

    > - It is required for initial authentication to request an operational
    > certificate (in Germany the birth certificate is required if you
    > request a national ID card or a passport)

    > - It should not be used for day-to-day operational tasks (you would not
    > use the birth certificate to identify yourself other than to the
    > register office. Only rarely it is requested, e.g., when becoming a
    > governmental or public official)

But, you don't use your IDevID for day-to-day activities.
One needs an onboarding protocol to talk to an organizational CA to get the LDevID.

--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-