Use of a CWT identifier as a Confirmation Method
draft-schaad-cnf-cwt-id-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
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)
Network Working Group                                          J. Schaad
Internet-Draft                                            August Cellars
Intended status: Experimental                           October 22, 2018
Expires: April 25, 2019

            Use of a CWT identifier as a Confirmation Method
                       draft-schaad-cnf-cwt-id-00

Abstract

   TBD

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 25, 2019.

Copyright Notice

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

Schaad                   Expires April 25, 2019                 [Page 1]
Internet-Draft             CWT ID Confirmation              October 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions Used in This Document . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  CWT Id Confirmation Method  . . . . . . . . . . . . . . . . .   3
   4.  CWT Id in AS Response . . . . . . . . . . . . . . . . . . . .   3
   5.  Processing Rules for the Issuer of a CWT Id Confirmation
       Method  . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Processing Rules for the CWT Id Confirmation Method . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   In many cases an authorization in the form of a COSE Web Token (CWT)
   [RFC8392] will be issued in the ACE OAuth [I-D.ietf-ace-oauth-authz]
   framework with a minimal set of privileges and a Proof-of-Possession
   claim [I-D.ietf-ace-cwt-proof-of-possession].  It may then become
   necessary to issue a new token for a shorter period with more
   capabilities, but use the same information for validation.  In these
   cases it makes sense to issue a new authorization token which refers
   the the first token to provide the additional capabilities.  This
   document defines a new confirmation type that allows this type of
   referencing to be done.

   This differs from the refresh token in that the new token will be
   limited to the duration of the existing CWT, while a new POP CWT
   would be issued when using a refresh token.

1.1.  Conventions Used in This Document

   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.

2.  Terminology

   o  "Relying Party" is used in this document to refer to the party
      which is relying on the contents of a CWT in order to make a
      security decision.  In other OAuth documents, this is normally
      referred to as the XXXXXX.

Schaad                   Expires April 25, 2019                 [Page 2]
Internet-Draft             CWT ID Confirmation              October 2018

   o  "Referenced CWT" is used to denote the CWT which is referred to or
      referenced by a referencing CWT.  The referenced CWT has a
      confirmation type with the POP keying information in it.

   o  "Referencing CWT" is used to denote the CWT which is making a
      reference to a second CWT.  The referencing CWT contains the
      confirmation type defined in this document.

3.  CWT Id Confirmation Method

   The CWT Id confirmation method is identified by TBD1 in the 'cnf'
   element (defined in [I-D.ietf-ace-cwt-proof-of-possession].  For use
Show full document text