RFC 7671: The DNS-Based Authentication of Named Entities (DANE) Protocol: Updates and Operational Guidance
In plain English — editorial summary, not part of the RFC
This document clarifies and updates the DNS-Based Authentication of Named Entities (DANE) TLSA specification (RFC 6698), based on subsequent implementation experience. It also contains guidance for implementers, operators, and protocol developers who want to use DANE records.
Document record
- Document ID
- RFC7671
- Published
- October 2015
- Authors
- V. Dukhovni; W. Hardaker
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 33
- Also known as
- —
- Updates:
- RFC 6698
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7672SMTP Security via Opportunistic DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS)Current
October 2015
- RFC 8314Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and AccessUpdated
January 2018
- RFC 7250Using Raw Public Keys in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)Current
June 2014
- RFC 7218Adding Acronyms to Simplify Conversations about DNS-Based Authentication of Named Entities (DANE)Current
April 2014
- RFC 8460SMTP TLS ReportingCurrent
September 2018
- RFC 7673Using DNS-Based Authentication of Named Entities (DANE) TLSA Records with SRV RecordsCurrent
October 2015
- RFC 7662OAuth 2.0 Token IntrospectionCurrent
October 2015
- RFC 7685A Transport Layer Security (TLS) ClientHello Padding ExtensionCurrent
October 2015
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?