Subject: [scim] Fwd: New Version Notification for draft-hunt-idevent-distribution-01.txt

From: Phil Hunt <[email-masked]>
Date: Thu, 29 Sep 2016 15:27:09 -0700

This is a substantial re-work of the distribution draft that Marius, Morteza and myself have been working on.

The following major changes:

1.  Specifies a fairly simple HTTP POST delivery method for now that provides assured delivery
2.  Proposes a registry so that new methods may be defined as needed.
3.  Profiles SCIM for subscription registration and management including appropriate metadata

This more or less should line up with the distribution objective in the charter as a starting point for discussion.

I would like to thank my co-author Marius and the OIDF RISC working group for providing substantial input into the draft.

Phil

@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-hunt-idevent-distribution-01.txt
> Date: September 29, 2016 at 3:15:05 PM PDT
> To: "Phil Hunt" <[email-masked]>, "Morteza Ansari" <[email-masked]>, "Marius Scurtescu" <[email-masked]>
> 
> 
> A new version of I-D, draft-hunt-idevent-distribution-01.txt
> has been successfully submitted by Phil Hunt and posted to the
> IETF repository.
> 
> Name:		draft-hunt-idevent-distribution
> Revision:	01
> Title:		SET Token Distribution and Subscription Management Profile
> Document date:	2016-09-29
> Group:		Individual Submission
> Pages:		30
> URL:            https://www.ietf.org/internet-drafts/draft-hunt-idevent-distribution-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-hunt-idevent-distribution/
> Htmlized:       https://tools.ietf.org/html/draft-hunt-idevent-distribution-01
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-hunt-idevent-distribution-01
> 
> Abstract:
>   The specification defines how a subscriber to a feed of security
>   events (SETs) may query for, subscribe and receive SETs from a
>   security event feed.  The specification defines a single mandatory-
>   to-implement method using HTTP Post to deliver events to registered
>   subscribers and a registry for new methods.
> 
> 
> 
> 
> 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
>