[lamps] Murray Kucherawy's No Objection on draft-ietf-lamps-e2e-mail-guidance-15: (with COMMENT)

Murray Kucherawy via Datatracker <noreply@ietf.org> Thu, 07 March 2024 15:35 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: spasm@ietf.org
Delivered-To: spasm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 93F24C14F5F4; Thu, 7 Mar 2024 07:35:48 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Murray Kucherawy via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-lamps-e2e-mail-guidance@ietf.org, lamps-chairs@ietf.org, spasm@ietf.org, housley@vigilsec.com
X-Test-IDTracker: no
X-IETF-IDTracker: 12.6.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Murray Kucherawy <superuser@gmail.com>
Message-ID: <170982574859.24902.16086446062160319991@ietfa.amsl.com>
Date: Thu, 07 Mar 2024 07:35:48 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/vriIOQkuQntu2dS3fVNwqTeZrDw>
Subject: [lamps] Murray Kucherawy's No Objection on draft-ietf-lamps-e2e-mail-guidance-15: (with COMMENT)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2024 15:35:48 -0000

Murray Kucherawy has entered the following ballot position for
draft-ietf-lamps-e2e-mail-guidance-15: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-lamps-e2e-mail-guidance/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for this.  It's well written and provides good coverage of the material.
 I'll be going to YES once the DISCUSS is resolved.

Given the use of BCP 14 keywords in this document, I would prefer this be done
as a BCP or a Standards Track document (specifically, an Applicability
Statement).  It really is specifying something that's got compliance
requirements and use of existing protocols to achieve a particular outcome. 
You might even consider Experimental if you're simply not sure about how robust
the advice in here is.  The IESG will take up some future discussion about what
guidance we might want to provide for future efforts like this one.

I'm curious: If there are no committed or planned implementations, what was the
source for most of this advice?  Prior working groups in the area of email
security, like DKIM and DMARC, have firmly avoided providing any sort of user
interface advice on the basis that we simply do not have experience from which
to develop such advice.  I'm wondering what's different now.

The discussion about lock icons and such was interesting.  Over on the DKIM
list, there was some recent discussion about whether such user indications are
useful at all, whether they highlight security or non-security of a message. 
Some studies were cited that suggest these simply have never worked.