Re: [Uta] Revised wording on security consideration re TLS-Required

Viktor Dukhovni <ietf-dane@dukhovni.org> Sat, 30 March 2019 20:01 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D53BA120269 for <uta@ietfa.amsl.com>; Sat, 30 Mar 2019 13:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 JgAmTV-ES8Uv for <uta@ietfa.amsl.com>; Sat, 30 Mar 2019 13:01:25 -0700 (PDT)
Received: from straasha.imrryr.org (straasha.imrryr.org [100.2.39.101]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F9F012026D for <uta@ietf.org>; Sat, 30 Mar 2019 13:01:24 -0700 (PDT)
Received: from [192.168.1.161] (unknown [192.168.1.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by straasha.imrryr.org (Postfix) with ESMTPSA id 9C38058C2C for <uta@ietf.org>; Sat, 30 Mar 2019 16:01:23 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <1E84FE7F-EE90-459C-A94F-C161524C2AA8@dukhovni.org>
Date: Sat, 30 Mar 2019 16:01:23 -0400
Content-Transfer-Encoding: quoted-printable
Reply-To: uta@ietf.org
Message-Id: <6C89DD9E-D435-4A14-B6B1-4B128CA25192@dukhovni.org>
References: <mailman.116.1553713216.11047.uta@ietf.org> <20190330184458.GF35679@kduck.mit.edu> <1E84FE7F-EE90-459C-A94F-C161524C2AA8@dukhovni.org>
To: uta@ietf.org
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/5u2XK7PQOrJA7-fpnErbF6YvGOQ>
Subject: Re: [Uta] Revised wording on security consideration re TLS-Required
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Sat, 30 Mar 2019 20:01:27 -0000

Oops, second paragraph should read: The header does *not* ...

> On Mar 30, 2019, at 3:05 PM, Viktor Dukhovni <ietf-dane@dukhovni.org> wrote:
> 
> Essentially, all MTAs are intermediate MTAs.  The header is added to the
> message via the sender's *MUA*, and conveys the same sender preference to
> every SMTP relay (MTA) en-route.  For this header to be effective at
> achieving its goal, there needs to be no prior difference between the MSA's
> first relay hop and further downstream relays.  TLS-related delivery issues
> can occur at any hop along the path from sender to recipient.
> 
> The header does obligate every en-route MTA to ignore its local policy.
> Where such local policy mandates TLS, it will likely trump the header.
> Where the MTA has no explicit policy and would otherwise follow the
> hints (DANE or MTA-STS) from the next-hop destination, the header should
> generally allow delivery when operational errors would otherwise break
> such delivery by promising and not delivering on the requirements of DANE
> or MTA-STS.

-- 
	Viktor.