Security Event Token (SET)
draft-ietf-secevent-token-09

Document Type Active Internet-Draft (secevent WG)
Last updated 2018-04-19 (latest revision 2018-04-17)
Replaces draft-hunt-idevent-token
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Yaron Sheffer
Shepherd write-up Show (last changed 2018-03-05)
IESG IESG state In Last Call (ends 2018-05-03)
Consensus Boilerplate Yes
Telechat date On agenda of 2018-05-10 IESG telechat
Responsible AD Benjamin Kaduk
Send notices to Yaron Sheffer <yaronf.ietf@gmail.com>
IANA IANA review state IANA - Review Needed
IANA action state None
Security Events Working Group                               P. Hunt, Ed.
Internet-Draft                                                    Oracle
Intended status: Standards Track                                M. Jones
Expires: October 19, 2018                                      Microsoft
                                                              W. Denniss
                                                                  Google
                                                               M. Ansari
                                                                   Cisco
                                                          April 17, 2018

                       Security Event Token (SET)
                      draft-ietf-secevent-token-09

Abstract

   This specification defines the Security Event Token (SET) data
   structure.  A SET describes statements of fact from the perspective
   of an issuer about a subject.  These statements of fact represent an
   event that occurred directly to or about a security subject, for
   example, a statement about the issuance or revocation of a token on
   behalf of a subject.  This specification is intended to enable
   representing security- and identity-related events.  A SET is a JSON
   Web Token (JWT), which can be optionally signed and/or encrypted.
   SETs can be distributed via protocols such as HTTP.

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 October 19, 2018.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Hunt, et al.            Expires October 19, 2018                [Page 1]
Internet-Draft          draft-ietf-secevent-token             April 2018

   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.

Table of Contents

   1.  Introduction and Overview . . . . . . . . . . . . . . . . . .   3
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   4
     1.2.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  The Security Event Token (SET)  . . . . . . . . . . . . . . .   5
     2.1.  Illustrative Examples . . . . . . . . . . . . . . . . . .   6
       2.1.1.  SCIM Example  . . . . . . . . . . . . . . . . . . . .   6
       2.1.2.  Logout Example  . . . . . . . . . . . . . . . . . . .   8
       2.1.3.  Consent Example . . . . . . . . . . . . . . . . . . .   8
       2.1.4.  RISC Example  . . . . . . . . . . . . . . . . . . . .   9
     2.2.  Core SET Claims . . . . . . . . . . . . . . . . . . . . .  10
     2.3.  Explicit Typing of SETs . . . . . . . . . . . . . . . . .  12
     2.4.  Security Event Token Construction . . . . . . . . . . . .  13
   3.  Requirements for SET Profiles . . . . . . . . . . . . . . . .  14
   4.  Preventing Confusion between SETs and other JWTs  . . . . . .  15
     4.1.  Distinguishing SETs from ID Tokens  . . . . . . . . . . .  16
     4.2.  Distinguishing SETs from Access Tokens  . . . . . . . . .  16
     4.3.  Distinguishing SETs from other kinds of JWTs  . . . . . .  17
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
     5.1.  Confidentiality and Integrity . . . . . . . . . . . . . .  18
     5.2.  Delivery  . . . . . . . . . . . . . . . . . . . . . . . .  18
     5.3.  Sequencing  . . . . . . . . . . . . . . . . . . . . . . .  18
     5.4.  Timing Issues . . . . . . . . . . . . . . . . . . . . . .  19
     5.5.  Preventing Confusion  . . . . . . . . . . . . . . . . . .  19
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  19
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
     7.1.  JSON Web Token Claims Registration  . . . . . . . . . . .  20
       7.1.1.  Registry Contents . . . . . . . . . . . . . . . . . .  20
     7.2.  Media Type Registration . . . . . . . . . . . . . . . . .  20
Show full document text