IETF Logo Mail Archive

Re: [Ietf-dkim] DKIM-FBL

"Murray S. Kucherawy" <superuser@gmail.com> Thu, 28 September 2023 02:41 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: ietf-dkim@ietfa.amsl.com
Delivered-To: ietf-dkim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94E9AC15DD5E for <ietf-dkim@ietfa.amsl.com>; Wed, 27 Sep 2023 19:41:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 VLjhRud20fPC for <ietf-dkim@ietfa.amsl.com>; Wed, 27 Sep 2023 19:41:42 -0700 (PDT)
Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7CFAC14CE5E for <ietf-dkim@ietf.org>; Wed, 27 Sep 2023 19:41:42 -0700 (PDT)
Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-9a1bcc540c0so320216766b.1 for <ietf-dkim@ietf.org>; Wed, 27 Sep 2023 19:41:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695868900; x=1696473700; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=r/+6x47WXZQ8Kmp1GqKQGvUGyIREomXfD1V9cbuJHwo=; b=b2cQyjc4qFTajjPig+FQm0HjpyopT+VXF4rqRiuGkTlSlgZ4bGl9qWUvBmCIE3Cig7 vQqvecHTFgWRFs3t0Gp/lwVbB8zAp/TL7jjS7iH9abObiG7ceW230iYlu8cR+go7vFqv mRrjmZcfpm+xymF+3pdMtm5a/9l8twufnczEtKBCYnvsVUgqaAXStxFwLced74eQ4b1S jekiIQAmWgg20Lor//jRlUiJ7+eGzhi0pBm2kx3jdTdVCMWx7vrm0tZb+f6vQCTflshq VlEsWzLu0EqU5ICg8O63oM1MDzKzg+WBxzGjinCtAxDt6MQDZr0aigo2l0ul6/+EivAi 1hCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695868900; x=1696473700; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=r/+6x47WXZQ8Kmp1GqKQGvUGyIREomXfD1V9cbuJHwo=; b=gJWHVSwLCJnR0qEC5HyQsl7G+TFGaFp5FsE2iINww77bdcb36o5IH+bcvlQ2MdkXUg RmSdFHvX7vGnOycSxdWSmxuKFAG+eUS5QzDzmu+EyTi7xfPlsfGj/dcOx1tPqp50ISBQ EfnXUaZ7P9mRcnedEFMTUPqzaICpkUV/h+G8e/Y+rVJBbZWyxmm3qNZkohZmnrctzJnb W0Jo3ZUcACH+o+j5HNsnHIFTCoKHf2VS69LHZsLQ8XlnTpfHHzJpjJ/usR42VRJajKPe msjKX7d4us2LU6JWnBDPUUNnkOtSDzeiEtT2Cf3yLjuregxqgHXEeMptsMK7//ElAq8O I2uA==
X-Gm-Message-State: AOJu0YwL9ScqXIJQaVnuo9Pb/nojqDD+Lh034fhHjvVF2jBawNBZlw7s urwA1byiJf7NoWiJ4leSjdjS5uPrsDUuCovkB+rmj3z9DYI=
X-Google-Smtp-Source: AGHT+IHA/FJPN6JGhfuaoBLJGPQryo/pXKp5uprxhTljcMhZZoREwdixky5dpQADcGFyC5YaRLUz3vSOw3EF9QNE704=
X-Received: by 2002:a17:907:d490:b0:9b2:b532:d8d7 with SMTP id vj16-20020a170907d49000b009b2b532d8d7mr3049574ejc.5.1695868900494; Wed, 27 Sep 2023 19:41:40 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR11MB4351A3ED766A2A9D1EB44007F7C2A@MN2PR11MB4351.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB4351A3ED766A2A9D1EB44007F7C2A@MN2PR11MB4351.namprd11.prod.outlook.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 27 Sep 2023 19:41:29 -0700
Message-ID: <CAL0qLwa-31yiRrt64Y0WjgWH5aD_Li9QNBkY4ZpNQkG0B3w+oA@mail.gmail.com>
To: "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>
Cc: "ietf-dkim@ietf.org" <ietf-dkim@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006651720606623f55"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/vf79Nxb4Fp9c9jCvXpeid4yZIrw>
Subject: Re: [Ietf-dkim] DKIM-FBL
X-BeenThere: ietf-dkim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-dkim/>
List-Post: <mailto:ietf-dkim@ietf.org>
List-Help: <mailto:ietf-dkim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Sep 2023 02:41:46 -0000

I'm betting the chairs would want this not to consume any of the
so-far-meager energy this WG is showing.  I can imagine that ietf-smtp
would be a reasonable place to at least announce that you're working on
this.  I don't know that that's a good home for ongoing discussion either
though.

We don't really have a venue that talks about feedback loops that I can
find, which seems to me to be the primary thing here.  It almost seems like
the old MARF list (if it's still open) might be, though I don't know who
might be paying attention.  Or you could always use the ART list.

If you're trying to identify a venue for processing it, there's no WG that
comes to mind.  You could take it to DISPATCH and see what they recommend.
But unless lots of people show up and want this to happen inside the IETF,
I would consider using the ISE route.

-MSK

On Wed, Sep 27, 2023 at 4:37 AM Brotman, Alex <Alex_Brotman=
40comcast.com@dmarc.ietf.org> wrote:

> Hey folks,
>
> I'm not entirely sure this is the right place for this.  Someone else
> suggested the DMARC list, and I thought perhaps the "smtp" list might make
> more sense.  If I'm shuffled off to one of those lists, I'll let this
> thread know.
>
> I've attached a draft that uses attributes of a passing DKIM signature to
> create a DNS label that can be used to discover an FBL address.  This
> feedback address can be used by message receivers to provide a copy of FN
> (and potentially FP) (Spam/Not-Spam) reports to the DKIM signers.  This
> allows for entities to perhaps sign with more than one signature, and
> provide feedback to each signer if desired (or each can list multiple rcpts
> if desired).  With traditional FBLs, the lookup is likely based off the
> final sender IP address, which could be the original sender, or an
> intermediary.  This DKIM-based method could aid both MBPs and ESPs in
> fighting outbound abuse from their platforms.  There are also methods in
> the document to attempt to do more to make reports smaller, aiding storage
> and PII concerns.  Thanks for your time and feedback.
>
> --
> Alex Brotman
> Sr. Engineer, Anti-Abuse & Messaging Policy
> Comcast
>
>
> _______________________________________________
> Ietf-dkim mailing list
> Ietf-dkim@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-dkim
>

v2.23.0 | Report a Bug | By Email