On 10 January 2015 at 08:09, Constantine A. Murenin
<cnst(_at_)netbsd(_dot_)org> wrote:
I am sincerely asking for the IETF to not approve HTTP/2 as a standard
without the compatibility issues as above being addressed first. The policy
to abandon the http:// address scheme and adopt https:// will only promote a
significant link rot for the future generations to experience well into the
future (didn't we think TLS 1.0 was good enough?), and will curtail
independent and hobbyist operators.
For the sake of clarity: no such policy exists in the specification as
drafted by this working group. The policy comes from specific
implementers, most notably Chrome and Firefox, as discussed by Amos
and Willy. I recommend taking your complaint up with those
implementers through their recommended feature request/bug reporting
channels.