Tommy:
I suspect they are likely on list and can speak for themselves and do a
much better job of it, however aiui it was the absolute worst case where
QUIC connection setup was also included. This was a brief hallway
discussion back in Singapore so things may have progressed.
Vinny:
The draft I cited makes its specific use case not to include
multiplexing as it announces a separate ALPN and operates on a
different, dedicated port. If my memory serves me right previous
discussion in both the doh WG and related DNS working groups on the
subject of multiplexing were largely dismissive of it over a lack of
separation of concerns, privacy, among others.
- J
On 07/10/2020 14:39, Vinny Parla (vparla) wrote:
Hi,
What I am driving at in my original question is do we envision mixing
Content and DNS together in a multiplexed session or will DNS continue
to be an entirely independent channel (whether over HTTP/2 /3 Do53 DoQ
DoH).
-Vinny
*From:* Tommy Pauly <[email protected]>
*Sent:* Wednesday, October 7, 2020 9:23 AM
*To:* James <[email protected]>
*Cc:* Vinny Parla (vparla) <[email protected]>; [email protected]
*Subject:* Re: [dns-privacy] DNS and QUIC,HTTP/3 Long term vision...
Can you cite this claim about DNS over HTTP/3? The per-query cost once
an HTTP/3 connection is established should be minimal. If you’re
taking into account all setup overhead for an HTTPS connection as a
“per query” cost, that’s not representative of how DoH is reasonably
used (and would be a issue with existing DoH).
Thanks,
Tommy
On Oct 6, 2020, at 2:03 PM, James <[email protected]
<mailto:[email protected]>> wrote:
My most recent observations of discussions around DNS over QUIC
and HTTP/3 was that some folks had attempted DNS over HTTP/3,
however the overheads (~14KiB for a query at worst-case) made it
impractical and infeasible. With regards to DNS over QUIC, the
current dprive working group adopted draft [1] is focusing on stub
to recursive, but not necessarily as a multiplex with an existing
QUIC connection.
- J
1:https://tools.ietf.org/html/draft-ietf-dprive-dnsoquic-00
<https://tools.ietf.org/html/draft-ietf-dprive-dnsoquic-00>
On Mon, 5 Oct 2020 at 17:31, Vinny Parla (vparla)
<[email protected]
<mailto:[email protected]>> wrote:
Hi,
It was suggested that I ask this question on the 3 lists:
Now that QUIC & HTTP/3 is imminent…
I would like to know what the opinion is of the community on
the long term view of DNS.
Would DNS remain an independent channel or would it be
subsumed in a multiplexed stream via HTTP/3 in some future
version?
For example, would a browser perform DNS queries over a QUIC
multiplexed session?
(e.g. similar to how today an http proxy can perform DNS
queries on behalf of the client using that proxy)
Would love to hear from implementors what their long term view
is of this in particular.
Thanks,
-Vinny
_______________________________________________
dns-privacy mailing list
[email protected] <mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/dns-privacy
<https://www.ietf.org/mailman/listinfo/dns-privacy>
_______________________________________________
dns-privacy mailing list
[email protected] <mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/dns-privacy
<https://www.ietf.org/mailman/listinfo/dns-privacy>
_______________________________________________
dns-privacy mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dns-privacy
