QUIC is now RFC 9000
fastly.com
QUIC is now RFC 9000
1–10 of 246 posts
Re: QUIC is now RFC 9000
#2> The use of pre-ticked opt-in boxes is invalid underthe GDPR. Silence orinactivity on the part of the data subject, as well as merely proceeding with a service cannot beregarded as an active indication of choice.
[0] https://edpb.europa.eu/sites/default/files/files/file1/edpb_...
Re: QUIC is now RFC 9000
#3Re: QUIC is now RFC 9000
#4Oh my mistake, they have several RFCs from 8999-9002.
Re: QUIC is now RFC 9000
#5I'm sorry, I'll show myself out.
Re: QUIC is now RFC 9000
#6Should have waited for 9001. Oh my mistake, they have several RFCs from 8999-9002.
> The IETF just published QUIC as RFC 9000, supported by RFC 9001, RFC 9002, and RFC 8999
Re: QUIC is now RFC 9000
#7https://www.fastly.com/why-fastly-loves-quic-http3 is a 404 on this page fyi
Re: QUIC is now RFC 9000
#8https://www.fastly.com/why-fastly-loves-quic-http3 is a 404 on this page fyi
Re: QUIC is now RFC 9000
#9Should have waited for 9001. Oh my mistake, they have several RFCs from 8999-9002.
Re: QUIC is now RFC 9000
#10The QUIC Wikipedia page[0] makes it sound like a substantial amount of traffic, due largely to Facebook, Google, and the Google Chrome browser, uses QUIC already. Facebook claims 75% of their traffic (for the app?) is via QUIC[1]
[0]: https://en.wikipedia.org/wiki/QUIC
[1]: https://engineering.fb.com/2020/10/21/networking-traffic/how...