OSCORE Profile of ACE v2
draft-palombini-ace-oscore-profile-v2-00

Document Type Active Internet-Draft (individual)
Author Francesca Palombini 
Last updated 2020-09-21
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)
ACE Working Group                                           F. Palombini
Internet-Draft                                               Ericsson AB
Intended status: Standards Track                      September 21, 2020
Expires: March 25, 2021

                        OSCORE Profile of ACE v2
                draft-palombini-ace-oscore-profile-v2-00

Abstract

   This document specifies a profile for the Authentication and
   Authorization for Constrained Environments (ACE) framework.  It
   utilizes Object Security for Constrained RESTful Environments
   (OSCORE) to provide communication security and proof-of-possession
   for a key owned by the client and bound to an OAuth 2.0 access token.
   Additionally, this profile provides OSCORE identifiers negotiation
   between Client and Resource Server.

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 March 25, 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

Palombini                Expires March 25, 2021                 [Page 1]
Internet-Draft          OSCORE Profile of ACE v2          September 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.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Background  . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Client-AS Communication . . . . . . . . . . . . . . . . . . .   5
     3.1.  C-to-AS: POST to token endpoint . . . . . . . . . . . . .   5
     3.2.  AS-to-C: Access Token . . . . . . . . . . . . . . . . . .   6
   4.  Client-RS Communication . . . . . . . . . . . . . . . . . . .  10
     4.1.  C-to-RS: POST to authz-info endpoint  . . . . . . . . . .  10
     4.2.  RS-to-C: 2.01 (Created) . . . . . . . . . . . . . . . . .  11
     4.3.  OSCORE Setup  . . . . . . . . . . . . . . . . . . . . . .  12
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  12
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
     7.1.  ACE Profile Registry  . . . . . . . . . . . . . . . . . .  13
     7.2.  OAuth Parameters Registry . . . . . . . . . . . . . . . .  13
     7.3.  OAuth Parameters CBOR Mappings Registry . . . . . . . . .  13
     7.4.  OSCORE Security Context Parameters Registry . . . . . . .  14
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  14
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   An OSCORE profile of ACE is defined in [I-D.ietf-ace-oscore-profile].
   That profiles describes how to set up OSCORE between nodes, while the
   OSCORE Sender and Recipient Identifiers, i.e. the identifiers of the
   OSCORE keying material, are assigned by the Authorization Server.
   This has some limitations, especially if the OSCORE profile is used
   in conjuction with other mechamisms that also derive identifiers, in
   which case there needs to be a mechanism in place to avoid
   collisions.

   This document describes a new OSCORE profile that builds on
   [I-D.ietf-ace-oscore-profile], and adds a mechanism for negotiating
   identifiers between Client and Resource Server.

Palombini                Expires March 25, 2021                 [Page 2]
Internet-Draft          OSCORE Profile of ACE v2          September 2020

1.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text