IETF Logo Mail Archive

Re: [Bimi] Proposal to Clarify Role of MUA in BIMI Evaluation

Dave Crocker <dhc@dcrocker.net> Mon, 18 July 2022 20:22 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: bimi@ietfa.amsl.com
Delivered-To: bimi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 737F8C13C52C for <bimi@ietfa.amsl.com>; Mon, 18 Jul 2022 13:22:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.112
X-Spam-Level:
X-Spam-Status: No, score=-2.112 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qIObHFhfTQb4 for <bimi@ietfa.amsl.com>; Mon, 18 Jul 2022 13:22:35 -0700 (PDT)
Received: from bee.birch.relay.mailchannels.net (bee.birch.relay.mailchannels.net [23.83.209.14]) (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 3EF14C13C535 for <bimi@ietf.org>; Mon, 18 Jul 2022 13:22:34 -0700 (PDT)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id D1205802385 for <bimi@ietf.org>; Mon, 18 Jul 2022 20:22:32 +0000 (UTC)
Received: from gcp-us-central1-a-smtpout1.hostinger.io (unknown [127.0.0.6]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 1BC0980146B for <bimi@ietf.org>; Mon, 18 Jul 2022 20:22:32 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1658175752; a=rsa-sha256; cv=none; b=GbRBYY3R7BzO1Djy0vZdIUo1pcwyoIgM9/ZaDLIXPIy22MLsBEKmg+eEhG3KVCw1HiiUvG vXJkDljeNUygDrroN1JSaLZN1en3ZeJniewCVKW4STou/akf4yhX+h2vbgxnRinU537Ex5 PXWGN4BjSYB3x/PNks+M984uxcPW0xwE8QEhQPhBeJg9D9fAZIF8S9EgPi0WzMUJwHke0F IopMsnlwVDTU6/rNzrqs/ldI3l7toSh3zNQkwhOtcf/QZoISMFJSZtas0NItliGSaP63pr HZxUUndMNj6CAe1aXbvcvDMusuy9bMaQvPowD4j9yKqDpb2omYGAyQdqwsuHFg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1658175752; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=l/ZBilHrLEMXIPwO1FnZYdXTTEZpiJRtbtZbeCLtwzQ=; b=le15hvU9IwelQuEaLaW2IKmlsarVNC0FB1Dlr73hGe5+AOJPuGrTpR3n9bzd6N+CZ1IXCR LppBWK/1khgFZy+bzqM2BfnhHH4soRy0iO4Vdj1IgJDbC00t800Xf3DGh1oE7sOPKNPEPt VnxgNFVNlWdebA2YB4EN/xxHH6P8ShgtkDoEWn86y7vxOSsMpr0J+4guo3x0bG7bWX9zkU Fdv12Z4GoeoI8N9gnzpdiKCmrWJ3ZD7PO1D729Q9Pt2UiTQCKAcyoqAyS7rf3JIhge+wDR mMEj6XnhadnwTLl4yt+1/1K2ebfLQjdEvUawmrQqlbitkHbs36Vps9ZtZIxfww==
ARC-Authentication-Results: i=1; rspamd-674ffb986c-r82sq; auth=pass smtp.auth=hostingeremail smtp.mailfrom=dhc@dcrocker.net
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Chemical-Arithmetic: 14be0e0f1352935e_1658175752445_578536588
X-MC-Loop-Signature: 1658175752445:2168308326
X-MC-Ingress-Time: 1658175752445
Received: from gcp-us-central1-a-smtpout1.hostinger.io (gcp-us-central1-a-smtpout1.hostinger.io [35.184.15.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256) by 100.124.238.78 (trex/6.7.1); Mon, 18 Jul 2022 20:22:32 +0000
Received: from [192.168.0.104] (c-73-170-122-71.hsd1.ca.comcast.net [73.170.122.71]) (Authenticated sender: dhc@dcrocker.net) by smtp.hostinger.com (smtp.hostinger.com) with ESMTPSA id 4Lmtg86kNQz2cFhQ; Mon, 18 Jul 2022 20:22:28 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcrocker.net; s=hostingermail-a; t=1658175751; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=l/ZBilHrLEMXIPwO1FnZYdXTTEZpiJRtbtZbeCLtwzQ=; b=K3H52c3EDfQPSQvfk6b6J+6wYzISiXCLZbWLaKH5v7L5U7jFeY4OT0ET3wfpMCiUbGJf7b uPdL7xrv2O9r3Bx+JOuxhY5zNDGXwcYVbFZPQcNBAq6O6hRXnS57BqerEWSw3WwPfkuVWm EgkMxtSxDM5zlmeAaUaHLtF5RDqPn/dRh+FMCGMvMMIV1DGCekRH8zE9B8OZGufJLzz71U JfDIclvKi6gmtt+BjHttB61xHABNLYArc7GU50UQIItd3iya/X/AJ6Bjd+wkN2ylCS2F01 1SXcKlEejnAGHX78eveNqQ9smY1FgycAmp+VctwYd93r3PwJ+CqoLwIbJlQmlA==
Message-ID: <12a85dfe-664f-d757-0fa2-81f17c8088c2@dcrocker.net>
Date: Mon, 18 Jul 2022 13:22:28 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Reply-To: dcrocker@bbiw.net
Content-Language: en-US
To: Ken O'Driscoll <ken=40wemonitoremail.com@dmarc.ietf.org>, Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>
Cc: "bimi@ietf.org" <bimi@ietf.org>
References: <DE61AC51-4BC3-44FF-862D-7D8ADFB3BC29@proofpoint.com> <20CBD506-7E50-4161-ADE6-64614630B1B2@proofpoint.com> <CAHej_8kridbc322MDRpxfgd+8Y2yNacxTAtvr+HF=+wevdRQhw@mail.gmail.com> <VI1PR01MB70538965904FD08A49F75C37C78C9@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> <11A2B052-A26C-4A9C-9D88-72B594DA1C59@proofpoint.com> <VI1PR01MB70537BA29DA1F456B858C17FC78C9@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> <6993E8B6-11A0-4AF3-A94E-044F880E56BC@proofpoint.com> <CAHej_8kjwtGE4rDrXfTpgThOD-jh7t0GK9EUnVjVZT_OJzzsvg@mail.gmail.com> <VI1PR01MB705353E36328899609DE2471C78C9@VI1PR01MB7053.eurprd01.prod.exchangelabs.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
In-Reply-To: <VI1PR01MB705353E36328899609DE2471C78C9@VI1PR01MB7053.eurprd01.prod.exchangelabs.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/bimi/rO9K-I2qbvQ5IwjVpTg-5HNuc80>
Subject: Re: [Bimi] Proposal to Clarify Role of MUA in BIMI Evaluation
X-BeenThere: bimi@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Brand Indicators for Message Identification <bimi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bimi>, <mailto:bimi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bimi/>
List-Post: <mailto:bimi@ietf.org>
List-Help: <mailto:bimi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bimi>, <mailto:bimi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2022 20:22:40 -0000

On 7/18/2022 12:41 PM, Ken O'Driscoll wrote:
> I don't believe that an internet standard can address individual MUA 
> design issues.


IMAP and POP are examples of protocols created for MUAs.  They do not 
specify the way an MUA can/should implement these details or how things 
should be presented to users, but they very much dictate their realm of 
functionality.  That naturally pertains to some aspects of MUA design.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email