- From: Simpson, Robby (GE Energy Management) <robby.simpson@ge.com>
- Date: Wed, 10 Sep 2014 00:08:53 +0000
- To: Martin Thomson <martin.thomson@gmail.com>
- CC: RUELLAN Herve <Herve.Ruellan@crf.canon.fr>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On 9/9/14, 6:37 PM, "Martin Thomson" <martin.thomson@gmail.com> wrote: >On 9 September 2014 11:43, Simpson, Robby (GE Energy Management) ><robby.simpson@ge.com> wrote: >>A piggyback ACK, if possible, would help here. > >? My 4th concern from the start of this thread. >>>> Bottom line: I think we need text regarding the acknowledgement of >>>> SETTINGS during the connection preface. > >https://github.com/http2/http2-spec/commit/293e6d041fd9a903ee6dd10b4eee62e >0dd618e76 Thanks! This resolves my 2nd concern. >> OK. So the "configurations" in this case are the various "starting" >> mechanisms (i.e., HTTP Upgrade, TLS, Prior Knowledge), specifically HTTP >> Upgrade. Perhaps "some configurations" should be changed to state the >> HTTP Upgrade starting mechanism specifically. > >TLS 1.3 might allow the server to send application data first. Might. > >Enumerating the options like this doesn't seem to be particularly >useful here. For one, it runs the risk of proscribing behaviour. Makes sense - I agree with you. I withdraw my 3rd concern.
Received on Wednesday, 10 September 2014 00:09:32 UTC