<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.reddy-add-server-policy-selection" target="https://datatracker.ietf.org/doc/html/draft-reddy-add-server-policy-selection-09">
   <front>
      <title>DNS Server Selection: DNS Server Information with Assertion Token</title>
      <author initials="T." surname="Reddy.K" fullname="Tirumaleswar Reddy.K">
         <organization>Akamai</organization>
      </author>
      <author initials="D." surname="Wing" fullname="Dan Wing">
         <organization>Citrix Systems, Inc.</organization>
      </author>
      <author initials="M." surname="Richardson" fullname="Michael Richardson">
         <organization>Sandelman Software Works</organization>
      </author>
      <author initials="M." surname="Boucadair" fullname="Mohamed Boucadair">
         <organization>Orange</organization>
      </author>
      <date month="October" day="7" year="2021" />
      <abstract>
	 <t>   The document defines a mechanism that is meant to communicate DNS
   resolver information to DNS clients for use as a criteria for server
   selection decisions.  Such an information that is cryptographically
   signed to attest its authenticity is used for the selection of DNS
   resolvers.  Typically, evaluating the resolver information and the
   signatory, DNS clients with minimal or no human intervention can
   select the DNS servers for resolving domain names.

   This assertion is useful for encrypted DNS (e.g., DNS-over-TLS, DNS-
   over-HTTPS, or DNS-over-QUIC) servers that are either public
   resolvers or discovered in a local network.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-reddy-add-server-policy-selection-09" />
   
</reference>
