AAA-based assisted EDHOC Authentication
draft-ingles-radex-radius-edhoc-00

Document Type Active Internet-Draft (individual)
Last updated 2020-08-05
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)
Network Working Group                                          E. Ingles
Internet-Draft                                      University of Murcia
Intended status: Experimental                                  D. Garcia
Expires: February 6, 2021                            Odin Solutions S.L.
                                                                R. Marin
                                                    University of Murcia
                                                          August 5, 2020

                AAA-based assisted EDHOC Authentication
                   draft-ingles-radex-radius-edhoc-00

Abstract

   This document describes a proposal to place EDHOC server in an
   external Authentication, Authorization and Accounting (AAA) server.
   The purpose is to centralize the EDHOC authentication in AAA
   infrastructure.

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 February 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

Ingles, et al.          Expires February 6, 2021                [Page 1]
Internet-Draft     draft-ingles-radex-radius-edhoc-00        August 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  EDHOC support in AAA  . . . . . . . . . . . . . . . . . . . .   3
   3.  EDHOC Overview  . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Introduction  . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  EDHOC protocol overview . . . . . . . . . . . . . . . . .   4
     3.3.  EDHOC key derivation  . . . . . . . . . . . . . . . . . .   4
   4.  Integration Overview  . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Mapping EDHOC entities to AAA infrastructure  . . . . . .   5
     4.2.  Assumptions . . . . . . . . . . . . . . . . . . . . . . .   5
     4.3.  Protocol Exchange . . . . . . . . . . . . . . . . . . . .   5
     4.4.  EDHOC-message Attribute . . . . . . . . . . . . . . . . .   6
     4.5.  EDHOC-key attribute . . . . . . . . . . . . . . . . . . .   7
     4.6.  Table of Attribute  . . . . . . . . . . . . . . . . . . .   8
   5.  Open Issues . . . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

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
   mainly due to two main characteristics, namely, it works on top of
   any reliable transport, which means it can be carried over a protocol
   such as CoAP and provides 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.  EDHOC
   has another characteristic that makes it an interesting alternative
   that is work underlining, it is designed to be lightweight, for which
   is build using COSE, reducing the overhead of the protocol.  The
   proposal of this protocol coalesces with the advancement of the new
   set of technologies known as LPWAN, which generally have high
   constrains in the link, even more than traditional IoT networks.
Show full document text