CurrentPROPOSED STANDARDIETF stream

RFC 9493: Subject Identifiers for Security Event Tokens

In plain English — editorial summary, not part of the RFC

Security events communicated within Security Event Tokens may support a variety of identifiers to identify subjects related to the event. This specification formalizes the notion of Subject Identifiers as structured information that describes a subject and named formats that define the syntax and semantics for encoding Subject Identifiers as JSON objects. It also establishes a registry for defining and allocating names for such formats as well as the JSON Web Token (JWT) "sub_id" Claim.

Document record

Document ID
RFC9493
Published
December 2023
Authors
A. Backman; M. Scurtescu; P. Jain
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
18
Also known as

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/9493-subject-identifiers-for-security-event-tokens