A DNS Resource Record for TLS Server Name Indication (DNS SNI)
draft-schwartz-dns-sni-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Benjamin M. Schwartz | ||
| Last updated | 2017-08-21 (Latest revision 2017-02-17) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-schwartz-dns-sni-02.txt
https://www.ietf.org/archive/id/draft-schwartz-dns-sni-02.txt
Abstract
The SNI record type allows a domain owner to specify the "server name" to indicate in TLS connections, if it is different from the domain name. This allows domains that use shared hosting and wildcard or multi-domain (UCC) certificates to change the only domain name shown in cleartext, to prevent a passive adversary from identifying exactly which domain a user is accessing.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)