oxidecomputer / oxidecomputer/progenitor
Support for scoped IPv6 link-local addresses.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 136
- Avg merge
- 8h 36m
- Merged PRs (30d)
- 14
Description
Progenitor-generated clients use the reqwest crate, which uses the url crate under the hood for URL representation. The url crate has stated that support for scoped addresses is a #wontfix issue. This prevents the use of progenitor-generated clients on multi-homed systems where use of link-local addresses is required.
Concretely, this prevents use of progenitor-generated clients for our core routing protocol, where prefix exchange takes place over link-local addresses.
In building out the routing protocol machinery, I tried a number of Rust HTTP clients, and hyper was the only one I found to support link-local addressing.
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 by tracing how generated Rust clients select and use their HTTP client and review the linked reqwest and url discussions about scoped addresses. Done means generated clients can use scoped IPv6 link-local URLs, with coverage for that scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100