Identifier Negotiation for the OSCORE Profile of ACE
draft-palombini-ace-oscore-profile-id-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

          Identifier Negotiation for the OSCORE Profile of ACE
                draft-palombini-ace-oscore-profile-id-00

Abstract

   This document defines a mechanism to negotiate OSCORE security
   material identifiers for the OSCORE profile of ACE.

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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Palombini                Expires March 25, 2021                 [Page 1]
Internet-Draft      Id Negotiation for OSCORE Profile     September 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Identifiers Negotiation . . . . . . . . . . . . . . . . . . .   4
     3.1.  C-to-AS:  . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  C-to-RS: POST to authz-info endpoint  . . . . . . . . . .   4
     3.3.  RS-to-C: 2.01 (Created) . . . . . . . . . . . . . . . . .   4
     3.4.  Not Supported . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  OAuth Parameters Registry . . . . . . . . . . . . . . . .   5
     5.2.  OAuth Parameters CBOR Mappings Registry . . . . . . . . .   6
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   In the OSCORE profile, the client and resource server receive the
   OSCORE Sender and Recipient Identifiers from the AS.  This has some
   limitations, especially if the OSCORE profile is used in conjuction
   with other mechamisms that also derive identifiers, in which case
   either collisions would happen, or longer identifiers need to be used
   as a result.  This document describes a way to negotiate the
   identifiers so that collisions does not happen even if other
   authentication mechanisms are used.

1.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   Readers are expected to be familiar with the terms and concepts
   described in [I-D.ietf-ace-oauth-authz]
   [I-D.ietf-ace-oscore-profile], such as Authorization Server (AS) and
   Resource Server (RS).

   Readers are expected to be familiar with the terms and concepts
   described in [RFC8613], especially on the use of Sender, Recipient
   and Context Identifiers.

Palombini                Expires March 25, 2021                 [Page 2]
Internet-Draft      Id Negotiation for OSCORE Profile     September 2020

2.  Background

   TODO: introduce OSCORE Sender and Recipient Identifiers and how they
   are used in OSCORE.

   The OSCORE profile specifies that the AS assigns and sends the OSCORE
   Sender and Recipient Identifiers to both Client and RS, together with
   the rest of the input material to derive the complete OSCORE Security
   Context.  That is done by including these identifiers in the Access
   Token and Access Information response to the Client.  The access
Show full document text