<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-tls-sni-encryption" target="https://datatracker.ietf.org/doc/html/draft-ietf-tls-sni-encryption-09">
   <front>
      <title>Issues and Requirements for Server Name Identification (SNI) Encryption in TLS</title>
      <author initials="C." surname="Huitema" fullname="Christian Huitema">
         <organization>Private Octopus Inc.</organization>
      </author>
      <author initials="E." surname="Rescorla" fullname="Eric Rescorla">
         <organization>RTFM, Inc.</organization>
      </author>
      <date month="October" day="28" year="2019" />
      <abstract>
	 <t>This document describes the general problem of encrypting the Server Name Identification (SNI) TLS parameter. The proposed solutions hide a hidden service behind a fronting service, only disclosing the SNI of the fronting service to external observers. This document lists known attacks against SNI encryption, discusses the current &quot;HTTP co-tenancy&quot; solution, and presents requirements for future TLS-layer solutions.

 In practice, it may well be that no solution can meet every requirement and that practical solutions will have to make some compromises.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-tls-sni-encryption-09" />
   
</reference>
