- From: Roberto Peon <grmocg@gmail.com>
- Date: Fri, 8 Nov 2013 12:39:49 -0800
- To: Mike Bishop <Michael.Bishop@microsoft.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
- Message-ID: <CAP+FsNeZdVkSdZJMqJ=v2J1x9wNizaX3R+fRk7-xn8reGRMZyQ@mail.gmail.com>
As far as I can tell you have included everything discussed, including hop-by-hop vs end-to-end distinctions, a workable extension id space, as well as an example. Coolness! -=R On Nov 8, 2013 11:25 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 <Michael.Bishop@microsoft.com> > > > 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:40:16 UTC