oxidecomputer / oxidecomputer/maghemite

Use progenitor-based client once scoped link-local v6 addresses are supported.

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

want
Dominant language
Rust
Stars
94
Forks
6
Avg merge
1d 8h
Merged PRs (30d)
12

Description

The code that we currently use for sending requests to peer routers for prefix exchange uses hyper and manual message construction.

https://github.com/oxidecomputer/maghemite/blob/60a08589b2ef44f1f4b9b24c56e8e331639a85c2/ddm/src/exchange.rs#L109-L118

https://github.com/oxidecomputer/maghemite/blob/60a08589b2ef44f1f4b9b24c56e8e331639a85c2/ddm/src/exchange.rs#L165-L178

This is because progenitor-based clients do not currently support scoped v6 addresses.

When this is addressed, we should switch to using a progenitor-based client to get more compile time safety and make things less error prone.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking progenitor issue 296 to confirm scoped IPv6 address support, then inspect ddm/src/exchange.rs at the linked lines. The work is complete when prefix-exchange requests use a progenitor-based client instead of hyper and manual message construction.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
networking
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.