Re: [dmarc-ietf] hints for receivers

Scott Kitterman <sklist@kitterman.com> Sat, 20 April 2013 18:20 UTC

Return-Path: <sklist@kitterman.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEFCD21F8C69 for <dmarc@ietfa.amsl.com>; Sat, 20 Apr 2013 11:20:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tfWstsx423xq for <dmarc@ietfa.amsl.com>; Sat, 20 Apr 2013 11:20:17 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id BCBCB21F8E36 for <dmarc@ietf.org>; Sat, 20 Apr 2013 11:20:15 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 420BB20E40D2; Sat, 20 Apr 2013 14:20:05 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1366482015; bh=EXgbJbFBUXaLpLZ3UdTK5+PjyRWkei+QHqfpIM7960E=; h=From:To:Subject:Date:In-Reply-To:References:From; b=mLEQQcvpebX4arg7SKFj+YP4nQgNBdRYSMTPodSsoLPOanKpTweziauJ3yx59PwhA TyhURabIjRlS0sBfZyMlIkLT3Uh1u2Bz/mwUPDanXCdi8GjjlTgdhXiVcnNczalrtL kAKUM1a4LYyWB/njhWJXoc8pO9g3peZOlihz6LWw=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 262BA20E409E; Sat, 20 Apr 2013 14:20:04 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Sat, 20 Apr 2013 14:20:03 -0400
Message-ID: <5757433.jhuOLl2NjA@scott-latitude-e6320>
User-Agent: KMail/4.9.5 (Linux/3.5.0-27-generic; KDE/4.9.5; i686; ; )
In-Reply-To: <CAL0qLwbnhiOuPDD8nt8HKT5zbp7pOtivW7XRFxszTLRpasE3Cg@mail.gmail.com>
References: <8598319F-D23B-4A5D-9896-0D2CF5D27F94@eudaemon.net> <1581179.AB75fythCq@scott-latitude-e6320> <CAL0qLwbnhiOuPDD8nt8HKT5zbp7pOtivW7XRFxszTLRpasE3Cg@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
Subject: Re: [dmarc-ietf] hints for receivers
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmarc>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Apr 2013 18:20:19 -0000

On Saturday, April 20, 2013 10:49:00 AM Murray S. Kucherawy wrote:
> On Sat, Apr 20, 2013 at 10:21 AM, Scott Kitterman 
<sklist@kitterman.com>wrote:
> > Most of the current deployment is at large providers that can do
> > significant
> > data analysis to effectively identify lists.  As a small domain, there's
> > no way
> > I can do the same.
> > 
> > If there were a protocol method to share this information, either among
> > trusted receivers or via 'hints', it could be useful to smaller providers
> > that
> > don't have the scale to mine the data themselves.
> 
> Why would you, as a small-scale receiver, believe what an unfamiliar sender
> claims about whether its traffic transits lists, ultimately meaning "don't
> be so strict with this message"?  That seems a big loophole with little
> benefit to me, regardless of your size, given the nature of the problem
> space; malicious senders will always use it, and good senders that use it
> will be spoofed more easily.

I probably wouldn't.  My point wasn't to advance a particular solution, but to 
suggest that the experience base with how large providers with extensive data 
mining capability prefer to do things probably isn't universally applicable.

I solution involving receiver collaboration is more likely to be useful.

Scott K