SLA for verification event
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 78
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Implementation feedback:
We would like to perform a health check for an SSF stream, which uses the verification event on periodic basis. This design also relies on an SLA for verification event transmission times. The SSF spec does not specify how this SLA will be agreed on between a transmitter and a receiver. We think it would make sense to add SLA in the Stream Configuration similar to inactivity_timeout (https://openid.net/specs/openid-sharedsignals-framework-1_0-final.html#section-8.1.1-20 [openid.net].
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the SSF specification's Stream Configuration section and compare the proposed SLA with the existing inactivity_timeout setting. Review the three issue comments before deciding how transmitter and receiver agreement should be represented; done means reaching and documenting a clear design for the verification-event transmission SLA.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100