Re: [spfbis] Review of draft-ietf-spfbis-experiment-05

Scott Kitterman <spf2@kitterman.com> Mon, 23 April 2012 19:46 UTC

Return-Path: <spf2@kitterman.com>
X-Original-To: spfbis@ietfa.amsl.com
Delivered-To: spfbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65F3521E8015 for <spfbis@ietfa.amsl.com>; Mon, 23 Apr 2012 12:46:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.583
X-Spam-Level:
X-Spam-Status: No, score=-2.583 tagged_above=-999 required=5 tests=[AWL=0.016, 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 j4jyjNEDHh+d for <spfbis@ietfa.amsl.com>; Mon, 23 Apr 2012 12:46:00 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id DFF8E21F84FB for <spfbis@ietf.org>; Mon, 23 Apr 2012 12:45:59 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 391F820E40E9; Mon, 23 Apr 2012 15:45:59 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1335210359; bh=bH3zeFRYbfk5OCHcJluGZ867hdwVRavPPnnKHj/1Q24=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=ERqsj5Ybb5Up1gLCEhGcmnpuk7B33cj2AsoPI3GVzsiLREDKuCRlyGxGzHcwxn+OV xWcX2Dg6iFMD22JKbj2NMJ2fzSH20sUNMVjk6pHhQBau/j1l4a8GL3618K0DTE9Pns ut9NJKWlg0K7wkEzT8hoZSHzaZHFmwzuPMB2njUU=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 1DB9E20E40E3; Mon, 23 Apr 2012 15:45:58 -0400 (EDT)
From: Scott Kitterman <spf2@kitterman.com>
To: spfbis@ietf.org
Date: Mon, 23 Apr 2012 15:45:58 -0400
Message-ID: <2620539.Fpf1xB4moR@scott-latitude-e6320>
User-Agent: KMail/4.8.2 (Linux/3.2.0-23-generic-pae; KDE/4.8.2; i686; ; )
In-Reply-To: <CAJ4XoYe1Vkge=2iWrFgzRyZL-XVt-7bhUCf=xJHhvZcR6mGFiA@mail.gmail.com>
References: <CAC4RtVAV5PH+VMzppVxAQgGq0f28ARN846e17G_8sbLCThm-KA@mail.gmail.com> <9452079D1A51524AA5749AD23E0039280FF5C4@exch-mbx901.corp.cloudmark.com> <CAJ4XoYe1Vkge=2iWrFgzRyZL-XVt-7bhUCf=xJHhvZcR6mGFiA@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: [spfbis] Review of draft-ietf-spfbis-experiment-05
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SPFbis discussion list <spfbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spfbis>, <mailto:spfbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spfbis>
List-Post: <mailto:spfbis@ietf.org>
List-Help: <mailto:spfbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spfbis>, <mailto:spfbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Apr 2012 19:46:01 -0000

On Monday, April 23, 2012 11:13:35 AM Dotzero wrote:
> On Mon, Apr 23, 2012 at 10:34 AM, Murray S. Kucherawy <msk@cloudmark.com> 
wrote:
> >> -----Original Message-----
> >> From: Dotzero [mailto:dotzero@gmail.com]
> >> Sent: Monday, April 23, 2012 5:58 AM
> >> To: Murray S. Kucherawy
> >> Cc: spfbis@ietf.org
> >> Subject: Re: [spfbis] Review of draft-ietf-spfbis-experiment-05
> >> 
> >> It is absolutely incorrect to say that their accuracies are about the
> >> same. I can consistently game PRA to get a neutral outcome regardless
> >> of what the originating domain publishes in it's record. If there is a
> >> Sender field then that is the PRA per the spec. I cannot do the the
> >> same for SPF.
> > 
> > Based on the data collected about actual live mail streams, SPF and Sender
> > ID reach the same pass/fail conclusion about messages at least 80%, and
> > as much as 95%, of the time.  Do you have different data?
> > 
> > We're specifically not doing a comparison of the weaknesses of the two.
> >  We're only citing empirical data.
> You stated that their accuracies are comparable. Given the known
> weakness of PRA (based on emperical data/testing), that is an
> incorrect statement. The whole point of SPF (and presumably SIDF) is
> to mitigate abuse. You have not provided complete details about the
> dataset you are referring to so it is hard to draw detailed conlusions
> regarding key points:
> 
> 1) What percentage of the dataset does not have a Sender field?
> 2) For data points where there is a Sender field, what percentage of
> those data points have a Sender field that is aligned with the Mail
> From (and conceivably From)?
> 3) What percentage of the messages were "abusive"? Would the mail
> stream selected be a likely target for the particular type of abuse I
> am pointing out? If not, why would you expect to see this particular
> type of abuse?
> 4) To what extent is the dataset representative of the mail streams
> that various types and sizes of receivers might receive? That is, is
> the dataset truly representative or are there potential issues with
> self selection, etc?

Perhaps it would be enough to say that there isn't any evidence of accuracy 
improvement associated with the additional complexity of Sender ID?

Scott K