5 ms·
Having service location be at the TCP/IP level is a major contributor to the IPV4 crisis. We have 48 bit addresses, but 16 of those bIts are relatively unused.
by exabrial 8y ago
Having service location be at the TCP/IP level is a major contributor to the IPV4 crisis. We have 48 bit addresses, but 16 of those bIts are relatively unused.
Rather than solving the problem the pragmatically (and in a backwards compatible way), we're pushing a reinvention of the wheel (protocol).
IPv4 certainly has problems but I think they were solvable without bisecting the internet.
- solidsnack9000 8y agoIs SRV part of the problem in your view?
- inopinatus 8y agoI think they're saying that address records are part of the address-exhaustion problem. If we used SRV records instead then the port numbers become available for service endpoint discrimination, and this is a 16-bit space as alluded to. If adopted some time back this would indeed have conserved IPv4 address space; certainly there would have been far fewer 1:1 assignments for SSL termination, and a public cloud load balancer would be able to handle many distinct customers on a single IP address and so on. In practice there'd be some introductory issues in deviating from the well-known ports involving gateway traversal (particularly corporate firewalls), but we've cleared such hurdles before.
- exabrial 8y agoNo I'm saying the opposite, SRV was a a potential cure
- axaxs 8y agoIPv4, don't get me wrong, I like much more than IPv6 for many reasons(128 bits? Overkill). There are more people on Earth than ipv4 addresses, you can't solve that problem without heavy NATing, which has its own drawbacks.
- exabrial 8y agoI think you missed my point, so I'll explain another way because I think it's important to make. If you look at the TCP packet, bits 16-31 are constant for all HTTP traffic. Because they are a fixed value, they're wasted (non-unique). With the current system, we can only have 2,147,483,647 web servers. Using SRV records, these bits become distinguishable, giving us 281,474,976,710,656 possible addresses for web servers. [Yes this is an oversimplification for the pedantic]
- icedchai 8y agoThe Host: header has allowed multiple web servers at the same public IP address for ages. Now, all you need is a reverse proxy...
- axaxs 8y agoI'm not sure I get your point clearly, even now. Are you stating dst port could be used for other things? I'm honestly unclear how 'static' bits in TCP relate to IPv4.
- haldean 8y agoI think they're saying that most things that go over TCP are HTTP, which means usually those bits are set to 80 or 443. With SRV records we could be using more ports, and then presumably do port based routing instead of host based routing on the back end.
- spatular 8y agoIdea is to treat (ip, port) pair as single 6-byte endpoint address. Each endpoint would be able to run just one service (well, two, one for tcp, another for udp). Type of service would be determined by looking up PTR record. On the downside you won't be able to easily tell if two services run on a same machine or not. SSH and HTTP endpoints would be related only through DNS. I think doing it in compatible way that doesn't require replacing routers would require NATs on both sides, and client that looks up PTR records before connecting.