8 ms·
RFC 9114 – HTTP/3
- mndrix 4y ago> This document describes a mapping of HTTP semantics over QUIC. Hooray!
- rektide 4y agoIt's so cool to have this split. QUIC is so capable, such a neat set of ideas for a transport. That HTTP can express itself in terms of another spec is one of the most compelling, longest-hardest won & best victories for "abstraction" that computing has seen. That we'll be able to iterate on HTTP in new ways, by having a common semantic base, keeps the future open & iterable. Huge wins. Obligatory link to Mark Nottingham's "A New Definition of HTTP3"[1], which talks about the split of HTTP into a semantic definition in RFC9110[2] & the creation of HTTP2/RFC9113 and HTTP3 (over QUIC, this document). [1] https://www.mnot.net/blog/2022/06/06/http-core https://www.mnot.net/blog/2022/06/06/http-core https://news.ycombinator.com/item?id=31647149 https://news.ycombinator.com/item?id=31647149 (3 points, 26m ago, 0 comments) [2] "HTTP Semantics" https://www.rfc-editor.org/rfc/rfc9110 https://www.rfc-editor.org/rfc/rfc9110 [3] "HTTP2" https://www.rfc-editor.org/rfc/rfc9113 https://www.rfc-editor.org/rfc/rfc9113
- iforgotpassword 4y ago> It's so cool to have this split. QUIC is so capable, such a neat set of ideas for a transport. That's what I thought too. A while ago, I wanted to use it in an Android app. I thought this was going to be a no-brainer. After all, Google more or less invented QUIC as SPDY about a decade ago. To my understanding, since they just YOLO'd it they agreed to form a proper working group and create quic. So here we are, ten years later, Google is heavily using quic for all their web stuff, and I naively assumed that Android would've had a native quic implementation for a while now, either directly in the SDK/runtime, or some first party library from Google. Nada. There is cronet, the networking engine of chrome as a library, which does speak quic but only exposes classes and functions to speak http, so you cannot even use its quic implementation directly. I went on and had to use some C library and JNI to do it, which is just ridiculous. Sorry for this tangentially related vent, I'm still in disbelief.
- Matthias247 4y agoNote that even the previous draft specification (https://datatracker.ietf.org/doc/draft-ietf-quic-http/34/ https://datatracker.ietf.org/doc/draft-ietf-quic-http/34/) was a mapping of HTTP semantics on top of QUIC. It didn't carry too many transport specific concerns - which e.g. HTTP/2 did, since it cared about flow control and other things. I have yet to read RFC 9114, but I guess it's refinded to fit better on top of the new HTTP semantics spec (RFC 9110).
- rektide 4y agoI'd be aghast to see a significant rewrite of a specification as it moves from draft to rfc. The draft, at it's end, should closely mirror the final spec.
- akshayshah 4y agoThis is great! Despite how little the draft has changed over the last year, many communities seemed reluctant to work on an implementation until the RFC was published. Go definitely fell into this camp. Kudos to .NET for shipping HTTP/3 support in Kestrel already! I have to say that I'm most excited for RFC 9110 (HTTP semantics), though :)
- taftster 4y agoFor the lazy: https://www.rfc-editor.org/info/rfc9110 https://www.rfc-editor.org/info/rfc9110
- pbronez 4y agoThey killed the teapot! https://www.rfc-editor.org/rfc/rfc9110.html#name-418-unused https://www.rfc-editor.org/rfc/rfc9110.html#name-418-unused
- eyelidlessness 4y agoTime for an RFC for HTTP 42 I’m a bowl of petunias.
- techdragon 4y agoI’d prefer HTTP 442 “Oh no, not again.”
- JoshTriplett 4y agoThey at least reserve 418 so that it won't get used for anything else. But it looks like they don't list 451, defined in RFC 7725: https://datatracker.ietf.org/doc/html/rfc7725 https://datatracker.ietf.org/doc/html/rfc7725
- withinboredom 4y agoWe return 418 in a few places at work for endpoints that are only accessible to employees and you are not logged in. It’s a silly little Easter egg. Shame to see it going away.
- autoexec 4y agoSeveral characteristics of HTTP/3 provide an observer an opportunity to correlate actions of a single client or server over time. These include the value of settings, the timing of reactions to stimulus, and the handling of any features that are controlled by settings. As far as these create observable differences in behavior, they could be used as a basis for fingerprinting a specific client. HTTP/3's preference for using a single QUIC connection allows correlation of a user's activity on a site. Reusing connections for different origins allows for correlation of activity across those origins. Several features of QUIC solicit immediate responses and can be used by an endpoint to measure latency to their peer; this might have privacy implications in certain scenarios. It feels like we've been moving backwards in terms of privacy since HTTP/2 even as those same privacy issues have been increasingly exploited by private companies and governments. It's sad to see the situation continuously worsened instead of being improved over time. It feels like a push for performance whatever the cost, or perhaps (more pessimistically) a push to degrade privacy and security while justifying it or distracting us from it with increased performance. It's strange to see security and privacy issues inherent to these specifications acknowledged, but not addressed.
- deleted 4y ago[deleted]
- simmervigor 4y agoFor what it's worth, the HTTP/2 specification contains almost identical phrasing as HTTP/3 [1]. That's not unexpected, the considerations are similar: using a single connection with connection-specific values has potential implications. However, the possibility for fingerprinting is inherent in every protocol and HTTP semantics itself paints out the ways common features might get used. Considerations are just that. Choices in light of considerations can be traded off by client implementations - they can make their own choices about how to address these matters. The work in the IETF to define oblivious DNS and oblivious HTTP [2] protocols is a step towards reducing such surfaces, at the trade off of functionality. [1] https://www.rfc-editor.org/rfc/rfc9113.html#section-10.8 https://www.rfc-editor.org/rfc/rfc9113.html#section-10.8 [2] https://datatracker.ietf.org/wg/ohai/about/ https://datatracker.ietf.org/wg/ohai/about/
- nateberkopec 4y agoWhy does HTTP3 still support server push? When Chrome dropped it from their HTTP/2 implementation, I thought it was dead. Cloudflare has also said they’re not implementing server push in their HTTP/3 support and will instead encourage Early Hints.
- PikachuEXE 4y agoI don't understand why server push is in the standard but not Early Hints. I saw some articles but seems both server side & client side support are lacking. (I can be wrong) At least I don't see early hint in Nginx...
- simmervigor 4y ago103 Early Hints is RFC 8297. It defines a status code. Because status codes are an HTTP semantic, they are common across all HTTP/1.1, HTTP/2, and HTTP/3. There's nothing special that needs to be done from a specification perspective, early hints _can_ work on any version. Whether implementations support that is a slightly different matter.
- francislavoie 4y agoFYI early hints support is coming to Go, so it's possible that Caddy will gain support for it in a while (it'll need Caddy to have Go 1.19 as minimum so it's still like about a year or so away probably)
- gedw99 4y agoSo the golang quic module will need to implement it . I have been using quic with golang and am looking forward to trying this out
- simmervigor 4y agoCo-chair of the QUIC WG here. Early in the process, we decided it was important that HTTP/3 provide parity with HTTP/2. That helps application developers to migrate back and forth between versions with less friction. So we include features of bidirectional stream multiplexing, request/response stream cancellation, server push, header compression, and graceful connection closure. Some of those are more optional than others i.e. Server Push. Whether implementations choose to support a feature or not, at least the IETF maintain the close parity at the protocol level. Stream prioritization is a different matter. That was very tricky in HTTP/3 [1], and through the process we designed Extensible Priorities, which is simpler and works over both H2 and H3. That was published today also as RFC 9218[2]. [1] https://blog.cloudflare.com/adopting-a-new-approach-to-http-prioritization/ https://blog.cloudflare.com/adopting-a-new-approach-to-http-... [2] https://www.rfc-editor.org/info/rfc9218 https://www.rfc-editor.org/info/rfc9218 Edit: typo fix
- inopinatus 4y agoIt's nice to have progress in some areas. However, I'm disappointed to observe that we're on to version 3 and the HTTP editors are still writing tortured thickets of handwaving cross-references to avoid specifying which DNS records it uses. Instead, HTTP continues to refer normatively to the http(s) URIs, which eventually confess: "This specification does not mandate a particular registered name lookup technology". and then everyone squats the A/AAAA address records by default, effectively denying them for any other purpose. There are some obvious consequential misbehaviours (such as the perennial "apex record" problem), but more broadly, HTTP subverts the DNS by de facto appropriating potentially all labels, and continuing to do so represents a middle finger in the face of every other protocol designer. This situation gets more rusted-on and harder to figure out remediation with each revision, and there's a lesson or two in here for anyone who develops protocols for a living.
- zarzavat 4y agoI don’t understand. What has DNS got to do with HTTP? If I connect to http://foobar.onion/ http://foobar.onion/ it’s not using DNS, isn’t that what they mean by “not requiring a particular lookup technology”? And what is the issue with A/AAAA records exactly?
- stock_toaster 4y agoI assume the parent was hoping for SRV record support.
- inopinatus 4y agoSRV is a probably a smidgen shy of what HTTP needs in 2022, although if the protocol were invented today it’d be a shoo-in for resolution in the common case.
- inopinatus 4y agoThis is pointless hairsplitting. RFC7686 is a DNS RFC, one that specifies and enables special application handling when stipulated conditions are met. Even if HTTP/3 defined its use of DNS records adequately, the special case still takes precedence and onion routing continues to occur in browsers supporting it. In my view the use of a special-case TLD is deeply problematic since it contains the potential to leak your use of Tor via applications or resolvers that do not grok the exception, but that's a design problem for another day. The problems with using host address records for service location are multifaceted but the most significant are a) their conflict with other services at the same label, most commonly when the web hosting requires a CNAME, which cannot co-exist with any other record, and b) they're crude; full-grown origin discovery could support priorities, fallbacks, protocol upgrades, variation by transport, alternate ports and more besides.
- thayne 4y agoI'm a little surprised they kept http push, since early hints is often a better solution and browsers don't support server push.
- altairprime 4y agoThey explain why above: https://news.ycombinator.com/item?id=31648565 https://news.ycombinator.com/item?id=31648565
- thayne 4y agoI started writing this before, the above question was posted.
- exabrial 4y agoYou know what http needs? Built in port location as part of the protocol... preferably via DNS.
- charcircuit 4y agoSRV records already exist.
- M2Ys4U 4y agoYes, but their use isn't defined for HTTP, and browsers don't support using SRV records for resolution.
- charcircuit 4y agoA records aren't defined either.
- M2Ys4U 4y agoIndeed, but the SRV resords spec states that they shouldn't be used where the protocol in question doesn't specify their use: "In general, it is expected that SRV records will be used by clients for applications where the relevant protocol specification indicates that clients should use the SRV record. Such specification MUST define the symbolic name to be used in the Service field of the SRV record as described below. It also MUST include security considerations. Service SRV records SHOULD NOT be used in the absence of such specification." -- RFC 2782
- bawolff 4y agoIt really doesn't.
- inopinatus 4y agoIt really does, but it also already has it via RFC7838 (HTTP Alternative Services / ALTSVC), which is normative for HTTP/3¹, albeit an optional client behaviour. Unfortunately not via DNS; you still have to run the origin on a well-known port if not specified in the URI. Clients supporting ALTSVC are then defined to use them at a requirement level of "should"². [1] https://datatracker.ietf.org/doc/html/rfc9114#section-3.1.1 https://datatracker.ietf.org/doc/html/rfc9114#section-3.1.1 [2] https://datatracker.ietf.org/doc/html/rfc7838#section-2.4 https://datatracker.ietf.org/doc/html/rfc7838#section-2.4
- thayne 4y ago> the "http" scheme associates authority with the ability to receive TCP connections on the indicated port of whatever host is identified within the authority component. Because HTTP/3 does not use TCP, HTTP/3 cannot be used for direct access to the authoritative server for a resource identified by an "http" URI Was the possibility of using a different scheme (maybe http3 or h3) considered in addition to the altsvc mechansims?
- simmervigor 4y agoYes it was, there was a pretty lengthy discussion dating back to 2017 on the issue tracker https://github.com/quicwg/base-drafts/issues/253 https://github.com/quicwg/base-drafts/issues/253 TL;DR just like HTTP/2, we wanted to avoid friction in deploying these protocols. Having to rewrite URLs because of new schemes is pretty unpalatable, it has major impact. Instead, HTTP/3 can rely on other IETF-defined mechanisms like Alt-Svc (RFC 7838) and the more recent SVCB / HTTPS RR [1] DNS-based methods. The latter has been deployed on Cloudflare a while [2] and supported in Firefox. Other user agents have also expressed interest or intent to support it. The net outcome is that developers can by and large focus on HTTP semantics, and let something a little further down the stack worry more about versions. Sometime devs will need to peek into that area, but not the majority. [1] - https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-10 https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-... [2] - https://blog.cloudflare.com/speeding-up-https-and-http-3-negotiation-with-dns/ https://blog.cloudflare.com/speeding-up-https-and-http-3-neg...
- deleted 4y ago[deleted]
- dfawcus 4y agoAm I the only one who finds the HTML rendered version[1] from the IETF site easier to read than the one from the rfc-editor site? [1] https://datatracker.ietf.org/doc/html/rfc9114 https://datatracker.ietf.org/doc/html/rfc9114
- capableweb 4y agoAm I the only one who think there should be a "Am I the only one?" law named after some famous internet citizen who said something clever about "Am I the only one..." messages? As one data point, I find https://www.rfc-editor.org/rfc/rfc9114.html https://www.rfc-editor.org/rfc/rfc9114.html easier on the eyes, mainly because of the font choice. I also like that I can link directly to titles (https://www.rfc-editor.org/rfc/rfc9114.html#name-other-schemes https://www.rfc-editor.org/rfc/rfc9114.html#name-other-schem...) where the title itself is visible in the URL rather than just the section-number (https://www.rfc-editor.org/rfc/rfc9114.html#section-3.1.2 https://www.rfc-editor.org/rfc/rfc9114.html#section-3.1.2) as if I'm participating in a discussion about the RFC and links are being thrown around, I can know which section is being referred to without opening the link. But, I can also see how some people prefer the datatracker viewer. The only thing it's really missing is a Table of Contents as a sidebar so it's easier to navigate. Otherwise they are mostly the same.
- dfawcus 4y agoActually, it is that sidebar navigation which is one of the things bugging me, making the whole RFC harder to read. That said, when I'm implementing, I often refer to the text versions - especially as they're easier to diff. As to ToC, that 9114 render seems particularly bad for some reason. Whereas this one does have a ToC with links: https://datatracker.ietf.org/doc/html/rfc4128 https://datatracker.ietf.org/doc/html/rfc4128 That said, if I disable CSS (uMatrix) for the rfc-editor version, the ToC appears inline near the start, and looks a lot nicer. Possibly nicer then than the datatracker render.
- eadmund 4y agoI'm with you. I don't know who decided that RFCs should be displayed in a proportional font, but he was IMHO mistaken. At least they are still available as plain text.
- tannhaeuser 4y agoSo was it really worth it to make it so damn complicated and put it out of range for most developers and existing programs in terms of implementation effort, sidestepping IP networking even, for actual hypertext transport when the web is contracting as we speak? Ignoring incidental use of HTTP for "REST APIs" (an oxymoron in itself).
- api 4y agoHappy to see UDP being used here, because it means that networks that don't properly support UDP are now "broken." There was for a time a risk that the Internet would become a HTTP-only network (at least at the endpoint) supporting TCP to port 80 and 443 and not a lot else. Really. I've seen networks like this.