libp2p / libp2p/specs

Proposal: WebTransport over HTTP/2

Open
#534 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

explorative
Dominant language
No language data
Stars
1.8k
Forks
320
Avg merge
11d 15h
Merged PRs (30d)
1

Description

Current draft: https://datatracker.ietf.org/doc/draft-ietf-webtrans-http2/.

WebTransport/H2 is intended as a fallback for users that aren't able to establish a QUIC connection (most likely due to UDP blocking). It layers a WebTransport session over a single HTTP/2 stream.

Since this is just a fallback, this is only worth our time if / once the following hold true:

  • WebTransport/H3 is relied on by many users of libp2p.
  • All major browsers support the protocol.
  • The specification is stable, probably after WGLC.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked WebTransport over HTTP/2 draft and comparing it with the repository's existing specifications. Check whether WebTransport over HTTP/3 is widely relied on, major browsers support the protocol, and the specification has stabilized after WGLC. Done means reaching a project decision about whether this fallback is worth specifying.

Written by the indexing model from the issue text.

Assessment

Domain
networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.