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

Barry Leiba <barryleiba@computer.org> Mon, 23 April 2012 04:52 UTC

Return-Path: <barryleiba.mailing.lists@gmail.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 335E821F8542 for <spfbis@ietfa.amsl.com>; Sun, 22 Apr 2012 21:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 8V8mJeiw-joE for <spfbis@ietfa.amsl.com>; Sun, 22 Apr 2012 21:52:31 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9903B21F8537 for <spfbis@ietf.org>; Sun, 22 Apr 2012 21:52:30 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so6817559ghb.31 for <spfbis@ietf.org>; Sun, 22 Apr 2012 21:52:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=cbSwb98IdzLACKBxmPF1cTFDeppIEVeNZTdV+rh/IN8=; b=HA6QzFE8jcPjGzYSkMcGttMdt4a/3b+7fxImqWm6GeOUBg17OS3epYAqNdbZ4vl5Lp GW5FWoyAvhBOC2NgSfWbzCLVnYklMppbKNSjnJK26Yek7WPlxkXxNEs99BvvnvK8CFs1 NAXgbBPT7RC7TgcGZFueP3LfJlsPG4xpXWkiLwHUmPr0EsUC2s6vlPv6o52r5H1rfCPg pjmOLpxLkwfvMAd8EssBTb8ArkBnyLY1kkenWnABNfGsloaxCMTR25e6iI8jzKEr3jS9 pk4tGR/r+AYVOv2pdIVvJfvCtcusTtcAXRP6jPxonI5XQFKNHAD8FKvH1WTMpy0oqs3x G3sA==
MIME-Version: 1.0
Received: by 10.236.154.35 with SMTP id g23mr13331799yhk.107.1335156749413; Sun, 22 Apr 2012 21:52:29 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.152.14 with HTTP; Sun, 22 Apr 2012 21:52:29 -0700 (PDT)
In-Reply-To: <9452079D1A51524AA5749AD23E0039280FED0D@exch-mbx901.corp.cloudmark.com>
References: <CAC4RtVAV5PH+VMzppVxAQgGq0f28ARN846e17G_8sbLCThm-KA@mail.gmail.com> <9452079D1A51524AA5749AD23E0039280FED0D@exch-mbx901.corp.cloudmark.com>
Date: Mon, 23 Apr 2012 00:52:29 -0400
X-Google-Sender-Auth: p_SMr3inyJjLbn9VBkqJ0-8e2qg
Message-ID: <CAC4RtVA8i1MrZ1+vEicstYyDDJu=1N=BW-9_UtPgL1QrUm0fvQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Content-Type: multipart/alternative; boundary="20cf303b427dc4ab4704be516732"
Cc: "spfbis@ietf.org" <spfbis@ietf.org>
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:52:34 -0000

Ah... Then the whole item 3 needs to be reworded to say what is actually
the case with respect to processing cost and accuracy.  If there actually
is a benefit to SPF here, say so.

Barry

On Sunday, April 22, 2012, Murray S. Kucherawy wrote:

>  Comments inline (alas):****
>
> ** **
>
> *From:* spfbis-bounces@ietf.org <javascript:_e({}, 'cvml',
> 'spfbis-bounces@ietf.org');> [mailto:spfbis-bounces@ietf.org<javascript:_e({}, 'cvml', 'spfbis-bounces@ietf.org');>]
> *On Behalf Of *Barry Leiba
> *Sent:* Sunday, April 22, 2012 1:58 PM
> *To:* spfbis@ietf.org <javascript:_e({}, 'cvml', '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.]***
> *
>
> ** **
>