Re: [Bimi] (non)desire for bimi

Terry Zink <tzink@terryzink.com> Thu, 14 February 2019 17:08 UTC

Return-Path: <tzink@terryzink.com>
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 65794130E2F for <bimi@ietfa.amsl.com>; Thu, 14 Feb 2019 09:08:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=terryzink.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 HrbKVCO99Bwq for <bimi@ietfa.amsl.com>; Thu, 14 Feb 2019 09:08:05 -0800 (PST)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-eopbgr760049.outbound.protection.outlook.com [40.107.76.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F00E128701 for <bimi@ietf.org>; Thu, 14 Feb 2019 09:08:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=terryzink.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xzBclKg/5D+Ja5fXy1uwTKzLyQDQiem5Oxh0RsQjYJg=; b=fWySR0GngICOMkDPn+8OCWND2F7Wxcee3DpJhie4nYGOmB60TGOaCZrsdduvBwsw/SJ7b3jHOQiYVju01rsbH3lILkhXdHZ6WFXsnbGdnSI9AsBgjwVNxcx3B9eHI3jU2ppbBPTdwzh31MouSSpuqSm2j5Nqx9HAm4VrnPn8/pQ=
Received: from BL0PR11MB3107.namprd11.prod.outlook.com (20.177.205.141) by BL0PR11MB2913.namprd11.prod.outlook.com (20.177.147.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1622.16; Thu, 14 Feb 2019 17:08:00 +0000
Received: from BL0PR11MB3107.namprd11.prod.outlook.com ([fe80::e934:a609:cbdd:1bda]) by BL0PR11MB3107.namprd11.prod.outlook.com ([fe80::e934:a609:cbdd:1bda%3]) with mapi id 15.20.1622.016; Thu, 14 Feb 2019 17:08:00 +0000
From: Terry Zink <tzink@terryzink.com>
To: "bimi@ietf.org" <bimi@ietf.org>
Thread-Topic: [Bimi] (non)desire for bimi
Thread-Index: AQHUxFQrlnICsfeFJUyWrugVUJNeRqXfg1XE
Date: Thu, 14 Feb 2019 17:08:00 +0000
Message-ID: <BL0PR11MB3107712FFFD2D92E911B909DA9670@BL0PR11MB3107.namprd11.prod.outlook.com>
References: <aa919aeb-caa1-6494-259d-a553b238c268@cs.tcd.ie>
In-Reply-To: <aa919aeb-caa1-6494-259d-a553b238c268@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=tzink@terryzink.com;
x-originating-ip: [174.21.90.137]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d8b0b3b7-f678-4a3a-067c-08d6929ef994
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600110)(711020)(4605077)(2017052603328)(7153060)(7193020); SRVR:BL0PR11MB2913;
x-ms-traffictypediagnostic: BL0PR11MB2913:
x-microsoft-exchange-diagnostics: 1; BL0PR11MB2913; 23:iccTX0kvnSGK40lQFOAW0XDVhbs0Sw4EEMgJcQJ30kZNTdfZiMQ7Gwz3vkqfMVlUaDyGSTUZEN/aOP/W3fJc6fW5VRTb4WjW7E2PZULri3v7g92R/nu/qg2sa+aDo3IFhgbiDmSWZcJX1cYAA4ABACzyzaki0zFXyF3W2kUukr5JSNfsb6v2M27ZDKF7N+CxCmVlbTE/ZADV8iY1NhFtrXdQ52Zi5QePgZISbjmLm8zAGm1E928/an0wMckAT/lefyS4lWH+5m7qEaR6Ysrhenih9BZd7zO09cLJKWO7M+dwwvchAoGfcgg5TD9qJWVjKZHJn4+2nUxbyfmlAZDULgzIpX+B4Y13gJjWb2FQbGYC43gHoFHP28uJYMryhL9aBDCchHnop7tn+e4ntfT+1gyUfX6udjTVDOmcqWWjse1BstH1L1g1lqZ81te4bzke6ZpWy8mmOS+tkA+LMooD/UkvZmO0wAhxwfySzsdi4IGf/Mr8161RIc0KWzrt2jUjtmH6Za+Wi+PbCqXaIe9F52kX6RmZpOfO+TsHqP4WOs+kgnXfKd48MpRcB34yjJFJ2S/1YItZbpULco9WibdZjAz9JjIFA5XvCXLWcs9uloOQjRbQ7fPj1KLEWJmdlTKfArYiON//RjS6pdKl/83BkU3FP6PibCNq4uSYmfIsCsc1VwvzZatCkMxRff+xtZnwKZryCKG7uPK5z9r0t5hCPmTxCJDjDGcbMRR1x9BwAbzWgtLrtQNJxHejIOM0g1vXQbB4XfDZjnGma3TkrS/PF9GVSVtQcuO+HukQLngUw/U8W3rkfcXqvETOOGwwuVQW5WvtVmlmtxKGXknbznuStFuTYraqfib/hqHFQoT5NcugvgJFzNV64WHFdVEgXsxs5r/NyTbI1AHr4EY5eO8cmolvHUxj7j9OZgjNjgapS1w+Nz327qCA1+2meJnS7JXgHb1JFysBd+DZoONN/RKLy+z6ujBxKX2itwGRvnJnysd7JE7Jho4AwCnOw/boxnlu9mIO7BJ08jGF+Q9X7SXtsVGzZzKJZCExdxVeyDi9KlbO3uCPU12GNpBIvxDvjqB6glSOsuWnBQ591eSGqz4+Fw2n7oS7WmlF1bDtI79O2jepyWOy2S2JOMcJEzBBcfD6Y0Zt0zYVwdXI92B5+/iyM4xYDoMq94uNqqpM8nEfi8oZ+GoYkguPjDLeQ7Tvi2r2oL3/oF/FTeu5aplkVnLWYYGJ2OQUtTJhzs5/UV3w9ppLTAHxStl112RBipkyqvf3eHxvBdJ/Z2BLIhsSgvxWp/WkUkr//kEhgkVXvS1k/DNKh2tEg9VEppMBbddHNkYF6b9ZZ0h+xr472jmMpGkL7iDmyq6BIAamiWlBp7Y5uSVgG8Nphb0YqeFXFNL8Dwjk
x-microsoft-antispam-prvs: <BL0PR11MB2913B1CF97366788FAF8EB59A9670@BL0PR11MB2913.namprd11.prod.outlook.com>
x-forefront-prvs: 09480768F8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39830400003)(396003)(136003)(366004)(376002)(346002)(199004)(189003)(446003)(561944003)(566704002)(14454004)(105586002)(2906002)(476003)(6916009)(53546011)(6506007)(11346002)(106356001)(53936002)(14444005)(25786009)(229853002)(97736004)(256004)(8936002)(71190400001)(71200400001)(486006)(66066001)(105004)(33656002)(7736002)(5640700003)(186003)(316002)(99286004)(2501003)(55016002)(74316002)(68736007)(6116002)(6246003)(7696005)(6436002)(9686003)(19627405001)(26005)(1730700003)(76176011)(81166006)(8676002)(81156014)(102836004)(45080400002)(66574012)(54896002)(86362001)(508600001)(3846002)(2351001); DIR:OUT; SFP:1101; SCL:1; SRVR:BL0PR11MB2913; H:BL0PR11MB3107.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: terryzink.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: N5r2klMrFt9xm6xCPj/veshBjUtQl9s7JYGzkV1PCpGZ8KB0jh5z7Xg++024gJa32vx39NuVyMya2QxHvL3z0pcS4DF9zcSXVesW6tBrtAXYjgKZTO/dQgdP4L6EBoNZqEdCEpYgZsVvQ3N3SYIxEMPOCcuQGEyJMk+lls7dDieNpbN7WisMXRgltFeOs3URXn5D4Y1HVBATVpU5lxFgSmHYTJEzhswdGvyHL8DvkRa8+uHhuiP3HuVsCVqJsAzYW2kZxHdeAb5k22nY2P+23S5c65h/VR2DJ5/PVrkwa1YRpgCNByzYuewzY3MomBN3yDMwMeD9X0sYTd+WizZduv9cLE8WdKWPfT5b72f8bCmnN4I+Rep9e65TLmkXlP2g7+M22sa/0ilKhBAexPzC/e0mRAieRS0F4ButQyj2Usw=
Content-Type: multipart/alternative; boundary="_000_BL0PR11MB3107712FFFD2D92E911B909DA9670BL0PR11MB3107namp_"
MIME-Version: 1.0
X-OriginatorOrg: terryzink.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d8b0b3b7-f678-4a3a-067c-08d6929ef994
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Feb 2019 17:08:00.7018 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 470dd1c0-25dc-4cce-857e-0d65849495b7
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR11MB2913
Archived-At: <https://mailarchive.ietf.org/arch/msg/bimi/4AY9QvAHXdJH5zKsSqZCccKIkjk>
Subject: Re: [Bimi] (non)desire for bimi
X-BeenThere: bimi@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 14 Feb 2019 17:08:08 -0000

