EAP method based on EDHOC Authentication
draft-ingles-eap-edhoc-01

Document Type Active Internet-Draft (individual)
Authors Eduardo Ingles Sanchez  , Dan Garcia-Carrillo  , Rafael Marin-Lopez 
Last updated 2020-11-02
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
EMU Working Group                                              E. Ingles
Internet-Draft                                      University of Murcia
Intended status: Experimental                         D. Garcia-Carrillo
Expires: May 6, 2021                                University of Oviedo
                                                          R. Marin-Lopez
                                                    University of Murcia
                                                        November 2, 2020

                EAP method based on EDHOC Authentication
                       draft-ingles-eap-edhoc-01

Abstract

   This document describes a proposal of an EAP method based on the
   EDHOC authentication protocol.

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 May 6, 2021.

Copyright Notice

   Copyright (c) 2020 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
   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.

Ingles, et al.             Expires May 6, 2021                  [Page 1]
Internet-Draft          draft-ingles-eap-edhoc-01          November 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  The EAP-EDHOC Conversation  . . . . . . . . . . . . . . .   2
       2.1.1.  Transport and Message Correlation . . . . . . . . . .   4
       2.1.2.  Identity  . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Identity Verification . . . . . . . . . . . . . . . . . . . .   5
   4.  Key Hierarchy . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   EDHOC [I-D.selander-lake-edhoc] is a new protocol for autentication
   and key derivation that has been proposed as an alternative in IoT to
   provide a secure exchange in an end-to-end fashion.  This key
   material can be futher used to run other protocols such as OSCORE, as
   well as providing key material to any other protocol that needs pre-
   shared key material to secure the communications.  Provides
   authentication and key material generation, which are basic pillars
   to the design of an EAP method.  And indeed the most important thing
   is that it is lightweight and designed for IoT.  In addition, the
   EDHOC implementation that exists on the device can be reused to
   establish OSCORE Security Associations (SAs) for the authentication
   process.  EAP is a protocol that allows to implement different
   authentication mechanims, provides a framework for key management and
   has integration with AAA infrastructures.  For these reasons, this
   new EAP method will allow the different applications and use cases to
   take advantage of EAP.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

2.  Protocol Overview

2.1.  The EAP-EDHOC Conversation

   The exchange of messages befalls between two entities that EDHOC
   identifies as Initiator (I) and Responder (R).  In this EAP method,

Ingles, et al.             Expires May 6, 2021                  [Page 2]
Internet-Draft          draft-ingles-eap-edhoc-01          November 2020

   we establish equivalence with those terms.  On the one hand, EAP peer
Show full document text