Nimble out-of-band authentication for EAP (EAP-NOOB)
draft-ietf-emu-eap-noob-03
Document | Type | Active Internet-Draft (emu WG) | |
---|---|---|---|
Authors | Tuomas Aura , Mohit Sethi , Aleksi Peltonen | ||
Last updated | 2021-02-13 (latest revision 2020-12-13) | ||
Replaces | draft-aura-eap-noob | ||
Stream | IETF | ||
Intended RFC status | Proposed Standard | ||
Formats | plain text xml pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication (wg milestone: Nov 2019 - WG adopts initial dr... ) | |
Document shepherd | Joseph Salowey | ||
Shepherd write-up | Show (last changed 2021-02-08) | ||
IESG | IESG state | Publication Requested | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Roman Danyliw | ||
Send notices to | joe@salowey.net |
Network Working Group T. Aura Internet-Draft Aalto University Intended status: Standards Track M. Sethi Expires: June 16, 2021 Ericsson A. Peltonen Aalto University December 13, 2020 Nimble out-of-band authentication for EAP (EAP-NOOB) draft-ietf-emu-eap-noob-03 Abstract The 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. The EAP method is intended for bootstrapping all kinds of Internet-of-Things (IoT) devices that have no pre-configured authentication credentials. The method makes use of a user-assisted one-directional OOB message between the peer device and authentication server to authenticate the in-band key exchange. The device must have an input or output interface, such as a display, microphone, speaker or blinking light, which can send or receive dynamically generated messages of tens of bytes in length. 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 June 16, 2021. Copyright Notice Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. Aura, et al. Expires June 16, 2021 [Page 1] Internet-Draft EAP-NOOB December 2020 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 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 . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Protocol overview . . . . . . . . . . . . . . . . . . . . 5 3.2. Protocol messages and sequences . . . . . . . . . . . . . 8 3.2.1. Common handshake in all EAP-NOOB exchanges . . . . . 8 3.2.2. Initial Exchange . . . . . . . . . . . . . . . . . . 10 3.2.3. OOB Step . . . . . . . . . . . . . . . . . . . . . . 11 3.2.4. Completion Exchange . . . . . . . . . . . . . . . . . 13 3.2.5. Waiting Exchange . . . . . . . . . . . . . . . . . . 15 3.3. Protocol data fields . . . . . . . . . . . . . . . . . . 16 3.3.1. Peer identifier and NAI . . . . . . . . . . . . . . . 16 3.3.2. Message data fields . . . . . . . . . . . . . . . . . 18 3.4. Fast reconnect and rekeying . . . . . . . . . . . . . . . 23 3.4.1. Persistent EAP-NOOB association . . . . . . . . . . . 23 3.4.2. Reconnect Exchange . . . . . . . . . . . . . . . . . 24 3.4.3. User reset . . . . . . . . . . . . . . . . . . . . . 27 3.5. Key derivation . . . . . . . . . . . . . . . . . . . . . 28 3.6. Error handling . . . . . . . . . . . . . . . . . . . . . 31 3.6.1. Invalid messages . . . . . . . . . . . . . . . . . . 33 3.6.2. Unwanted peer . . . . . . . . . . . . . . . . . . . . 33 3.6.3. State mismatch . . . . . . . . . . . . . . . . . . . 33 3.6.4. Negotiation failure . . . . . . . . . . . . . . . . . 33 3.6.5. Cryptographic verification failure . . . . . . . . . 34 3.6.6. Application-specific failure . . . . . . . . . . . . 34 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35 4.1. Cryptosuites . . . . . . . . . . . . . . . . . . . . . . 35 4.2. Message Types . . . . . . . . . . . . . . . . . . . . . . 36Show full document text