Better ordering of `HpkeConfigList`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 70
- Forks
- 16
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 30
Description
DAP says that the list served from /hpke_config is an "HpkeConfigList structure contains one or more HpkeConfig structures in decreasing order of preference" (1). Right now, we have no logic for deciding configuration preference. At a minimum it seems like we should prefer newer HPKE configs over older ones, on the premise that we're trying to get clients to move forward. We could also use a mechanism to indicate if a particular algorithm set is preferred.
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
Start with the code path that serves /hpke_config and read DAP section 4.7.1, linked in the issue. Define how configurations are ordered, including whether newer configs alone are preferred or algorithm sets also need an explicit preference mechanism; done should include a documented policy and coverage for the resulting order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100