<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.livingood-doh-implementation-risks-issues" target="https://datatracker.ietf.org/doc/html/draft-livingood-doh-implementation-risks-issues-04">
   <front>
      <title>Centralized DNS over HTTPS (DoH) Implementation Issues and Risks</title>
      <author initials="J." surname="Livingood" fullname="Jason Livingood">
         <organization>Comcast</organization>
      </author>
      <author initials="M." surname="Antonakakis" fullname="Manos Antonakakis">
         <organization>Georgia Institute of Technology</organization>
      </author>
      <author initials="B." surname="Sleigh" fullname="Bob Sleigh">
         <organization>BT Plc</organization>
      </author>
      <author initials="A." surname="Winfield" fullname="Alister Winfield">
         <organization>Sky</organization>
      </author>
      <date month="September" day="16" year="2019" />
      <abstract>
	 <t>   The DNS over HTTPS (DoH) protocol is specified in RFC8484.  This
   document considers Centralized DoH deployment, which seems one likely
   way that DoH may be implemented, based on recent industry discussions
   and testing.  This describes that implementation model, as well the
   potential associated risks and issues.  The document also makes
   recommendations pertaining to the implementation of DoH, as well as
   recommendations for further study prior to widespread adoption.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-livingood-doh-implementation-risks-issues-04" />
   
</reference>
