On 6/1/2015 10:16 AM, Richard Barnes wrote: > Do it. Do it boldly and fearlessly. Make the statement and implement it. > ... > Don't be tied to legacy. Anything that doesn't support HTTPS at this > point needs to upgrade and deserves to be broken. Leaving out the have-nots - or those whose access is blocked by others when content cannot be scanned - isn't moving forward. HTTP isn't legacy. It's open. I thought the IETF was too. Joe PS - I noticed you didn't PGP-sign this post. Hello, pot. (ref: http://en.wikipedia.org/wiki/The_pot_calling_the_kettle_black)