SMTP TLS Reporting
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 34
- Abstract
- A number of protocols exist for establishing encrypted channels between SMTP Mail Transfer Agents (MTAs), including STARTTLS, DNS- Based Authentication of Named Entities (DANE) TLSA, and MTA Strict Transport Security (MTA-STS). These protocols can fail due to misconfiguration or active attack, leading to undelivered messages or delivery over unencrypted or unauthenticated channels. This document describes a reporting mechanism and format by which sending systems can share statistics and specific information about potential failures with recipient domains. Recipient domains can then use this information to both detect potential attacks and diagnose unintentional misconfigurations.
- Publication Date
- 2018-09-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC8460- Link
- https://doi.org/10.17487/RFC8460
- Author(s)
- Daniel MargolisAlex BrotmanBinu RamakrishnanJanet JonesMark Risher
- Keyword(s)
- DANE, MTA-STS
Latest version of IETF RFC 8460
Document Versions — IETF RFC 8460
-
▶ IETF RFC 8460 (2018-09-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 1952 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 3339 [Active*]
- IETF RFC 3492 [Active*]
- IETF RFC 3986 [Active, Amended*]
- IETF RFC 5234 [Active, Amended*]
- IETF RFC 5280 [Active, Amended*]
- IETF RFC 5321 [Active*]
- IETF RFC 5322 [Active, Amended*]
- IETF RFC 5891 [Active*]
- IETF RFC 5952 [Active*]
- IETF RFC 6068 [Active*]
- IETF RFC 6376 [Active*]
- IETF RFC 6522 [Active*]
- IETF RFC 6698 [Active*]
- IETF RFC 6713 [Active*]
- IETF RFC 7208 [Active*]
- IETF RFC 7231 [Superseded*]
- IETF RFC 7405 [Active*]
- IETF RFC 7493 [Active*]
- IETF RFC 7671 [Active*]
- IETF RFC 7672 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8461 [Active*]
Bibliographic Reference(s)
- IETF RFC 3207 [Active*]
- IETF RFC 3464 [Active*]
- IETF RFC 3501 [Superseded*]
- IETF RFC 3864 [Active*]
- IETF RFC 6533 [Active*]
- IETF RFC 7435 [Active*]
- IETF RFC 7469 [Active*]
- IETF RFC 7489 [Superseded*]
- IETF RFC 8098 [Active*]
- IETF RFC 8126 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8460.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 8460, SMTP TLS Reporting. Available at https://doi.org/10.17487/RFC8460
Snippet:
IETF RFC 8460, SMTP TLS Reporting. Available at https://doi.org/10.17487/RFC8460
HTML (ISO 690 compliant)
Preview:
IETF RFC 8460, SMTP TLS Reporting. Available at https://doi.org/10.17487/RFC8460
Snippet:
<span class="citation"><cite>IETF RFC 8460</cite>, SMTP TLS Reporting. Available at <a href="https://doi.org/10.17487/RFC8460" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8460</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc8460">IETF RFC 8460</cite>, SMTP TLS Reporting <span class="doi">10.17487/RFC8460</span> </li>
Referenced By
- IETF RFC 8461 [Active*]
- IETF RFC 9170 [Active*]