Fwd: New Version Notification for draft-ietf-httpbis-header-structure-03.txt

This draft proposes solutions for a number of issues; see the change notes at the end as well as the issues closed to date:
  https://github.com/httpwg/http-extensions/issues?q=is%3Aissue+label%3Aheader-structure+is%3Aclosed <https://github.com/httpwg/http-extensions/issues?q=is:issue+label:header-structure+is:closed>

I'm planning on talking about the open issues in London:
  https://github.com/httpwg/http-extensions/issues?q=is%3Aissue+label%3Aheader-structure+is%3Aopen <https://github.com/httpwg/http-extensions/issues?q=is:issue+label:header-structure+is:open>
... but if you have feedback before that, it'd be great to hear it on the issues or here.

Cheers,


> Begin forwarded message:
> 
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-ietf-httpbis-header-structure-03.txt
> Date: 2 February 2018 at 10:49:51 am AEDT
> To: "Poul-Henning Kamp" <phk@varnish-cache.org>, "Mark Nottingham" <mnot@mnot.net>
> 
> 
> A new version of I-D, draft-ietf-httpbis-header-structure-03.txt
> has been successfully submitted by Mark Nottingham and posted to the
> IETF repository.
> 
> Name:		draft-ietf-httpbis-header-structure
> Revision:	03
> Title:		Structured Headers for HTTP
> Document date:	2018-02-01
> Group:		httpbis
> Pages:		18
> URL:            https://www.ietf.org/internet-drafts/draft-ietf-httpbis-header-structure-03.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-httpbis-header-structure/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-httpbis-header-structure-03
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-header-structure-03
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-httpbis-header-structure-03
> 
> Abstract:
>   This document describes a set of data types and parsing algorithms
>   associated with them that are intended to make it easier and safer to
>   define and handle HTTP header fields.  It is intended for use by new
>   specifications of HTTP header fields as well as revisions of existing
>   header field specifications when doing so does not cause
>   interoperability issues.
> 
> 
> 
> 
> 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/