Add protocol version and variant identifier
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Originally submitted by Nat (Nat Sakimura) on 2022-01-26
It probably is a good idea to have a parameter to state that the messages involved is for FAPI v.2 Baseline so that appropriate verification can be invoked by the receiver of the message, especially as it is there v.2.
Bitbucket status: open
Bitbucket origin: issue 469
Contributor guide
No contributing guide indexed for this repository
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
The issue does not identify a file, test, or entry point. Start by reviewing the FAPI v2 Baseline message and verification specifications, then clarify the proposed protocol-version and variant parameters with the maintainers; the work is done when their names, placement, and verification behavior are specified and accepted.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100