Subject: [Id-event] Security Event Token (SET) delivery specifications updated

From: Mike Jones <[email-masked]>
Date: Tue, 23 Oct 2018 23:19:52 +0000

Now that the Security Event Token (SET) specification is RFC 8417<http://self-issued.info/?p=1891>, the SecEvent working group<https://datatracker.ietf.org/group/secevent/charter/> is working on defining the SET delivery mechanisms.  This week, both the push-based and poll-based SET delivery specs have been updated to simplify their exposition and reduce duplication of text between the drafts.  Thanks to Annabelle Backman for doing the bulk of the recent work on the push-based delivery spec.  The latest versions of both specs contain these updates:

  *   Addressed problems identified in my 18-Jul-18 review message titled "Issues for both the Push and Poll Specs".
  *   Changes to align terminology with RFC 8417, for instance, by using the already defined term SET Recipient rather than SET Receiver.
  *   Applied editorial and minor normative corrections.
  *   Updated Marius Scurtescu's contact information.

In addition, the latest version of the poll delivery spec also contains this update:

  *   Begun eliminating redundancies between this specification and "Push-Based Security Event Token (SET) Delivery Using HTTP", referencing, rather that duplicating common normative text.

The specifications are available at:

  *   https://tools.ietf.org/html/draft-ietf-secevent-http-push-03
  *   https://tools.ietf.org/html/draft-ietf-secevent-http-poll-01

HTML-formatted versions are also available at:

  *   http://self-issued.info/docs/draft-ietf-secevent-http-push-03.html
  *   http://self-issued.info/docs/draft-ietf-secevent-http-poll-01.html

                                                         -- Mike

P.S.  This notice was also posted at http://self-issued.info/?p=1927 and as @selfissued<https://twitter.com/selfissued>.