oxidecomputer / oxidecomputer/maghemite
Consider using MP_UNREACH_NLRI to withdraw IPv4 Unicast routes after negotiating ENHE
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 6
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 12
Description
We currently encode IPv4 Unicast advertisements in MP_REACH_NLRI if we've negotiated ENHE (v6 next-hops), but IPv4 Unicast withdrawals are still encoded via the traditional withdrawn routes field (pre MP-BGP field).
So far I haven't seen interop issues (FRR, Arista EOS) because of this, but we may want to consider encoding v4 uni withdrawals in MP_UNREACH_NLRI when we've negotiated ENHE to avoid possible problems later.
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
Locate the ENHE negotiation path and the IPv4 Unicast withdrawal encoding, then compare the existing traditional withdrawn-routes handling with MP_UNREACH_NLRI. Check the relevant protocol tests or interoperability coverage; done means withdrawals use MP_UNREACH_NLRI after ENHE negotiation without regressing existing route advertisements.
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
- 42/100