[TLS] Next Protocol Negotiation 03

[Adam Langley <[e-mail]>]

With httpbis active, several people have suggested that it's time to
make another pass at making NPN a little more formal.

Previous drafts have omitted some details so that the more important
aspects were clearer. Paul Hoffman also made a valiant attempt [2] at
making it more "IETF friendly" to see whether that would get anywhere.

In contrast, the current draft [1] is complete and sufficient to
produce an interoperable implementation with what's running on
www.google.com.

Perforce, it includes the current extension and handshake message
numbers. I understand that using these numbers without permission has
upset some people. However, we stand up, evaluate and tear down TLS
work at a rate far in excess of what the WG could usefully process.
Standardising every experiment before testing it would waste RFCs and
allocations, not to mention years. Therefore the extension and
handshake numbers were randomly generated.

NPN is included in several TLS implementations and used quite
regularly on the Internet and I would like the TLS WG to consider its
adoption.


Cheers

AGL


[1] https://tools.ietf.org/html/draft-agl-tls-nextprotoneg-03
[2] https://tools.ietf.org/html/draft-agl-tls-nextproto-00