Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ROADMAP.md: Add isolated item for WebRTC #414

Merged
merged 3 commits into from
May 24, 2022
Merged

ROADMAP.md: Add isolated item for WebRTC #414

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cb92011
ROADMAP.md: Add isolated item for WebRTC
mxinden May 20, 2022
df4fb0c
ROADMAP.md: Reference WebTransport protocol
mxinden May 23, 2022
a6ba7c0
Merge branch 'master' into webrtc-roadmap
mxinden May 24, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 22 additions & 3 deletions ROADMAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,7 @@ third-party ownership of data.
- [✈️ WebTransport](#✈️-webtransport)
- [⏱ Full Observability](#⏱-full-observability)
- [🧪 Automated compatibility testing](#🧪-automated-compatibility-testing)
- [WebRTC](#webrtc)
- [🤝 Low latency, efficient connection handshake](#🤝-low-latency-efficient-connection-handshake)
- [🛣️ Peer Routing Records](#🛣️-peer-routing-records)
- [🗣️ Polite peering](#🗣️-polite-peering)
Expand Down Expand Up @@ -282,6 +283,27 @@ the [libp2p test-plans repository].

- [First proof of concept](https://github.com/libp2p/test-plans/pull/20)

### WebRTC

**Status**: In progress

**What?** WebRTC is a transport protocol supported by all major browsers. Those
browsers allow the establishment of connections to remote endpoints that don't
have a TLS certificate signed by a trusted certificate authority. In addition
WebRTC includes hole punching capabilities.

**Why?** In most p2p networks the majority of nodes do not have a signed TLS
certificate. With WebRTC browsers will thus be able to connect to these
previously unreachable nodes. In addition, being able to hole punch allows
mxinden marked this conversation as resolved.
Show resolved Hide resolved
browsers to connect to nodes behind firewalls and NATs e.g. other browsers. Note
that the former, namely connecting without trusted TLS certificate, can as well
be achieved with the [WebTransport](#✈️-webtransport) protocol.

**Links:**

- Tracking issue https://github.com/libp2p/specs/issues/220
- Specification draft https://github.com/libp2p/specs/pull/412

### 🤝 Low latency, efficient connection handshake

**High priority for: IPFS**
Expand Down Expand Up @@ -464,9 +486,6 @@ popular frontend tooling (webpack, parcel, etc.). Developers should be
able to cherry-pick the features to incorporate in their bundle, and
tree-shaking should produce good results.

In terms of transports, hardening our WebRTC support and enabling it by
default will bring a huge boost to general browser connectivity.

Targeting the [WASM runtime](#libp2p-as-a-wasm-library)
deserves a special mention, as we're likely to see more user interest in
this area. Finally, we should continue supporting the
Expand Down