Skip to content

roadmap: move WebTransport to Done section #460

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

Merged
marten-seemann merged 2 commits into from
Jan 31, 2023
Merged

roadmap: move WebTransport to Done section #460

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dbe9aeb
roadmap: move WebTransport to Done
marten-seemann Sep 28, 2022
0d16f46
Apply suggestions from code review
marten-seemann Jan 31, 2023
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
44 changes: 23 additions & 21 deletions ROADMAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,6 @@ third-party data ownership.
- [🚑 Self-healing networks](#-self-healing-networks)
- [📮 Offline message queue / postbox](#-offline-message-queue--postbox)
- [Evolve](#evolve)
- [✈️ WebTransport](#️-webtransport)
- [⏱ Full Observability](#-full-observability)
- [🧪 Automated compatibility testing](#-automated-compatibility-testing)
- [Stream Migration Protocol](#stream-migration-protocol)
Expand Down Expand Up @@ -217,26 +216,6 @@ roaming, etc.

These are the projects pushing the existing libp2p stack forward.

### ✈️ WebTransport

**Status**: In progress

**What?** WebTransport is a browser-API offering low-latency, bidirectional
client-server messaging running on top of QUIC. The browser API allows the
establishment of connections to servers that don't have a TLS certificate
signed by a certificate authority if the hash of the certificate is known in
advance.

**Why?** This allows libp2p nodes running in the browser (using js-libp2p) to
connect to the rest of the libp2p network.

**Links:**

- [IETF draft](https://datatracker.ietf.org/doc/draft-ietf-webtrans-http3/)
- [W3C Browser API](https://w3c.github.io/webtransport/)
- [libp2p spec discussion](https://github.com/libp2p/specs/pull/404)
- [webtransport-go](https://github.com/marten-seemann/webtransport-go/)

### ⏱ Full Observability

**What?** libp2p should expose a wide set of metrics, making it easy to
Expand Down Expand Up @@ -664,3 +643,26 @@ to the rest of the system.
vision](https://github.com/libp2p/specs/blob/master/connections/hole-punching.md).

- [NAT traversal tracking issue](https://github.com/libp2p/specs/issues/312).


### ✈️ WebTransport

**Status**: Done

**What?** WebTransport is a browser-API offering low-latency, bidirectional
client-server messaging running on top of QUIC. The browser API allows the
establishment of connections to servers that don't have a TLS certificate
signed by a certificate authority if the hash of the certificate is known in
advance.

**Why?** This allows libp2p nodes running in the browser (using js-libp2p-webtransport) to
connect to the rest of the libp2p network.

**Links:**

- [IETF draft](https://datatracker.ietf.org/doc/draft-ietf-webtrans-http3/)
- [W3C Browser API](https://w3c.github.io/webtransport/)
- [libp2p Specification](https://github.com/libp2p/specs/tree/master/webtransport)
- [webtransport-go](https://github.com/marten-seemann/webtransport-go/)
- [go-libp2p WebTransport](https://github.com/libp2p/go-libp2p/tree/master/p2p/transport/webtransport)
- [js-libp2p WebTransport](https://github.com/libp2p/js-libp2p-webtransport/)