[Uta] Protocol Action: 'SMTP Require TLS Option' to Proposed Standard (draft-ietf-uta-smtp-require-tls-09.txt)

The IESG <iesg-secretary@ietf.org> Mon, 05 August 2019 16:10 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: uta@ietf.org
Delivered-To: uta@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CEF7120071; Mon, 5 Aug 2019 09:10:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.99.1
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, uta-chairs@ietf.org, valery@smyslov.net, draft-ietf-uta-smtp-require-tls@ietf.org, uta@ietf.org, Valery Smyslov <valery@smyslov.net>, alexey.melnikov@isode.com, rfc-editor@rfc-editor.org
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <156502140623.24510.1889222146690697269.idtracker@ietfa.amsl.com>
Date: Mon, 05 Aug 2019 09:10:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/RaVKY9WY7gx1uXpQwHaW0zBQrTQ>
Subject: [Uta] Protocol Action: 'SMTP Require TLS Option' to Proposed Standard (draft-ietf-uta-smtp-require-tls-09.txt)
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.29
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2019 16:10:07 -0000

The IESG has approved the following document:
- 'SMTP Require TLS Option'
  (draft-ietf-uta-smtp-require-tls-09.txt) as Proposed Standard

This document is the product of the Using TLS in Applications Working Group.

The IESG contact persons are Adam Roach, Alexey Melnikov and Barry Leiba.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-uta-smtp-require-tls/




Technical Summary

  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 message
  header field, RequireTLS. If the REQUIRETLS option or RequireTLS
  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 DANE be ignored when relaying a
  message for which security is unimportant.

Working Group Summary

  The WG consensus for adoption this draft was clear. The draft was
  well discussed in the WG and has undergone significant changes
  during this discussion. At some point there was a strong consideration 
  to split the draft into two, separating SMTP service extension 
  and mail header field, but the final consensus was that 
  it's better to define them in a single document.

Document Quality

  There are at least two implementations of the early version of the draft.
  A few major vendors and operators express an interest in this technology
  and have indicated that they evaluate a possibility to implement (or use) it.

Personnel

  Valery Smyslov (shepherd)
  Alexey Melnikov (AD)

RFC Editor Note

In Appendix A.1 (REQUIRETLS SMTP Option), 1st sentence:

OLD:
   The TLS-Required SMTP option is used to express the intent of the
       ^^^^^^^^^^^^
   sender that the associated message be relayed using TLS.

NEW:
   The REQUIRETLS SMTP option is used to express the intent of the
       ^^^^^^^^^^
   sender that the associated message be relayed using TLS.