4 ms·

While I agree that HTTP (and everything else) should support SRV records, they wouldn't do anything for IPv4 exhaustion.

• inopinatus 7y ago
  I beg to differ. Having run LIRs and with friends at RIRs I know for certain that many large IPv4 allocation requests were justified on the basis of needing separate addresses for websites. Policy may be tighter now than it’s ever been, but the lack of aggregation due to well-known-port fixation drove and continues to drive unnecessary assignments.
  • swinglock 7y ago
    Shouldn't the HTTP 1.1 Host header invalidate that argument?
    • inopinatus 7y ago
      Many people expected as much, but in practice not nearly to the extent that was desired, partly because SSL was a problem until SNI came along (and that far too late) and also because it comes after the TCP handshake, which precludes a whole class of traffic routing and service options. Fine for low-end shared hosting, not fine for many other applications.