IETF Logo Mail Archive

Re: [Iot-onboarding] EduRoam for IoT

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 09 December 2019 17:45 UTC

Return-Path: <mcr+ietf@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 DDD0312083E for <iot-onboarding@ietfa.amsl.com>; Mon, 9 Dec 2019 09:45:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 Q2QUGXPqEeie for <iot-onboarding@ietfa.amsl.com>; Mon, 9 Dec 2019 09:45:27 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7EDB120849 for <iot-onboarding@ietf.org>; Mon, 9 Dec 2019 09:45:26 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id B4AE03897B for <iot-onboarding@ietf.org>; Mon, 9 Dec 2019 12:41:25 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 890EC68B for <iot-onboarding@ietf.org>; Mon, 9 Dec 2019 12:45:10 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: iot-onboarding@ietf.org
In-Reply-To: <62187F87-EC6B-4A34-ACDC-9E5BA5001A0E@cisco.com>
References: <80fc1573-62f9-26a6-5b55-6ff33c0b1a94@afnic.fr> <62187F87-EC6B-4A34-ACDC-9E5BA5001A0E@cisco.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.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-sha256"; protocol="application/pgp-signature"
Date: Mon, 09 Dec 2019 12:45:10 -0500
Message-ID: <21488.1575913510@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/7ladAtzRRyRAQyz2LgwspEdGtOQ>
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: Mon, 09 Dec 2019 17:45:32 -0000

Eliot Lear <lear@cisco.com> wrote:
    > I think what you are aiming for is a LoRa-enabled router that can do a
    > radius transaction that has the appropriate federated wrapper, such as
    > PEAP/EAP-TLS.  Will the LoRa device know its home network?

At bytes/day?

I don't think that it is network onboarding, but application onboarding that
is desired.

To repost what I posted to the RIPE IoT list:

My colleagues at CIRALabs did something that might be similar to what you
want, as it deals with the connection/onboarding to the *application* server,
not the network itself, which is assumed to be managed by the Telco:

https://github.com/CIRALabs/CIRA-Secure-IoT-Registry/blob/master/CIRA%20Labs%20-%20Secure%20IoT%20Registry%202019-11-14.pdf



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

v2.23.0 | Report a Bug | By Email