IETF Logo Mail Archive

Re: [Iot-onboarding] So... looking where we are

Michael Richardson <mcr@sandelman.ca> Thu, 29 November 2018 16:08 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: iot-onboarding@ietfa.amsl.com
Delivered-To: iot-onboarding@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06F3A130E05 for <iot-onboarding@ietfa.amsl.com>; Thu, 29 Nov 2018 08:08:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 gRD6CoOM2aP2 for <iot-onboarding@ietfa.amsl.com>; Thu, 29 Nov 2018 08:08:07 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D1F21271FF for <iot-onboarding@ietf.org>; Thu, 29 Nov 2018 08:08:07 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [80.233.33.183]) by relay.sandelman.ca (Postfix) with ESMTPS id 1C4C21F8BD; Thu, 29 Nov 2018 16:08:05 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 6BA4B163B; Thu, 29 Nov 2018 11:07:31 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Eliot Lear <lear@cisco.com>
cc: iot-onboarding@ietf.org
In-reply-to: <E743C0EF-7540-4EEF-A9DD-B995F396AB42@cisco.com>
References: <E743C0EF-7540-4EEF-A9DD-B995F396AB42@cisco.com>
Comments: In-reply-to Eliot Lear <lear@cisco.com> message dated "Tue, 27 Nov 2018 10:14:11 -0000."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Thu, 29 Nov 2018 16:07:31 -0000
Message-ID: <29755.1543507651@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/b7rymJUF4zgLiyOpxE_cLEUv8UA>
X-Mailman-Approved-At: Thu, 29 Nov 2018 08:24:12 -0800
Subject: Re: [Iot-onboarding] So... looking where we are
X-BeenThere: iot-onboarding@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <iot-onboarding.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-onboarding/>
List-Post: <mailto:iot-onboarding@ietf.org>
List-Help: <mailto:iot-onboarding-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2018 16:08:09 -0000

Eliot Lear <lear@cisco.com> wrote:
    > * Who becomes the root of trust at the end of onboarding (if any)

Maybe we could ask:
      "Is the transfer of ownership communicated by a change, or addition, to
      the root of trust?"

      (and a related SUIT-like question: does the transfer of ownership
      include the right to decide what firmware runs?)

    > * Could/Is the resulting credential be used for application identity?
    > * What happens if the box gets reset?
                                     ^factory

    > * How can transfer of ownership occur?
    > * How can transfer to a different cloud service (if applicable) occur?
    > * What sort of manufacturing requirements are there?
    > * What sort of crypto requirements are there?
    > * Reference link

    > The one in red is the one that Dave called out as not well-formed.

What's this colour stuff? :-)

v2.23.0 | Report a Bug | By Email