Re: [dnsext] Obsoleting SPF RRTYPE

"John Levine" <johnl@taugh.com> Fri, 26 April 2013 21:50 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67C9D21F9CF2 for <dnsext@ietfa.amsl.com>; Fri, 26 Apr 2013 14:50:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.766
X-Spam-Level:
X-Spam-Status: No, score=-110.766 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, 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 L7h05muB1Z5A for <dnsext@ietfa.amsl.com>; Fri, 26 Apr 2013 14:50:30 -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 ED97E21F9CEB for <dnsext@ietf.org>; Fri, 26 Apr 2013 14:50:29 -0700 (PDT)
Received: (qmail 66223 invoked from network); 26 Apr 2013 21:50:18 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 26 Apr 2013 21:50:18 -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=517af69a.xn--9vv.k1304; i=johnl@user.iecc.com; bh=ZcVqatb2TCZAK9E3ws8ik9HGGUlAqAVeociILZzCuF0=; b=b6slyj2eqpDazQrLYjfeJ4BGT+XukWhAWZZK/pBoL7UWp7FlSenw19xs/rn4CpqZyi8HPq+1Q2K5vlcyIIM/0TXmTEqx38lLK1Rx2uEVDOtXzjlmy02+MsYLDyYKXf6HwzA6KgOGG5UPgYRZuW+EfHckSMP7BM3qIOEiEAYnjbY=
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=517af69a.xn--9vv.k1304; olt=johnl@user.iecc.com; bh=ZcVqatb2TCZAK9E3ws8ik9HGGUlAqAVeociILZzCuF0=; b=1QCd0pIuUG3HKGuZMB2z1iszC3m5rsJ4YawxntUxBPWbcTrM0OROEDmkekJu6OasxR6yRYfIeXZclCG7IEmIIbjZfv/lqa2EZGHyUPEvSEPPRKoR8RNkJ4x7uOGOCH7PnmQZMJKHRAYABmw9DSmgP2WsBvDFjvFRHnlr590XDZQ=
Date: Fri, 26 Apr 2013 21:49:56 -0000
Message-ID: <20130426214956.75110.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: dnsext@ietf.org
In-Reply-To: <8CD461F5-2A96-4BC5-8934-1181CB134F7E@virtualized.org>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 7bit
Subject: Re: [dnsext] Obsoleting SPF RRTYPE
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2013 21:50:31 -0000

>Well, deprecating the SPF RR will certainly teach the DNSEXT/IESG/IETF community a good lesson.  (Seriously?)

This may come as a surprise, but this isn't all about you.  

The spfbis group is cleaning up a protocol that is in use at hundreds
of thousands of mail systems all over the world including most,
probably all, of the largest ones.  For all its warts, SPF works fine
as is, and they have no incentive to change.  Hence the narrow charter
of the group only to clean up the existing spec, not to extend or
change it.

I go to a industry meetings like MAAWG with all of the large mail
operators, and I can assure you that if the IETF were so silly as to
publish an spfbis that demanded a switch to type 99, the large mail
systems would say, wow, that was dumb, I guess we'll be looking for
mail standards somewhere else.

>> Thus, I maintain that we take our licks on this one and just take steps to ensure that nobody follows
>this path again.
>
>And how do you propose that exactly, particularly given the precedent set by SPFBIS?

Provide the tools and processes so that people can use new RRTYPEs in
new designs.  (Insert usual point about provisioning.)

Don't shoot yourself in the foot by demanding that we break one that's
a decade old and likely in wider use than 95% of all of the other IETF
protocols.

R's,
John