Discover public address for ~non-dial `Transport` (e.g. WebRTC)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.6k
- Forks
- 1.3k
- Avg merge
- 8h 47m
- Merged PRs (30d)
- 19
Description
Description
A rust-libp2p server offering WebRTC Direct will most likely not have outgoing WebRTC Direct connections and thus not discover its public address e.g. through libp2p Identify protocol.
Motivation
A rust-libp2p server should be able to discover its public WebRTC Direct address in order to advertise it and thus enable clients (e.g. browsers) to actually connect to them.
Requirements
Open questions
Is an initial Swarm::dial to a bootstrap node at startup time via WebRTC Direct good enough? One would learn ones public address through libp2p Identify.
Are you planning to do it yourself in a pull request?
No
Contributor guide
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 WebRTC Direct specification linked in the issue, then trace how libp2p Identify and the initial Swarm::dial to a bootstrap node expose addresses. Clarify the missing requirements and determine what behavior would let a server discover and advertise its public WebRTC Direct address so browsers can connect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- audio-video-rtc, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100