Re: [T2TRG] Report from breakout on using application credentials to enable network access

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 14 April 2017 17:31 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: t2trg@ietfa.amsl.com
Delivered-To: t2trg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C7831294C8 for <t2trg@ietfa.amsl.com>; Fri, 14 Apr 2017 10:31:22 -0700 (PDT)
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, RP_MATCHES_RCVD=-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 19yyxIJXr31F for <t2trg@ietfa.amsl.com>; Fri, 14 Apr 2017 10:31:19 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D78FB1294B8 for <t2trg@irtf.org>; Fri, 14 Apr 2017 10:31:16 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 2B345203B8; Fri, 14 Apr 2017 13:56:06 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A1B9B636BB; Fri, 14 Apr 2017 13:31:15 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: =?utf-8?Q?Dan_Garc=C3=ADa_Carrillo?= <dan.garcia@um.es>
cc: t2trg@irtf.org
In-Reply-To: <CBF2A279-A163-4B0C-9F53-6EDD21511A7B@um.es>
References: <3e12961e-0ba7-f580-2837-1971e47e0840@ericsson.com> <E2FA0FF2-57F4-489C-AC7A-5B9763DF655E@um.es> <CBF2A279-A163-4B0C-9F53-6EDD21511A7B@um.es>
X-Mailer: MH-E 8.6; nmh 1.6+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: Fri, 14 Apr 2017 13:31:15 -0400
Message-ID: <21025.1492191075@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/CRaIJ2aFE8CSaHNL3GMD7c5Jda0>
Subject: Re: [T2TRG] Report from breakout on using application credentials to enable network access
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <t2trg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/t2trg>, <mailto:t2trg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/t2trg/>
List-Post: <mailto:t2trg@irtf.org>
List-Help: <mailto:t2trg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/t2trg>, <mailto:t2trg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 17:31:23 -0000

Dan García Carrillo <dan.garcia@um.es> wrote:
    > Regarding the topic of network access for IoT devices.  We are
    > currently working on that, using RADIUS and EAP. Concretely, we are
    > using CoAP to transport EAP messages. The proposal is in
    > draft-marin-ace-wg-coap-eap.

    > We have a functional prototype of the protocol for Contiki O.S. and we
    > have performed some tests comparing the performance to PANATIKI's
    > implementation of the PANA protocol for Contiki O.S shown in this
    > article. http://www.mdpi.com/1424-8220/16/3/358

What node provides the authenticator function?
Do you have that part in Contiki?  Your document says you run that on a Linux
system using hostapd.

How do you establish the radius shared secret for node A or B,
so that it can help enroll some future node E.  Or must it always go through
pre-established controller C?

If that's an intended limitation, then it can't work for enrolling nodes
in a route-over mesh, only for single-hop networks.

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