Hi there,
On the main quicwg.org site I see the link to slack but there seems to
be no obvious link/way to sign up. If you think appropriate would you
please be able to send an invite link?
I'm not building an implementation, but I'm looking for advice from
implementers/people familiar with the spec as we are interested in
trialing QUIC in a new area - seeing if it will optimize our (very
expensive) bandwidth consumption with our android app where millions of
people connect from very poor mobile reception to a long-lived XMPP
service. From the research I have seen, I understand that QUIC so far
has mostly been tested with regards throughput/latency/blocking but not
so much focused on bandwidth reduction which I believe we can see due to
reducing signalling overhead and the connection migration features.
Currently with TCP+TLS we have very large overheads due to frequent
reconnects and small packet contents (TCP overhead is the same as the
total contents being transferred, TLS is the same again mostly due to
the initial certificate transfer even when 50%+ of our conns reuse a TLS
session). Additionally, as QUIC is implemented in user-space rather than
kernel, I'd be interested to understand if there are ways with some of
the different implementations that we could save the connection state
between app restarts and treat it as if it were a connection migration,
as many (esp low-end) devices frequently kill apps to save memory/cpu.
Mark
