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: Salvatore Loreto <salvatore.loreto@ericsson.com>
Date: Wed, 12 Feb 2014 10:58:49 +0000
To: "<emile.stephan@orange.com> " <emile.stephan@orange.com>
CC: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <BADECA9F-054A-4BA8-B1AC-447734C89227@ericsson.com>
+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.

/Salvatore

On Feb 12, 2014, at 12:52 PM, <emile.stephan@orange.com>
 wrote:

> All,
> 
> I create an entry in github to discuss this aspect,  see https://github.com/http2/http2-spec/issues/381 ;
> 
> HTTP2 is carried over TCP. So when HTTP1 and HTTP2 are not carried on the same TCP port, browsers need a mechanism to discover this port. DNS SRV provides such a mechanism and is already standardized. So I propose to add this discovery mechanism in a new section in section 3.
> 
> Regards
> Emile
> 
> _________________________________________________________________________________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> 
> 
Received on Wednesday, 12 February 2014 10:59:14 UTC

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