FYI: Just published this draft describing transport of DNS over a
dedicated QUIC connection.
-- Christian Huitema

-------- Forwarded Message --------
Subject:        New Version Notification for draft-huitema-quic-dnsoquic-00.txt
Date:   Mon, 10 Apr 2017 09:45:37 -0700
From:   [email protected]
To:     Melinda Shore <[email protected]>, Sara Dickinson
<[email protected]>, Christian Huitema <[email protected]>, Allison
Mankin <[email protected]>, Janardhan Iyengar <[email protected]>,
Jana Iyengar <[email protected]>



A new version of I-D, draft-huitema-quic-dnsoquic-00.txt
has been successfully submitted by Christian Huitema and posted to the
IETF repository.

Name:           draft-huitema-quic-dnsoquic
Revision:       00
Title:          Specification of DNS over QUIC
Document date:  2017-04-10
Group:          Individual Submission
Pages:          18
URL:            
https://www.ietf.org/internet-drafts/draft-huitema-quic-dnsoquic-00.txt
Status:         https://datatracker.ietf.org/doc/draft-huitema-quic-dnsoquic/
Htmlized:       https://tools.ietf.org/html/draft-huitema-quic-dnsoquic-00
Htmlized:       
https://datatracker.ietf.org/doc/html/draft-huitema-quic-dnsoquic-00


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 has privacy properties
   similar to DNS over TLS specified in RFC7858, and performance similar
   to classic DNS over UDP.

                                                                                
  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

_______________________________________________
dns-privacy mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dns-privacy

Reply via email to