Nimble out-of-band authentication for EAP (EAP-NOOB)
draft-aura-eap-noob-04

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            T. Aura
Internet-Draft                                          Aalto University
Intended status: Standards Track                                M. Sethi
Expires: April 25, 2019                                         Ericsson
                                                        October 22, 2018

          Nimble out-of-band authentication for EAP (EAP-NOOB)
                         draft-aura-eap-noob-04

Abstract

   Extensible Authentication Protocol (EAP) 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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 25, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Aura & Sethi             Expires April 25, 2019                 [Page 1]
Internet-Draft                  EAP-NOOB                    October 2018

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  EAP-NOOB protocol . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Protocol overview . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Protocol messages and sequences . . . . . . . . . . . . .   8
       3.2.1.  Initial Exchange  . . . . . . . . . . . . . . . . . .   8
       3.2.2.  OOB Step  . . . . . . . . . . . . . . . . . . . . . .  10
       3.2.3.  Completion Exchange . . . . . . . . . . . . . . . . .  11
       3.2.4.  Waiting Exchange  . . . . . . . . . . . . . . . . . .  13
     3.3.  Protocol data fields  . . . . . . . . . . . . . . . . . .  15
       3.3.1.  Peer identifier, realm and NAI  . . . . . . . . . . .  15
       3.3.2.  Message data fields . . . . . . . . . . . . . . . . .  16
     3.4.  Fast reconnect and rekeying . . . . . . . . . . . . . . .  21
       3.4.1.  Persistent EAP-NOOB association . . . . . . . . . . .  21
       3.4.2.  Reconnect Exchange  . . . . . . . . . . . . . . . . .  22
       3.4.3.  User reset  . . . . . . . . . . . . . . . . . . . . .  25
     3.5.  Key derivation  . . . . . . . . . . . . . . . . . . . . .  26
     3.6.  Error handling  . . . . . . . . . . . . . . . . . . . . .  29
       3.6.1.  Invalid messages  . . . . . . . . . . . . . . . . . .  31
       3.6.2.  Unwanted peer . . . . . . . . . . . . . . . . . . . .  31
       3.6.3.  State mismatch  . . . . . . . . . . . . . . . . . . .  31
       3.6.4.  Negotiation failure . . . . . . . . . . . . . . . . .  31
       3.6.5.  Cryptographic verification failure  . . . . . . . . .  32
       3.6.6.  Application-specific failure  . . . . . . . . . . . .  32
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  33
     4.1.  Cryptosuites  . . . . . . . . . . . . . . . . . . . . . .  33
     4.2.  Message Types . . . . . . . . . . . . . . . . . . . . . .  33
     4.3.  Error codes . . . . . . . . . . . . . . . . . . . . . . .  34
     4.4.  Domain name reservation considerations  . . . . . . . . .  35
   5.  Implementation Status . . . . . . . . . . . . . . . . . . . .  36
     5.1.  Implementation with wpa_supplicant and hostapd  . . . . .  36
     5.2.  Protocol modeling . . . . . . . . . . . . . . . . . . . .  37
   6.  Security considerations . . . . . . . . . . . . . . . . . . .  37
Show full document text