Re: [Bimi] (non)desire for bimi

"A. Schulze" <sca@andreasschulze.de> Sat, 16 February 2019 14:04 UTC

Return-Path: <sca@andreasschulze.de>
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 289CC130E74 for <bimi@ietfa.amsl.com>; Sat, 16 Feb 2019 06:04:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=andreasschulze.de header.b=DeUaIMXk; dkim=pass (2048-bit key) header.d=andreasschulze.de header.b=EbrzadW3
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 qyyr7UOFqZ_w for <bimi@ietfa.amsl.com>; Sat, 16 Feb 2019 06:04:18 -0800 (PST)
Received: from mta.somaf.de (mta.somaf.de [IPv6:2001:470:77b3:103::25]) (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 0CEF1130E73 for <bimi@ietf.org>; Sat, 16 Feb 2019 06:04:17 -0800 (PST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=andreasschulze.de; i=@andreasschulze.de; q=dns/txt; s=ed25519; t=1550325854; h=from : subject : to : references : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding : from : subject : date; bh=P8ZWeQZaXbezem86Jjx3LmzOZ2e+Jk3aLwHH7G9j4Oo=; b=DeUaIMXk2hZgHyjppcPuufOZxaMz0quRymIMghoc5qaJtzj5UjQXsCqb +6WEAcIKXfKeIqSd8x0Yr/2WGZVpDA==
From: "A. Schulze" <sca@andreasschulze.de>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=andreasschulze.de; s=20190120-D99A; t=1550325854; x=1555325854; bh=P8ZWeQZaXbezem86Jjx3LmzOZ2e+Jk3aLwHH7G9j4Oo=; h=From:Subject:To:References:Message-ID:Date:In-Reply-To: Content-Type:from:reply-to:subject:date:to:cc:content-type: message-id; b=EbrzadW39/SHO/alo5vA54yUCNsxAjJ9KOMqsniPpmdWaoT2q02YDLHu5wrrjqNRg 6ziTIStXa/Jcb7t1WnNC80oIyhyOxJIwbAI+vEVk4gqd/cL+KYkKWb3WtDZEJxO/rN H0PKskFAeSFJapzRCWmW7y5gAlzjAiGjP/jzeQqF+eSB02LvvoImeOacJtfTXGZxUa BDNSVct9jIb100/WT0aWgyJhdVlhLG1ga2hAk7RcnjFQnMGQvLHnlCJdtGBcDoAnLV pL+SqbI/rw8c8KCq9lnOThCGs3NYZJODJtBP1PYSkGXQqYoXIDFwQX/6ADBNcAukuo jgPXTEinTdmWA==
To: bimi@ietf.org
References: <aa919aeb-caa1-6494-259d-a553b238c268@cs.tcd.ie>
Message-ID: <3d9231e9-6936-cc02-000e-a4d7df919bb4@andreasschulze.de>
Date: Sat, 16 Feb 2019 15:03:40 +0100
MIME-Version: 1.0
In-Reply-To: <aa919aeb-caa1-6494-259d-a553b238c268@cs.tcd.ie>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/bimi/JesHjCtbuwIL8aIB7DF2D2lwYYk>
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: Sat, 16 Feb 2019 14:04:21 -0000


Am 14.02.19 um 11:57 schrieb Stephen Farrell:
> I also just do not want to see your logos, thanks.

Hello,

I agree with Stephen.

We all, but specially MUA developer/maintainer, fail to teach the user
what the technical meaning of RFC5322.From is.
It is simply text choosed by message originator, no difference to RFC5322.subject

Users expect this to be something other. That's the problem.

So we created these horrible zoo named SPF, DKIM, DMARC and ARC.
And what's the result?

RFC5322.From contain something I use to name "Display Name"
All the authentication tech ignore this part.
But what do MUAs present as "FROM" ?
Most of the time exactly this last piece of unauthenticated data.

All, what BIMI could do, is to teach
"Hey User, this message from $BRAND is only valid if you also see $BRAND's logo"

So BIMI sounds to me like an authentication method for the display name.
I would say, we failed...

Andreas