[TLS] assert TLSext in renego-ServerHello instead of disable renego

[Martin Rex <[e-mail]>]

Maybe a patched Server (one with support for secure renegotiation)
should ALWAYS assert this extension in a renegotiation TLS handshake
_with_ the verify_data of both server.finished and client.finished
in the ServerHello -- including when the client didn't send the
extension (maybe because the client didn't dare confusing an SSLv3 server).

If we recommend the Server to no longer perform insecure renegotiation,
we could instead recommend that the server unconditionally asserts the
ServerHello extension for the renegotiation handshake.  


This would even allow clients to agree to a secure renegotiation,
which did not dare proposing it (because of an interoperability
constraint with some legacy SSLv3 servers that choke on TLS extensions).

Those clients that propose the secure renegotiation may need a
fallback to a vanilla SSLv3 ClientHello.  Such a fallback would have
to be made at the apps level and is a significant change.  Allowing
server to assert this particular TLS extension in the ServerHello
of a _renegotiation_handhshake_ without having received it in the
ClientHello would obviate the need for the client to add a
TLS extension to the ClientHello, and therefore may obviate the
necessity of a re-connect fallback.


-Martin