Re: [Bimi] (non)desire for bimi

Richard Clayton <richard@highwayman.com> Mon, 18 February 2019 17:34 UTC

Return-Path: <richard@highwayman.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 B0949130E6E for <bimi@ietfa.amsl.com>; Mon, 18 Feb 2019 09:34:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Z07DFNgOQ0kg for <bimi@ietfa.amsl.com>; Mon, 18 Feb 2019 09:34:30 -0800 (PST)
Received: from mail.highwayman.com (happyday.demon.co.uk [80.177.121.10]) (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 11A94128D0B for <bimi@ietf.org>; Mon, 18 Feb 2019 09:34:30 -0800 (PST)
Received: from localhost ([127.0.0.1]:31321 helo=happyday.al.cl.cam.ac.uk) by mail.highwayman.com with esmtp (Exim 4.91) (envelope-from <richard@highwayman.com>) id 1gvmo0-000FNY-SL for bimi@ietf.org; Mon, 18 Feb 2019 17:34:27 +0000
Message-ID: <94f8IUC7kuacFAOU@highwayman.com>
Date: Mon, 18 Feb 2019 17:19:55 +0000
To: bimi@ietf.org
From: Richard Clayton <richard@highwayman.com>
References: <aa919aeb-caa1-6494-259d-a553b238c268@cs.tcd.ie> <3d9231e9-6936-cc02-000e-a4d7df919bb4@andreasschulze.de> <CAAYvrBvGediUY1W9PZ+JuS585Mk8wxLpFq7TZELSOF-NSp5CyQ@mail.gmail.com> <5c7a10e3-47a0-e84a-d78a-dea5c44fb2ae@dcrocker.net> <CAAYvrBumzJrj51VdOYEf_Tmo4X-MhvfuabWHb_p5embAe0uAow@mail.gmail.com> <0245cd12-2965-86ca-78e4-b3b1996e6efe@gmail.com> <A08D52DA-AC05-4A6A-BF9C-AEF2239E8F61@skyelogicworks.com> <6ac6da1c-6c60-b983-7e1a-90d3fb30ac5b@dcrocker.net> <6929D4C0-FE58-43E9-9605-98F040308B74@skyelogicworks.com>
In-Reply-To: <6929D4C0-FE58-43E9-9605-98F040308B74@skyelogicworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Mailer: Turnpike Integrated Version 5.03 M <X7x$+7Mf77fcnOKLMea+dOhW$8>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bimi/1ARVVUuvZTQlFwjSa8MpKGzF-9c>
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: Mon, 18 Feb 2019 17:34:33 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In message <6929D4C0-FE58-43E9-9605-98F040308B74@skyelogicworks.com>,
Thede Loder <thede=40skyelogicworks.com@dmarc.ietf.org> writes

>(That said, none of BIMI’s proponents are arguing that end users' choices 
>resulting from the display of logos will be a primary or substantive cause of 
>improvement in outcomes.  No one is saying that this mechanism should even be 
>considered for reasons other than for its potential to reduce safety.

     increase ?

>  If you 
>see language in the documentation asserting otherwise, please bring it to the 
>group’s attention )   

from the front page of the brand indicators website:

     "What If You Could Put Your Brand On Every Email and Users Could
     Trust It’s You?"

     "will use brand logos as indicators to help people avoid fraudulent
     email"

     "When users see your logo, they’ll trust the email"

     "Stop Phishing"

this reads to me that an improvement in outcomes is a key aim of BIMI
since there is very little other substantive messaging there:

Except of course it also says

     "giving marketers a huge new opportunity to put their brands in
     front of consumers for free"

     "we believe brand indicators will increase response rates,
     magnifying the power and reach of our marketing efforts."

But I look forward to the "forest" document which sets out the high
level of what is intended to be achieved, so that it is possible to
assess the technical suggestions against that...

... and yes, if the main driver here is marketing then say so and the
effort can be properly tuned, by those who are prepared to work on the
standard effort, to get that right.

But Aims first, Tech Details second: No point talking about certificate
pinning if there will only ever be one CA for example.

>The other reason I asked the question above was to motivate disclosure of 
>additional objections to BIMI.

it's hard to object to generic aims if they aren't documented and appear
to dilettantes like me to change with the year

>Regarding D, let’s begin a larger discussion of costs.  Given your experience, 
>where do you see the costs in doing a standard?  

Hiring me to read your last email, check your website text and proofread
the brief response that I have penned here would likely cost you $100 at
my chargeout rate.

The opportunity cost of doing this email rather than working on better
schemes for mitigating list bombing (say for a concrete example) is
substantially more than $100 given the cost to the community (and
particular victims) of that abuse.

Multiply my small contribution by all the experts who need to keep up
with email lists, consider the consequences of minor changes, brainstorm
major improvements etc. and you will soon be talking substantial sums. 

The IETF does not pay for the expertise they garner (and I think would
probably be rather worse off if they did) but "opportunity cost" is the
key issue here -- in my view.

- -- 
richard                                                   Richard Clayton

Those who would give up essential Liberty, to purchase a little temporary 
Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755

-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1

iQA/AwUBXGrpOzu8z1Kouez7EQJpCgCgn0xQxK5o32eG/EaZE8+oyHP/BW0AoKy1
7lI+D0FR5Peva1oVxKzgBluR
=Mh0c
-----END PGP SIGNATURE-----