3 ms·
Those powerful commercial influences should use their muscle to force the use of protocols other than TCP rather than the silliness of piling everything onto po
by kevin_thibedeau 6y ago
Those powerful commercial influences should use their muscle to force the use of protocols other than TCP rather than the silliness of piling everything onto port 80/443.
- pathseeker 6y agoI think you just mixed up HTTP and TCP. HTTP and it's secure friend HTTPS are on TCP port 80 and 443.
- snazz 6y agoThey do. HTTP/3 is over QUIC, which uses UDP (on ports 80 and 443, as it should). That effort has been spearheaded by Google. Edit: Also, putting everything on port 443 is a major security and privacy boon. Internet service providers can no longer just block ports for services they don't like.
- kevin_thibedeau 6y agoQUIC would never have been needed if it was actually possible to use SCTP without unnecessary roadblocks.
- zozbot234 6y agoIs there an actual problem with routing SCTP over the Internet? ISTM that the main issue would be enterprise middleboxes being generally unable to deal with it, in which case QUIC may turn out to be more of a stopgap solution.
- kevin_thibedeau 6y agos/generally unable/not compliant with IP standards/
- Reelin 6y agoThis might be naive, but it bugs me that protocol ports are visible to intermediaries. HTTPS encrypts the URL path. Why don't TCP and UPD encrypt (or otherwise scramble) their port numbers? (Yes, I know, those protocols don't include cryptographic provisions. Maybe they should be updated?)
- TeMPOraL 6y agoFor better or worse, one of the main drivers behind piling everything onto ports 80 and 443 is the silliness of corporate security theatre. If your product/service/idea communicates by any other port, regular employees most likely won't be able to use it, and you'll have harder time selling it, as dealing with IT is often too much of a hassle for the interested manager.