W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2014

Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade

From: Josh Goodall <joshua.goodall@gmail.com>
Date: Mon, 17 Feb 2014 16:01:50 +1100
Message-Id: <9E529263-C8FB-494C-B2A8-DB626C8D0876@gmail.com>
To: IETF HTTP WG <ietf-http-wg@w3.org>
On 12/02/2014 11:58 p.m., Salvatore Loreto wrote:
> +1 x DNS SRV
> 
> but I think it would be great to generalise its usage to discover if a domain support HTTP/1.1 or HTTP/2 or both
> independently if they run on different ports or on the same port.

A strong +1 for mandating SRV for HTTP/2.x discovery, because:

* It is also the way to lookup both IPv4 and IPv6 simultaneously in a single query/response. Today we have unfortunate race conditions with dual-stack browsers issuing double queries. IPv6 needs your support!

* It does away with the naked-domain-can’t-be-an-alias bug. Hosting providers everywhere will cheer for you.

* No new protocol should be using A (host) records to find service endpoints, SRV is the proper and extensible way. “A” is for Archaic. Philosophically, we shouldn’t lookup a hostname at all, we should lookup a service and be told on which host(s) to find it.

See RFC6186 for a worked example of how SRV records can be adopted for a specific application. Note also, IANA/IETF already expected HTTP to be using SRV, see RFC6335 (BCP165) sec.5 which deprecated “www”… but it just never took off. Well now’s the only chance to fix that.



Josh.


* discussed well in http://labs.apnic.net/presentations/store/2012-08-28-dual-stack-quality-apnic34.pdf
Received on Monday, 17 February 2014 05:02:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:24 UTC