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

"Murray S. Kucherawy" <msk@cloudmark.com> Mon, 23 April 2012 03:51 UTC

Return-Path: <msk@cloudmark.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 181F521F84DF for <spfbis@ietfa.amsl.com>; Sun, 22 Apr 2012 20:51:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.639
X-Spam-Level:
X-Spam-Status: No, score=-102.639 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599, 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 au0CNDX+xKq8 for <spfbis@ietfa.amsl.com>; Sun, 22 Apr 2012 20:51:46 -0700 (PDT)
Received: from mail.cloudmark.com (cmgw1.cloudmark.com [208.83.136.25]) by ietfa.amsl.com (Postfix) with ESMTP id 52E9F21F84F8 for <spfbis@ietf.org>; Sun, 22 Apr 2012 20:51:46 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com ([72.5.239.26]) by mail.cloudmark.com with bizsmtp id 1Frl1j0010as01C01FrlB8; Sun, 22 Apr 2012 20:51:45 -0700
X-CMAE-Match: 0
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=2.0 cv=RaES+iRv c=1 sm=1 a=QMZKka45TBd+hNGtXG2bIg==:17 a=ldJM1g7oyCcA:10 a=w0_tcEhzsP4A:10 a=zutiEJmiVI4A:10 a=kj9zAlcOel0A:10 a=xqWC_Br6kY4A:10 a=48vgC7mUAAAA:8 a=6oOKkq69zweqNnNsXDwA:9 a=82MWxT46JCWIyOdjoGUA:7 a=CjuIK1q_8ugA:10 a=lZB815dzVvQA:10 a=uDqZWuVI5siDKuBy:21 a=kWv-wJhs9-teDX1_:21 a=QMZKka45TBd+hNGtXG2bIg==:117
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::54de:dc60:5f3e:334%10]) with mapi id 14.01.0355.002; Sun, 22 Apr 2012 20:51:45 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "spfbis@ietf.org" <spfbis@ietf.org>
Thread-Topic: [spfbis] Review of draft-ietf-spfbis-experiment-05
Thread-Index: AQHNIMqwFmLLWp0VJEuOTXJcBTjdz5anzRGA//+OihCAAHiZAP//5QzwgAB83oD//46t8A==
Date: Mon, 23 Apr 2012 03:51:45 +0000
Message-ID: <9452079D1A51524AA5749AD23E0039280FED45@exch-mbx901.corp.cloudmark.com>
References: <CAC4RtVAV5PH+VMzppVxAQgGq0f28ARN846e17G_8sbLCThm-KA@mail.gmail.com> <3850142.Cln9WJldGb@scott-latitude-e6320> <9452079D1A51524AA5749AD23E0039280FECB6@exch-mbx901.corp.cloudmark.com> <16903045.7Ta8mtnNKj@scott-latitude-e6320>
In-Reply-To: <16903045.7Ta8mtnNKj@scott-latitude-e6320>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [67.160.203.60]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudmark.com; s=default; t=1335153105; bh=8SxkyV6FN+RQVgvtS8h/mIQ1D+TpBqAElifTOxj9tfw=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=KaYHD5wSbK2xbeKd7oQnhC3NJQZfCMxCaMaN+XKGcivHGmwEdEBzst2kFGARUarR+ Ic/jnIQO2D0j9ASp9nTd8dJ3Zdmk+Ia+qIUBta/6p8BqVZWg8YDvALrfkENfjt+YQ5 VpFR42YPbPq4TtiErh24heGTyV7FnTmAL6Vp0Dh4=
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 03:51:47 -0000

> -----Original Message-----
> From: spfbis-bounces@ietf.org [mailto:spfbis-bounces@ietf.org] On Behalf Of Scott Kitterman
> Sent: Sunday, April 22, 2012 8:29 PM
> To: spfbis@ietf.org
> Subject: Re: [spfbis] Review of draft-ietf-spfbis-experiment-05
> 
> Since Sender ID makes use of SPF records, it is possible to make the
> claim that lack of publishing Sender ID specific records is not a sign
> of disinterest in Sender ID, but in fact a sign that few senders find
> problems with publishing an SPF records for both.
> 
> Since a large number of domains (I don't have a number I can support,
> but it's clear that SPF was widely adopted before the Sender ID RFCs
> were published) published records before they were used for both
> protocols, I think it's an important point that all those domains were
> opt-ed in to the Sender ID experiment involuntarily.

Taken together, this says early SPF adopters became unwitting participants in the Sender ID experiment, but it didn't make a difference in the end because it didn't cause any problems.  If that's the case, then why is highlighting who was "here" first (in terms of the DNS mechanism) an important thing?

> There are any number of ways we could re-write history to make things
> more palatable, but I think it's important that what we say be correct.

I think there's a difference between deliberate historical revisionism and an effort to avoid details that don't appear to be relevant to the matter at hand.  The actual history is well-documented if the curious want to go unearth it.  We aren't trying to hide anything; we're just trying to (and need to) avoid showing bias.

-MSK