IETF Logo Mail Archive

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

Dave Crocker <dcrocker@gmail.com> Sun, 07 June 2020 21:53 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 2B7AE3A0A96 for <dmarc@ietfa.amsl.com>; Sun, 7 Jun 2020 14:53:16 -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 yai7EgoonTOH for <dmarc@ietfa.amsl.com>; Sun, 7 Jun 2020 14:53:14 -0700 (PDT)
Received: from mail-qk1-x744.google.com (mail-qk1-x744.google.com [IPv6:2607:f8b0:4864:20::744]) (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 04AF93A0A80 for <dmarc@ietf.org>; Sun, 7 Jun 2020 14:53:14 -0700 (PDT)
Received: by mail-qk1-x744.google.com with SMTP id w3so15496638qkb.6 for <dmarc@ietf.org>; Sun, 07 Jun 2020 14:53:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=2Y8Eeff7mcFeVcfhOKybwMc4Ff0VTcB6+UAU5SnQw9w=; b=BjUsfC1D/Aurz/B+Z8ulyU/JA3bxxh/H8/TwXVXHENqO/3pCqL5MDOx5icS/IinPTf isDWUp0nEx7yOTBxuxT0B7s1BqB0TLwuMHNwFC3LS0qg1pTQf4oA7tbrNnTs/ftYmRts MvKz5RljFifzc/uqErv7993/c7pacE54kxS1/SzXcUsAEU2ot0asscITl071TZlrEsHx dLjRANe2FTCV7U4qAZzZkkzL8HGO6puMa6IWUFCxmXtACkqBWI81gsYSJhmLn5qHtzgU iUjOB1HzQvwKBrSFF1fQT2jQr6Tx5IfzH/3Sf6AYEXRI6ZSk+L79jQL09H9mmj09n351 H2zg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=2Y8Eeff7mcFeVcfhOKybwMc4Ff0VTcB6+UAU5SnQw9w=; b=oVqA75Io2FhX3rlJAuITI/g1wndW9zAhA/HSgDbggjLoZfTqD+x+0QuCSkf5p49V1J mNHr0crnY4yYoADjL++dV8p/PMfYAsQ4W6+74trUGt9m6sa9nRswi2fByyVn2GrjeYZ2 j2R11TJGMCk+rIzggS3L8dLZMXnge0fz2FETzUIRIqkOnWINobEmiipqbxLCaNCNd6EV oYJ/dWTjd/pimGWJTmn7LRIU07GJpqG1NphFW4YhBcYhZp5vwdRRsgWUo3ETda32gWfS 2UxWDeyF+Wy0hGYIfhviLTEz62SISbOILadEK1GO5pK0wdPa6p49ZNQmVexzFFLWyelV v7UQ==
X-Gm-Message-State: AOAM5317E61k4DkTSAeBVgkcnAhEItdDSGbitSV3d4Ckp5MFPvq4TKzH ivTSpaalOLEqz0tZzS4c9WcXqQXb
X-Google-Smtp-Source: ABdhPJzw911q7AIffvJm0zRQSSKjydx/eEnv/QuPNMbroLDnV8Z3ddd75wtS4alLF0W5GezJS3xDHA==
X-Received: by 2002:a37:a147:: with SMTP id k68mr19591985qke.62.1591566791252; Sun, 07 Jun 2020 14:53:11 -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 i94sm6116410qtd.2.2020.06.07.14.53.10 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 07 Jun 2020 14:53:10 -0700 (PDT)
To: 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> <46e045ae-9691-4f5b-86bf-142c066458d8@www.fastmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <fbbcc299-98f3-5d23-15e1-1f89fa03b9a7@gmail.com>
Date: Sun, 07 Jun 2020 14:53:08 -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: <46e045ae-9691-4f5b-86bf-142c066458d8@www.fastmail.com>
Content-Type: multipart/alternative; boundary="------------7C14176FE9E9294D85C9859A"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/rCpdC9TTJa4FCbj3MGHXOoCaiuQ>
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: Sun, 07 Jun 2020 21:53:22 -0000

On 6/7/2020 10:53 AM, Stan Kalisch wrote:
> Assuming this can be practically done, I would rephrase this, 
> "...[E]stablish how MUAs should display trust data to users."
>
Since there has been a demonstrated lack of efficacy in this sort of 
display, there needs to be an objective basis for knowing that any new 
such requirement will be useful.  Good luck with that.


On 6/6/2020 2:42 PM, Scott Kitterman wrote:
> 1.  I think the domain displayed to the end user matters.  In my sample size
> of 1, it matters to me.  I know I'm not the average user, but independent of
> t

I might be wrong, but I believe the IETF does not intend to make global 
standards on the basis of possible utility for only one engineer working 
on the specification.  Or two.  Or three.

cf, above.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email