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

Jim Fenton <fenton@bluepopcorn.net> Sun, 14 February 2016 19:55 UTC

Return-Path: <fenton@bluepopcorn.net>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEC011B2BCC for <perpass@ietfa.amsl.com>; Sun, 14 Feb 2016 11:55:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.006
X-Spam-Level:
X-Spam-Status: No, score=-2.006 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7C6RuicQJx4x for <perpass@ietfa.amsl.com>; Sun, 14 Feb 2016 11:55:47 -0800 (PST)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BAF31B2AF7 for <perpass@ietf.org>; Sun, 14 Feb 2016 11:55:47 -0800 (PST)
Received: from splunge.local ([IPv6:2001:470:1f05:bfe:8c73:ddf7:e711:2a12]) (authenticated bits=0) by v2.bluepopcorn.net (8.14.3/8.14.3/Debian-9.4) with ESMTP id u1EJtdLT032431 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <perpass@ietf.org>; Sun, 14 Feb 2016 11:55:41 -0800
References: <20160213233657.2473.73478.idtracker@ietfa.amsl.com>
From: Jim Fenton <fenton@bluepopcorn.net>
X-Enigmail-Draft-Status: N1110
To: perpass list <perpass@ietf.org>
X-Forwarded-Message-Id: <20160213233657.2473.73478.idtracker@ietfa.amsl.com>
Message-ID: <56C0DBC0.2070506@bluepopcorn.net>
Date: Sun, 14 Feb 2016 11:55:44 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <20160213233657.2473.73478.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------070600030203040605040704"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluepopcorn.net; s=supersize; t=1455479741; bh=dg2RJhAD75YxrfWVs3+lbpdXrJDzh/3Sa5u8L03Lwfg=; h=Subject:References:From:To:Date:In-Reply-To; b=MwxEcUOmVjdUgAh/mi3cIr7nE/Ac5VptIUfhBOuNzQCVQitWu/+XtUnCB9fBJtzc4 ADW9AtLE7fxSKj2vWx72FuZyupIeA0oQr0Zmp3UL/jpXvbk5AwX+arsyalfzRQQxon wVjsIdCu/VvJowsk2cNrRAn9e2RqgFsPrC4FqBFI=
Archived-At: <http://mailarchive.ietf.org/arch/msg/perpass/baHx0nbC5iDeFSa0KJnqQmJgDvM>
Subject: [perpass] Fwd: New Version Notification for draft-fenton-smtp-require-tls-01.txt
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Feb 2016 19:55:48 -0000

Hi,

I thought I would point out this draft on the perpass list, because its
primary purpose is to give email senders some degree of control over
whether their messages are sent between MTAs using TLS -- and therefore
how susceptible messages are to pervasive passive surveillance.

Discussion of this draft has thus far been on the ietf-smtp list.

-Jim


-------- Forwarded Message --------
Subject: 	New Version Notification for draft-fenton-smtp-require-tls-01.txt
Date: 	Sat, 13 Feb 2016 15:36:57 -0800
From: 	internet-drafts@ietf.org
To: 	Jim Fenton <fenton@bluepopcorn.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
URL:            https://www.ietf.org/internet-drafts/draft-fenton-smtp-require-tls-01.txt
Status:         https://datatracker.ietf.org/doc/draft-fenton-smtp-require-tls/
Htmlized:       https://tools.ietf.org/html/draft-fenton-smtp-require-tls-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-fenton-smtp-require-tls-01

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 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 tools.ietf.org.

The IETF Secretariat