W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2016

Decomposing HTTP

From: Mike Bishop <Michael.Bishop@microsoft.com>
Date: Tue, 15 Mar 2016 22:48:51 +0000
To: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <BL2PR03MB19057E859217B2A3F7AF525F87890@BL2PR03MB1905.namprd03.prod.outlook.com>
Bringing back this draft so it's alive for BA.  It's pretty much a straight renewal of the 2nd version (with a name change so it shows up in the WG); there was good feedback on the first version, and that has been incorporated.

This started last summer after discussions at the HTTP Workshop. In our discussions, it became clear that there are actually 2 distinct layers in HTTP 2: the "semantic" layer, which didn't really change much if at all; and the "framing" layer, the mapping between HTTP and TCP, which changed radically. This draft attempts to identify the requirements handled by the framing layer, and looks at how they have been dealt with in various mappings of the HTTP semantic layer to different transport protocols.

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, March 14, 2016 3:31 PM
To: Mike Bishop <Michael.Bishop@microsoft.com>
Subject: New Version Notification for draft-bishop-httpbis-decomposing-http-00.txt

A new version of I-D, draft-bishop-httpbis-decomposing-http-00.txt
has been successfully submitted by Mike Bishop and posted to the IETF repository.

Name:		draft-bishop-httpbis-decomposing-http
Revision:	00
Title:		Decomposing the Hypertext Transfer Protocol
Document date:	2016-03-14
Group:		Individual Submission
Pages:		16
URL:            https://www.ietf.org/internet-drafts/draft-bishop-httpbis-decomposing-http-00.txt

Status:         https://datatracker.ietf.org/doc/draft-bishop-httpbis-decomposing-http/

Htmlized:       https://tools.ietf.org/html/draft-bishop-httpbis-decomposing-http-00

   The Hypertext Transfer Protocol in its various versions combines
   concepts of both an application and transport-layer protocol.  As
   this group contemplates employing alternate transport protocols
   underneath HTTP, this document attempts to delineate the boundaries
   between these functions to define a shared vocabulary in discussing
   the revision and/or replacement of one or more of these components.


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 Tuesday, 15 March 2016 22:49:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 22 March 2016 12:47:11 UTC