draft-ietf-secevent-subject-identifiers-01.txt   draft-ietf-secevent-subject-identifiers-02.txt 
Security Events Working Group A. Backman, Ed. Security Events Working Group A. Backman, Ed.
Internet-Draft Amazon Internet-Draft Amazon
Intended status: Standards Track M. Scurtescu Intended status: Standards Track M. Scurtescu
Expires: April 25, 2019 Google Expires: April 26, 2019 Coinbase
October 22, 2018 October 23, 2018
Subject Identifiers for Security Event Tokens Subject Identifiers for Security Event Tokens
draft-ietf-secevent-subject-identifiers-01 draft-ietf-secevent-subject-identifiers-02
Abstract Abstract
Security events communicated within Security Event Tokens may support Security events communicated within Security Event Tokens may support
a variety of identifiers to identify the subject and/or other a variety of identifiers to identify the subject and/or other
principals related to the event. This specification formalizes the principals related to the event. This specification formalizes the
notion of subject identifiers as named sets of well-defined claims notion of subject identifiers as named sets of well-defined claims
describing the subject, a mechanism for representing subject describing the subject, a mechanism for representing subject
identifiers within a [JSON] object such as a JSON Web Token [JWT] or identifiers within a [JSON] object such as a JSON Web Token [JWT] or
Security Event Token [SET], and a registry for defining and Security Event Token [SET], and a registry for defining and
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 25, 2019. This Internet-Draft will expire on April 26, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 29 skipping to change at page 4, line 29
including international dialing prefix, formatted according to E.164 including international dialing prefix, formatted according to E.164
[E164]. The "phone" claim is REQUIRED and MUST NOT be null or empty. [E164]. The "phone" claim is REQUIRED and MUST NOT be null or empty.
The Phone Number Subject Identifier Type is identified by the name The Phone Number Subject Identifier Type is identified by the name
"phone". "phone".
Below is a non-normative example Subject Identifier for the Email Below is a non-normative example Subject Identifier for the Email
Subject Identifier Type: Subject Identifier Type:
{ {
"subject_type": "phone", "subject_type": "phone",
"phone": "+1 (206) 555-0100", "phone": "+12065550100",
} }
Figure 2: Example: Subject Identifier for the Phone Number Subject Figure 2: Example: Subject Identifier for the Phone Number Subject
Identifier Type. Identifier Type.
3.3. Issuer and Subject Subject Identifier Type 3.3. Issuer and Subject Subject Identifier Type
The Issuer and Subject Subject Identifier Type describes a subject The Issuer and Subject Subject Identifier Type describes a subject
that is an account identified by a pair of "iss" and "sub" claims, as that is an account identified by a pair of "iss" and "sub" claims, as
defined by [JWT]. These claims MUST follow the formats of the "iss" defined by [JWT]. These claims MUST follow the formats of the "iss"
skipping to change at page 10, line 5 skipping to change at page 9, line 49
(This section to be removed by the RFC Editor before publication as (This section to be removed by the RFC Editor before publication as
an RFC.) an RFC.)
Draft 00 - AB - First draft Draft 00 - AB - First draft
Draft 01 - AB: * Added reference to RFC 5322 for format of "email" Draft 01 - AB: * Added reference to RFC 5322 for format of "email"
claim. * Renamed "iss_sub" type to "iss-sub". * Renamed claim. * Renamed "iss_sub" type to "iss-sub". * Renamed
"id_token_claims" type to "id-token-claims". * Added text specifying "id_token_claims" type to "id-token-claims". * Added text specifying
the nature of the subjects described by each type. the nature of the subjects described by each type.
Draft 02 - AB: * Corrected format of phone numbers in examples. *
Updated author info.
Authors' Addresses Authors' Addresses
Annabelle Backman (editor) Annabelle Backman (editor)
Amazon Amazon
Email: richanna@amazon.com Email: richanna@amazon.com
Marius Scurtescu Marius Scurtescu
Google Coinbase
Email: mscurtescu@google.com Email: marius.scurtescu@coinbase.com
 End of changes. 7 change blocks. 
6 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/