<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-add-ddr" target="https://datatracker.ietf.org/doc/html/draft-ietf-add-ddr-05">
   <front>
      <title>Discovery of Designated Resolvers</title>
      <author initials="T." surname="Pauly" fullname="Tommy Pauly">
         <organization>Apple Inc.</organization>
      </author>
      <author initials="E." surname="Kinnear" fullname="Eric Kinnear">
         <organization>Apple Inc.</organization>
      </author>
      <author initials="C. A." surname="Wood" fullname="Christopher A. Wood">
         <organization>Cloudflare</organization>
      </author>
      <author initials="P." surname="McManus" fullname="Patrick McManus">
         <organization>Fastly</organization>
      </author>
      <author initials="T." surname="Jensen" fullname="Tommy Jensen">
         <organization>Microsoft</organization>
      </author>
      <date month="January" day="31" year="2022" />
      <abstract>
	 <t>   This document defines Discovery of Designated Resolvers (DDR), a
   mechanism for DNS clients to use DNS records to discover a resolver&#x27;s
   encrypted DNS configuration.  This mechanism can be used to move from
   unencrypted DNS to encrypted DNS when only the IP address of a
   resolver is known.  This mechanism is designed to be limited to cases
   where unencrypted resolvers and their designated resolvers are
   operated by the same entity or cooperating entities.  It can also be
   used to discover support for encrypted DNS protocols when the name of
   an encrypted resolver is known.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-add-ddr-05" />
   
</reference>
