Support for QUIC

[RaeesBhatti]

QUIC is a transport layer protocol introduced by Google as a successor to SPDY. It is very similar to TCP + TLS + HTTP/2 but it works on UDP instead of TCP. It has great tolerance for network interruptions and "dramatically" reduces connection establishment time by providing 0-RTT handshakes.
proto-quic is standalone library for QUIC. There is also libquic and go-quic (implementation in GoLang).

Google has been using it heavily across all its sites since a 2013. Almost all of the Google sites are powered by QUIC right now, so, its battle tested.

What do you think? Are you interested in adding support in Proxygen?

[w-o-o]

We are interested in supporting QUIC for sure. However, no ETA to share now.

[afrind]

We're involved with the QUIC standardization efforts through the IETF, but we're not likely to add support for "google" QUIC.

[lnicco]

closing this since as @afrind said we do not have plans to support "google QUIC"

[rektide]

https://code.facebook.com/posts/608854979307125/building-zero-protocol-for-fast-secure-mobile-connections/ makes me feel like Facebook may have an implementation of QUIC tucked under a mattress somewhere, & the modified Zero protocol alteration of it. These sure would be great to get to see.

[afrind]

We are currently building an implementation of IETF QUIC, which is evolving from Google QUIC. We don’t have an implementation of Google QUIC and we don’t have plans to support it. We plan to open source our IETF QUIC implementation and the proxygen integration with it as soon as we practically can. From: rektide <notifications@github.com> Reply-To: facebook/proxygen <reply@reply.github.com> Date: Friday, November 3, 2017 at 8:09 PM To: facebook/proxygen <proxygen@noreply.github.com> Cc: Alan Frindell <afrind@fb.com>, Mention <mention@noreply.github.com> Subject: Re: [facebook/proxygen] Support for QUIC (#127) https://code.facebook.com/posts/608854979307125/building-zero-protocol-for-fast-secure-mobile-connections/ makes me feel like Facebook may have an implementation of QUIC tucked under a mattress somewhere, & the modified Zero protocol alteration of it. These sure would be great to get to see. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#127 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AH4Iab-R9PYfek5-z1s4CJidviBcMWtpks5sy6s5gaJpZM4Ko4dQ>.

[vinothchandar]

We plan to open source our IETF QUIC implementation and the proxygen integration with it as soon as we practically can.

@afrind is there a rough ETA? Also curious, if you have any explicit goals for reducing the client binary size. We (at Uber) are also exploring this route, with a focus of having a thin binary that can be put inside apps easily. Would be thrilled to connect over this..

[edsburke]

Hi FB team, I am bumping this thread to bring up extensive community interests in FB Quic. Would you please share its current status and ETA to open source it? Your feedback would be very appreciated.

Thanks a lot.

[afrind]

We are still in the process of building and testing IETF QUIC. Now that fizz has been open sourced, all of the requisite dependencies of our iQUIC implementation are available. I still can't commit to a specific open source timeline for quic itself, but I would expect it to happen in 2019, hopefully no later than iQUIC gaining RFC status.

[edsburke]

Thank you @afrind for your quick response. Is it going to be QUIC over TCP as aforementioned, or over UDP instead?

Regarding the proxygen, will iQUIC be integrated into it as default transport protocol? Thank you very much!!

[afrind]

IETF QUIC is only defined over UDP. Zero Protocol (gQUIC crypto over TCP) is a FB specific thing, and I'm not sure it's open source plans.

For proxygen, I don't think it will be the default, but it will be like one line of config to enable a QUIC server (assuming you already had HTTPS), and similarly simple on the client?

[edsburke]

Thanks a log @afrind. This makes it quite clear.