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

Patrik Fältström <paf@frobbit.se> Wed, 21 August 2013 18:13 UTC

Return-Path: <paf@frobbit.se>
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 90E4111E8137 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:13:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
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 1279geHTMDCh for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:13:56 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id B435E11E812E for <ietf@ietf.org>; Wed, 21 Aug 2013 11:13:56 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::14] (unknown [IPv6:2a02:80:3ffc::14]) by mail.frobbit.se (Postfix) with ESMTPSA id DF8A121F96; Wed, 21 Aug 2013 20:13:54 +0200 (CEST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
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
From: Patrik Fältström <paf@frobbit.se>
In-Reply-To: <5214F97B.2080400@dcrocker.net>
Date: Wed, 21 Aug 2013 20:13:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se>
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> <5214F97B.2080400@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1508)
Cc: 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 18:13:57 -0000

On 21 aug 2013, at 19:31, Dave Crocker <dhc@dcrocker.net> wrote:

> Assuming that your conclusion is based on pragmatics and not
> mathematical purity -- that is, that it is concerned with significant
> operational effort, rather than a stray implementation here or there,
> which counts as "noise" in any legitimate statistical analysis -- what
> is the basis for your conclusion?

As I did show, the numbers comes directly from tcpdump on my auth DNS server, where I checked how many do query for TXT and SPF(*). I do not understand the question. What else do you want?

As a few others have said, 4408 do have an error that makes it impossible to use RFC 4408 for migration from TXT to SPF which was the original intent. I do not understand how the conclusion, given the number of SPF queries that is made, on how to fix the problem with RFC 4408 is to deprecate the SPF RRtype.

And to your question on deprecation, yes, to me one do need much more arguments to deprecate something. Specifically when originally the intent was to migrate to what is now to be deprecated.

And this is why I am objecting to 4408bis to be published as an RFC.

If you had an RFC without issues that really did talk about a migration strategy (including having examples using SPF records and not TXT which one should migrate from) and still people did not migrate, then we would have a different discussion.

But we are not there. A proper migration strategy to SPF has not been published.

   Patrik

(*) I have now removed TXT version of the SPF record for frobbit.se to see whether the number of queries for SPF RRType go up or not.