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

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

From: Roberto Peon <grmocg@gmail.com>
Date: Thu, 22 May 2014 10:57:55 -0700
Message-ID: <CAP+FsNfqbp+5MV3ujzvgTAHW-Ov_uDkY-PMxZPWKhWnvZ4CX6Q@mail.gmail.com>
To: James M Snell <jasnell@gmail.com>
Cc: Mike Bishop <Michael.Bishop@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
Yup.


On Thu, May 22, 2014 at 10:41 AM, James M Snell <jasnell@gmail.com> wrote:

> +1... many times over.
>
> On Thu, May 22, 2014 at 10:34 AM, Mike Bishop
> <Michael.Bishop@microsoft.com> wrote:
> > When we decided in Zurich to foreclose the option to extend HTTP/2, we
> > thought that we were close to done with the basic protocol.  And it’s
> true
> > -- the fundamentals of HTTP/2 haven’t changed all that much since then.
>  But
> > various cases keep coming up where certain parties need to add one more
> > feature.  While these aren’t core to the HTTP/2 protocol, they’re also
> not
> > worth versioning the protocol for later, and so we’ve added them to the
> spec
> > for experimentation as optional components.
> >
> > This draft proposes that many of these would be perfectly valid use-cases
> > for extensions, and that we might make progress more quickly if we add a
> > simple extension model.  I believe that the time we take in getting the
> > extension model right will be more than offset by the ability to unblock
> the
> > protocol and still handle new situations as they arise, even though we’re
> > late in the process.
> >
> > I want to emphasize that the goal of the extension model is simplicity in
> > the core protocol, and I’d welcome feedback on how to simplify it
> further.
> >
> > Sent from Windows Mail
> >
> > From: internet-drafts@ietf.org
> > Sent: ‎Thursday‎, ‎May‎ ‎22‎, ‎2014 ‎10‎:‎24‎ ‎AM
> > To: Mike Bishop, Mike Bishop
> >
> >
> > A new version of I-D, draft-bishop-http2-extension-frames-01.txt
> > has been successfully submitted by Mike Bishop and posted to the
> > IETF repository.
> >
> > Name:  draft-bishop-http2-extension-frames
> > Revision: 01
> > Title:  Extension Frames in HTTP/2
> > Document date: 2014-05-22
> > Group:  Individual Submission
> > Pages:  18
> > URL:
> >
> http://www.ietf.org/internet-drafts/draft-bishop-http2-extension-frames-01.txt
> > Status:
> > https://datatracker.ietf.org/doc/draft-bishop-http2-extension-frames/
> > Htmlized:
> > http://tools.ietf.org/html/draft-bishop-http2-extension-frames-01
> > Diff:
> > http://www.ietf.org/rfcdiff?url2=draft-bishop-http2-extension-frames-01
> >
> > Abstract:
> >    This document describes a proposed modification to the HTTP/2
> >    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 Thursday, 22 May 2014 17:58:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:30 UTC