Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard

Ted Lemon <Ted.Lemon@nominum.com> Wed, 21 August 2013 16:22 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B11E11E8110 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 09:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.437
X-Spam-Level:
X-Spam-Status: No, score=-106.437 tagged_above=-999 required=5 tests=[AWL=-0.138, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, 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 rMoAR06lBwXq for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 09:22:52 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id 4624511E8112 for <ietf@ietf.org>; Wed, 21 Aug 2013 09:22:52 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKUhTpW6kqA31AqKrhSAP2wsIl6s3UpLcP@postini.com; Wed, 21 Aug 2013 09:22:52 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id AE1C61B82AD for <ietf@ietf.org>; Wed, 21 Aug 2013 09:22:51 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 174F019006E; Wed, 21 Aug 2013 09:22:51 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 21 Aug 2013 09:22:51 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Patrik Fältström <paf@frobbit.se>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Thread-Topic: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Thread-Index: AQHOneqwiRHwqjkl/E2l9OdgBMkwq5mff1gAgAA3SoCAADGQgIAAAzeAgAAEfYCAAA4tgIAALbyAgAAjDoA=
Date: Wed, 21 Aug 2013 16:22:50 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077525FC8E@mbx-01.win.nominum.com>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se>
In-Reply-To: <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <B988836A0E47D44EAFA2BCCFDD0FDB0A@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 16:23:02 -0000

On Aug 21, 2013, at 7:17 AM, Patrik Fältström <paf@frobbit.se> wrote:
> My conclusion is that a statement that nobody queries for it is false.

I am curious if the folks who did the analysis of query rates know the answers to the following questions:

1. Per unit of mail delivered (as opposed to per domain), for what percentage of delivered mail for which SPF TXT records exist do SPF RRtype records _also_ exist?   I wasn't clear on whether an attempt was made to come up with an answer to this question.

2. Per unit of mail received, for what percentage of received mail does the receiver currently issue SPF RRtype queries.

The reason I ask these questions is that the rationale for the decision made by the working group was that the data supported it, and I think that was a good rationale, but only if the data _actually_ supports it.   But I don't think that the data was analyzed on the basis of units of mail delivered, but rather on the basis of number of queries seen.

The reason I think the distinction is important is that as several people have observed, there are some heavy hitters in this discussion—Yahoo and Google, for example.   If the heavy hitters  all already publish the SPF RRtype, that might make a difference.

Actually, I just checked.   Right now, none of them seem to publish SPF RRtype records.   Yahoo doesn't even publish a TXT record containing SPF information.   An argument could be made that if we really wanted to push the adoption of SPF RRtypes, getting Google, Yahoo and Hotmail to publish SPF RRtype records would actually make it worthwhile to query SPF first, because most queries probably go to those domains.

I think the people who are pushing for a different outcome than the spfbis working group arrived at would do a lot to make their case if they could use their collective influence to get these three domain owners to publish SPF RRtype records.   This is a really easy thing to do; if it can't be done, that's a pretty clear indication that the SPF RRtype is doomed.