Add support for ip6zone protocol in quic transport
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.8k
- Forks
- 320
- Avg merge
- 11d 15h
- Merged PRs (30d)
- 1
Description
It would be great, if quic (and maybe other transports as well) had support for the ip6zone protocol, so that it supports multiaddresses like these:
/ip6/fe80::9700:803e:ca65:66e8:c21/ip6zone/wlan0/udp/12345/quic-v1
This would enable usage of libp2p on local networks without any IP address assignment by utilizing the inherent link-local addresses of the peers. Currently, this isn't possible, because the Unix socket API requires the scope_id of a socket_addr to be set to the index of the network interface which should be used to talk to link-local IP addresses, but no libp2p transport supports this.
Ideally, quic would support interface indices and on Unix systems additionally network interface names as the value of ip6zone.
I have a working prototype of this over at the rust implementation: https://github.com/libp2p/rust-libp2p/pull/5609
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 example multiaddress and the Unix socket scope_id requirement described in the issue, then review the Rust prototype in libp2p/rust-libp2p PR 5609. Done means the specification defines ip6zone handling for QUIC, including interface indices and Unix interface names, and clarifies whether other transports are covered.
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