<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.campling-ech-deployment-considerations" target="https://datatracker.ietf.org/doc/html/draft-campling-ech-deployment-considerations-11">
   <front>
      <title>Encrypted Client Hello Deployment Considerations</title>
      <author initials="A." surname="Campling" fullname="Andrew Campling">
         </author>
      <author initials="P. A." surname="Vixie" fullname="Paul A. Vixie">
         <organization>Red Barn</organization>
      </author>
      <author initials="D." surname="Wright" fullname="David Wright">
         <organization>UK Safer Internet Centre</organization>
      </author>
      <author initials="A." surname="Taddei" fullname="Arnaud Taddei">
         <organization>Broadcom</organization>
      </author>
      <author initials="S." surname="Edwards" fullname="Simon Edwards">
         <organization>Broadcom</organization>
      </author>
      <date month="January" day="23" year="2026" />
      <abstract>
	 <t>   (Editorial note: to be updated as the text in the main body of the
   document is finalised) This document is intended to inform the
   community about the impact of the deployment of the proposed
   Encrypted Client Hello (ECH) standard that encrypts Server Name
   Indication (SNI) and other data.  Data encapsulated by ECH (ie data
   included in the encrypted ClientHelloInner) is of legitimate interest
   to on-path security actors including those providing inline malware
   detection, parental controls, content filtering to prevent access to
   malware and other risky traffic, mandatory security controls etc.

   The document includes observations on current use cases for SNI data
   in a variety of contexts.  It highlights how the use of that data is
   important to the operators of both public and private networks and
   shows how the loss of access to SNI data will cause difficulties in
   the provision of a range of services to end-users, including the
   potential weakening of cybersecurity defences.  Some mitigations are
   identified that may be useful for inclusion by those considering the
   adoption of support for ECH in their software.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-campling-ech-deployment-considerations-11" />
   
</reference>
