Issues and Requirements for Server Name Identification (SNI) Encryption in TLS
RFC 8744
Revision differences
Document history
Date | By | Action |
---|---|---|
2020-07-28
|
(System) | Received changes through RFC Editor sync (created alias RFC 8744, changed title to 'Issues and Requirements for Server Name Identification (SNI) Encryption in TLS', … Received changes through RFC Editor sync (created alias RFC 8744, changed title to 'Issues and Requirements for Server Name Identification (SNI) Encryption in TLS', changed abstract to '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.', changed pages to 13, changed standardization level to Informational, changed state to RFC, added RFC published event at 2020-07-28, changed IESG state to RFC Published) |
2020-07-28
|
(System) | RFC published |