IETF Logo Mail Archive

Re: [Iot-onboarding] EduRoam for IoT

sandoche Balakrichenan <sandoche.balakrichenan@afnic.fr> Tue, 10 December 2019 12:40 UTC

Return-Path: <sandoche.balakrichenan@afnic.fr>
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 8D317120810 for <iot-onboarding@ietfa.amsl.com>; Tue, 10 Dec 2019 04:40:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 BDduLGVkM32r for <iot-onboarding@ietfa.amsl.com>; Tue, 10 Dec 2019 04:39:58 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 58EC212081C for <iot-onboarding@ietf.org>; Tue, 10 Dec 2019 04:39:58 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 563A82806DE; Tue, 10 Dec 2019 13:39:56 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id 4D56F280717; Tue, 10 Dec 2019 13:39:56 +0100 (CET)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id 43D582806DE; Tue, 10 Dec 2019 13:39:56 +0100 (CET)
Received: from zimbra.afnic.fr (hebe.prod-int.prive.th3.nic.fr [10.1.81.80]) by relay01.prive.nic.fr (Postfix) with ESMTP id 3DE3B67F2EC0; Tue, 10 Dec 2019 13:39:56 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by zimbra.afnic.fr (Postfix) with ESMTP id 327B62D7C8BF; Tue, 10 Dec 2019 13:39:56 +0100 (CET)
Received: from zimbra.afnic.fr ([127.0.0.1]) by localhost (zimbra.afnic.fr [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 0pl_LkCy0jAP; Tue, 10 Dec 2019 13:39:55 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by zimbra.afnic.fr (Postfix) with ESMTP id 6AFAC2D7C8BD; Tue, 10 Dec 2019 13:39:55 +0100 (CET)
X-Virus-Scanned: amavisd-new at zimbra.afnic.fr
Received: from zimbra.afnic.fr ([127.0.0.1]) by localhost (zimbra.afnic.fr [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id g3FC61pXruU7; Tue, 10 Dec 2019 13:39:55 +0100 (CET)
Received: from Sandoches-MacBook-Pro.local (unknown [10.0.95.11]) by zimbra.afnic.fr (Postfix) with ESMTPA id 1B0AE2D7C8BA; Tue, 10 Dec 2019 13:39:55 +0100 (CET)
To: Rafa Marin-Lopez <rafa@um.es>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, iot-onboarding@ietf.org, Guillaume Schreiner <schreiner@unistra.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> <BFC66102-85AF-4C73-8552-B7D23BA9DEE6@um.es>
From: sandoche Balakrichenan <sandoche.balakrichenan@afnic.fr>
Message-ID: <3db36f1f-8fcf-35fc-c8f9-815ff34122a8@afnic.fr>
Date: Tue, 10 Dec 2019 13:39:52 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <BFC66102-85AF-4C73-8552-B7D23BA9DEE6@um.es>
Content-Type: multipart/alternative; boundary="------------423CDA815D1375DBB841AA79"
Content-Language: en-US
X-Bogosity: No, tests=bogofilter, spamicity=0.120752, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2019.11.5.63017
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/W9EjO05ZuXfAknsH_Lz2nDf3jQY>
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 12:40:02 -0000

Dear Rafa,

Thanks for the input.

We have collected some information based on feedback from different 
people and mailing lists. We will try to prepare a brief document based 
on these inputs and come back to the mailing list.

Sandoche.

On 10/12/2019 13:36, Rafa Marin-Lopez wrote:
> Dear Sandoche:
>
>> El 9 dic 2019, a las 22:40, sandoche Balakrichenan 
>> <sandoche.balakrichenan@afnic.fr 
>> <mailto:sandoche.balakrichenan@afnic.fr>> escribió:
>>
>>
>> On 09/12/2019 18:45, Michael Richardson wrote:
>>> Eliot Lear <lear@cisco.com <mailto: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?
>>
>> ==> Absolutely.
>>
>> Alternatives could be : 
>> https://datatracker.ietf.org/doc/draft-aura-eap-noob/?include_text=1
>
> When you use EAP you need an EAP lower-layer to transport EAP between 
> IoT device and the network. As you mention, you would like a generic 
> solution, which means that EAP lower-layer should operate in any 
> link-layer. PANA (https://tools.ietf.org/html/rfc5191) provides that. 
> Also CoAP-EAP 
> (https://tools.ietf.org/html/draft-marin-ace-wg-coap-eap-06, 
> https://www.mdpi.com/1424-8220/16/3/358) provides that feature, since 
> it is an EAP lower-layer based on CoAP.
>
>
> Best Regards.
>>
>> and evolving standards from the LAKE WG 
>> (https://datatracker.ietf.org/wg/lake/about/) using a PKI
>>
>>>
>>> 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.
>>
>> Sandoche.
>>
>> -- 
>> Iot-onboarding mailing list
>> Iot-onboarding@ietf.org <mailto:Iot-onboarding@ietf.org>
>> https://www.ietf.org/mailman/listinfo/iot-onboarding
>
> -------------------------------------------------------
> Rafa Marin-Lopez, PhD
> Dept. Information and Communications Engineering (DIIC)
> Faculty of Computer Science-University of Murcia
> 30100 Murcia - Spain
> Telf: +34868888501 Fax: +34868884151 e-mail: rafa@um.es 
> <mailto:rafa@um.es>
> -------------------------------------------------------
>
>
>
>

v2.23.0 | Report a Bug | By Email