Where are the places that block encrypted traffic?

[Sam Hartman <[e-mail]>]

>>>>> "Paul" == Paul Wouters <[e-mail]> writes:

    Paul> On Mon, 1 Jun 2015, Niels Dettenbach wrote:
    >> - And: there ARE poeples and services which doen't allow
    >> encrypted access for legal or organisational reasons - it would
    >> not be nice to block interested poeples from such user
    >> "societies" which are not usually free to decide for an
    >> alternative byself.

I've heard this assertion made multiple times.

As a software developer, I'd really appreciate  some concrete examples
of places that

* Generally permit public access to the Internet

* Prohibit https access.

I'm aware of organizations that:

* Don't want public access to the Internet.  For example please don't
surf the web from your cash register; isolated networks; white-list only
access.

* Places that require https traffic to go through a proxy that attempts
  to examine everything

* Places that inject an https root so they can MITM traffic

I don't think it's our job to make it easy to access the ietf's
resources from places that are trying to block access to us either in a
targeted manner or because they block large chunks of the internet whose
criteria would include the ietf.  Similarly, if an organization's policy
is that you have to use some proxy to access the IETF, I don't see a
problem with that.  Where are these places that block encrypted traffic
but are generally interested in public internet access?  I would like to
better understand real-world examples of these so I can factor them into
software design decisions.