add a QUIC blog post

[marten-seemann]

DO NOT MERGE / PUBLISH YET!

This is my first draft of a blog post about QUIC.
I'd like to ask for some feedback. Is everything understandable? Did I miss anything important?

[victorb]

Seems to be missing the header in the document to make it show up in the blog listing. Take a look at https://raw.githubusercontent.com/ipfs/blog/master/content/post/19-ipfs-0-4-3-released.md for an example of what I mean.

[lidel]

Did a first pass and added some suggestions as inline comments below:

[lidel]

Would be useful to provide info what secio is, or at least point at a relevant repo:

Suggested change

In order to establish a new encrypted connection between two hosts (the same applies to TLS 1.2 connection), the client first initiates a TCP connection. The three-way handshake necessary to establish a TCP connection takes one network roundtrip time. After that, the client initiates the cryptographic handshake (secio for libp2p connections, or TLS for browsers). Establishing a secio or TLS 1.2 connection takes another two roundtrip times. Once that is done, client and server are set up to exchange application data.

In order to establish a new encrypted connection between two hosts (the same applies to TLS 1.2 connection), the client first initiates a TCP connection. The three-way handshake necessary to establish a TCP connection takes one network roundtrip time. After that, the client initiates the cryptographic handshake ([secio](https://github.com/libp2p/go-libp2p-secio) for libp2p connections, or TLS for browsers). Establishing a secio or TLS 1.2 connection takes another two roundtrip times. Once that is done, client and server are set up to exchange application data.

[marten-seemann]

There's a secio spec in progress, so maybe we can link to that (if the spec lands before this blog post).

[lidel]

@marten-seemann @b5 asked if anyone been looking into weather or not flipping to QUIC helps with NAT traversal issues.
I wonder if it is something worth mentioning in blog post, and/or if we should ask for feedback on NAT traversal issues and QUIC (post already mentions middleboxes losing ability to mess things up etc)

[daviddias]

@marten-seemann what's the status on this post?

[marten-seemann]

Should be mostly done, but since we didn't publish it so far, I was considering delaying it until we roll out the next QUIC update later this quarter.

[Stebalien]

Status: A QUIC update is just around the corner but... go-ipfs is in a feature freeze. This should be published along with the 0.5.0 release.

[momack2]

Can we add context here about why WE are talking about it? Aka - "In 0.4.18, go-ipfs released experimental QUIC support, and in May 2019 libp2p released 0.1.0 of the go-libp2p-quic-transport. We aim for QUIC to become the default network transport in the near future to solve many of the long standing issues with TCP - including better NAT traversal, faster connection establishment, and lower resource utilization."

[momack2]

Note as well that there is a Node.js implementation in the works, and that folks can read more on that soon! (NearForm is working on a post about the implementation work which we've helped fund)

[jessicaschilling]

Closing due to age.