[Bimi] BIMI Reporting

Tom Bartel <tom.bartel@gmail.com> Wed, 06 April 2022 23:09 UTC

Return-Path: <tom.bartel@gmail.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 3B0B03A103A for <bimi@ietfa.amsl.com>; Wed, 6 Apr 2022 16:09:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.604
X-Spam-Level:
X-Spam-Status: No, score=0.604 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 jmIHiDAUEebT for <bimi@ietfa.amsl.com>; Wed, 6 Apr 2022 16:09:08 -0700 (PDT)
Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E87A33A1030 for <bimi@ietf.org>; Wed, 6 Apr 2022 16:09:07 -0700 (PDT)
Received: by mail-vs1-xe31.google.com with SMTP id t6so2025029vsq.11 for <bimi@ietf.org>; Wed, 06 Apr 2022 16:09:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=n38/YhTbQ4rIK0JMdUpged63UwLPsqOVanayjWKTmTs=; b=JgMigtQGuzBM672nAkg5KsYvyfxFsZ50/qV20eAvAq9Cv3KNE39s7Ht6gYix2m1I8G +KZ42Dvj+nsnB78AhFhQA9BiQHlgLf0sRoKKCttmuGrzahZ45OhdGoJVD+y871IQ5Pq7 2k8jq+f+m2ad00/pEonwevXtn1EDsSXHSgbl51q6/9w26C1fUNpp3hgAtKhbFDznjgAH DfqJfdDTnXjThrwqElzOgRRiUtubjSsiJujYHCB+9+xDCSPXgpExIeSIR4+ufjGpXDPA tB1+bOQue/jT2vSpJhsWe+1q9oUJYOuwvo1XxX+9ljA3jN+qE21YzEwYm11VMdC9ceYA G8gA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=n38/YhTbQ4rIK0JMdUpged63UwLPsqOVanayjWKTmTs=; b=GCpBqs5LE56flcHJsI6CMsLqAsSbum69TZ8gTstV1vCGyhymYlUQwADaKjmfrxZ0Jc AtVguziSxOdtlxvf8AT68jCtB0GsuLtbX72xsVBZ5j+aC7eNU20+7xaUNFmwposnen7Q 3y8EJjXnfhfPqgdPK29dK8t77yw+XN6T47Vu92z94hyzn8h6TfYAhrVILpXpAFhUxsvW HeFSUXKaR7Tc738nvOF28WLYc8vI9RLOpKA/A91xw+xWNeHfDDRfbrfPJrbiXxTEw8G5 TURsW9GevkbQtjrwXNXHRU1E9kf4enz/1RLhLJXR0xTIi4N2/nTND8/tZ03mFqsu6jby Yw7w==
X-Gm-Message-State: AOAM533+NnT6TpSfe9oSZCBf46ODNm5uDYhlliF3r06yDnPhicfeHFBg +uKi79uKrnFOhOzdFB1gqUWmWYsBbc6VzSxCT8oNdMLysXM=
X-Google-Smtp-Source: ABdhPJzEzSxcqJCZge7AQNHyGoxgKFeGg60B9k16a/ouPCu1bp0L2F8ZI4QSaDNyPPFVMk3z4EGu35QPA98C9vXqYKk=
X-Received: by 2002:a67:d38f:0:b0:327:e8fe:b672 with SMTP id b15-20020a67d38f000000b00327e8feb672mr3828352vsj.62.1649286546238; Wed, 06 Apr 2022 16:09:06 -0700 (PDT)
MIME-Version: 1.0
From: Tom Bartel <tom.bartel@gmail.com>
Date: Wed, 06 Apr 2022 17:08:40 -0600
Message-ID: <CALPyw-7QxK2aEUW4daYds5s-xaGCOmaS9YxjS6b1ksG3Zdb2Qg@mail.gmail.com>
To: bimi@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b8b06605dc0472f1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bimi/7RF94Kjyq26TTuKJe2Z2BBVpOx4>
Subject: [Bimi] BIMI Reporting
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: Wed, 06 Apr 2022 23:14:54 -0000

After reviewing the BIMI Reporting draft:


https://datatracker.ietf.org/doc/html/draft-adams-bimi-reporting


I think that it may be missing some useful data that would greatly benefit
BIMI (and DMARC) adoption. Through discussions with senders interested in
BIMI, it’s become apparent that they’ll need to measure the effectiveness
of their deployment (to justify their spend), and I don’t think that the
current reporting draft includes the necessary level of data.


I’d suggest the addition of an aggregate count per reporting period (e.g.
24 hours) of BIMI logos that were displayed by the MUA. This would be in
addition to the aggregate BIMI record evaluations already in the draft.


Senders ultimately want to know if the “juice will be worth the squeeze” -
that is, not only implementing DMARC, but the additional effort of implementing
BIMI, too.


I know that this level of reporting may happen elsewhere in the email
pipeline than where DMARC and initial BIMI evaluation occurs, though I
think it’s important enough to explore whether it can be added.


What do folks think? Does it make sense to add this additional reporting
signal to the BIMI Reporting draft?

Tom