[Top] [All Lists]

[ietf-smtp] Fwd: New Version Notification for draft-fenton-smtp-require-tls-01.txt

2016-02-13 17:43:28

I have submitted an update to this draft. Thanks to several of you for
excellent comments. Significant changes are:

- Conversion of REQUIRETLS from an SMTP verb to a MAIL FROM parameter to
better associate REQUIRETLS requirements with transmission of individual

- Addition of an option to require DNSSEC lookup of the remote mail
server, since this affects the common name of the certificate that is

- Clarified the wording to more clearly state that TLS sessions must be
established and not simply that STARTTLS is negotiated.

- Introduced need for minimum encryption standards (key lengths and

- Substantially rewritten Security Considerations section

Further comments are of course appreciated.


-------- Forwarded Message --------
Subject:        New Version Notification for 
Date:   Sat, 13 Feb 2016 15:36:57 -0800
From:   internet-drafts(_at_)ietf(_dot_)org
To:     Jim Fenton <fenton(_at_)bluepopcorn(_dot_)net>

A new version of I-D, draft-fenton-smtp-require-tls-01.txt
has been successfully submitted by Jim Fenton and posted to the
IETF repository.

Name:           draft-fenton-smtp-require-tls
Revision:       01
Title:          SMTP Require TLS Option
Document date:  2016-02-13
Group:          Individual Submission
Pages:          10

   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 prioritized over security.  This document
   describes a complementary SMTP service extension, REQUIRETLS.  If the
   REQUIRETLS option is used when sending a message, it causes message
   delivery to fail if a TLS connection with the required security
   characteristics cannot be completed with the next hop MTA or if that
   MTA does not also advertise that it supports REQUIRETLS.  Message
   originators may therefore expect transport security to be used for
   messages sent with this option.


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at

The IETF Secretariat

ietf-smtp mailing list
<Prev in Thread] Current Thread [Next in Thread>