Re: [Bimi] Bimi Goals (was: Re: Thoughts about MUA/BIMI)

Dave Crocker <dhc@dcrocker.net> Fri, 12 August 2022 21:40 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 9C24BC14CF17 for <bimi@ietfa.amsl.com>; Fri, 12 Aug 2022 14:40:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-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=ham 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 GQrKLw6hlVeb for <bimi@ietfa.amsl.com>; Fri, 12 Aug 2022 14:40:24 -0700 (PDT)
Received: from donkey.elm.relay.mailchannels.net (donkey.elm.relay.mailchannels.net [23.83.212.49]) (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 DE91FC14CF1E for <bimi@ietf.org>; Fri, 12 Aug 2022 14:40:23 -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 58AFC1224EC for <bimi@ietf.org>; Fri, 12 Aug 2022 21:40:22 +0000 (UTC)
Received: from gcp-us-central1-a-smtpout2.hostinger.io (unknown [127.0.0.6]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 7D8DB12256C for <bimi@ietf.org>; Fri, 12 Aug 2022 21:40:21 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1660340421; a=rsa-sha256; cv=none; b=k5luUPbxcbo880h4QqNWnkF4SjD1aTRzNvaOxsJYibL4IzdwOctcrZ9QGfOkkj/IoKfFFd p0c0WPle7o1YzbhVsUucCxcwa6qf4X+u8qCMTA+Fjds27i7Mqzjdg1RWuSQO57E2Zqztky q6TFWdNr6pzPu2zjv/v7nLe+9Okz0XlFbgdAWVIf89N8vhylfSV7v7OlHWQjduDaMyehJZ Ne4yPDoUURqof96ub7/YOOVnnQejxZu65KLF4pd0vggrg2n5IWLxeo4gUv33vcElOMJCLC 5QHSsiJhm0vKzYtdA2e8Q16wpv3ow1iRef9Z1I1Mrjc8QIu30fZje/5FpaJzeQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1660340421; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to: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=VWvlHZOkoe3b4EI5Z48XCGsrOBE5GKEdfp7jygDXHpA=; b=pMoaJlJMPjH0IcrQn8t8OyksetLY9h0ZZC54H/olpqsUo05Rzc/KMZuHuDI94nqFaV3s7E qApVhan3sP4byi7D/VVcLYCRrZWVh7LO0Z0Y0RJcsfjY0gIyrMFVJqAKABpffM3bbhv4D6 6VZDoeTz5ddnwKHbDYHE7doUBl3tW2WM3K4hwej6z7+Y0JXGe+fhfHqfKWELxkZpbQrczW XDqjRHnL1bBbYy16H1gs2/TuUQxJvWyUsaLhGkLlZPE9l+cqPmvism7q/LcKwJC3N18JYN kJcneAhe8UqqflV/NoOoarbkjgbIeJsr6EOAVEs+QX4kLHBStTKDNWEURIQM4w==
ARC-Authentication-Results: i=1; rspamd-7c478d8c66-n4qvx; 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-Belong-Oafish: 7413eacf15d125d8_1660340421856_2187341694
X-MC-Loop-Signature: 1660340421856:76522083
X-MC-Ingress-Time: 1660340421856
Received: from gcp-us-central1-a-smtpout2.hostinger.io (gcp-us-central1-a-smtpout2.hostinger.io [35.192.45.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.112.55.233 (trex/6.7.1); Fri, 12 Aug 2022 21:40:21 +0000
Received: from [192.168.0.113] (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 4M4HCR3jlHz7W9Qb; Fri, 12 Aug 2022 21:40:19 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcrocker.net; s=hostingermail-a; t=1660340420; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VWvlHZOkoe3b4EI5Z48XCGsrOBE5GKEdfp7jygDXHpA=; b=nu6ZSgV6L0zYSiullTntlU47w5hHRu/Jdp3A8Hjmr6QbXLWOlxgbitZvH+nCzfxKEbyhcS Jzn+KNA90yv2Oj1TDWlJY2UetJ5c8hBsnWhz2ANzi5grm/ysoFplr+yzRIOHA8dJe6qYkh 4xMf1Lk8UQtzk5IkuatMJCbIHsTCTUNIsJq/uG0TuFaz+sK9VU4HoulL0xa6WEvZvVu/eF LDlU/IMUBHuSOrKy8XNICnGMNm35plZjamdSJzvZ4Y58f9izNOtSM6+KjrAAiVzL0KYj7b IFjwb1pH5/uzTyKV4ZCmgVnzYog4kBShffeD5nw1eCNudjFNfNKaxxN8q4u+zA==
Message-ID: <ce92084e-9002-7c36-0d26-744dc86b0995@dcrocker.net>
Date: Fri, 12 Aug 2022 14:40:17 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0
Reply-To: dcrocker@bbiw.net
Content-Language: en-US
To: "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>, "BIMI (IETF) (bimi@ietf.org)" <bimi@ietf.org>
References: <MN2PR11MB435138DB4A7161A506B8CD25F7649@MN2PR11MB4351.namprd11.prod.outlook.com> <ea58765e-c46a-8f29-8af6-3373db343c27@dcrocker.net> <MN2PR11MB4351D981953EFD96C3E4A301F7679@MN2PR11MB4351.namprd11.prod.outlook.com> <494098D0C7B06400A7C08303@PSB> <MN2PR11MB43510121C7EBC6197AD3A2ADF7679@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
In-Reply-To: <MN2PR11MB43510121C7EBC6197AD3A2ADF7679@MN2PR11MB4351.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-CM-Analysis: v=2.4 cv=EqbBEAQA c=1 sm=1 tr=0 ts=62f6c8c4 a=RWeyNHkVnTTD7ejqcR0qZA==:117 a=RWeyNHkVnTTD7ejqcR0qZA==:17 a=IkcTkHD0fZMA:10 a=k7Ga1wGzAAAA:8 a=zhVYBJdE424stoLyn4IA:9 a=QEXdDO2ut3YA:10 a=ijMaxGghyylP-n2pFjDB:22
X-CM-Envelope: MS4xfCXVTiJbA6M0Wv6ANp++cSzt0wDvdG9YWaBbcUjxAU0p52apS8wCGJgTcjS1XCi92r2IN/JWMJOvkDOqkgLdKI6ZMXWXLVtF6ZKyQ3cnvxprrBAW1rkc s+SKCSskezYv8sQy76R6Ws9ZE+BPQ/Kk8SdXpoFsUYmX4meBCoQ/sXs0gziU7uuxEWxR7lzR0jvrGSMIPRxc77qCalieX9q/DrlsDTdNEUePCGZAkW0VUUdl t+JHdAvLn/yh/K4mNcRu4w==
Archived-At: <https://mailarchive.ietf.org/arch/msg/bimi/Y_G_n_Bw-YhgfW5eJjEcicZYIUM>
Subject: Re: [Bimi] Bimi Goals (was: Re: Thoughts about MUA/BIMI)
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: Fri, 12 Aug 2022 21:40:28 -0000

On 8/12/2022 10:58 AM, Brotman, Alex wrote:
> My apologies, I was not trying to suggest that other options cannot be considered.  I was noting how the document/spec is currently designed, and that both goals are important (perhaps independently).  It's entirely possible that we could alter the method to work as you'd suggested a few weeks ago, and the independent MBP can impose their own restrictions which could include any manner of things including DMARC.

Alex,

Your note seems to suggest the idea of parallel mechanisms, as 
alternatives.  In my experience, those don't work.  It was, in fact, a 
hallmark of the excessive complexity created in some/many of the OSI 
specifications.

If you don't mean that, then I'm not clear what you mean, concretely.

Note that while some of my posting(s) today do cite inherent limitations 
of basing Bimi on DMARC, et al,  at least one other posting discusses an 
add-on, for interacting with unaffiliated MUAs, that does not require 
any changes in the existing DMARC dependency.

The larger point I've raised is, really, not a new one, although 
apparently came up fairly recently in Bimi discussion:  Namely the need 
to carefully consider the larger operational context that is to be 
supported and development of very -- very -- clear understanding of the 
needs of that context and the reasons for excluding any plausible cases, 
including threats, operational challenges, semantic challenges -- such 
as loss of rights to use of the image -- etc.

One can easily imagine making a set of choices that only suit a very 
limited set of platform providers.  In business terms, narrowing the 
market segment to be served is hardly unusual.

But to the extent that this work is being done in public -- and 
especially since the discussion here is hosted on an IETF platform -- 
the lack of clarity about those choices should be remedied, IMO.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net