[This post was started at IETF 104, and since IETF 105 is in a few weeks, I figure I'd better finish it.] There's an ongoing discussion in the HTTP community over what constitutes authority for an origin.  The URI identifies a resource using a scheme (https), host (www.evequefou.be)

There were many great conversations and much excellent work done last week at IETF 101 in London. As is so often the case lately, many of our decisions had to balance the intersection of privacy and manageability. TLS is the fundamental protocol that provides security on the Internet -- it

IETF 100 took place a few weeks ago in Singapore, and across multiple venues, there was one topic that surfaced repeatedly, and opinions vary so widely that we might almost consider it a holy war: middleboxes. Some people I've attempted to describe the problem to hadn't heard that term, so

In my previous post, I talked about why QUIC matters to the future of the Internet. I'd also like to look a little more closely at why it matters to HTTP specifically. Obviously, the benefits we're able to import from TCP developments will benefit HTTP immediately - the ability to

In my long-ago last post on HTTP/2, I said that I would follow up with a discussion of QUIC and why I believe it's important. Real life has been unfortunately busy, but it's time now. Firstly, I don't intend to knock TCP. Not only has it served the Internet

You may have heard this term "QUIC" floating around the Internet, and not known what to do with it. Is it an adverb? An acronym? A bad pun? And what does it have to do with HTTP/2? Let's do a QUICk survey and find out. This will be the