oxidecomputer / oxidecomputer/maghemite
BGP should set DSCP bits
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 6
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 12
Description
RFC 4271 Appendix E:
If a local system TCP user interface supports setting the DSCP field
[RFC2474] for TCP connections, then the TCP connection used by BGP
SHOULD be opened with bits 0-2 of the DSCP field set to 110 (binary).
This seems simple enough to do via setsockopt, so we should consider adding support for this (default value w/ ability to override).
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
No file or test is named. Locate the BGP TCP connection setup and inspect how socket options are handled in this Rust routing stack; start with the setsockopt support referenced by the issue. Done means BGP connections use the RFC 4271 DSCP default while allowing that value to be overridden, with relevant coverage added where the existing project tests socket behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100