oxidecomputer / oxidecomputer/maghemite
bgp: need handling for originated updates that exceed the max update size
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 6
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 12
Description
SessionRunner.send_update() does not have handling for generation of multiple Update messages if the full list of originated routes would cause the size of the UpdateMessage to exceed the max size. This should be added and tested (probably along with support for RFC 8654)
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 at SessionRunner.send_update() and trace how originated routes are assembled into an UpdateMessage. Review RFC 8654 alongside the existing BGP update-size handling, then add coverage for originated routes that exceed the maximum update size. Done means the routes are split across multiple Update messages and the relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100