Re: New Version Notification for draft-mcmanus-httpbis-h2-websockets-00.txt

Doesn’t the introduction of a new pseudo-header field violate RFC 7540 Section 8.1.2.1, which says endpoints MUST NOT generate new pseudo-header fields?

Or is the position that that MUST NOT implicitly applies only if there are no negotiated extensions in use?

Cory

> On 15 Oct 2017, at 07:12, Patrick McManus <mcmanus@ducksong.com> wrote:
> 
> FYI - also see https://github.com/mcmanus/draft-h2ws/blob/master/README.md
> 
> Comments, expressions of interest, etc are very welcome.
> 
> 
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>
> Date: Sun, Oct 15, 2017 at 10:08 AM
> Subject: New Version Notification for draft-mcmanus-httpbis-h2-websockets-00.txt
> To: Patrick McManus <mcmanus@ducksong.com>
> 
> 
> 
> A new version of I-D, draft-mcmanus-httpbis-h2-websockets-00.txt
> has been successfully submitted by Patrick McManus and posted to the
> IETF repository.
> 
> Name:           draft-mcmanus-httpbis-h2-websockets
> Revision:       00
> Title:          Bootstrapping WebSockets with HTTP/2
> Document date:  2017-10-15
> Group:          Individual Submission
> Pages:          7
> URL:            https://www.ietf.org/internet-drafts/draft-mcmanus-httpbis-h2-websockets-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-mcmanus-httpbis-h2-websockets/
> Htmlized:       https://tools.ietf.org/html/draft-mcmanus-httpbis-h2-websockets-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-mcmanus-httpbis-h2-websockets-00
> 
> 
> Abstract:
>    This document defines a mechanism for running the WebSocket Protocol
>    [RFC6455] over a single stream of an HTTP/2 connection.
> 
> 
> 
> 
> 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
> 
>