Re: Demultiplexing HTTP and DNS on the same listener [New Version Notification for draft-dkg-dprive-demux-dns-http-02] from Martin Thomson on 2017-05-04 (ietf-http-wg@w3.org from April to June 2017)

From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 4 May 2017 10:21:20 +1000
To: Mike Bishop <Michael.Bishop@microsoft.com>
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, Patrick McManus <mcmanus@ducksong.com>, HTTP Working Group <ietf-http-wg@w3.org>, DNS Privacy Working Group <dns-privacy@ietf.org>
Message-ID: <CABkgnnVLasxAfsezDp4H0cSOme5okHUY0ruG7EzgsNEW89SmDQ@mail.gmail.com>

On 4 May 2017 at 10:14, Mike Bishop <Michael.Bishop@microsoft.com> wrote:
> It's ALPN.  At first blush, I would pick a different ALPN token for h2+DNS and define it as a new, derivative protocol.

For DKG to realize his goal, every client would have to offer that
label.  That's not impossible, nor does it make it a bad choice, but
you have to realize that this isn't as good an outcome.

Received on Thursday, 4 May 2017 00:21:55 UTC