webtransport: define how to use CA-signed certificates
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.8k
- Forks
- 320
- Avg merge
- 11d 15h
- Merged PRs (30d)
- 1
Description
WebTransport currently only defines how to use self-signedf certificates, using serverCertificateHashes.
It should be possible to use CA-signed certificates once https://github.com/w3c/webtransport/issues/411 is resolved.
Contributor guide
No contributing guide indexed for this repository
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 by reading the WebTransport specification discussion and the linked W3C issue 411 to understand the dependency and the intended CA-signed certificate behavior. Define the required specification changes only after that issue is resolved; done means the libp2p WebTransport specification clearly documents how CA-signed certificates are used.
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
- 20/100