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 On Mon, 5 Oct 2020 at 17:31, Vinny Parla (vparla) <vparla= [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] > https://www.ietf.org/mailman/listinfo/dns-privacy >
_______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
