W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2017

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

From: Patrick McManus <mcmanus@ducksong.com>
Date: Sun, 15 Oct 2017 18:39:34 +0000 (UTC)
Message-ID: <CAOdDvNrTeZkeYybjcCmQnAK4zEmRSbL=7kBRxjPSo+ODsdVJyA@mail.gmail.com>
To: Cory Benfield <cory@lukasa.co.uk>
Cc: Patrick McManus <mcmanus@ducksong.com>, HTTP Working Group <ietf-http-wg@w3.org>, hybi <hybi@ietf.org>
On Sun, Oct 15, 2017 at 11:43 AM, Cory Benfield <cory@lukasa.co.uk> wrote:

> 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?
>
>
right - negotiating an extension via 7540 section 5.5 is an opt-in
procedure that lets you do just about anything you agree to.. the spec
tries to draw a bright line between extensions that can be ignored safely
and those that cannot and need to be negotiated (such as this one). Enjoy
the example in there about changing the layout of the HEADERS frame :).
This is also why extensions are hop to hop.

one of the reasons I chose the pseudo header to only apply to CONNECT is
already very special purpose - so the exception doesn't pollute very far as
a practical matter.




> 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/d
> raft-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
>
>
>
Received on Sunday, 15 October 2017 18:39:58 UTC

This archive was generated by hypermail 2.3.1 : Monday, 9 September 2019 17:48:38 UTC