IETF RFC 8689
[ACTIVE]
SMTP Require TLS Option
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 16
- Abstract
- The SMTP STARTTLS option, used in negotiating transport-level encryption of SMTP connections, is not as useful from a security standpoint as it might be because of its opportunistic nature; message delivery is, by default, prioritized over security. This document describes an SMTP service extension, REQUIRETLS, and a message header field, TLS-Required. If the REQUIRETLS option or TLS-Required message header field is used when sending a message, it asserts a request on the part of the message sender to override the default negotiation of TLS, either by requiring that TLS be negotiated when the message is relayed or by requesting that recipient-side policy mechanisms such as MTA-STS and DNS-Based Authentication of Named Entities (DANE) be ignored when relaying a message for which security is unimportant.
- Publication Date
- 2019-11-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC8689- Link
- https://doi.org/10.17487/RFC8689
- Author(s)
- Jim Fenton
- Keyword(s)
- SMTP
Latest version of IETF RFC 8689
Document Versions — IETF RFC 8689
-
▶ IETF RFC 8689 (2019-11-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IANA, "Mail Parameters", <http://www.iana.org/assignments/mail-parameters>. EXTERNAL
- IANA, "Permanent Message Header Field Names", <https://www.iana.org/assignments/message-headers>. EXTERNAL
- IANA, "Simple Mail Transfer Protocol (SMTP) Enhanced Status Codes Registry", <https://www.iana.org/assignments/smtp-enhanced-status-codes>. EXTERNAL
- IETF RFC 2119 [Active*]
- IETF RFC 3207 [Active*]
- IETF RFC 3461 [Active*]
- IETF RFC 4033 [Active*]
- IETF RFC 4034 [Active*]
- IETF RFC 4035 [Active*]
- IETF RFC 5234 [Active, Amended*]
- IETF RFC 5248 [Active*]
- IETF RFC 5321 [Active*]
- IETF RFC 5322 [Active, Amended*]
- IETF RFC 6125 [Superseded*]
- IETF RFC 7525 [Superseded*]
- IETF RFC 7672 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8314 [Active*]
- IETF RFC 8461 [Active*]
Bibliographic Reference(s)
- IETF RFC 1939 [Active*]
- IETF RFC 2033 [Active*]
- IETF RFC 3501 [Superseded*]
- IETF RFC 4880 [Superseded*]
- IETF RFC 5228 [Active*]
- IETF RFC 5598 [Active*]
- IETF RFC 6409 [Active*]
- IETF RFC 8551 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8689.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 8689, SMTP Require TLS Option. Available at https://doi.org/10.17487/RFC8689
Snippet:
IETF RFC 8689, SMTP Require TLS Option. Available at https://doi.org/10.17487/RFC8689
HTML (ISO 690 compliant)
Preview:
IETF RFC 8689, SMTP Require TLS Option. Available at https://doi.org/10.17487/RFC8689
Snippet:
<span class="citation"><cite>IETF RFC 8689</cite>, SMTP Require TLS Option. Available at <a href="https://doi.org/10.17487/RFC8689" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8689</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc8689">IETF RFC 8689</cite>, SMTP Require TLS Option <span class="doi">10.17487/RFC8689</span> </li>
Referenced By
- IETF RFC 10003 [Active*]
- IETF RFC 9525 [Active*]