< draft-backman-secevent-token-02.txt		draft-backman-secevent-token-03.txt >
	skipping to change at page 1, line 14 ¶		skipping to change at page 1, line 14 ¶
	Internet-Draft Amazon		Internet-Draft Amazon
	Intended status: Standards Track W. Denniss		Intended status: Standards Track W. Denniss
	Expires: June 2, 2018 Google		Expires: June 2, 2018 Google
	M. Ansari		M. Ansari
	Cisco		Cisco
	M. Jones		M. Jones
	Microsoft		Microsoft
	November 29, 2017		November 29, 2017
	Security Event Token (SET)		Security Event Token (SET)
	draft-backman-secevent-token-02		draft-backman-secevent-token-03
	Abstract		Abstract
	This specification defines the Security Event Token, which may be		This specification defines the Security Event Token, which may be
	distributed via a protocol such as HTTP. The Security Event Token		distributed via a protocol such as HTTP. The Security Event Token
	(SET) specification profiles the JSON Web Token (JWT), which can be		(SET) specification profiles the JSON Web Token (JWT), which can be
	optionally signed and/or encrypted. A SET describes a statement of		optionally signed and/or encrypted. A SET describes a statement of
	fact from the perspective of an issuer that it intends to share with		fact from the perspective of an issuer that it intends to share with
	one or more receivers.		one or more receivers.
	skipping to change at page 22, line 35 ¶		skipping to change at page 22, line 35 ¶
	The editors would like to thank Phil Hunt for his SET draft - on		The editors would like to thank Phil Hunt for his SET draft - on
	which much of this specification is based - and his continuing		which much of this specification is based - and his continuing
	contributions to this draft.		contributions to this draft.
	The editors would like to thank the participants on the IETF secevent		The editors would like to thank the participants on the IETF secevent
	mailing list and related working groups for their support of this		mailing list and related working groups for their support of this
	specification.		specification.
	Appendix B. Change Log		Appendix B. Change Log
	Draft 00 - A. Backman - First Draft		Draft 00 - A. Backman - Forked from draft-ietf-secevent-token-03
			o Cleaned up text in section 2.
			o Simplified JWT claim descriptions in section 2.1.
			o Removed "txn" claim.
			o Replaced multi-part "events" claim with "event" claim that
			contains a single event payload.
			o Removed references to JWT "sub" claim and added
			"event.event_subject" claim.
			o Replaced JWT "toe" claim with "event.event_time" claim.
			o Added Subject Identifier Types and defined "implicit", "email",
			"phone_number", and "iss_sub" types.
			o Added Related Events event definition.
			o Added guidance for event extensions.
	Draft 01 - A. Backman		Draft 01 - A. Backman
	o Added Acknowledgements section.		o Added Acknowledgements section.
	o Relaxed event_subject claim definition to allow usage of JWT "sub"		o Relaxed event_subject claim definition to allow usage of JWT "sub"
	claim.		claim.
	Draft 02 - A. Backman		Draft 02 - A. Backman
End of changes. 2 change blocks.
	2 lines changed or deleted		23 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/