Re: [Emu] [saag] Fwd: New Version Notification for draft-aura-eap-noob-00.txt

Aura Tuomas <tuomas.aura@aalto.fi> Thu, 18 February 2016 18:07 UTC

Return-Path: <tuomas.aura@aalto.fi>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F15B1B2CDA; Thu, 18 Feb 2016 10:07:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.206
X-Spam-Level:
X-Spam-Status: No, score=-4.206 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.006] autolearn=ham
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 G-KgEr7AhidU; Thu, 18 Feb 2016 10:07:47 -0800 (PST)
Received: from smtp-out-01.aalto.fi (smtp-out-01.aalto.fi [130.233.228.120]) by ietfa.amsl.com (Postfix) with ESMTP id A4F981ACE42; Thu, 18 Feb 2016 10:07:46 -0800 (PST)
Received: from smtp-out-01.aalto.fi (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 47D0A11530D_6C60871B; Thu, 18 Feb 2016 18:07:45 +0000 (GMT)
Received: from EXHUB02.org.aalto.fi (exhub02.org.aalto.fi [130.233.222.119]) by smtp-out-01.aalto.fi (Sophos Email Appliance) with ESMTP id F2BED1152C9_6C60870F; Thu, 18 Feb 2016 18:07:44 +0000 (GMT)
Received: from EXMDB01.org.aalto.fi ([169.254.2.222]) by EXHUB02.org.aalto.fi ([130.233.222.119]) with mapi id 14.03.0224.002; Thu, 18 Feb 2016 20:07:44 +0200
From: Aura Tuomas <tuomas.aura@aalto.fi>
To: Josh Howlett <Josh.Howlett@jisc.ac.uk>, Mohit Sethi <mohit.m.sethi@ericsson.com>, "saag@ietf.org" <saag@ietf.org>, "emu@ietf.org" <emu@ietf.org>
Thread-Topic: [saag] Fwd: New Version Notification for draft-aura-eap-noob-00.txt
Thread-Index: AQHRYmyDaEz8z8wkLU+ZyRerPC0UrZ8iJdqAgA/XEQCAACY7gA==
Date: Thu, 18 Feb 2016 18:07:44 +0000
Message-ID: <7F9C975440487E49BBD35F4FB088ED74CFCDBF14@EXMDB01.org.aalto.fi>
References: <20160208123035.1562.80507.idtracker@ietfa.amsl.com> <56B8B561.8040300@ericsson.com> <VI1PR07MB1581CE8A426823CC02C94E7DBCAF0@VI1PR07MB1581.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR07MB1581CE8A426823CC02C94E7DBCAF0@VI1PR07MB1581.eurprd07.prod.outlook.com>
Accept-Language: fi-FI, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [85.76.161.31]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/emu/z7RFEydyEOPs6zD6G75UsmxpSH8>
Subject: Re: [Emu] [saag] Fwd: New Version Notification for draft-aura-eap-noob-00.txt
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2016 18:07:50 -0000

Hi Josh,

Good observation; we may need to be clearer about the intended usage scenarios for EAP-NOOB.

In the home setting, the AAA server would typically be a cloud-based service, where the consumer can register a user account. This does require the 802.1X authentication (i.e. WPA2-Enterprise) to be configured at the home NAS, so that authentication for "@eap-noob.net" is forwarded to the cloud-based AAA server. You only need to configure the NAS once, and all future devices can be connected without touching the NAS.

This is a change from the way home wireless routers are configured today. We think that, as the number of IoT devices grows, configuring them with a shared passphrase will be too inconvenient. Obviously, the shared passphrase is also vulnerable to a single untrusted IoT device that may leak the passphrase, and using EAP helps to isolate the devices. 

Of course, the benefits of EAP-NOOB will be greater in organizations which already use 802.1X authentication and which have larger numbers of IoT devices than a single home. 

Anything else that we need to address?

Tuomas



-----Original Message-----
From: Josh Howlett [mailto:Josh.Howlett@jisc.ac.uk] 
Sent: Thursday, 18 February, 2016 19:28
To: Mohit Sethi <mohit.m.sethi@ericsson.com>; saag@ietf.org; emu@ietf.org
Cc: Aura Tuomas <tuomas.aura@aalto.fi>
Subject: RE: [saag] Fwd: New Version Notification for draft-aura-eap-noob-00.txt

Hi Mohit,

This is an interesting draft, but I'm struggling to understand how this would be deployed in the consumer settings that the document alludes to. For example, who do you anticipate will be operating the NAS (the consumer?), AAA server (the vendor?), and the AAA fabric between these actors?

Josh.

> -----Original Message-----
> From: saag [mailto:saag-bounces@ietf.org] On Behalf Of Mohit Sethi
> Sent: 08 February 2016 15:34
> To: saag@ietf.org; emu@ietf.org
> Cc: tuomas.aura@aalto.fi
> Subject: [saag] Fwd: New Version Notification for 
> draft-aura-eap-noob-00.txt
> 
> Dear all
> 
> We have just submitted a new IETF Draft titled “Nimble out-of-band 
> authentication for EAP (EAP-NOOB)”.
> 
> The draft defines an EAP method where the authentication is based on a 
> user-assisted out-of-band (OOB) channel between the server and peer. 
> It is intended as a generic bootstrapping solution for 
> Internet-of-Things devices which have no pre-configured authentication 
> credentials and which are not yet registered on the authentication 
> server. Consider devices you just bought or borrowed.
> 
> The EAP-NOOB method is more generic than most ad-hoc bootstrapping 
> solutions in that it supports many types of OOB channels. We specify 
> the exact in-band messages but only the OOB message contents and not 
> the OOB channel details. Also, EAP-NOOB supports ubicomp devices with 
> only output (e.g. display) or only input (e.g. camera). Moreover, it 
> makes combined use of both secrecy and integrity of the OOB channel 
> for more robust security than the ad-hoc solutions. We have put a lot 
> of effort into designing a robust security protocol.
> 
> For one application example, we have used an earlier version of the 
> protocol for bootstrapping security for ubiquitous displays: the user 
> can configure wireless network access, link the device to a cloud 
> service, and register ownership of the device for a specific cloud 
> user – all in one simple step of scanning a QR code with a smart 
> phone. There seemed to more potential to this idea than just using it 
> for our own system, and thus we decided to write a generic EAP method for out-of-band authentication.
> 
> The draft is available here:
> https://tools.ietf.org/html/draft-aura-eap-noob-00
> 
> Please see if you can make use of it. We look forward to your feedback 
> and comments.
> 
> Regards
> /--Mohit
> 
> 
> -------- Forwarded Message --------
> Subject: 	New Version Notification for draft-aura-eap-noob-00.txt
> Date: 	Mon, 08 Feb 2016 04:30:35 -0800
> From: 	internet-drafts@ietf.org
> To: 	Tuomas Aura <tuomas.aura@aalto.fi>, Mohit Sethi
> <mohit@piuha.net>
> 
> 
> 
> A new version of I-D, draft-aura-eap-noob-00.txt has been successfully 
> submitted by Tuomas Aura and posted to the IETF repository.
> 
> Name:		draft-aura-eap-noob
> Revision:	00
> Title:		Nimble out-of-band authentication for EAP (EAP-NOOB)
> Document date:	2016-02-08
> Group:		Individual Submission
> Pages:		35
> URL:https://www.ietf.org/internet-drafts/draft-aura-eap-noob-00.txt
> Status:https://datatracker.ietf.org/doc/draft-aura-eap-noob/
> Htmlized:https://tools.ietf.org/html/draft-aura-eap-noob-00
> 
> 
> Abstract:
>     Extensible Authentication Protocol (EAP) [RFC3748] provides support
>     for multiple authentication methods.  This document defines the EAP-
>     NOOB authentication method for nimble out-of-band (OOB)
>     authentication and key derivation.  This EAP method is intended for
>     bootstrapping all kinds of Internet-of-Things (IoT) devices that have
>     a minimal user interface and no pre-configured authentication
>     credentials.  The method makes use of a user-assisted one-directional
>     OOB channel between the peer device and authentication server.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of 
> submission until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
> 
> 
> _______________________________________________
> saag mailing list
> saag@ietf.org
> https://www.ietf.org/mailman/listinfo/saag

Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.

Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 2881024, VAT number GB 197 0632 86. The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.