On Wed, Mar 28, 2018 at 6:43 PM, Mike Bishop <mbishop@evequefou.be> wrote: > > - Section 4 says that CONNECT is defined in RFC 7540, Section 8.3, > which isn’t quite accurate. > - 7540 just has the description of how CONNECT gets mapped into > HTTP/2’s framing layer, because it’s not quite the same as other methods. > This document probably doesn’t need to actually modify 7540, because it’s > employing the extension framework defined therein. > - The CONNECT method itself is actually defined in 7231, section > 4.3.6. You’re changing how the authority is interpreted in these requests; > are we sure this doesn’t need to be marked as modifying 7231? > > This is interesting, and I've made a small edit so that the text says the "usage of the connect method in http/2 is defined by 7540.." to make it more clear. But I do think 7540 defines more than mere header mappings vs 7231.. it for example says explicitly "a TCP connection to the server identified in the :authority", which is exactly the thing being overriden by this extension.. so I think we're ok with not updating 7231 > > - > - > - Section 5 “replaces the GET based request in [RFC6455]” and makes > other modifications to the requirements contained therein. This seems to > suggest that it updates RFC6455 as well. > > I'm not entirely sure if it updates 6455 or just sort of incorporates 6455 into a whole new use case, but in any event its useful reading for consumers of 6455 so I agree we should add that meta data. I am curious about Mark and/or Alexey's take on this too. Thanks! >
Received on Wednesday, 2 May 2018 20:52:35 UTC