oxidecomputer / oxidecomputer/maghemite
Extend rack underlay routing protocols to support multicast address advertisement
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 6
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 12
Description
As per RFD 448:
To avoid centralizing all information through Omicron, we will plumb multicast address advertisement and underlay mechanics through to ddm and mgd accordingly, akin to the implementation work on boundary tunnel routing.
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 reading RFD 448 and the boundary tunnel routing implementation in PR 77. Trace how multicast address advertisement and underlay mechanics should pass through ddm and mgd. Done means the routing stack supports this advertisement path consistently across those components, with the relevant tests updated or added.
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
- 30/100