Security Event Token (SET)
RFC 8417

Document Type RFC - Proposed Standard (July 2018; No errata)
Last updated 2018-07-09
Replaces draft-hunt-idevent-token
Stream IETF
Formats plain text pdf html bibtex
Reviews GENART will not review this version
Stream WG state Submitted to IESG for Publication
Document shepherd Yaron Sheffer
Shepherd write-up Show (last changed 2018-03-05)
IESG IESG state RFC 8417 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Benjamin Kaduk
Send notices to Yaron Sheffer <yaronf.ietf@gmail.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                      P. Hunt, Ed.
Request for Comments: 8417                                        Oracle
Category: Standards Track                                       M. Jones
ISSN: 2070-1721                                                Microsoft
                                                              W. Denniss
                                                                  Google
                                                               M. Ansari
                                                                   Cisco
                                                               July 2018

                       Security Event Token (SET)

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 is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8417.

Hunt, et al.                 Standards Track                    [Page 1]
RFC 8417                           SET                         July 2018

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.

Hunt, et al.                 Standards Track                    [Page 2]
RFC 8417                           SET                         July 2018

Table of Contents

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