draft-ietf-secevent-token-12.txt   draft-ietf-secevent-token-13.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Internet-Draft Oracle Internet-Draft Oracle
Intended status: Standards Track M. Jones Intended status: Standards Track M. Jones
Expires: November 10, 2018 Microsoft Expires: November 10, 2018 Microsoft
W. Denniss W. Denniss
Google Google
M. Ansari M. Ansari
Cisco Cisco
May 9, 2018 May 9, 2018
Security Event Token (SET) Security Event Token (SET)
draft-ietf-secevent-token-12 draft-ietf-secevent-token-13
Abstract Abstract
This specification defines the Security Event Token (SET) data This specification defines the Security Event Token (SET) data
structure. A SET describes statements of fact from the perspective structure. A SET describes statements of fact from the perspective
of an issuer about a subject. These statements of fact represent an of an issuer about a subject. These statements of fact represent an
event that occurred directly to or about a security subject, for event that occurred directly to or about a security subject, for
example, a statement about the issuance or revocation of a token on example, a statement about the issuance or revocation of a token on
behalf of a subject. This specification is intended to enable behalf of a subject. This specification is intended to enable
representing security- and identity-related events. A SET is a JSON representing security- and identity-related events. A SET is a JSON
skipping to change at page 4, line 30 skipping to change at page 4, line 30
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
For purposes of readability, examples are not URL encoded. For purposes of readability, examples are not URL encoded.
Implementers MUST percent encode URLs as described in Section 2.1 of Implementers MUST percent encode URLs as described in Section 2.1 of
[RFC3986]. [RFC3986].
Throughout this document, all figures MAY contain spaces and extra Throughout this document, all figures may contain spaces and extra
line-wrapping for readability and space limitations. Similarly, some line-wrapping for readability and space limitations. Similarly, some
URIs contained within examples have been shortened for space and URIs contained within examples have been shortened for space and
readability reasons. readability reasons.
1.2. Definitions 1.2. Definitions
The following definitions are used with SETs: The following definitions are used with SETs:
Security Event Token (SET) Security Event Token (SET)
A SET is a JWT [RFC7519] conforming to this specification. A SET is a JWT [RFC7519] conforming to this specification.
skipping to change at page 25, line 23 skipping to change at page 25, line 23
Appendix A. Acknowledgments Appendix A. Acknowledgments
The editors would like to thank the members of the IETF SCIM working The editors would like to thank the members of the IETF SCIM working
group, which began discussions of provisioning events starting with group, which began discussions of provisioning events starting with
draft-hunt-scim-notify-00 in 2015. The editors would like to thank draft-hunt-scim-notify-00 in 2015. The editors would like to thank
the participants in the IETF id-event mailing list, the Security the participants in the IETF id-event mailing list, the Security
Events working group, and related working groups for their Events working group, and related working groups for their
contributions to this specification. The specification incorporates contributions to this specification. The specification incorporates
suggestions made by many people, including Annabelle Backman, John suggestions made by many people, including Annabelle Backman, John
Bradley, Alissa Cooper, Ned Freed, Dick Hardt, Russ Housley, Benjamin Bradley, Alissa Cooper, Ned Freed, Dick Hardt, Russ Housley, Benjamin
Kaduk, Mark Lizar, Alexey Melnikov, Andrew Nash, Eric Rescorla, Adam Kaduk, Mirja Kuehlewind, Mark Lizar, Alexey Melnikov, Andrew Nash,
Roach, Justin Richer, Nat Sakimura, Marius Scurtescu, and Yaron Eric Rescorla, Adam Roach, Justin Richer, Nat Sakimura, Marius
Sheffer. Scurtescu, Yaron Sheffer, and Martin Vigoureux.
Appendix B. Change Log Appendix B. Change Log
[[ to be removed by the RFC Editor before publication as an RFC ]] [[ to be removed by the RFC Editor before publication as an RFC ]]
From the original draft-hunt-idevent-token: From the original draft-hunt-idevent-token:
Draft 01 - PH - Renamed eventUris to events Draft 01 - PH - Renamed eventUris to events
Draft 00 - PH - First Draft Draft 00 - PH - First Draft
skipping to change at page 30, line 38 skipping to change at page 30, line 38
Protocol (SIP) Via Header Field Parameter to Indicate Received Protocol (SIP) Via Header Field Parameter to Indicate Received
Realm". Realm".
o Added normative references for base64url and UTF-8. o Added normative references for base64url and UTF-8.
o Section 5.1 - Changed SHOULD to MUST in "personally identifiable o Section 5.1 - Changed SHOULD to MUST in "personally identifiable
information MUST be encrypted using JWE [RFC7516] or ...". information MUST be encrypted using JWE [RFC7516] or ...".
o Section 5.2 - Changed "MUST consider" to "must consider". o Section 5.2 - Changed "MUST consider" to "must consider".
Draft 13 - ph - Added edit from Martin Vigoureaux regarding a non-
normative "MAY" in Section 1.1. Updated acknowledgements.
Authors' Addresses Authors' Addresses
Phil Hunt (editor) Phil Hunt (editor)
Oracle Corporation Oracle Corporation
Email: phil.hunt@yahoo.com Email: phil.hunt@yahoo.com
Michael B. Jones Michael B. Jones
Microsoft Microsoft
Email: mbj@microsoft.com Email: mbj@microsoft.com
URI: http://self-issued.info/ URI: http://self-issued.info/
William Denniss William Denniss
Google Google
Email: wdenniss@google.com Email: wdenniss@google.com
Morteza Ansari Morteza Ansari
Cisco Cisco
Email: morteza.ansari@cisco.com Email: morteza.ansari@cisco.com
 End of changes. 6 change blocks. 
6 lines changed or deleted 9 lines changed or added

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