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

Scott Kitterman <spf2@kitterman.com> Mon, 23 April 2012 04:07 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 D326621E8018 for <spfbis@ietfa.amsl.com>; Sun, 22 Apr 2012 21:07:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level:
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019, 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 JXv-9On9758r for <spfbis@ietfa.amsl.com>; Sun, 22 Apr 2012 21:07:11 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 04C4521E8013 for <spfbis@ietf.org>; Sun, 22 Apr 2012 21:07:11 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 8940F20E40E0; Mon, 23 Apr 2012 00:07:10 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1335154030; bh=tj2fKImPS+qsASoAzD6fOOCMzJ9kZGTdzZV7mRPTwHk=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=bf0tq6jlnXg1+m/hg7MOWg1iiQrT5VEc0N3F+Pl8j1F3bIx+l8tGaaq9c1ftm+G+E OThN8OLELYrs/oxnmrq7o+dLkyzZDlsrUzyUcdIhBXcXNeWQgAmgXSZbxr+48HSfN7 Vx8wBrdJLuc/sF9DIkqMeEyZxSWJ5Xbfs2Sidrf0=
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 5550320E4091; Mon, 23 Apr 2012 00:07:10 -0400 (EDT)
From: Scott Kitterman <spf2@kitterman.com>
To: spfbis@ietf.org
Date: Mon, 23 Apr 2012 00:07:09 -0400
Message-ID: <1464772.NHJB6P54Ra@scott-latitude-e6320>
User-Agent: KMail/4.8.2 (Linux/3.2.0-23-generic-pae; KDE/4.8.2; i686; ; )
In-Reply-To: <9452079D1A51524AA5749AD23E0039280FED0D@exch-mbx901.corp.cloudmark.com>
References: <CAC4RtVAV5PH+VMzppVxAQgGq0f28ARN846e17G_8sbLCThm-KA@mail.gmail.com> <9452079D1A51524AA5749AD23E0039280FED0D@exch-mbx901.corp.cloudmark.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 04:07:12 -0000

On Monday, April 23, 2012 03:40:21 AM Murray S. Kucherawy wrote:
> Comments inline (alas):
> 
> From: spfbis-bounces@ietf.org [mailto:spfbis-bounces@ietf.org] On Behalf Of
> Barry Leiba Sent: Sunday, April 22, 2012 1:58 PM
> To: spfbis@ietf.org
> Subject: [spfbis] Review of draft-ietf-spfbis-experiment-05
> 
> OLD
>    3.  Although the two mechanisms often used different email addresses
>        as the subject being evaluated, no data collected showed any
>        substantial operational benefit (e.g., cheaper processing,
>        improved accuracy) to using Sender-ID over SPF.
> 
> I suggest "to using either mechanism over the other."
> 
> [MSK: I don't think that's correct.  Sender ID has a substantially higher
> processing cost given that it requires accepting the DATA part of the
> message and has an obviously higher cost to extract the various identifiers
> the PRA algorithm considers.  SPF, purely compute-wise, is cheaper. 
> However, their accuracy is comparable.  If we want to be clear, we can say
> their accuracies are about the same, but SPF is operationally cheaper.]

SPF is also not fundamentally incompatible with existing internet standards in 
a way that prevents it from being advanced, documented in a different appeal 
[1].  One very good answer to "Why advance SPF and not Sender ID?" is that 
there are standards issues with Sender ID that don't exist with SPF.  Even if 
they had equivalent operational complexity/cost, that would, IMO, be enough to 
be determinant.

Scott K

[1] http://www.ietf.org/iesg/appeal/leibzon-2005-08-29.txt