OSCOAP profile of the Authentication and Authorization for Constrained Environments Framework
draft-seitz-ace-oscoap-profile-04

Document Type Active Internet-Draft (individual)
Last updated 2017-07-24
Replaces draft-seitz-ace-ocsoap-profile
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                                               L. Seitz
Internet-Draft                                              RISE SICS AB
Intended status: Standards Track                            F. Palombini
Expires: January 24, 2018                                    Ericsson AB
                                                           M. Gunnarsson
                                                            RISE SICS AB
                                                           July 23, 2017

 OSCOAP profile of the Authentication and Authorization for Constrained
                         Environments Framework
                   draft-seitz-ace-oscoap-profile-04

Abstract

   This memo specifies a profile for the Authentication and
   Authorization for Constrained Environments (ACE) framework.  It
   utilizes Object Security of CoAP (OSCOAP) and Ephemeral Diffie-
   Hellman over COSE (EDHOC) to provide communication security, server
   authentication, and proof-of-possession for a key owned by the client
   and bound to an OAuth 2.0 access token.

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 http://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 January 24, 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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Seitz, et al.           Expires January 24, 2018                [Page 1]
Internet-DraOSCOAP profile of the Authentication and Authoriz  July 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Client to Resource Server . . . . . . . . . . . . . . . . . .   3
     2.1.  Signaling the use of OSCOAP . . . . . . . . . . . . . . .   3
     2.2.  Key establishment for OSCOAP  . . . . . . . . . . . . . .   4
       2.2.1.  Using the pop-key with OSCOAP directly (OSCOAP) . . .   4
       2.2.2.  Using the pop-key with EDHOC (EDHOC+OSCOAP) . . . . .   7
     2.3.  Client to Authorization Server  . . . . . . . . . . . . .  13
   3.  Resource Server to Authorization Server . . . . . . . . . . .  14
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   5.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  14
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  14
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  15
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   This memo specifies a profile of the ACE framework
   [I-D.ietf-ace-oauth-authz].  In this profile, a client and a resource
   server use CoAP [RFC7252] to communicate.  The client uses an access
   token, bound to a key (the proof-of-possession key) to authorize its
   access to the resource server.  In order to provide communication
   security, proof of possession, and server authentication they use
   Object Security of CoAP (OSCOAP) [I-D.ietf-core-object-security] and
   Ephemeral Diffie-Hellman Over COSE (EDHOC)
   [I-D.selander-ace-cose-ecdhe].  Optionally the client and the
   resource server may also use CoAP and OSCOAP to communicate with the
   authorization server.  The use of EDHOC in this profile in addition
   to OSCOAP, provides perfect forward secrecy (PFS) and the initial
   proof-of-possession, which ties the proof-of-possession key to an
   OSCOAP security context.
Show full document text