QUIC codec for netty

236 views
Skip to first unread message

Anuradha Jayalath

unread,
Mar 21, 2017, 5:02:40 AM3/21/17
to QUIC Prototype Protocol Discussion group
Hi all,

I am trying to write a QUIC codec(Encoders and Decoders) for netty framework. As I found there are several wire specification documents. The latest one I found is this. My Question is do I have to worry about older versions of QUIC or just writing the codec based on the latest draft document is enough.

Ian Swett

unread,
Mar 21, 2017, 9:18:02 AM3/21/17
to proto...@chromium.org, Marten Seemann, Lucas Clemente, Ryan Hamilton
Thanks for your interest.  Netty is a great networking framework, based on my experience.

All deployments of QUIC I'm aware of are currently based on Google QUIC, typically supporting v35 and above.

Google is actively working on migrating towards the IETF document you linked to, but we're months from having implemented it as it's currently specified. 

If your hope is to interop with QUIC deployments at Google, Chrome, and QuicGo(https://github.com/lucas-clemente/quic-go) in the next few months, you'd want to implement the Google QUIC.  If you're willing to wait longer, then the IETF document you pointed to is the right place to start.
 

On Tue, Mar 21, 2017 at 5:02 AM, Anuradha Jayalath <aniro...@cse.mrt.ac.lk> wrote:
Hi all,

I am trying to write a QUIC codec(Encoders and Decoders) for netty framework. As I found there are several wire specification documents. The latest one I found is this. My Question is do I have to worry about older versions of QUIC or just writing the codec based on the latest draft document is enough.

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+unsubscribe@chromium.org.
To post to this group, send email to proto...@chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

Anuradha Jayalath

unread,
Mar 21, 2017, 9:30:16 AM3/21/17
to proto...@chromium.org
Thanks for the acknowledgement. I think I have to read QUIC  wire specifications not IETF one.
Reply all
Reply to author
Forward
0 new messages