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

Fwd: New Version Notification for draft-nottingham-binary-structured-headers-01.txt

From: Mark Nottingham <mnot@mnot.net>
Date: Fri, 10 Jan 2020 17:13:56 +1100
Message-Id: <0EE4E68D-1F8F-4E6F-AF17-8B77BEBBBDDF@mnot.net>
To: HTTP Working Group <ietf-http-wg@w3.org>
FYI. Beyond some tweaks to the straw-man wire format, the biggest change is to add some data in Appendix A about how often the directly represented fields map successfully (based upon about 400 million HTTP exchanges in the HTTP archive).

Next step is to try to to roughly quantify how much more efficient the binary format is over parsing text, I think.

Feedback appreciated; this is still mostly a thought experiment.

Cheers,


> Begin forwarded message:
> 
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-nottingham-binary-structured-headers-01.txt
> Date: 10 January 2020 at 5:05:55 pm AEDT
> To: "Mark Nottingham" <mnot@mnot.net>
> 
> 
> A new version of I-D, draft-nottingham-binary-structured-headers-01.txt
> has been successfully submitted by Mark Nottingham and posted to the
> IETF repository.
> 
> Name:		draft-nottingham-binary-structured-headers
> Revision:	01
> Title:		Binary Structured HTTP Headers
> Document date:	2020-01-10
> Group:		Individual Submission
> Pages:		21
> URL:            https://www.ietf.org/internet-drafts/draft-nottingham-binary-structured-headers-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-nottingham-binary-structured-headers/
> Htmlized:       https://tools.ietf.org/html/draft-nottingham-binary-structured-headers-01
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-nottingham-binary-structured-headers
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-nottingham-binary-structured-headers-01
> 
> Abstract:
>   This specification defines a binary serialisation of Structured
>   Headers for HTTP, along with a negotiation mechanism for its use in
>   HTTP/2.  It also defines how to use Structured Headers for many
>   existing headers - thereby "backporting" them - when supported by two
>   peers.
> 
> 
> 
> 
> 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
> 

--
Mark Nottingham   https://www.mnot.net/


Received on Friday, 10 January 2020 06:14:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:45 UTC