Opened 6 years ago

Last modified 6 years ago

#387 new defect

Eliot Lear feedback on HTTP case study in draft-iab-transition-principles-05

Reported by: dthaler@… Owned by: draft-iab-protocol-transitions@…
Priority: major Milestone: milestone1
Component: draft-iab-protocol-transitions Version: 1.0
Severity: In WG Last Call Keywords:


HTTP/2 versus HTTP/1.1 goes tot he heart of RFC 5218. Because HTTP1.1 has "enjoyed" wild success, there is an opportunity to revisit that. For instance, is it still enjoying wild success or is it simply now just wild? That is, has H2 taken its primary use case, leaving everything other than what it was designed to do? And maybe that's okay. One could argue that the other use cases look a lot like CoAP, and yet CoAP may only cover a fraction.

I'd suggest that there is an entire topic that you could plumb and is worth hitting head on: has the world become more 2-sided? One thing we might stand to learn from HTTP/1.1 and HTTP2 is how much code was needed where to get bank for the buck? The Alexa 12, for instance, would argue that hitting just a handful of browsers made a massive difference re what we see on the Internet, and the value is sufficient to just those sites, and a few content networks like Akamai to sustain the new protocol. It doesn't really say, however, how to turn off the old stuff, or even whether it is necessary to do so.

Change History (1)

comment:1 Changed 6 years ago by dthaler@…

  • Component changed from draft-iab-rfc-editor-model-v2 to draft-iab-protocol-transitions
  • Owner set to draft-iab-protocol-transitions@…
Note: See TracTickets for help on using tickets.