[hybi] Proposal: HTTP upgrade process

[Greg Wilkins <[e-mail]>]

All,

there has been a lot of posting about the -76/-00 style handshake,
it's HTTP compliance issues, it's fast fail (or otherwise)
characteristics, it security features etc.    I don't think any of the
conversations have been very productive nor is there any apparent
convergence on a solution.

I think the reason for his is that we are starting with a solutions
(the 8 random bytes etc.) and trying to reverse engineer the
requirements for it and a retrospective consensus for it's inclusion
into the draft. Thus I would like to propose  that we re-start
consideration of the handshake with the -75 style handshake and try to
move forward from there by identifying problems/requirements,
discussing solutions and then applying the consensus solution to move
forward.

Instead of contributors having to make the case of why the random
8-bytes etc. should be excluded from the protocol, those that support
random bytes should clearly make the case for their inclusion.   We
need to identify the issues with a simple upgrade request, and then
discuss various solutions as to how to address these - it may be that
the random 8 bytes solution is the best solution, but if so, then
there can be no harm in conducting a process that verifies this is the
case.

Note that I'm not saying that we should immediately publish a -01
draft with the handshake reverted, as I think it would be sufficient
for us just to restart our discussions from that simpler base (but I
would not object to a reset -01 draft either).


regards