Re: [apps-discuss] Updating the status of SPF

Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 11 August 2011 21:35 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DF2F21F8B7F for <apps-discuss@ietfa.amsl.com>; Thu, 11 Aug 2011 14:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level:
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599]
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 Y0USlwc0QKM2 for <apps-discuss@ietfa.amsl.com>; Thu, 11 Aug 2011 14:35:54 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 1816F21F8B7B for <apps-discuss@ietf.org>; Thu, 11 Aug 2011 14:35:54 -0700 (PDT)
Received: from shinkuro.com (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id B154C1ECB41D for <apps-discuss@ietf.org>; Thu, 11 Aug 2011 21:36:29 +0000 (UTC)
Date: Thu, 11 Aug 2011 17:36:26 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: apps-discuss@ietf.org
Message-ID: <20110811213626.GU95640@shinkuro.com>
References: <201108092337.39408.scott@kitterman.com> <F5833273385BB34F99288B3648C4F06F13512DF6CD@EXCH-C2.corp.cloudmark.com> <CAHhFybqGT8z8ZM7LUP2B7YTVKi-bPH37ZQN896en1DaEpsTTjA@mail.gmail.com> <201108111546.05901.scott@kitterman.com> <CAHhFybp3K8HQU7gmDqpQmv+HLiSy+J4EoEb=gTCwt3wZi6jgWA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAHhFybp3K8HQU7gmDqpQmv+HLiSy+J4EoEb=gTCwt3wZi6jgWA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [apps-discuss] Updating the status of SPF
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 21:35:55 -0000

On Thu, Aug 11, 2011 at 11:19:06PM +0200, Frank Ellermann wrote:
> 
> If you insist on it the WG should IMHO still be free to say whatever
> it likes to say about the type 99 DNS SPF RR; maybe kill it for good.

The plain fact is that once a DNS RRTYPE is allocated, it can't be
"killed".  You can deprecate its use and tell new software not to look
it up.  But the code point will remain assigned, I predict, until we
stop using the DNS (which, at the rate we are adding lard to spackle
to baling-wire, might be any day now, but that's a digression for
another list).

For the little it us no doubt worth, it is the "TXT is now used
everywhere, and so we're not going to deprecate that even in new
versions of the protocol, pppptttthhht" argument that annoys people
who see the problems with TXT records whenever they're overloaded in
yet another protocol.  In effect, once you adopt TXT, you're going to
use it forever.  This same attitude is why we still have A-record MX
fallback all these years later.

But I do agree that, if people are wedded to using their bad idea
forever, one isn't going to change their mind, and it is silly to have
two mechanisms for achieving the same goal one of which is never used
(particularly if it causes additional DNS load).

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com