libp2p / libp2p/developer-meetings
[Protocol Design] Protocol Negotiation 2.0
@Stebalien is already working on this.
Since Jun 22, 2018.
- Dominant language
- No language data
- Stars
- 7
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
[Protocol Design] Protocol Negotiation 2.0
Name: @Stebalien
Length (choose one): 30m: 5 minute presentation, 25 minute discussion
Title (~1-7 words): Protocol Negotiation 2.0
Abstract (1 sentence up to a couple paragraphs, as you prefer):
Multistream select is currently inefficient both in terms of round trips and bandwidth, handles things like TCP's simultaneous connect poorly, and isn't usable for packet connections. Incidentally, the bandwidth inefficiency discourages long protocol names like /ipfs/QmId/path/to/my/protocol/RFC. Supporting names like this is a goal of the protocol.
I plan on presenting a new protocol negotiation protocol and hope to present an upgrade path (but that'll probably take some discussion).
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.
Assessment
This issue has not been assessed yet.