W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

Re: New Version Notification for draft-bishop-http2-extension-frames-00.txt

From: James M Snell <jasnell@gmail.com>
Date: Fri, 8 Nov 2013 12:13:22 -0800
Message-ID: <CABP7Rbdv4QG-tBjyd5BR4-4OOzp-g9_NoTh-VOSg1Qw_18St7Q@mail.gmail.com>
To: Mike Bishop <Michael.Bishop@microsoft.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
On Fri, Nov 8, 2013 at 12:06 PM, James M Snell <jasnell@gmail.com> wrote:
> It's great to see work being done on the extension model but I'm not
> convinced that the approach you suggest in this draft is the best way
> forward.
>
> The approach that I would like to see is this:
>
> For Frames:
>
> 1. Clearly define the notion that some frames are *always* end-to-end,
> while others are *always* hop-by-hop
> 2. Clearly differentiate these types using the MSB of the frame type.
> If the MSB is set, the frame is end-to-end
> 3. Specify that end-to-end frames are *always* subject to flow control
> 4. Change the type of the DATA frame to 0x80
> 5. Dedicate 10 frame types at the top of each range (0xF5-FF and
> 0x75-7F) as "private use" frame types that cannot be assigned by IANA.
> 6. Require that end-to-end frames are only sent on open streams
> (basically, whenever a DATA frame can be sent)

Missed one:

  7. Require that implementations ignore-but-forward unknown
end-to-end frames; while allowing them to ignore-and-drop unknown
hop-by-hop frames... with the option of signaling an error if they so
choose.


>
> For Settings:
>
> Dedicate some portion of the possible range of settings as "private
> use" that cannot be assigned by IANA
>
> - James
>
> On Fri, Nov 8, 2013 at 11:21 AM, Mike Bishop
> <Michael.Bishop@microsoft.com> wrote:
>> Since I was volunteered at the working group meeting to share this, here’s
>> the current version of my draft.  I will re-emphasize that this is strictly
>> a strawman, and any suggestions on how to improve this are more than
>> welcome.
>>
>> Sent from Windows Mail
>>
>> From: internet-drafts@ietf.org
>> Sent: ‎Friday‎, ‎November‎ ‎8‎, ‎2013 ‎11‎:‎16‎ ‎AM
>> To: Mike Bishop
>>
>>
>> A new version of I-D, draft-bishop-http2-extension-frames-00.txt
>> has been successfully submitted by Mike Bishop and posted to the
>> IETF repository.
>>
>> Filename:  draft-bishop-http2-extension-frames
>> Revision:  00
>> Title:   Extension Frames in HTTP/2.0
>> Creation date:  2013-11-08
>> Group:   Individual Submission
>> Number of pages: 10
>> URL:
>> http://www.ietf.org/internet-drafts/draft-bishop-http2-extension-frames-00.txt
>> Status:
>> http://datatracker.ietf.org/doc/draft-bishop-http2-extension-frames
>> Htmlized:
>> http://tools.ietf.org/html/draft-bishop-http2-extension-frames-00
>>
>>
>> Abstract:
>>    This document describes a proposed modification to the HTTP/2.0
>>    specification to better support the creation of extensions without
>>    the need to version the core protocol or invoke additional protocol
>>    identifiers.
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
Received on Friday, 8 November 2013 20:14:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:19 UTC