Subject Identifiers for Security Event Tokens
draft-ietf-secevent-subject-identifiers-06

Document Type Active Internet-Draft (individual)
Last updated 2020-09-04
Replaces draft-backman-secevent-subject-identifiers
Stream (None)
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Yes
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD Benjamin Kaduk
Send notices to (None)
Security Events Working Group                            A. Backman, Ed.
Internet-Draft                                                    Amazon
Intended status: Standards Track                            M. Scurtescu
Expires: March 8, 2021                                          Coinbase
                                                      September 04, 2020

             Subject Identifiers for Security Event Tokens
               draft-ietf-secevent-subject-identifiers-06

Abstract

   Security events communicated within Security Event Tokens may support
   a variety of identifiers to identify the subject and/or other
   principals related to the event.  This specification formalizes the
   notion of subject identifiers as named sets of well-defined claims
   describing the subject, a mechanism for representing subject
   identifiers within a JSON object such as a JSON Web Token (JWT) or
   Security Event Token (SET), and a registry for defining and
   allocating names for these claim sets.

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 8, 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

Backman & Scurtescu       Expires March 8, 2021                 [Page 1]
Internet-Draft        secevent-subject-identifiers        September 2020

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . .   4
     2.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Subject Identifiers . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Subject Identifier Types versus Principal Types . . . . .   5
     3.2.  Subject Identifier Type Definitions . . . . . . . . . . .   5
       3.2.1.  Account Subject Identifier Type . . . . . . . . . . .   6
       3.2.2.  Email Subject Identifier Type . . . . . . . . . . . .   6
       3.2.3.  Phone Number Subject Identifier Type  . . . . . . . .   7
       3.2.4.  Issuer and Subject Subject Identifier Type  . . . . .   7
       3.2.5.  Aliases Subject Identifier Type . . . . . . . . . . .   8
   4.  Subject Identifiers in JWTs . . . . . . . . . . . . . . . . .   9
     4.1.  "sub_id" Claim  . . . . . . . . . . . . . . . . . . . . .   9
     4.2.  "sub_id" and "iss_sub" Subject Identifiers  . . . . . . .  11
   5.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  12
     5.1.  Identifier Correlation  . . . . . . . . . . . . . . . . .  12
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
     6.1.  Confidentiality and Integrity . . . . . . . . . . . . . .  12
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
     7.1.  Security Event Subject Identifier Types Registry  . . . .  13
       7.1.1.  Registry Location . . . . . . . . . . . . . . . . . .  13
       7.1.2.  Registration Template . . . . . . . . . . . . . . . .  13
       7.1.3.  Initial Registry Contents . . . . . . . . . . . . . .  14
       7.1.4.  Guidance for Expert Reviewers . . . . . . . . . . . .  15
     7.2.  JSON Web Token Claims Registration  . . . . . . . . . . .  16
       7.2.1.  Registry Contents . . . . . . . . . . . . . . . . . .  16
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  17
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  17
   Change Log  . . . . . . . . . . . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  19

1.  Introduction

   As described in Section 1.2 of SET [RFC8417], the subject of a
Show full document text