Subject: [httpwg/http-extensions] Making tls-commit and tls-ports mutually exclusive (#207)

From: HTTP issue updates <[email-masked]>
Date: Wed, 29 Jun 2016 18:25:51 -0700

This probably isn't the end of this issue though.  We require that an opportunistic upgrade uses the same hostname.  The text I added here lifts the requirement regarding port numbers, but should it also say that the hostname needs to remain the same?

I've left this open here, but I think that we probably should leave the hostname requirement in place.  That way, we still retain some of the aspects of http:// authority.
You can view, comment on, or merge this pull request online at:

  https://github.com/httpwg/http-extensions/pull/207

-- Commit Summary --

  * Making tls-commit and tls-ports mutually exclusive

-- File Changes --

    M draft-ietf-httpbis-http2-encryption.md (4)

-- Patch Links --

https://github.com/httpwg/http-extensions/pull/207.patch
https://github.com/httpwg/http-extensions/pull/207.diff

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/207