rfc9493v3.txt		rfc9493.txt
	Internet Engineering Task Force (IETF) A. Backman, Ed.		Internet Engineering Task Force (IETF) A. Backman, Ed.
	Request for Comments: 9493 Amazon		Request for Comments: 9493 Amazon
	Category: Standards Track M. Scurtescu		Category: Standards Track M. Scurtescu
	ISSN: 2070-1721 Coinbase		ISSN: 2070-1721 Coinbase
	P. Jain		P. Jain
	Fastly		Fastly
	October 2023		December 2023
	Subject Identifiers for Security Event Tokens		Subject Identifiers for Security Event Tokens
	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 subjects related to the event.		a variety of identifiers to identify subjects related to the event.
	This specification formalizes the notion of Subject Identifiers as		This specification formalizes the notion of Subject Identifiers as
	structured information that describes a subject and named formats		structured information that describes a subject and named formats
	that define the syntax and semantics for encoding Subject Identifiers		that define the syntax and semantics for encoding Subject Identifiers
	skipping to change at line 687 ¶		skipping to change at line 687 ¶
	8.1. Security Event Identifier Formats Registry		8.1. Security Event Identifier Formats Registry
	This document defines Identifier Formats, for which IANA has created		This document defines Identifier Formats, for which IANA has created
	and maintains a new registry titled "Security Event Identifier		and maintains a new registry titled "Security Event Identifier
	Formats". Initial values for the "Security Event Identifier Formats"		Formats". Initial values for the "Security Event Identifier Formats"
	registry are given in Section 3. Future assignments are to be made		registry are given in Section 3. Future assignments are to be made
	through the Specification Required registration policy [BCP26] and		through the Specification Required registration policy [BCP26] and
	shall follow the template presented in Section 8.1.1.		shall follow the template presented in Section 8.1.1.
	It is suggested that multiple Designated Experts be appointed who are		It is suggested that multiple designated experts be appointed who are
	able to represent the perspectives of different applications using		able to represent the perspectives of different applications using
	this specification in order to enable broadly informed review of		this specification in order to enable broadly informed review of
	registration decisions.		registration decisions.
	8.1.1. Registration Template		8.1.1. Registration Template
	Format Name:		Format Name:
	The name of the Identifier Format, as described in Section 3. The		The name of the Identifier Format, as described in Section 3. The
	name MUST be an ASCII string consisting only of lowercase		name MUST be an ASCII string consisting only of lowercase
	characters ("a" - "z"), digits ("0" - "9"), underscores ("_"), and		characters ("a" - "z"), digits ("0" - "9"), underscores ("_"), and
End of changes. 2 change blocks.
	2 lines changed or deleted		2 lines changed or added
This html diff was produced by rfcdiff 1.48.