EAP-based Authentication Service for CoAP
draft-marin-ace-wg-coap-eap-06

Document Type Active Internet-Draft (individual)
Last updated 2017-10-25
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)
ACE Working Group                                               R. Marin
Internet-Draft                                                 D. Garcia
Intended status: Experimental                       University of Murcia
Expires: April 27, 2018                                 October 24, 2017

               EAP-based Authentication Service for CoAP
                     draft-marin-ace-wg-coap-eap-06

Abstract

   This document describes an authentication service that uses EAP
   transported by means of CoAP messages with two purposes:

   o  Authenticate two CoAP endpoints.

   o  Bootstrap key material to protect CoAP messages exchanged between
      them.

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 27, 2018.

Copyright Notice

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

Marin & Garcia           Expires April 27, 2018                 [Page 1]
Internet-Draft                  CoAP-EAP                    October 2017

   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.  General Architecture  . . . . . . . . . . . . . . . . . . . .   3
   3.  General Flow Operation  . . . . . . . . . . . . . . . . . . .   3
     3.1.  EAP in CoAP with AUTH option  . . . . . . . . . . . . . .   4
     3.2.  CoAP-EAP with DTLS  . . . . . . . . . . . . . . . . . . .   7
     3.3.  CoAP as EAP lower-layer . . . . . . . . . . . . . . . . .  10
     3.4.  Optimization Considerations . . . . . . . . . . . . . . .  11
   4.  Key Derivation for protecting CoAP messages . . . . . . . . .  11
     4.1.  Deriving COAP_PSK . . . . . . . . . . . . . . . . . . . .  11
     4.2.  Deriving DTLS_PSK . . . . . . . . . . . . . . . . . . . .  12
   5.  Generating AUTH option  . . . . . . . . . . . . . . . . . . .  13
   6.  Implementation  . . . . . . . . . . . . . . . . . . . . . . .  14
   7.  Future Work: CoAP Intermediaries  . . . . . . . . . . . . . .  15
   8.  Use Case Scenario . . . . . . . . . . . . . . . . . . . . . .  16
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  17
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  17
     10.1.  Authorization  . . . . . . . . . . . . . . . . . . . . .  18
     10.2.  Cryptographic suite selection  . . . . . . . . . . . . .  18
     10.3.  Additional Security Consiederation . . . . . . . . . . .  18
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  18
     12.2.  Informative References . . . . . . . . . . . . . . . . .  20
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  20

1.  Introduction

   The goal of this document is to describe an authentication service
   that uses the Extensible Authentication Protocol (EAP) [RFC3748].
   The authentication service is built on top of the Constrained
   Application Protocol (CoAP) [RFC7252] and allows authenticating two
   CoAP endpoints by using EAP without the need of additional protocols
   to bootstrap a security association between them.

   In particular, the document describes how CoAP can be used as EAP
   lower-layer [RFC3748] to transport EAP between a CoAP server (EAP
   peer) and the CoAP client (EAP authenticator) using CoAP messages.
   The CoAP client may contact with a backend AAA infrastructure to
   complete the EAP negotiation as described in the EAP specification
   [RFC3748].

Marin & Garcia           Expires April 27, 2018                 [Page 2]
Internet-Draft                  CoAP-EAP                    October 2017
Show full document text