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

Re: I-D Action: draft-ietf-httpbis-http2-encryption-07.txt

From: Kari hurtta <hurtta-ietf@elmme-mailer.org>
Date: Tue, 4 Oct 2016 19:03:20 +0300 (EEST)
To: HTTP working group mailing list <ietf-http-wg@w3.org>
CC: Kari hurtta <hurtta-ietf@elmme-mailer.org>
Message-Id: <20161004160321.DFB4C111E5@welho-filter1.welho.com>

> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-httpbis-http2-encryption-07

2.  Using HTTP URIs over TLS
https://tools.ietf.org/html/draft-ietf-httpbis-http2-encryption-07#section-2

|    An origin server that supports the resolution of "http" URIs can
|    indicate support for this specification by providing an alternative
|    service advertisement [RFC7838] for a protocol identifier that uses
|    TLS, such as "h2" [RFC7540].

This allows also other than "h2" (for example "http/1.1", which
is HTTP/1.1 over TLS).

2.1.  Alternative Server Opt-In
https://tools.ietf.org/html/draft-ietf-httpbis-http2-encryption-07#section-2.1

|    Clients MUST NOT send "http" requests over a connection with the "h2"
|    protocol identifier, unless they have obtained a valid http-
|    opportunistic response for an origin (as per Section 2.3), and:

But this part is specific to "h2".


What part of this specification is valid when prococol
identifier is not "h2" ?

/ Kari Hurtta
Received on Tuesday, 4 October 2016 16:04:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 October 2016 16:04:07 UTC