RFC 6394
Use Cases and Requirements for DNS-Based Authentication of Named Entities (DANE), October 2011
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6394
Discuss this RFC: Send questions or comments to the mailing list dane@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6394
Abstract
Many current applications use the certificate-based authentication features in Transport Layer Security (TLS) to allow clients to verify that a connected server properly represents a desired domain name. Typically, this authentication has been based on PKIX certificate chains rooted in well-known certificate authorities (CAs), but additional information can be provided via the DNS itself. This document describes a set of use cases in which the DNS and DNS Security Extensions (DNSSEC) could be used to make assertions that support the TLS authentication process. The main focus of this document is TLS server authentication, but it also covers TLS client authentication for applications where TLS clients are identified by domain names. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.