W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Re: draft-ietf-httpbis-http2-latest, 6.2 HEADERS again

From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 7 Jul 2014 09:41:35 -0700
Message-ID: <CABkgnnXEJgHn9Oxv9RrLDOrMNq56+wpEBPHY4D-o=aUMXgMY6w@mail.gmail.com>
To: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
Cc: HTTPBIS working group mailing list <ietf-http-wg@w3.org>
https://github.com/http2/http2-spec/commit/f8020a699206671915bcd1fd6c18ed8b722d2767

On 6 July 2014 03:09, Kari Hurtta <hurtta-ietf@elmme-mailer.org> wrote:
>
> Hypertext Transfer Protocol version 2
> draft-ietf-httpbis-http2-latest, July 5, 2014
> http://http2.github.io/http2-spec/
>
>
> 6.2 HEADERS
> http://http2.github.io/http2-spec/#HEADERS
>
>> END_SEGMENT (0x2): Bit 2 being set indicates that this frame is the last for the
>>    current segment.
>
> Should this be:
>
>>  END_SEGMENT (0x2): Bit 2 being set indicates that this header block is the last
>>     for the current segment.
>
> because
>
>> END_SEGMENT, like END_STREAM, applies to a complete sequence of
>> HEADERS and CONTINUATION frames.
>
> Therefore "this frame" is incorrect.
>
> Same formalation is on END_STREAM:
>
>> END_STREAM (0x1): Bit 1 being set indicates that the header block (Section 4.3) is
>> the last that the endpoint will send for the identified stream.
>
>
> In other hand "this header block" may refer "a complete sequence of
> HEADERS and CONTINUATION frames."
>
> / Kari Hurtta
>
>
>
Received on Monday, 7 July 2014 16:42:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:09 UTC