In 2011 there was the DNS-EASY ( Workshop on DNS health and security ) held
at in Rome (http://www.gcsec.org/event/dns-easy-2011-workshop )
It was organized by the "Global Cyber Security Center" and held in some
building that was somehow affiliated with the postal service / postel.it.
This location blocked all port 443 (and 22, and.. and.. and...). This made
people sad, and so I ended up spinning up a VPN server on port 80 for most
of the attendees...
Sure, anecdotal info, but....
W
On Wed, Jun 3, 2015 at 11:04 AM Tim Bray <tbray(_at_)textuality(_dot_)com>
wrote:
I travel heavily and visit many different kinds of public & private
institutions; and it has been many years since I’ve observed HTTPS
blockage. Even in China, it seems the blockage is more domain-based than
protocol-based.
So yes, I’d like to hear evidence for the claim of protocol blockage.
On Tue, Jun 2, 2015 at 7:23 PM, Sam Hartman
<hartmans-ietf(_at_)mit(_dot_)edu> wrote:
"Mark" == Mark Andrews <marka(_at_)isc(_dot_)org> writes:
to be clear, none of this is the sort of thing I was looking for. All
of this is discussions of parts of the Internet that aren't particularly
transparent or interested in letting you have open access to large
portions of the net.
I don't care if the ietf website is accessible from a hotel before you
accept the network's terms.
Based on the discussion so far I'd like to see better justification for
the claim that there are portions of the network that block TLS before
we make it.
--
- Tim Bray (If you’d like to send me a private message, see
https://keybase.io/timbray)