Thanks for your comments, Stephen. Here are my thoughts.

> I'd be interested in some kind of verifiable backup
> for that "clear demand" claim

To me, it seems intuitively obvious. For example, in the Office 365 web interface, I see logos from several different companies in the list view and the sender photo when I open the message - Amazon, Lyft, Facebook, LinkedIn, Netflix, BackCountry, Quora, etc (this is displayed via Microsoft's Brand Cards program). My old Yahoo Mail interface has something similar. For a while, Gmail showed a company logo pulled from its Google+ page.

How does this not show demand? Isn't this an example of web mail providers wanting to enhance the user experience, and companies happily obliging, and me as a user being pleased?

I am not representative of the entire space, but I really *like* those sender photos.

> I use the Internet. I do not want logos added to mail
> headers that increase the attack surface of my MUAs,
> (and MS/MTAs), that likely enable additional tracking
> of mail users, including me, and where mobile device
> and web MUAs are unlikely to offer me an option to
> turn all that off, even if some desktop MUAs might
> (eventually), at the risk of making messages harder
> to comprehend.

I'm not sure I understand this comment. The logos are not added to mail headers, but instead headers point to a location where the logo can be picked up and then shown to the end user. What's the difference between the sender/brand providing an authoritative source (DNS record that points to a CDN) vs Office 365/Yahoo pulling from their own internal database?


> I also just do not want to see your logos, thanks.

Again, I am not sure I understand this comment.

Logos are everywhere. Most large companies have Facebook and Twitter pages, and they all have logos. You see logos painted on the sides of walls, on stores, on TV, in newspapers, on web pages, as favicons, etc.

Are you saying these are all fine but in the sender photo it isn't? What's the fundamental difference between seeing a company's logo in the sender photo vs seeing it in the body of an email? Is it just a matter of turning of HTML and preventing those from loading?

> As someone who sends email (not as a bulk sender)
> from various domains that I operate, I do not want
> to pay €€€ to someone for an additional cert, nor
> for an "approved" logo, in order to increase the
> chances that my mail gets delivered.

Nobody is going to make you buy a cert, nobody is going to make you buy a logo, and so forth. It's up to you.

BIMI is an add-on; it augments the default experience, the lack of it doesn't downgrade the default experience.

> I also do not want to have to check if someone else
> has abused a logo I may use in some CT log. I do
> not want to have to process additional headers in my
> MTAs nor retrieve and store your logos in some new
> image store. I do not want to have to deal with any
> of the new problems that'll arise when any of that
> breaks.

Again, I'm unclear about the context of this statement. Nobody is going to make you as a sender, brand, or receiver send with BIMI. Nobody is going to make you retrieve logos from a store, nobody is going to make you verify any log, nobody is going to make you process additional headers.

Instead, it's about enhancing the email experience for those motivated to do so. And, BIMI provides a way to do this.

--Terry

________________________________
From: bimi <bimi-bounces@ietf.org> on behalf of Stephen Farrell <stephen.farrell@cs.tcd.ie>
Sent: Thursday, February 14, 2019 2:57 AM
To: bimi@ietf.org
Subject: [Bimi] (non)desire for bimi


(Sorry for not replying in-thread but I just subscribed
to the list, and this perhaps also deserves a separate
thread.)

>>> * Internet users want it - clear demand
>>
>> That claim keeps being made but I've never seen any serious
>> documentation for it.
>
> Marketing people want it -- that may not be documented but I have
> sufficient anecdotes to hand to believe it be the main driver here.

I'd be interested in some kind of verifiable backup
for that "clear demand" claim - I'm unaware that
such exists, other than perhaps as Richard says for
marketing purposes, and ISTM those purposes are amply
met already via mail bodies.

Meanwhile...

I use the Internet. I do not want logos added to mail
headers that increase the attack surface of my MUAs,
(and MS/MTAs), that likely enable additional tracking
of mail users, including me, and where mobile device
and web MUAs are unlikely to offer me an option to
turn all that off, even if some desktop MUAs might
(eventually), at the risk of making messages harder
to comprehend.

I also just do not want to see your logos, thanks.
Imposing those on me would decrease the utility of
mail. And regardless of what PKI were built I would
not treat bimi'd messages any better, more likely
I'd consider them badly.

As someone who sends email (not as a bulk sender)
from various domains that I operate, I do not want
to pay €€€ to someone for an additional cert, nor
for an "approved" logo, in order to increase the
chances that my mail gets delivered. Things in that
respect are bad enough, and this proposal seems to
me likely to only worsen the situation for those
who operate small domains, presumably to the benefit
of those who operate large mail infrastructures
and CAs who issue certs for money.

I also do not want to have to check if someone else
has abused a logo I may use in some CT log. I do
not want to have to process additional headers in my
MTAs nor retrieve and store your logos in some new
image store. I do not want to have to deal with any
of the new problems that'll arise when any of that
breaks.

So: No thanks, from me. Personally, as a mail user
I only see downsides to this whole idea.

Thanks,
S.