8000 p2p: QUIC transport [tracking issue] · Issue #4302 · cometbft/cometbft · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
p2p: QUIC transport [tracking issue] #4302
Open
@melekes

Description

@melekes

Feature Request

Summary

Currently, we're using TCP as our default transport protocol. QUIC has a few benefits compared to TCP:

  • no head-of-line blocking
  • built-in streams (no need for out-of-protocol multiplexing)
  • 0-RTT handshake

Furthermore, adopting QUIC will eliminate the need for custom encryption (SecretConnection) and framing. There is nothing terrible about custom encryption except that it's custom. On the other hand, custom framing interferes with the underlying transport and prevents us from fully utilizing the underlying connection buffers.

High-level steps

  • Extract transport from the p2p package
  • Allow for different protocols in NetAddr
  • Implement QUIC transport
  • Evaluate QUIC and
  • Support both TCP and QUIC in v1, but mark TCP as deprecated
  • Drop support for TCP in v2
    OR
  • Drop QUIC if its performance and stability are not up to par

Execution steps

Steps

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestp2ptrackingA complex issue broken down into sub-problems

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0