Subject: [Id-event] Fwd: New Version Notification for draft-ietf-secevent-token-01.txt

From: Phil Hunt <[email-masked]>
Date: Thu, 9 Mar 2017 21:21:00 -0800

This update includes the terminology refinements discussed last week plus the editorial feedback from Yaron.

The draft does not include the recent discussion on sub/iss handling, nor does it include AT/IDToken/SET differentiation. As proposed by Yaron, we should keep discussing and work on it during the Chicago meeting.

As far as I remember this revision includes only editorial changes.

Phil

Oracle Corporation, Identity Cloud Architect & Standards
@independentid
www.independentid.com <http://www.independentid.com/>[email-masked] <mailto:[email-masked]>

> Begin forwarded message:
> 
> From: [email-masked]
> Subject: New Version Notification for draft-ietf-secevent-token-01.txt
> Date: March 9, 2017 at 9:15:25 PM PST
> To: "Phil Hunt" <[email-masked]>, "Morteza Ansari" <[email-masked]>, "Michael B. Jones" <[email-masked]>, "Michael Jones" <[email-masked]>, <[email-masked]>, "William Denniss" <[email-masked]>
> 
> 
> A new version of I-D, draft-ietf-secevent-token-01.txt
> has been successfully submitted by Phil Hunt and posted to the
> IETF repository.
> 
> Name:		draft-ietf-secevent-token
> Revision:	01
> Title:		Security Event Token (SET)
> Document date:	2017-03-09
> Group:		secevent
> Pages:		18
> URL:            https://www.ietf.org/internet-drafts/draft-ietf-secevent-token-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-secevent-token/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-secevent-token-01
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-secevent-token-01
> 
> Abstract:
>   This specification defines the Security Event Token, which may be
>   distributed via a protocol such as HTTP.  The Security Event Token
>   (SET) specification profiles the JSON Web Token (JWT), which can be
>   optionally signed and/or encrypted.  A SET describes a statement of
>   fact from the perspective of an issuer that it intends to share with
>   one or more receivers.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>