Specification of DNS over Dedicated QUIC Connections
draft-huitema-dprive-dnsoquic-00
| Document | Type | Replaced Internet-Draft (dprive WG) | |
|---|---|---|---|
| Authors | Christian Huitema , Allison Mankin , Sara Dickinson | ||
| Last updated | 2020-04-22 (Latest revision 2020-03-05) | ||
| Replaces | draft-huitema-quic-dnsoquic | ||
| Replaced by | RFC 9250 | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dprive-dnsoquic | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-huitema-dprive-dnsoquic-00.txt
Abstract
This document describes the use of QUIC to provide transport privacy for DNS. The encryption provided by QUIC has similar properties to that provided by TLS, while QUIC transport eliminates the head-of- line blocking issues inherent with TCP and provides more efficient error corrections than UDP. DNS over QUIC (DoQ) has privacy properties similar to DNS over TLS (DoT) specified in RFC7858, and performance characteristics similar to classic DNS over UDP.
Authors
Christian Huitema
Allison Mankin
Sara Dickinson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)