Re: [Http-srv] Alternative to SRV?

[Ray Bellis <[e-mail]>]

On 24/08/2018 05:06, Shumon Huque wrote:

> Before designing yet another record to solve this problem, I think we 
> need to first determine if that path would have support from HTTP folks. 
> Or, if there is already momentum behind the dns-alt-svc draft, and if it 
> is more likely to gain traction, then perhaps working on refining it is 
> the best option. Otherwise we risk defining an SRV version 2 record 
> which will again be ignored.

It's completely unclear to me whether ALTSVC would be deployable as the 
primary means of directing web clients to the primary target for the 
initial HTTP connections.

It is, after all, a DNS encoding of the HTTP *Alternate* Service feature.

> [deleted]
> 
> I've also proposed that client behavior when processing ALTSVC responses 
> should be to shuffle or randomize the ALTSVC RRs (of equal priority), 
> and also shuffle address records for each server if there are multiple 
> of them (if they are returned by the server in additional data). This 
> would ensure better load balancing behavior regardless of whether the 
> DNS server shuffles or randomizes the records.

We specifically heard at the side meeting that the browser folks don't 
want load balancing information stored in the DNS.  What we haven't 
heard (that I know of) is what the web *content* folks think of that.

I do know that some of the hardware GLB appliances that use DNS tricks 
to implement load-balancing do a pitifully poor job of DNS compliance.

FWIW, I'd also like to do away with underscore labels for these records, 
since (again from the web / DNS hosting point of view) they interact 
badly with DNS wildcard records.

Ray