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: <emile.stephan@orange.com>
Date: Wed, 12 Feb 2014 20:01:55 +0000
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
CC: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <6002_1392235316_52FBD334_6002_1133_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB909D13415@PEXCVZYM14.corporate.adroot.infra.ftgroup>
Hi Salvatore,

AFAIK, SRV allow you to set the port you want in the record. I don't have the need for coexistence and migration. Can you detail the cases ?

Regards
Emile

-----Message d'origine-----
De : Salvatore Loreto [mailto:salvatore.loreto@ericsson.com] 
Envoyé : mercredi 12 février 2014 11:59
À : STEPHAN Emile IMT/OLN
Cc : HTTP Working Group
Objet : Re: issue 381: Discovery of the support of the HTTP2 protocol: DNS-based Upgrade

+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.
> 
> 


_________________________________________________________________________________________________________________________

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 20:02:25 UTC

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