Do it. Do it boldly and fearlessly. Make the statement and implement it.
"""
However, as there may be tools that could be affected by this, and
recognising that there are a number of IETF participants who prefer to
continue to access materials via cleartext, or who have issues with using
standard confidentiality services, the IESG are also requiring that public
information continue to be made available in cleartext form.
"""
Don't be tied to legacy. Anything that doesn't support HTTPS at this point
needs to upgrade and deserves to be broken.
The IETF needs to be a leader here.
--Richard
On Mon, Jun 1, 2015 at 12:43 PM, The IESG <iesg(_at_)ietf(_dot_)org> wrote:
Hi All,
The IESG are planning to agree an IESG statement on "HTTPS Everywhere
for the IETF," please see [1] for the current text.
We are seeking community feedback on this and welcome assistance
from the community in identifying any cases where a change or
additional guidance is needed to put this into effect.
The IESG plans to finalise this statement just after IETF-93 in Prague.
* Please send general feedback intended for discussion to
ietf(_at_)ietf(_dot_)org
* Comments about specific issues arising can be sent to
iesg(_at_)ietf(_dot_)org
or tools-discuss(_at_)ietf(_dot_)org as appropriate (use
iesg(_at_)ietf(_dot_)org if not sure)
Regards,
Terry & Stephen (for the IESG)
[1] https://trac.tools.ietf.org/group/iesg/trac/wiki/HttpsEverywhere