oxidecomputer / oxidecomputer/maghemite
bgp: consider implementing RFC 7607 handling for ASN 0
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 6
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 12
Description
RFC 7607 provides explicit guidance for the handling of ASN 0, which is registered by IANA as "reserved."
This states the expected handling for ASN 0 as it relates to UPDATE and OPEN messages, particularly around the use of ASN 0 in the AS_PATH and AGGREGATOR / AS4_AGGREGATOR path attributes.
We should consider widening the use of the Asn type with codified restrictions on the use of ASN 0.
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 RFC 7607 and locating the Rust Asn type and its uses in UPDATE and OPEN message handling. Trace how ASN 0 currently appears in AS_PATH, AGGREGATOR, and AS4_AGGREGATOR attributes. Done means the RFC’s ASN 0 restrictions are codified consistently and covered by tests for the affected message and path-attribute cases.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100