Skip to content
This repository has been archived by the owner on Feb 23, 2022. It is now read-only.

Investigate QUIC and the unreliable datagram extension for peer to peer #198

Closed
zmanian opened this issue Feb 4, 2019 · 4 comments
Closed
Labels
C:p2p Component: P2P, networking S:proposal Status: Proposal

Comments

@zmanian
Copy link
Contributor

zmanian commented Feb 4, 2019

The IETF QUIC (a UDP based protocol which combines some characteristics of connections and TLS) is also potentially having datagram semantics.

It also includes a datagram semantics over the same connection.

This will eliminate RTT overhead on sending votes to peers.
https://datatracker.ietf.org/doc/draft-pauly-quic-datagram/?include_text=1

@thanethomson
Copy link

Since there's been talk of moving to libp2p, would the best way to go about doing this be to contribute an implementation of the draft spec to go-libp2p-quic-transport? Or would we want to create our own implementation from scratch?

@liamsi
Copy link
Contributor

liamsi commented Feb 5, 2019

Speaking of libp2p: I heard rumours about adding something more noise like to libp2p (I could not find any spec etc yet though).
Some background https://forum.web3.foundation/t/transport-layer-authentication-libp2ps-secio/69

@tac0turtle
Copy link
Contributor

tac0turtle commented Sep 28, 2020

Should issues like these be moved to the spec repo for further investigation?

@tac0turtle tac0turtle transferred this issue from tendermint/tendermint Oct 26, 2020
@tac0turtle tac0turtle added C:p2p Component: P2P, networking S:proposal Status: Proposal labels Oct 26, 2020
@cmwaters
Copy link
Contributor

QUIC is being considered as part of the LibP2P migration so I think it's fine to close this issue. More information can be found in this ADR

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
C:p2p Component: P2P, networking S:proposal Status: Proposal
Projects
None yet
Development

No branches or pull requests

5 participants