Subject: [Id-event] Subscription / Stream Verification - Do we need it?

From: Phil Hunt <[email-masked]>
Date: Mon, 27 Feb 2017 15:58:15 -0800

In writing the new transmission draft, one of the features in draft-hunt-idevent-distribution was the ability for the publisher/transmitter to send test events which confirm the receiver is parsing the event successfully.  This seems particularly useful when setting up configurations where encrypted SETs will be used and trying to figure out if they are working. They can also be used as “pings” to allow operations centers to confirm the delivery system is working.

It occurs to me that we can make it optional for the publisher, but it will have to be a MUST implement by any party that receives a verify event.  That said, some profiling specs can simply agree it is not a necessary event (e.g. in a best effort scenario).  However, the way specs are written it would be hard to specify the conditions under which parties don’t care if it works well. 8-)

Is there any objection to keeping the verify event?  We can always pull it if it turns out it really isn’t needed.

Phil

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