Re: [Iot-onboarding] EduRoam for IoT

Kent Watsen <kent@watsen.net> Tue, 10 December 2019 16:05 UTC

Return-Path: <0100016ef08f03cb-1772e182-32d4-4821-8b58-8781d7b83334-000000@amazonses.watsen.net>
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 9663B12089D for <iot-onboarding@ietfa.amsl.com>; Tue, 10 Dec 2019 08:05:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 uv1O_DsoAUuS for <iot-onboarding@ietfa.amsl.com>; Tue, 10 Dec 2019 08:05:36 -0800 (PST)
Received: from a8-88.smtp-out.amazonses.com (a8-88.smtp-out.amazonses.com [54.240.8.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C3DF1201EA for <iot-onboarding@ietf.org>; Tue, 10 Dec 2019 08:05:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1575993935; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=6oqq6ZJqViBI4tx+++ZpdJS/OeJZug2egVsQQvWvqIA=; b=Zb026R1cWRDwmBkEaZw5nI/yqeW9yAfE517CfGDhvOFk7tEVNcRcdjtP2IZ8KMw+ BBAFmmZqnwTqbca87lTKcgoVoNmtn4ifVuMosyfPikYx0oLuyKFMZk/ZbGtGa8zRVu9 J3wUzjQrDMXPikM6if+4xXjdFjrWLzfh/YdmSLck=
From: Kent Watsen <kent@watsen.net>
Message-ID: <0100016ef08f03cb-1772e182-32d4-4821-8b58-8781d7b83334-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F06526B0-6289-4C02-8435-8169DD8049D7"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 10 Dec 2019 16:05:34 +0000
In-Reply-To: <d224dc38-c0c6-9aac-c0d2-ee83e1483a02@afnic.fr>
Cc: Michael Richardson <mcr@sandelman.ca>, iot-onboarding@ietf.org, Guillaume Schreiner <schreiner@unistra.fr>
To: sandoche Balakrichenan <sandoche.balakrichenan@afnic.fr>
References: <80fc1573-62f9-26a6-5b55-6ff33c0b1a94@afnic.fr> <62187F87-EC6B-4A34-ACDC-9E5BA5001A0E@cisco.com> <21488.1575913510@localhost> <c4f6ea01-4d52-7cd8-4cdf-b6f5714d1f95@afnic.fr> <22415.1575990074@localhost> <d224dc38-c0c6-9aac-c0d2-ee83e1483a02@afnic.fr>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.12.10-54.240.8.88
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/qIyLZ0zkNltPBEEycFIncMTTw2Y>
Subject: Re: [Iot-onboarding] EduRoam for IoT
X-BeenThere: iot-onboarding@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IoT onboarding mechanisms <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: Tue, 10 Dec 2019 16:05:37 -0000


> On Dec 10, 2019, at 10:38 AM, sandoche Balakrichenan <sandoche.balakrichenan@afnic.fr> wrote:
> 
> 
> On 10/12/2019 16:01, Michael Richardson wrote:
>> sandoche Balakrichenan <sandoche.balakrichenan@afnic.fr> wrote:
>>     >> I don't think that it is network onboarding, but application onboarding that
>>     >> is desired.
>>     >>
>>     > ==> Application onboarding is for the LoRaWAN scenario.
>> 
>>     > Don't we have the need for network onboarding for other IoT networks?
>> 
>>     > The objective is to come with a generic solution, if possible.
>> 
>> Then, I think that you want a BRSKI based system, if you want to address a
>> large number of context.  I am skeptical that this can include LoRA.
>> 
> +1
> 
> BRSKI is a promising reference. We will dig further into it for the IoTRoam use-case.
> 
> Sandoche.


You may also be interested in SZTP (RFC 8572).

Kent