[Openid-specs-ab] Fwd: New Version Notification for draft-hunt-idevent-token-03.txt

Vladimir Dzhuvinov vladimir at connect2id.com
Fri Aug 19 14:41:56 UTC 2016


I just went through the new version, the text has a much better
structure and clarity now.

Thanks everyone!


On 18/08/16 19:10, Phil Hunt via Openid-specs-ab wrote:
> Draft 03 has been published.
>
> This includes editorial clarifications to:
> * Define the outer layer as a SET “envelope”, vs embedded JSON as “payload”
> * Clarify that only a single event should be conveyed plus optional extensions.
> * General edits to improve readability
> * Register the “events” claim as a  JWT attribute (see IANA considerations)
>
> Many thanks to Mike and Sarah and who contributed significant editorial feedback.
>
> Phil
>
> @independentid
> www.independentid.com <http://www.independentid.com/>phil.hunt at oracle.com <mailto:phil.hunt at oracle.com>
>
>
>
>
>
>> Begin forwarded message:
>>
>> From: internet-drafts at ietf.org
>> Subject: New Version Notification for draft-hunt-idevent-token-03.txt
>> Date: August 18, 2016 at 9:03:35 AM PDT
>> To: "Michael B. Jones" <mbj at microsoft.com>, "William Denniss" <wdenniss at google.com>, "Phil Hunt" <phil.hunt at yahoo.com>, "Morteza Ansari" <morteza.ansari at cisco.com>, "Michael Jones" <mbj at microsoft.com>
>>
>>
>> A new version of I-D, draft-hunt-idevent-token-03.txt
>> has been successfully submitted by Phil Hunt and posted to the
>> IETF repository.
>>
>> Name:		draft-hunt-idevent-token
>> Revision:	03
>> Title:		Security Event Token (SET)
>> Document date:	2016-08-18
>> Group:		Individual Submission
>> Pages:		16
>> URL:            https://www.ietf.org/internet-drafts/draft-hunt-idevent-token-03.txt
>> Status:         https://datatracker.ietf.org/doc/draft-hunt-idevent-token/
>> Htmlized:       https://tools.ietf.org/html/draft-hunt-idevent-token-03
>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-hunt-idevent-token-03
>>
>> 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) and may be
>>   optionally signed and/or encrypted.  A SET describes a statement of
>>   fact that may be shared by an event publisher with event subscribers.
>>
>>
>>
>>
>> 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
>>
>
>
>
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-ab

-- 
Vladimir Dzhuvinov :: vladimir at connect2id.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20160819/1569e53f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3711 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20160819/1569e53f/attachment.p7s>


More information about the Openid-specs-ab mailing list