Re: [TLS] Security concerns around co-locating TLS and non-secure on same port (WGLC: draft-ietf-tsvwg-iana-ports-08)

[Nicolas Williams <[e-mail]>]

On Mon, Nov 08, 2010 at 08:47:46PM -0600, Marsh Ray wrote:
> Are people actually making that many new app protocols not based on
> TCP port 443?

I see lots of port 80 stuff still.  Don't you?  Do you live in a better
world than I do?  :)

> It seems like the general trend is to run all new things over TCP
> 443 whether it fits the HTTP 'web services' model or not. Because,
> ironically, everything else is more likely to be "managed" out of
> existence by the firewall admin. :-)
> 
> Microsoft, for example, has that VPN protocol that transparently
> multiplexes on that port. There's also the "next protocol
> notification" proposal being circulated.

Well, it's true that because of firewalls everything runs on ports 80
and 443, often doing CONNECT.

Nico
--