- From: Mark Nottingham <mnot@mnot.net>
- Date: Sun, 6 Jul 2014 10:58:20 +1000
- To: K.Morgan@iaea.org
- Cc: msweet@apple.com, gregw@intalio.com, squid3@treenet.co.nz, ietf-http-wg@w3.org
On 5 Jul 2014, at 5:44 pm, K.Morgan@iaea.org wrote: > That doesn't help for direct h2c communications (ie without upgrade). > I know it seems far-fetched right now, but it's conceivable that http/2 might actually replace http/1.x, in which case upgrade would no longer be needed and there would be no way to pre-negotiate the settings for a low-resource alpn token. If you’re doing a prior knowledge connection <http://http2.github.io/http2-spec/#known-http>, you still need to pre-arrange what protocol you’re going to speak; that gives you an opportunity to figure out which ALPN token to use. -- Mark Nottingham http://www.mnot.net/
Received on Sunday, 6 July 2014 00:58:53 UTC