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:50 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 E282DC157B50 for <bimi@ietfa.amsl.com>; Mon, 18 Jul 2022 13:50:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 iag6UAr5lTMV for <bimi@ietfa.amsl.com>; Mon, 18 Jul 2022 13:50:26 -0700 (PDT)
Received: from cyan.ash.relay.mailchannels.net (cyan.ash.relay.mailchannels.net [23.83.222.47]) (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 7CF8CC13C532 for <bimi@ietf.org>; Mon, 18 Jul 2022 13:50:24 -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 D52BA5A1F4F for <bimi@ietf.org>; Mon, 18 Jul 2022 20:50:20 +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 269985A1FC9 for <bimi@ietf.org>; Mon, 18 Jul 2022 20:50:20 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1658177420; a=rsa-sha256; cv=none; b=GjNg/0wNYHzJ6NEdp6Oy5INQbGTHZTQSZswtRh1R1Cn8i2OXentDCKFDeJC5JtpWgZLqRn ZsT8nQi1jwBj/VOJzw+cAcccasbQZvbhvuTxj6u7Oym+DU3SZaqcyx5moxPwKD+eGt7ak8 1D+jSnwLabErCx0op5WPFaWayfk7EcB5h5024dG2xTySBq1jXjtKfVFFC7C/owHHOqA3ZW 5LpbXR0XbOtOdRzMMI7rLhsKA23EpOYNGEyJxoMVK1scjLXjERpZavZnPOB6roerOuz9fb sog9UCvQJylDpoRvE5e5iWagGugXzOKGuOCFfLwdzhOl6sLbhu1pN71E23jwLA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1658177420; 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=N6mMPUEWnHy5iSFjw6z+vB9QV0+AHcczvMqBTRsdxfE=; b=m8txNKnFwmkoIaFfsTPw72vT2iRlB77oresYrBib9ycRvNIxm7UhgouO59B2Ouu0xJo4eT vLESkNl5e1SnfL6xd61f93COd66c740wGp8CuGlViDtb6B4BV5IZhY9hC2EqYECNfEwecI N91HzZsBp8paSdKUs1/F2AErbmOS0excJcR0PgE2kMzOySvx0GFzUDBipaP+f/01E8iVJY 2F/vzhMgx2xMGOORNXx8W/tITx6pemvZm4iYyxH2MMjHaL/Trq79YVcC4bRNMTOTv+K9FA YPB185z0npasUpJlH5Y4vtSndsTEd/moCcyZyoa3y+wjqtRWWaF7JRysLIm7Xw==
ARC-Authentication-Results: i=1; rspamd-689699966c-fdbdj; 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-Average-Gusty: 16515669144f21c3_1658177420521_3019128445
X-MC-Loop-Signature: 1658177420521:606418889
X-MC-Ingress-Time: 1658177420521
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.98.242.215 (trex/6.7.1); Mon, 18 Jul 2022 20:50:20 +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 4LmvHD0YYcz2cFgy; Mon, 18 Jul 2022 20:50:15 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcrocker.net; s=hostingermail-a; t=1658177418; 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=N6mMPUEWnHy5iSFjw6z+vB9QV0+AHcczvMqBTRsdxfE=; b=IUnwp6zwEUz+5IDmcQKbJ8fx8bz9k+e0A8LkfgD5ljqbUx8t6YD5haqB3hACpRB1ZM2Rxo 5wN3fcGS+M7fu9sShCuIK1t7Cr2Rh+R5v4B/PUU+23mtJ992oV2UgbF1aTJej7eIK95Ojt fsX/2GXDTu79zGvQoYyeuXAbzLFniCAYmo7ikYHbspxIIK+5f1nC1SULC2FQHVTbvBsX3R wGdBZ0P8ylA0cCqyn5TFHDBJKI49ZaU7eG3Jxy4B4QL5i2hoZQyeY8rhqwY0fpAZLDEn/i 5KahEszfkraI17lSfi8V/ISOr6765jsdve17sIevpPnPFUaZTv0kBovyObju6A==
Message-ID: <4e9ab94e-8675-df70-3e4b-00edcedb266e@dcrocker.net>
Date: Mon, 18 Jul 2022 13:50:15 -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
From: Dave Crocker <dhc@dcrocker.net>
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> <12a85dfe-664f-d757-0fa2-81f17c8088c2@dcrocker.net>
Organization: Brandenburg InternetWorking
In-Reply-To: <12a85dfe-664f-d757-0fa2-81f17c8088c2@dcrocker.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/bimi/011zbRI1bcs4q_TaVHZulB_o4B8>
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:50:29 -0000

On 7/18/2022 1:22 PM, Dave Crocker wrote:
> 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. 

Addendum:

DKIM is designed as an end-to-end mechanism.  Both ends can be 
implemented in MUAs.  There is nothing that dictates that any aspect of 
DKIM be implemented in the email handling infrastructure.  The choice to 
implement it in that infrastructure is operational, rather than 
architectural.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email