Subject: Dynamic discovery of the support for HTTP/2 during domain name resolution

From: <[email-masked]>
Date: Sun, 2 Mar 2014 22:13:27 +0000

Hi

I created an issue on github, https://github.com/http2/http2-spec/issues/418, about refining the Prior Knowledge approach used in the spec. I propose , see https://github.com/http2/http2-spec/pull/420, to add a new section which describes the discovery about the support for HTTP2 during the domain name resolution:

                 <section anchor="discover-domain-http2" title="Dynamic discovery of the support for HTTP/2">
        <t>
          A client that makes a request to a resource resolves the domain name before establishing the TCP connection with the server.
        </t>
        <t>
          A client connected to an enterprise network previously determines the domain name of the local server or of the enterprise forward-proxy. This lookup is dynamic. It is made, as an example, with a call to the function FindProxyForURL() of the proxy.pac file discovered dynamically with DNS WPAD.
        </t>
        <t>
          The knowledge about the support for HTTP2 may be learned dynamically during the resolution of the actual domain name. DNS SRV is an available solution for discovering dynamically the support for HTTP/2. The SRV record provides the client with the host and port of a server which supports HTTP2 (e.g. _h2-10._tcp.example.com 3600 IN SRV 0 33 9876 h2srv.example.com). The support about HTTP2 for a server is valid only for the duration given by the Time To Live of the DNS SRV record.
        </t>

      </section>

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.

Subject: RE: Preliminary agenda for London: explicit proxy discussion in HTTPbis
From: "DRUTA, DAN" <[email-masked]>
To: STEPHAN Emile IMT/OLN <[email-masked]>, Martin Thomson <[email-masked]>, Mark Nottingham <[email-masked]>
Cc: "Smith, Kevin, (R&D) Vodafone Group" <[email-masked]>, "[email-masked]" <[email-masked]>
Date: Fri, 28 Feb 2014 10:01:55 +0000

We've had several informal discussions over the last few meetings and the outcome of those discussions was that before we can talk more about the proxy we should:
- Have a concrete proposal
- Show a concrete implementation
Now we got both and I think it will make sense to allocate some time to at least identify if there's any particular aspects that have to be addressed in the spec based on the proposal.
I'm not sure how many folks will be able to participate on Sat and that could be a continuation of the discussion but at least frame it during the regular meeting.

Best Regards,
Dan
-----Original Message-----
From: [email-masked] [mailto:[email-masked]]
Sent: Friday, February 28, 2014 12:40 AM
To: Martin Thomson; Mark Nottingham
Cc: Smith, Kevin, (R&D) Vodafone Group; [email-masked]
Subject: RE: Preliminary agenda for London: explicit proxy discussion in HTTPbis

Hi,

Then it is preferable to have these discussions before Wednesday in the HTTPbis meeting. Why waiting Toronto HTTPbis meeting to decide ?

Regards
Emile

-----Message d'origine-----
De : Martin Thomson [mailto:[email-masked]]
Envoyé : jeudi 27 février 2014 19:30
À : Mark Nottingham
Cc : Smith, Kevin, (R&D) Vodafone Group; [email-masked]
Objet : Re: Preliminary agenda for London

On 26 February 2014 17:23, Mark Nottingham <[email-masked]> wrote:
> I also suspect we’ll get a lot more done in small-group discussion on Saturday, rather than queue-for-the-mic IETF fashion during the week, since this area still needs a *lot* of discussion.

And I'll note for the record, and for the large number of people unfamiliar with the process, the process point here.

No final decisions can be made at this meeting.  It's the practice of the IETF that decisions are made and confirmed on working group mailing lists.

I expect that we'll reach some informal conclusions during this meeting, but those decisions will be brought back here for confirmation.

-----Message d'origine-----
De : Mark Nottingham [mailto:[email-masked]]
Envoyé : jeudi 27 février 2014 02:24
À : Smith, Kevin, (R&D) Vodafone Group
Cc : [email-masked]
Objet : Re: Preliminary agenda for London

Hi Kevin,

As discussed, the Working Group is currently committed to shipping HTTP/2 for WGLC, and we have a number of issues to discuss in London.

If we get through those issues and have time left over (which I suspect we will), we can have a discussion of proxy work.

Additionally, we’re having a Design Team Meeting on the following Saturday:
  https://github.com/http2/wg_materials/blob/master/interim-14-03/arrangements.md
… where the schedule will be done in an unconference-ish way; i.e., driven by what the people who show up want to discuss.

I also suspect we’ll get a lot more done in small-group discussion on Saturday, rather than queue-for-the-mic IETF fashion during the week, since this area still needs a *lot* of discussion.

Cheers,

On 26 Feb 2014, at 11:24 pm, Smith, Kevin, (R&D) Vodafone Group <[email-masked]> wrote:

> Hi Mark,
>
> Please can we include a slot (e.g. 15mins) for the explicit proxy discussion in HTTPbis – Monday if possible?
>
> Cheers!
> Kevin

--
Mark Nottingham   http://www.mnot.net/

_________________________________________________________________________________________________________________________

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.