draft-ietf-dprive-unauth-to-authoritative-02.txt   draft-ietf-dprive-unauth-to-authoritative-03.txt 
Network Working Group P. Hoffman Network Working Group P. Hoffman
Internet-Draft ICANN Internet-Draft ICANN
Intended status: Experimental P. van Dijk Intended status: Experimental P. van Dijk
Expires: 18 December 2021 PowerDNS Expires: January 13, 2022 PowerDNS
16 June 2021 July 12, 2021
Recursive to Authoritative DNS with Unauthenticated Encryption Recursive to Authoritative DNS with Unauthenticated Encryption
draft-ietf-dprive-unauth-to-authoritative-02 draft-ietf-dprive-unauth-to-authoritative-03
Abstract Abstract
This document describes a use case and a method for a DNS recursive This document describes a use case and a method for a DNS recursive
resolver to use unauthenticated encryption when communicating with resolver to use unauthenticated encryption when communicating with
authoritative servers. The motivating use case for this method is authoritative servers. The motivating use case for this method is
that more encryption on the Internet is better, and some resolver that more encryption on the Internet is better, and some resolver
operators believe that unauthenticated encryption is better than no operators believe that unauthenticated encryption is better than no
encryption at all. The method described here is optional for both encryption at all. The method described here is optional for both
the recursive resolver and the authoritative server. This method the recursive resolver and the authoritative server. This method
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 18 December 2021. This Internet-Draft will expire on January 13, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents
license-info) in effect on the date of publication of this document. (https://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. Code Components carefully, as they describe your rights and restrictions with respect
extracted from this document must include Simplified BSD License text to this document. Code Components extracted from this document must
as described in Section 4.e of the Trust Legal Provisions and are include Simplified BSD License text as described in Section 4.e of
provided without warranty as described in the Simplified BSD License. the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Use Case for Unauthenticated Encryption . . . . . . . . . 3 1.1. Use Case for Unauthenticated Encryption . . . . . . . . . 3
1.2. Summary of Protocol . . . . . . . . . . . . . . . . . . . 3 1.2. Summary of Protocol . . . . . . . . . . . . . . . . . . . 3
1.3. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4 1.3. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4
2. Discovering Whether an Authoritative Server Uses 2. Discovery of Authoritative Server Encryption . . . . . . . . 4
Encryption . . . . . . . . . . . . . . . . . . . . . . . 4 3. Processing Discovery Responses . . . . . . . . . . . . . . . 5
3. Resolving with Encryption . . . . . . . . . . . . . . . . . . 5 3.1. Resolver Process as Pseudocode . . . . . . . . . . . . . 6
3.1. Resolver Session Failures . . . . . . . . . . . . . . . . 5 3.2. Resolver Session Failures . . . . . . . . . . . . . . . . 7
4. Serving with Encryption . . . . . . . . . . . . . . . . . . . 6 4. Serving with Encryption . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 7 8.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
A recursive resolver using traditional DNS over port 53 may wish A recursive resolver using traditional DNS over port 53 may wish
instead to use encrypted communication with authoritative servers in instead to use encrypted communication with authoritative servers in
order to limit snooping of its DNS traffic by passive or on-path order to limit snooping of its DNS traffic by passive or on-path
attackers. The recursive resolver can use unauthenticated encryption attackers. The recursive resolver can use unauthenticated encryption
(defined in [OPPORTUN]) to achieve this goal. (defined in [OPPORTUN]) to achieve this goal.
This document describes the use case for unauthenticated encryption This document describes the use case for unauthenticated encryption
in recursive resolvers in Section 1.1. The encryption method with in recursive resolvers in Section 1.1. The encryption method with
authoritative servers can be DNS-over-TLS [DNSOTLS] (DoT), DNS-over- authoritative servers can be DNS-over-TLS [DNSOTLS] (DoT), DNS-over-
HTTPS [DNSOHTTPS] (DoH), and/or DNS-over-QUIC [DNSOQUIC] (DoQ), as HTTPS [DNSOHTTPS] (DoH), and/or DNS-over-QUIC [DNSOQUIC] (DoQ).
described in Section 3.
The document also describes a discovery method that shows if an The document also describes a discovery method that shows if an
authoritative server supports encryption in Section 2. authoritative server supports encryption in Section 2.
See [FULL-AUTH] for a description of the use case and a proposed See [FULL-AUTH] for a description of the use case and a proposed
mechanism for fully-authenticated encryption. See [COMMON] for a mechanism for fully-authenticated encryption.
definition of the features that are in common between this document
and [FULL-AUTH].
NOTE: The draft uses the SVCB record as a discovery mechanism for NOTE: The draft uses the SVCB record as a discovery mechanism for
encryption by a particular authoritative server. Any record type encryption by a particular authoritative server. Any record type
that can show multiple types of encryption (currently DoT, DoH, and that can show multiple types of encryption (currently DoT, DoH, and
DoQ) can be used for discovery. Thus, this record type might change DoQ) can be used for discovery. Thus, this record type might change
in the future, depending on the discussion in the DPRIVE WG. in the future, depending on the discussion in the DPRIVE WG.
1.1. Use Case for Unauthenticated Encryption 1.1. Use Case for Unauthenticated Encryption
The use case in this document for unauthenticated encryption is The use case in this document for unauthenticated encryption is
skipping to change at page 3, line 27 skipping to change at page 3, line 23
use encryption with recursive resolvers if it doesn't cost much. In use encryption with recursive resolvers if it doesn't cost much. In
this use case, resolvers do not want to return an error for requests this use case, resolvers do not want to return an error for requests
that were sent over an encrypted channel if they would have been able that were sent over an encrypted channel if they would have been able
to give a correct answer using unencrypted transport. to give a correct answer using unencrypted transport.
Resolvers and authoritative servers understand that using encryption Resolvers and authoritative servers understand that using encryption
costs something, but are willing to absorb the costs for the benefit costs something, but are willing to absorb the costs for the benefit
of more Internet traffic being encrypted. The extra costs (compared of more Internet traffic being encrypted. The extra costs (compared
to using traditional DNS on port 53) include: to using traditional DNS on port 53) include:
* Extra round trips to establish TCP for every session (but not o Extra round trips to establish TCP for every session (but not
necessarily for every query) necessarily for every query)
* Extra round trips for TLS establishment o Extra round trips for TLS establishment
* Greater CPU use for TLS establishment o Greater CPU use for TLS establishment
* Greater CPU use for encryption after TLS establishment o Greater CPU use for encryption after TLS establishment
* Greater memory use for holding TLS state o Greater memory use for holding TLS state
This use case is not expected to apply to all resolvers or This use case is not expected to apply to all resolvers or
authoritative servers. For example, according to [RSO_STATEMENT], authoritative servers. For example, according to [RSO_STATEMENT],
some root server operators do not want to be the early adopters for some root server operators do not want to be the early adopters for
DNS with encryption. The protocol in this document explicitly allows DNS with encryption. The protocol in this document explicitly allows
authoritative servers to signal when they are ready to begin offering authoritative servers to signal when they are ready to begin offering
DNS with encryption. DNS with encryption.
1.2. Summary of Protocol 1.2. Summary of Protocol
This summary gives an overview of how the parts of the protocol work This summary gives an overview of how the parts of the protocol work
together. together.
* The resolver discovers whether any authoritative server of o The resolver discovers whether any authoritative server of
interest supports DNS with encryption by querying for the SVCB interest supports DNS with encryption by querying for the SVCB
records [SVCB]. As described in [DNS-SVCB], SVCB records can records [SVCB]. As described in [DNS-SVCB], SVCB records can
indicate that a server supports encrypted transport of DNS indicate that a server supports encrypted transport of DNS
queries. queries.
NOTE: In this document, the term "SVCB record" is used _only_ for NOTE: In this document, the term "SVCB record" is used _only_ for
SVCB records that indicate encryption as described in [DNS-SVCB]. SVCB records that indicate encryption as described in [DNS-SVCB].
SVCB records that do not have these indicators in the RDATA are SVCB records that do not have these indicators in the RDATA are
not included in the term "SVCB record" in this document. not included in the term "SVCB record" in this document.
* The resolver uses any authoritative server with a SVCB record that o The resolver uses any authoritative server with a SVCB record that
indicates encryption to perform unauthenticated encryption. indicates encryption to perform unauthenticated encryption.
* The resolver does not fail to set up encryption if the o The resolver does not fail to set up encryption if the
authentication in the TLS session fails. authentication in the TLS session fails.
1.3. Definitions 1.3. Definitions
The terms "recursive resolver", "authoritative server", and "classic The terms "recursive resolver", "authoritative server", and "classic
DNS" are defined in [DNS-TERM]. DNS" are defined in [DNS-TERM].
"DNS with encryption" means transport of DNS over any of DoT, DoH, or "DNS with encryption" means transport of DNS over any of DoT, DoH, or
DoQ. A server that supports DNS with encryption supports transport DoQ. A server that supports DNS with encryption supports transport
over one or more of DoT, DoH, or DoQ. over one or more of DoT, DoH, or DoQ.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [MUSTSHOULD1] [MUSTSHOULD2] when, and only when, they appear in 14 [MUSTSHOULD1] [MUSTSHOULD2] when, and only when, they appear in
all capitals, as shown here. all capitals, as shown here.
2. Discovering Whether an Authoritative Server Uses Encryption 2. Discovery of Authoritative Server Encryption
An authoritative server that supports DNS with encryption makes
itself discoverable by publishing one or more DNS SVCB records that
contain "alpn" parameter keys. SVCB records are defined in [SVCB],
and the DNS extension to those records is defined in [DNS-SVCB].
A recursive resolver discovers whether an authoritative server A recursive resolver discovers whether an authoritative server
supports DNS with encryption by using the discovery mechanism supports DNS with encryption by looking for cached SVCB records for
described in Section 2.1 of [COMMON]. A resolver MAY also use port the name of the authoritative server with a positive answer. A
probing, although the mechanism for that is not described here. cached DNS SVCB record with a negative answer indicates that the
authoritative server does not support any encrypted transport.
A resolver MAY also use port probing, although the mechanism for that
is not described here.
If the cache has no positive or negative answers for any SVCB record If the cache has no positive or negative answers for any SVCB record
for any of a zone's authoritative servers, the resolver MAY send for any of a zone's authoritative servers, the resolver MAY send
queries for the SVCB records (and for the A/AAAA records of names queries for the SVCB records (and for the A/AAAA records of names
mentioned in those SVCB records) for some or all of the zone's mentioned in those SVCB records) for some or all of the zone's
authoritative servers and wait for a positive response so that the authoritative servers and wait for a positive response so that the
resolver can use DNS with encryption for the original query. In this resolver can use DNS with encryption for the original query. In this
situation, the resolver MAY instead just use classic DNS for the situation, the resolver MAY instead just use classic DNS for the
original query but simultaneously queue queries for the SVCB (and original query but simultaneously queue queries for the SVCB (and
subsequent A/AAAA) records for some or all of the zone's subsequent A/AAAA) records for some or all of the zone's
authoritative servers so that future queries might be able to use DNS authoritative servers so that future queries might be able to use DNS
with encryption. with encryption.
DNSSEC validation of SVCB RRsets used strictly for this discovery DNSSEC validation of SVCB RRsets used strictly for this discovery
mechanism is not mandated. mechanism is not mandated.
3. Resolving with Encryption 3. Processing Discovery Responses
A resolver following this protocol processes the discovery response After a resolver has DNS SCVB records in its cache (possibly due to
using the processing mechanism described in [COMMON]. having just queried for them), it needs to use those records to try
to find an authoritative server that uses DNS with encryption. This
section describes how the resolver can make that selection.
A resolver MUST NOT attempt encryption for a server that has a
negative response in its cache for the associated DNS SVCB record.
After sending out all requests for SVCB records for the authoritative
servers in the NS RRset for a name, if all of the SVCB records for
those authoritative servers in the cache are negative responses, the
resolver MUST use classic (unencrypted) DNS instead of encryption.
Similarly, if none of the DNS SVCB records for the authoritative
servers in the cache have supported "alpn" parameters, the resolver
MUST use classic (unencrypted) DNS instead of encryption.
If there are any DNS SVCB records in the cache for the authoritative
servers for a zone with supported "alpn" parameters, the resolver
MUST try each indicated authoritative server using DNS with
encryption until it successfully sets up a connection. The resolver
only attempts to use the encrypted transports that are in the
associated SVCB record for the authoritative server. (( Note that
this completely prohibits "simple port 853 probing" even though that
is what some operators are currently doing. Does the WG want to be
this strict? ))
A resolver SHOULD keep a DNS with encryption session to a particular
server open if it expects to send additional queries to that server
in a short period of time. [DNS-OVER-TCP] says "both clients and
servers SHOULD support connection reuse" for TCP connections, and
that advice could apply as well for DNS with encryption, especially
as DNS with encryption has far greater overhead for re-establishing a
connection. If the server closes the DNS with encryption session,
the resolver can possibly re-establish a DNS with encryption session
using encrypted session resumption.
For any DNS with encryption protocols, TLS version 1.3 [TLS-13] or
later MUST be used.
A resolver following this protocol does not need to authenticate TLS A resolver following this protocol does not need to authenticate TLS
servers. Thus, when setting up a TLS connection, if the server's servers. Thus, when setting up a TLS connection, if the server's
authentication credentials do not match those expected by the authentication credentials do not match those expected by the
resolver, the resolver continues with the TLS connection. Privacy- resolver, the resolver continues with the TLS connection. Privacy-
oriented resolvers (defined in [PRIVACY-REC]) following this protocol oriented resolvers (defined in [PRIVACY-REC]) following this protocol
MUST NOT indicate that they are using encryption because this MUST NOT indicate that they are using encryption because this
protocol is susceptible to on-path attacks. protocol is susceptible to on-path attacks.
3.1. Resolver Session Failures 3.1. Resolver Process as Pseudocode
This section is meant as an informal clarification of the protocol,
and is not normative. The pseudocode here is designed to show the
intent of the protocol, so it is not optimized for things like
intersection of sets and other shortcuts.
In this code, "signal_rrset(this_name)" means an "SVCB" query for the
"'_dns'" prefix of "this_name". The "Query over secure transport
until successful" section ignores differences in name server
selection and retry behaviour in different resolvers.
# Inputs
ns_names = List of NS Rdatas from the NS RRset for the queried name
can_do_secure = List of secure transports supported by resolver
secure_names_and_transports = Empty list, filled in below
# Fill secure_names_and_transports with (name, transport) tuples
for this_name in ns_names:
if signal_rrset(this_name) is in the resolver cache:
if signal_rrset(this_name) positively does not exist:
continue
for this_transport in signal_rrset(this_name):
if this_transport in can_do_secure:
add (this_name, this_transport) to secure_names_and_transports
else: # signal_rrset(this_name) is not in the resolver cache
queue a query for signal_rrset(this_name) for later caching
# Query over secure transport until successful
for (this_name, this_transport) tuple in secure_names_and_transports:
query using this_transport on this_name
if successful:
finished
# Got here if no this_name/this_transport query was successful
# or if secure_names_and_transports was empty
query using classic DNS on any/all ns_names; finished
3.2. Resolver Session Failures
The following are some of the reasons that a DNS with encryption The following are some of the reasons that a DNS with encryption
session might fail to be set up: session might fail to be set up:
* The resolver receives a TCP RST response o The resolver receives a TCP RST response
* The resolver does not receive replies to TCP or TLS setup (such as o The resolver does not receive replies to TCP or TLS setup (such as
getting the TCP SYN message, the first TLS message, or completing getting the TCP SYN message, the first TLS message, or completing
TLS handshakes) TLS handshakes)
* The TLS handshake gets a definitive failure o The TLS handshake gets a definitive failure
* The encrypted session fails for reasons other than for o The encrypted session fails for reasons other than for
authentication, such as incorrect algorithm choices or TLS record authentication, such as incorrect algorithm choices or TLS record
failures failures
4. Serving with Encryption 4. Serving with Encryption
An authoritative server following this protocol publishes the An operator of an authoritative server following this protocol SHOULD
discovery records using the serving mechanism described in [COMMON]. publish SVCB records as described in Section 2. If they cannot
publish such records, the security properties of their authoritative
servers will not be found. If an operator wants to test serving
using encryption, they can publish SVCB records with short TTLs and
then stop serving with encryption after removing the SVCB records and
waiting for the TTLs to expire.
It is acceptable for an operator of authoritative servers to only
offer encryption on some of the named authoritative servers, such as
when the operator is determining how far to roll out encrypted
service.
A server MAY close an encrypted connection at any time. For example,
it can close the session if it has not received a DNS query in a
defined length of time. The server MAY close an encrypted session
after it sends a DNS response; however, it might also want to keep
the session open waiting for another DNS query from the resolver.
[DNS-OVER-TCP] says "both clients and servers SHOULD support
connection reuse" for TCP connections, and that advice could apply as
well for DNS with encryption, especially as DNS with encryption has
far greater overhead for re-establishing a connection. If the server
closes the DNS with encryption session, the resolver can possibly re-
establish a DNS with encryption session using encrypted session
resumption.
For any DNS with encryption protocols, TLS version 1.3 [TLS-13] or
later MUST be used.
5. IANA Considerations 5. IANA Considerations
Relevant IANA considerations are covered in [COMMON]. (( Update registration for TCP/853 to also include ADoT ))
(( Maybe other updates for DoH and DoQ ))
6. Security Considerations 6. Security Considerations
The method described in this document explicitly allows a resolver to The method described in this document explicitly allows a resolver to
perform DNS communications over traditional unencrypted, perform DNS communications over traditional unencrypted,
unauthenticated DNS on port 53, if it cannot find an authoritative unauthenticated DNS on port 53, if it cannot find an authoritative
server that advertises that it supports encryption. The method server that advertises that it supports encryption. The method
described in this document explicitly allows a resolver using described in this document explicitly allows a resolver using
encryption to choose to allow unauthenticated encryption. In either encryption to choose to allow unauthenticated encryption. In either
of these cases, the resulting communication will be susceptible to of these cases, the resulting communication will be susceptible to
skipping to change at page 6, line 37 skipping to change at page 8, line 34
Puneet Sood contributed many ideas to early drafts of this document. Puneet Sood contributed many ideas to early drafts of this document.
The DPRIVE Working Group has contributed many ideas that keep The DPRIVE Working Group has contributed many ideas that keep
shifting the focus and content of this document. shifting the focus and content of this document.
8. References 8. References
8.1. Normative References 8.1. Normative References
[COMMON] Dijk, P. V. and P. Hoffman, "Common Features for Encrypted [DNS-SVCB]
Recursive to Authoritative DNS", Work in Progress, Schwartz, B., "Service Binding Mapping for DNS Servers",
Internet-Draft, draft-pp-dprive-common-features-01, 19 May draft-schwartz-svcb-dns-03 (work in progress), April 2021.
2021, <https://www.ietf.org/archive/id/draft-pp-dprive-
common-features-01.txt>.
[DNS-SVCB] Schwartz, B., "Service Binding Mapping for DNS Servers",
Work in Progress, Internet-Draft, draft-schwartz-svcb-dns-
03, 19 April 2021, <https://www.ietf.org/archive/id/draft-
schwartz-svcb-dns-03.txt>.
[DNS-TERM] Hoffman, P. and K. Fujiwara, "DNS Terminology", Work in [DNS-TERM]
Progress, Internet-Draft, draft-ietf-dnsop-rfc8499bis-01, Hoffman, P. and K. Fujiwara, "DNS Terminology", draft-
20 November 2020, <https://www.ietf.org/archive/id/draft- ietf-dnsop-rfc8499bis-02 (work in progress), June 2021.
ietf-dnsop-rfc8499bis-01.txt>.
[FULL-AUTH] [FULL-AUTH]
Pauly, T., Rescorla, E., Schinazi, D., and C. A. Wood, Pauly, T., Rescorla, E., Schinazi, D., and C. A. Wood,
"Signaling Authoritative DNS Encryption", Work in "Signaling Authoritative DNS Encryption", draft-rescorla-
Progress, Internet-Draft, draft-rescorla-dprive-adox- dprive-adox-latest-00 (work in progress), February 2021.
latest-00, 26 February 2021,
<https://www.ietf.org/archive/id/draft-rescorla-dprive-
adox-latest-00.txt>.
[MUSTSHOULD1] [MUSTSHOULD1]
Bradner, S., "Key words for use in RFCs to Indicate Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[MUSTSHOULD2] [MUSTSHOULD2]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[OPPORTUN] Dukhovni, V., "Opportunistic Security: Some Protection [OPPORTUN]
Dukhovni, V., "Opportunistic Security: Some Protection
Most of the Time", RFC 7435, DOI 10.17487/RFC7435, Most of the Time", RFC 7435, DOI 10.17487/RFC7435,
December 2014, <https://www.rfc-editor.org/info/rfc7435>. December 2014, <https://www.rfc-editor.org/info/rfc7435>.
[SVCB] Schwartz, B., Bishop, M., and E. Nygren, "Service binding [SVCB] Schwartz, B., Bishop, M., and E. Nygren, "Service binding
and parameter specification via the DNS (DNS SVCB and and parameter specification via the DNS (DNS SVCB and
HTTPS RRs)", Work in Progress, Internet-Draft, draft-ietf- HTTPS RRs)", draft-ietf-dnsop-svcb-https-06 (work in
dnsop-svcb-https-06, 16 June 2021, progress), June 2021.
<https://www.ietf.org/archive/id/draft-ietf-dnsop-svcb-
https-06.txt>. [TLS-13] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>.
8.2. Informative References 8.2. Informative References
[DNS-OVER-TCP]
Dickinson, J., Dickinson, S., Bellis, R., Mankin, A., and
D. Wessels, "DNS Transport over TCP - Implementation
Requirements", RFC 7766, DOI 10.17487/RFC7766, March 2016,
<https://www.rfc-editor.org/info/rfc7766>.
[DNSOHTTPS] [DNSOHTTPS]
Hoffman, P. and P. McManus, "DNS Queries over HTTPS Hoffman, P. and P. McManus, "DNS Queries over HTTPS
(DoH)", RFC 8484, DOI 10.17487/RFC8484, October 2018, (DoH)", RFC 8484, DOI 10.17487/RFC8484, October 2018,
<https://www.rfc-editor.org/info/rfc8484>. <https://www.rfc-editor.org/info/rfc8484>.
[DNSOQUIC] Huitema, C., Mankin, A., and S. Dickinson, "Specification [DNSOQUIC]
of DNS over Dedicated QUIC Connections", Work in Progress, Huitema, C., Mankin, A., and S. Dickinson, "Specification
Internet-Draft, draft-ietf-dprive-dnsoquic-02, 22 February of DNS over Dedicated QUIC Connections", draft-ietf-
2021, <https://www.ietf.org/archive/id/draft-ietf-dprive- dprive-dnsoquic-02 (work in progress), February 2021.
dnsoquic-02.txt>.
[DNSOTLS] Hu, Z., Zhu, L., Heidemann, J., Mankin, A., Wessels, D., [DNSOTLS] Hu, Z., Zhu, L., Heidemann, J., Mankin, A., Wessels, D.,
and P. Hoffman, "Specification for DNS over Transport and P. Hoffman, "Specification for DNS over Transport
Layer Security (TLS)", RFC 7858, DOI 10.17487/RFC7858, May Layer Security (TLS)", RFC 7858, DOI 10.17487/RFC7858, May
2016, <https://www.rfc-editor.org/info/rfc7858>. 2016, <https://www.rfc-editor.org/info/rfc7858>.
[PRIVACY-REC] [PRIVACY-REC]
Dickinson, S., Overeinder, B., van Rijswijk-Deij, R., and Dickinson, S., Overeinder, B., van Rijswijk-Deij, R., and
A. Mankin, "Recommendations for DNS Privacy Service A. Mankin, "Recommendations for DNS Privacy Service
Operators", BCP 232, RFC 8932, DOI 10.17487/RFC8932, Operators", BCP 232, RFC 8932, DOI 10.17487/RFC8932,
 End of changes. 33 change blocks. 
80 lines changed or deleted 186 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/