metasystema.org
CurrentINFORMATIONALIETF stream

RFC 8744: Issues and Requirements for Server Name Identification (SNI) Encryption in TLS

In plain English — editorial summary, not part of the RFC

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 "HTTP co-tenancy" 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.

Document record

Document ID
RFC8744
Published
July 2020
Authors
C. Huitema
Status
INFORMATIONAL
Stream
IETF
Area
sec
Pages
13
Also known as
—

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8744-issues-and-requirements-for-server-name-identification-sni-encryption-in-tls