IETF Logo Mail Archive

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

Randy Bush <randy@psg.com> Sat, 01 December 2018 17:40 UTC

Return-Path: <randy@psg.com>
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 0611A130DDB for <iot-onboarding@ietfa.amsl.com>; Sat, 1 Dec 2018 09:40:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 IZGMlDS4ZZwN for <iot-onboarding@ietfa.amsl.com>; Sat, 1 Dec 2018 09:40:05 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 62E83130DD2 for <iot-onboarding@ietf.org>; Sat, 1 Dec 2018 09:40:05 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1gT9FK-0001E9-Tv; Sat, 01 Dec 2018 17:40:03 +0000
Date: Sat, 01 Dec 2018 09:40:02 -0800
Message-ID: <m2o9a5no25.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
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>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/IOyDg3K5pb5sK75QjOGsKwcyrxc>
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: Sat, 01 Dec 2018 17:40:07 -0000

first, i might ask on what board we are getting?  my take is the local
network which is under enterprise or personal control.  i.e. i do not
assume becoming part of the global internet.

> Is access to other IP-based devices required in order to fully onboard
> the device?

the access/authorisation/... controller of my lan/network

> Is full Internet access required for onboarding?

i would hope not.  if i want the device to transact with some remote
service, that would be controlled and mediated by my lan's access
service.

> Who becomes the root of trust at the end of onboarding (if any)

my enterprise/lan access/authorisation/... controller

---

ps:

nothing in red in repo/README.md i can see

if a list has an associated git-based repo, it might be cool to start a
conventon where message footers are auto-tagged with the repo url and
less bumph

> Iot-onboarding mailing list
> Iot-onboarding@ietf.org
> https://www.ietf.org/mailman/listinfo/iot-onboarding

randy

v2.23.0 | Report a Bug | By Email