3 ms·
Service discovery is already a function of DNS be it bare bones for decades like a SRV record saying which port the HTTP server is on to DNS-SD which is more ca
by zamadatix 5y ago
Service discovery is already a function of DNS be it bare bones for decades like a SRV record saying which port the HTTP server is on to DNS-SD which is more catalog style infrastructure. Things like LDAP clients actually obey service discovery already. Things like HTTPS servers/browsers have resisted it because of the current security infrastructure (name only based) issues it would open not the network infrastructure. It's not like the security infrastructure side even needs to be redone from the ground up it's just the juice from changing the existing infrastructure hasn't been deemed worth the squeeze by anyone yet.
TLS being deeply embedded has led to more problems than it avoids. Things like QUIC or HTTP/3 are the result of even just TCP sockets being OS managed. Getting anything new to happen when the old is 12 OS implementations updated independently of the program is never going to be popular with programs. That said Linux, FreeBSD, and Windows all support kTLS APIs already, in the case of the latter for about 2 decades. It can be useful in some situations but it's not a silver bullet.
Those layers already exist, actually an option at each layer: IPsec, DTLS, TLS, HTTPS. The lack of bottom up integration and universal adoption isn't from lack of having another option, fighting that it's easy to control the auth the way you want in the HTTPS layer is probably the main restriction.
Tracing tags are considered too problematic for privacy in modern protocols. E.g. QUIC offers an optional spin bit. Putting tracing tags about the full path of every packet certainly wouldn't fly, as convenient as it would make things. For debug packets only that's what ICMP already is.
.
There are a lot of cool things that could be done with a redesigned stack, mostly around preventing ossification of the lower layers, but it's not like it's ever been golden from day 1 or will ever be golden "if we just get it right next time"™. If the journey thus far has taught us anything it's that the internet protocol stack should design itself to avoid being everything included and instead try to be as transparent a transport it can so end applications can choose their own way of doing things without the assumptions of the transport getting in the way.