Re: [secdir] [taugh.com-standards] Secdir last call review of draft-ietf-dmarc-eaiauth-03

Benjamin Kaduk <kaduk@mit.edu> Mon, 25 March 2019 10:59 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DB8C1203E0; Mon, 25 Mar 2019 03:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 KjIG4osKjbi3; Mon, 25 Mar 2019 03:59:11 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84735120408; Mon, 25 Mar 2019 03:59:11 -0700 (PDT)
Received: from kduck.mit.edu (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x2PAx3p6001666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 25 Mar 2019 06:59:05 -0400
Date: Mon, 25 Mar 2019 05:59:03 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: John R Levine <johnl@taugh.com>
Cc: Leif Johansson <leifj@sunet.se>, Tim Wicinski <tjw.ietf@gmail.com>, ben@nostrum.com, adam@nostrum.com, secdir@ietf.org, dmarc@ietf.org, Murray Kucherawy <superuser@gmail.com>, Barry Leiba <barryleiba@computer.org>, Kurt Andersen <kurta@drkurt.com>
Message-ID: <20190325105902.GC77890@kduck.mit.edu>
References: <155350506670.22297.2525928721965597003@ietfa.amsl.com> <alpine.OSX.2.21.1903251056350.93990@ary.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.OSX.2.21.1903251056350.93990@ary.local>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/ZRTkPRunqP7uj2afc23DjfJmkH4>
Subject: Re: [secdir] [taugh.com-standards] Secdir last call review of draft-ietf-dmarc-eaiauth-03
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Mar 2019 10:59:21 -0000

On Mon, Mar 25, 2019 at 10:57:49AM +0000, John R Levine wrote:
> On Mon, 25 Mar 2019, Leif Johansson via Datatracker wrote:
> > The one issue I have is that the security considerations section claims
> > that the proposed changes attempts to mitigate some security issues
> > in email involving SPF, DMARC and/or DKIM but it is not obvious (at
> > least not to me) exactly what this amounts to.
> >
> > Additional text in the document to clarify this point seems like a good idea.
> 
> Maybe I should just take that out.  The only issue it mitigates is that 
> it makes DKIM and DMARC checks on EAI mail more reliable.

That seems important enough to state explicitly.

-Ben