Support zone id when parsing / formatting SocketAddrV6
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
SocketAddrV6 contains a field scope_id (AKA zone id in RFCs).
In RFC4007, a textual representation for an IPv6 address with a zone id is specified, where the zone id is appended to the ipv6 address with % as a separator.
I think it would be very useful and quite easy to add parsing of a numeric zone id to read_socket_addr_v6.
For improved usability, adding support for interface names would be nice, but those would need to be converted to interface indices using OS specific interfaces (like libc::if_nametoindex on linux).
When formatting a SocketAddrV6, the zone id could be printed if it's not 0. (But that could be seen as an incompatible change.)
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 with the SocketAddrV6 scope_id field and the read_socket_addr_v6 entry point described in the issue, then review RFC4007 section 11. Define the treatment of numeric zone IDs, interface names, and formatting when scope_id is nonzero; the work is complete when those choices are specified and their compatibility implications are resolved.
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
- Mostly clear
- Newbie friendliness
- 25/100