Update ALPN/NPN token from "h2-14" to "h2-15".

Update ALPN/NPN token from "h2-14" to "h2-15".

HTTP/2 draft-15 was published on 2014-10-27.  There are no functional changes
concerning the features that are currently implemented in Chromium.  See
https://tools.ietf.org/wg/httpbis/draft-ietf-httpbis-http2/.

This change is parallel to the server side change 79349571 by mlavan.

Two separate CLs will accompany this change:
 * Add HTTP_1_1_REQUIRED error code.  This will be silently ignored, as Chromium
only speaks HTTP/2 to peer that have explicitly acknowledged their support via
ALPN or NPN.
 * https://crrev.com/711563003

BUG=345769
Committed: https://crrev.com/6371af94b25f78f85691e892627a9e88832e2ba0
Cr-Commit-Position: refs/heads/master@{#303150}

[Bence, 2014-11-06 21:59:47]

bnc@chromium.org changed reviewers:
+ rch@chromium.org

[Bence, 2014-11-06 21:59:47]

Ryan: PTAL.  Thanks.

[Ryan Hamilton, 2014-11-06 22:06:26]

I'm sure we talked about this on the call yesterday, and that I missed it, but I
thought there was an HPACK change as part of -15. Is that a problem? Am I
misremembering?

[Bence, 2014-11-07 00:12:23]

On 2014/11/06 22:06:26, Ryan Hamilton wrote:
> I'm sure we talked about this on the call yesterday, and that I missed it, but
I
> thought there was an HPACK change as part of -15. Is that a problem? Am I
> misremembering?

Yes, you are right, we talked about that, and I think we were mistaken.  What we
hadn't realized is that while a new draft of HTTP/2 has been published
(draft-15), HPACK is still on draft-09 since July 31, so no change to HPACK is
official yet.  (Also, it seems that the proposed HPACK change has not even made
it to the editor's copy, see
http://http2.github.io/http2-spec/compression.html#changes.since.draft-ietf-h...)
 Therefore there is no need to change HPACK at this point.  Please let me know
if I am misunderstanding the situation.

[Ryan Hamilton, 2014-11-07 00:13:06]

On 2014/11/07 00:12:23, Bence wrote:
> On 2014/11/06 22:06:26, Ryan Hamilton wrote:
> > I'm sure we talked about this on the call yesterday, and that I missed it,
but
> I
> > thought there was an HPACK change as part of -15. Is that a problem? Am I
> > misremembering?
> 
> Yes, you are right, we talked about that, and I think we were mistaken.  What
we
> hadn't realized is that while a new draft of HTTP/2 has been published
> (draft-15), HPACK is still on draft-09 since July 31, so no change to HPACK is
> official yet.  (Also, it seems that the proposed HPACK change has not even
made
> it to the editor's copy, see
>
http://http2.github.io/http2-spec/compression.html#changes.since.draft-ietf-h...)
>  Therefore there is no need to change HPACK at this point.  Please let me know
> if I am misunderstanding the situation.

Ok, I trust you! LGTM

[Bence, 2014-11-07 00:19:07]

The CQ bit was checked by bnc@chromium.org

[commit-bot: I haz the power, 2014-11-07 00:21:32]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/707953002/20001

[commit-bot: I haz the power, 2014-11-07 01:25:17]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2014-11-07 01:26:46]

Patchset 2 (id:??) landed as
https://crrev.com/6371af94b25f78f85691e892627a9e88832e2ba0
Cr-Commit-Position: refs/heads/master@{#303150}