Well, you have to serve them all and let the client decide what to use, like with MX or SRV. Too bad HTTP is stuck in time and can't get any proper functionality.
And yes, I mean it is literally too bad. Why can HTTP hold 3 current standards at the same time, but still fail to work with basic internet infrastructure?
Are we at the point of desperation in the death gasps of DNSSEC where its advocates are now blaming other protocols for not rearchitecting the way they use the DNS to make it DNSSEC more viable? Because: nobody was ever going to do that.
I sometimes wonder that too. There are tons of simple things HTTP and web browsers could implement to make everyone's life better and easier. Make redundancy built-in, for example, or a primitive peer-to-peer content delivery for stuff like videos. But then I remember that megacorps always want to keep competition out, make everyone invest a lot into crappy traditional infrastructure to compete. They can't allow a competing alternative to work on many orders of magnitude cheaper infrastructure, they are only interested in increasing that cost for everyone and at such pace that nobody can keep up.
Well, you have to serve them all and let the client decide what to use, like with MX or SRV. Too bad HTTP is stuck in time and can't get any proper functionality.
And yes, I mean it is literally too bad. Why can HTTP hold 3 current standards at the same time, but still fail to work with basic internet infrastructure?