RFC 6698: The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA
In plain English — editorial summary, not part of the RFC
Encrypted communication on the Internet often uses Transport Layer Security (TLS), which depends on third parties to certify the keys used. This document improves on that situation by enabling the administrators of domain names to specify the keys used in that domain's TLS servers. This requires matching improvements in TLS client software, but no change in TLS server software. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6698
- Published
- August 2012
- Authors
- P. Hoffman; J. Schlyter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 37
- Also known as
- —
Topics
Referenced by
3 later RFCs formally update or obsolete part of this document.
- RFC 7218Adding Acronyms to Simplify Conversations about DNS-Based Authentication of Named Entities (DANE)Current
April 2014
- RFC 7671The DNS-Based Authentication of Named Entities (DANE) Protocol: Updates and Operational GuidanceCurrent
October 2015
- RFC 8749Moving DNSSEC Lookaside Validation (DLV) to Historic StatusCurrent
March 2020
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6024Trust Anchor Management RequirementsCurrent
October 2010
- RFC 6844DNS Certification Authority Authorization (CAA) Resource RecordObsoleted
January 2013
- RFC 7030Enrollment over Secure TransportUpdated
October 2013
- RFC 7250Using Raw Public Keys in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)Current
June 2014
- RFC 5758Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSACurrent
January 2010
- RFC 8080Edwards-Curve Digital Security Algorithm (EdDSA) for DNSSECCurrent
February 2017
- RFC 5272Certificate Management over CMS (CMC)Obsoleted
June 2008
- RFC 8410Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key InfrastructureUpdated
August 2018
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?