Re: [spfbis] there is no transitiion, was Last Call: <draft-ietf-spfbis-4408bis-19.txt>

"John Levine" <johnl@taugh.com> Wed, 21 August 2013 17:45 UTC

Return-Path: <johnl@iecc.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 5E4F211E8136 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 10:45:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.654
X-Spam-Level:
X-Spam-Status: No, score=-102.654 tagged_above=-999 required=5 tests=[AWL=-0.211, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, 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 h06eHuAgzZ2V for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 10:44:57 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 0F70311E80FA for <ietf@ietf.org>; Wed, 21 Aug 2013 10:44:56 -0700 (PDT)
Received: (qmail 83833 invoked from network); 21 Aug 2013 17:44:54 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 21 Aug 2013 17:44:54 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5214fc96.xn--9vv.k1308; i=johnl@user.iecc.com; bh=j5TGF71YPYJ+rKz53tojkviur97tuTA42Hk2XCE+82s=; b=LWy7HY461TO5E/Pswoc4u6n+FwhQoIWW8ZWPX6NlwuTAdF16Tx4O7PuBv6RBklGZuli4cqmWnu9+AjB2fit+aBkP+sBWNB0xXLb3+3Y26YlzUMgPDvklSl19RitRZGY8Ys7/da1MHUOUVSCXSh+fuDD6h0WomhCz1QQIcnRhLpCyxfUWLfTWyyWhfIkKnx9PfPYnxOdLhwCD9PJbJy2O6X5ecGh6HpTxOTBNvsAifAoJW7u27AHq+9i7K9twFpTO
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5214fc96.xn--9vv.k1308; olt=johnl@user.iecc.com; bh=j5TGF71YPYJ+rKz53tojkviur97tuTA42Hk2XCE+82s=; b=Xoq2lgSNOHjaLEGnqyiv3De+u5REd+GGndZ80rKTaiWBcUrGKEBS7dq3Sd2Z/cWsqbhuC6cXkSY7quHklHhqSVtXqOvBr8HRPEMn/rbW2PFYzXn7KhlXxG4ioNdplrOzbJWwfr54tauNY+UVWz4LnoK3ZTr8IHZrUNZ0aaxaQ2nfir58j4BIqOgp0Xp6ZbwGnrEhnrQS+xN2/TYSjjy9C1VBvhG2K6sZ7vEyFvqBGDFVB1HrPu/sXNVFoViGvJ4a
Date: Wed, 21 Aug 2013 17:44:32 -0000
Message-ID: <20130821174432.89957.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [spfbis] there is no transitiion, was Last Call: <draft-ietf-spfbis-4408bis-19.txt>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077525FC8E@mbx-01.win.nominum.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
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 17:45:01 -0000

>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.

This would require some reason why it is worth them spending time and
money to do something that has no operational benefit whatsoever.

If they start publishing type 99, something will break, because when
you change something in large systems, something always breaks.  Some
mail systems somewhere with bugs in type 99 handling that they never
noticed will start making mail fail.  For doing that, will anyone's
mail work better?  No.  Will their DNS work better?  No.

As I have mentioned a couple of times already, even though Yahoo
doesn't publish SPF (I believe due to political issues related to the
history of Domainkeys and DKIM), they do check SPF.  They used to
check both TXT and type 99, and stopped checking type 99.  What
argumment is there to spend money to revisit and reverse that
decision?

Arguments about DNS purity, and hypothetical arguments about other TXT
records that will never exist are unlikely to be persusasive.

R's,
John