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.

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

[Tracking Issue] Experimental WebTransport Transport #1717

Closed
10 tasks done
BigLep opened this issue Aug 23, 2022 · 3 comments
Closed
10 tasks done

[Tracking Issue] Experimental WebTransport Transport #1717

BigLep opened this issue Aug 23, 2022 · 3 comments
Assignees
Labels
P0 Critical: Tackled by core team ASAP

Comments

@BigLep
Copy link
Contributor

BigLep commented Aug 23, 2022

Done Criteria

WebTransport is another full-functioning transport in go-libp2p.
Two go-libp2p nodes can establish a connection using WebTransport following the spec.
The implementation is unit tested.
We have interoperability tests between versions.
libp2p documentation is updated for discoverability of this functionality

Why Important

This is covered more in the spec, but WebTransport provides a performant way for browsers (Chromium currently) to connect with the rest of the libp2p network.

Tasks

Notes

  1. Connectivity with other implementations will be added once they are created.
  2. This is intended to be a tracking issue that can link other issues and PRs to for delivering this work.
@marten-seemann marten-seemann changed the title [Tracking Issue] WebTransport Transport [Tracking Issue] Experimental WebTransport Transport Aug 23, 2022
@BigLep
Copy link
Contributor Author

BigLep commented Aug 23, 2022

@marten-seemann @MarcoPolo @p-shahi : I created this issue so we can taskify the WebTrasnport work. Please go ahead and add the relevant tasks to pull this effort off.

@marten-seemann
Copy link
Contributor

Just pointing out that our WebTransport will be marked as "experimental" at first. This means that we won't make any guarantees regarding backwards-compatibility as the IETF draft evolves towards RFC status. If the changes between two draft versions are too large (and too cumbersome to support at the same time), we might decide to drop support for the older version.

@p-shahi
Copy link
Member

p-shahi commented Nov 4, 2022

The last remaining open item for this issue was " initial interop with js-libp2p (manual testing is ok for now)" which is accomplished by this demo:
https://github.com/libp2p/js-libp2p-webtransport/tree/main/examples/fetch-file-from-kubo

Therefore, I am closing this issue.
Follow up work is tracked in #1827

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P0 Critical: Tackled by core team ASAP
Projects
Archived in project
Development

No branches or pull requests

3 participants