[Openid-specs-risc] openid/sharedsignals: New Issue opened

[github at oidf.org]

openid/sharedsignals event

Issue opened
Issue Title: Permanence of streams
https://github.com/openid/sharedsignals/issues/211

Copying discussion from meeting on 9/24: - [Tushar] the spec implicitly assumes that a stream is permanent once created. Should it support expirable streams? - [Tushar] Possible solution: verification events on a cadence - [Yair] A Rx (or Tx) can disable a stream - [Yair] As long as PUSH endpoint is returning success, nothing is wrong. But if endpoint starts sending 500, 400 etc, then Tx can do something about it. - [Yair] You cannot tell the difference between an Rx that has been sold, etc vs an Rx that is behaving well - [Yair] We shouldn't make verification event requests mandatory, but can make it optional. Possibly include a time value that indicates how long between requests before Tx kills stream. - [Shayne] I like the idea of an optional value in StreamConfiguration - [Apoorva] We could also make it any call, not just verification - [Shayne] Is that harder to implement? - [Yair] Agree that it could be any endpoint - status endpoint would work - [Shayne] That's nice because then you don't have to send unneccessary data
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20241008/6b4ab537/attachment.html>