Re: [dmarc-ietf] Fwd: New Version Notification for draft-crocker-dmarc-sender-01.txt

Joseph Brennan <brennan@columbia.edu> Mon, 27 July 2020 20:12 UTC

Return-Path: <jb51@columbia.edu>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F89B3A0B9F for <dmarc@ietfa.amsl.com>; Mon, 27 Jul 2020 13:12:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.362
X-Spam-Level:
X-Spam-Status: No, score=-0.362 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 DNjyBSabzeTR for <dmarc@ietfa.amsl.com>; Mon, 27 Jul 2020 13:12:31 -0700 (PDT)
Received: from mx0a-00364e01.pphosted.com (mx0a-00364e01.pphosted.com [148.163.135.74]) (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 19B1E3A0B9D for <dmarc@ietf.org>; Mon, 27 Jul 2020 13:12:30 -0700 (PDT)
Received: from pps.filterd (m0167069.ppops.net [127.0.0.1]) by mx0a-00364e01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 06RK530r021480 for <dmarc@ietf.org>; Mon, 27 Jul 2020 16:12:30 -0400
Received: from sendprodmail12.cc.columbia.edu (sendprodmail12.cc.columbia.edu [128.59.72.20]) by mx0a-00364e01.pphosted.com with ESMTP id 32j0kujdj0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <dmarc@ietf.org>; Mon, 27 Jul 2020 16:12:30 -0400
Received: from mail-il1-f200.google.com (mail-il1-f200.google.com [209.85.166.200]) by sendprodmail12.cc.columbia.edu (8.14.4/8.14.4) with ESMTP id 06RKCTho020753 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for <dmarc@ietf.org>; Mon, 27 Jul 2020 16:12:29 -0400
Received: by mail-il1-f200.google.com with SMTP id l17so12277172ilj.17 for <dmarc@ietf.org>; Mon, 27 Jul 2020 13:12:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=dp1doZYr5c+yG3W6Xa8E2Prs2e6HiokA2LzTpcJQL48=; b=MBwyNSKl20GwNDCAEPPNldUOgwh9RaU5YfSs95Q0lbJZ4w1tl8Q2MIXgQc6X9rxJBE UAkKaSfigWrN7Z6CB5Zx65EhwZmEOLG71PZ/2xCkii6wkbaRBhwNUbTTO5q6N0Rqi4hJ 1eGHUcUTqQo9KZvkSJgoTAwZotzAxidaiwq9CgwsLD8QPdbkYr5IPnVeEEEkNDI36jj2 LC8/mZjs0dc0uk5oR/JJpONdB03L+aGH/nPHtrBHvTy1pHgI+IsHx0SNGKRZE2Oj+TUo /LjBjv7X+KwI/6E3c4CEG+zWcySE1Z8drE2KqYsQM+IzTrIdGalxEJtqp7ormPAvhZjf LXvA==
X-Gm-Message-State: AOAM532z39uhrgTTm+0vBbBqgxPMHLfpOU0zwx4QvhSqjnirzsK7EaEQ zi7/vWMvkgzM1p7/KVFTJVPk2l6HCD5/vZsNZmjM4RYhW0q3WNAfW8w5nuiKUKKBieIwJwlM0Iq pGy/1bSMNaJX3S/H2CB+9BSbFiyMEMw==
X-Received: by 2002:a05:6638:258a:: with SMTP id s10mr28383129jat.101.1595880748816; Mon, 27 Jul 2020 13:12:28 -0700 (PDT)
X-Google-Smtp-Source: ABdhPJzIeufg8wxDr+q9AAi1SAGunarsxDP/xBYf15yIgHxnu2wZUJjSavtU5velmi68kS37eHxfWmN9Ansg4U/N3+w=
X-Received: by 2002:a05:6638:258a:: with SMTP id s10mr28383093jat.101.1595880748390; Mon, 27 Jul 2020 13:12:28 -0700 (PDT)
MIME-Version: 1.0
References: <159585216728.2214.8844545419487435807@ietfa.amsl.com> <bff8ea92-82cd-b389-df78-643e17209450@dcrocker.net> <5c414951-6c24-7af1-7a67-cc31a5390e23@tana.it> <47c7f86c-4cb5-712c-63c5-810b8b630823@dcrocker.net>
In-Reply-To: <47c7f86c-4cb5-712c-63c5-810b8b630823@dcrocker.net>
From: Joseph Brennan <brennan@columbia.edu>
Date: Mon, 27 Jul 2020 16:12:17 -0400
Message-ID: <CAMSGcLCm8LiJ1v2vCqe4pmRBrypumHahmkwJTRQ+u2a0oQrwNQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001cb22005ab71f1c5"
X-CU-OB: Yes
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-07-27_14:2020-07-27, 2020-07-27 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Zu91103gXScMLP8MnCamTJbc9z4>
Subject: Re: [dmarc-ietf] Fwd: New Version Notification for draft-crocker-dmarc-sender-01.txt
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2020 20:12:32 -0000

> On 7/27/2020 11:14 AM, Alessandro Vesely wrote:
>
> > Let's say I have From: real.bank, and Sender: phisher.example. The
> > above text seems to imply the receiver is looking up
> > _dmarc.phisher.example.  Correct?
>

Avoiding it by redefining From: to serve the former purpose of Sender: and
creating a new Author: to serve the former purpose of From: seems to me to
start us down a long road of new header fields every couple of years. They
are just names.

Verifying that the message really is from phisher.example is a useful data
point. The receiving system can choose to mark it with a warning like "you
never had mail before from phisher.example".

Consider a DMARC DNS tag for the bank to ask the receiving system to verify
the From, while the end-user system would not use that tag. I think this is
the distinction that should be made, for mailing lists to work but
sensitive data to be more protected than end-user mail.


-- 
Joseph Brennan
Lead, Email and Systems Applications
Columbia University Information Technology