Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify expected response when "state" is incorrect for Verification event #171

Closed
FragLegs opened this issue May 16, 2024 · 1 comment · Fixed by #182
Closed

Clarify expected response when "state" is incorrect for Verification event #171

FragLegs opened this issue May 16, 2024 · 1 comment · Fixed by #182
Assignees
Labels
bug Something isn't working spec:SSF v3 Address this issue before the v3 cutoff (June 15, 2024)

Comments

@FragLegs
Copy link
Contributor

In section 7.1.4.1, the SSF spec says that if the Receiver requests a Verification event with a state value and the Transmitter sends an incorrect state in the subsequent Verification event, the Receiver should respond with "setData".

Upon receiving a Verification event, the Event Receiver SHALL parse the SET and validate its claims. In particular, the Event Receiver SHALL confirm that the value for "state" is as expected. If the value of "state" does not match, an error response of "setData" SHOULD be returned (see Section 2.3 of {{RFC8935}} or {{RFC8936}}).

It is unclear what is being referenced and how exactly the Receiver should respond. We should add further clarification.

@FragLegs FragLegs added bug Something isn't working spec:SSF v3 Address this issue before the v3 cutoff (June 15, 2024) labels May 16, 2024
@tulshi
Copy link
Contributor

tulshi commented May 23, 2024

Define a new registry entry for section 7.1 of RFC8935 and include that in the IANA considerations of this spec.

@FragLegs FragLegs linked a pull request Jun 6, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working spec:SSF v3 Address this issue before the v3 cutoff (June 15, 2024)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants