Re: [dmarc-ietf] DMARC alignment conflicts with RFC 5322 on the use of the From and Sender header fields

Dave Crocker <dcrocker@gmail.com> Mon, 08 June 2020 03:13 UTC

Return-Path: <dcrocker@gmail.com>
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 617733A0991 for <dmarc@ietfa.amsl.com>; Sun, 7 Jun 2020 20:13:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 u4s2Um4slvCK for <dmarc@ietfa.amsl.com>; Sun, 7 Jun 2020 20:13:04 -0700 (PDT)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B3033A0990 for <dmarc@ietf.org>; Sun, 7 Jun 2020 20:13:04 -0700 (PDT)
Received: by mail-ot1-x32e.google.com with SMTP id g5so12475669otg.6 for <dmarc@ietf.org>; Sun, 07 Jun 2020 20:13:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=kYFrejVir68jI3lfN5Y1q6ajttbQigvxCY6AetGznBs=; b=CZDnxcavllewPntzU12Om2rK23KSq22+GCP/wglKCSonmLR4bEJPxHk5jI+sia+v6F g5P8GUtAfBFJz7ypO1PeTnXksgXWkZmbwV3QetK2v6RAfZAczMUzvlIErtv0MzMiikFu 82VbcI2EWnaSdf8KhIJallYmTrcLL/d/YA9jTDcwP9P7/MwWjPllre9DUWv7ZRO6QPer ZmGI27tbTlQlCCWxBzNgF7tj9SplpC1Zodt15K6J28v+r3SjdgWANL3eTmt/vN/FrUwx XoKajLjge6dzJs77RvvZrWTlGyf1B2U4kbbNfQqQwM61QBUG112BnWTAg31l8RoyOWAU Z7ew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=kYFrejVir68jI3lfN5Y1q6ajttbQigvxCY6AetGznBs=; b=WF3jUP735pQJDkMyIPy7O7kUUZ3tMtkrfaywtjAZaD3BWl0fHmylTXgET3Dp3r1iof SjZonBAg0VWE2D+Qk/zuP1v3MTzz+eRES8Jz8PMVaLYTUYUMGHbBh334XjwsSp5S89SM 9bg97Z+BdkhR+0j+bemzYLQXdxvuoUypiDTHWqfZ7fsuQaXhxX02lI1MpNzf33cJay+z 9XH/8EOaygNQPprCYBYgj2Lgpt1D642g72C6mFQUGS81jyBoftE0FmSP63VDhoPeZrzh 8wMJw1qYSTiFYNYm2nk24gAbAtSemf5uQxseMh7Y7IozwG99JCo1yQ5HiCaijab4L6zC zRNw==
X-Gm-Message-State: AOAM530gUAs6IduSJ8yW/kACZOO2Bdf+eoA1gM8tHKJAomlFbaZpmRzj kyIrsQg2xHnRf4Vcs82dXiqWZCJO
X-Google-Smtp-Source: ABdhPJxTvNAanJ0QC15nDzvJMP/tS5MdvhFKewAhTDVZejqKPVVejnD2MV7IdUcqusSQkKaG5RxW6A==
X-Received: by 2002:a9d:d0e:: with SMTP id 14mr15150340oti.42.1591585983294; Sun, 07 Jun 2020 20:13:03 -0700 (PDT)
Received: from ?IPv6:2600:1700:a3a0:4c80:5443:4b56:d117:6ef3? ([2600:1700:a3a0:4c80:5443:4b56:d117:6ef3]) by smtp.gmail.com with ESMTPSA id n60sm1253782otn.75.2020.06.07.20.13.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 07 Jun 2020 20:13:02 -0700 (PDT)
To: "Murray S. Kucherawy" <superuser@gmail.com>, fosterd@bayviewphysicians.com
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <DM5PR0601MB367115AD49513EAF3953716CF68B0@DM5PR0601MB3671.namprd06.prod.outlook.com> <11640715.3lbasgNmsr@sk-desktop> <25420528-d356-0273-ceb3-c44a3c94bc91@gmail.com> <3138524.EPDo7oxCqE@sk-desktop> <4620e21f-32c5-7735-9faf-a5b045f84c0d@bluepopcorn.net> <ac0f684a-4c00-0564-8cf9-5b955e037c87@tana.it> <14fe18acad53467a8027e680dfc1067e@bayviewphysicians.com> <CAL0qLwbkX0tVneKebQAeqNJ99wS6KcZdXx1+D0nBjsHiTFGaag@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <7ca6638f-7c98-3041-c24b-89a6d1d74681@gmail.com>
Date: Sun, 07 Jun 2020 20:13:01 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwbkX0tVneKebQAeqNJ99wS6KcZdXx1+D0nBjsHiTFGaag@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------AA4AB65006241970F3FA8AD7"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/cyfFmAJid1OeHFRDbSZgA5McAfA>
Subject: Re: [dmarc-ietf] DMARC alignment conflicts with RFC 5322 on the use of the From and Sender header fields
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, 08 Jun 2020 03:13:05 -0000

On 6/7/2020 8:04 PM, Murray S. Kucherawy wrote:
>
>      If I wanted an organization policy that controlled when Friendly
>     Name was displayed or DMARC status was displayed, I would have to
>     find and distribute plug-ins to all of these products.   As best
>     as I have been able to tell, no such plug-ins even exist for
>     Outlook and the other products do not accept extensions. There is
>     an opportunity here for valuable standardization.
>
>
> The IETF has routinely punted, at least in the email space, on the 
> idea of prescribing or proscribing user interface behaviors because we 
> are protocol engineers, not human factors experts.  Are you claiming 
> that's changed?

A 'friendly' amendment, or rather addition:

      The origination side of an email exchange has no authority over 
the reception side.  Different administrative authorities. Compliance 
with DMARC is voluntary -- and receiving administrations often implement 
behaviors that differ from what is requested via DMARC.

      There is no basis for believing that requests about MUA display 
will achieve meaningful support on the receive side, nevermind whether 
they would be at all useful.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net