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

"Murray S. Kucherawy" <msk@cloudmark.com> Thu, 11 August 2011 21:40 UTC

Return-Path: <msk@cloudmark.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 1C78111E8081 for <apps-discuss@ietfa.amsl.com>; Thu, 11 Aug 2011 14:40:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.572
X-Spam-Level:
X-Spam-Status: No, score=-103.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 JYKxU5KoL7Ef for <apps-discuss@ietfa.amsl.com>; Thu, 11 Aug 2011 14:40:27 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA5311E8080 for <apps-discuss@ietf.org>; Thu, 11 Aug 2011 14:40:27 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Thu, 11 Aug 2011 14:41:02 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Date: Thu, 11 Aug 2011 14:41:01 -0700
Thread-Topic: [apps-discuss] Updating the status of SPF
Thread-Index: AcxYbr1GpxWkEhFZR/C/pybU32EaRQAACh9g
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF6DC@EXCH-C2.corp.cloudmark.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> <20110811213626.GU95640@shinkuro.com>
In-Reply-To: <20110811213626.GU95640@shinkuro.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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:40:28 -0000

> -----Original Message-----
> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Andrew Sullivan
> Sent: Thursday, August 11, 2011 2:36 PM
> To: apps-discuss@ietf.org
> Subject: Re: [apps-discuss] Updating the status of SPF
> 
> This same attitude is why we still have A-record MX
> fallback all these years later.

This is the first time I've heard someone lament that old RFC974 provision.  I'll have to ask you to elaborate someday.

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

I'm viewing this more and more as something we should handle the same as a PS-DS promotion; do an interoperability report (in this case, about "the experiment"), remove unused stuff, generally tidy up, resolve errata, and allow nothing else.

That SPF used TXT the way it did may be unfortunate, but as you said, we're not going to change it.  We should document the discussion and the results of years of deployment, hold our noses and live with it.  I'd also be fine with including verbose admonitions to future protocol designers NOT to use this as an example of possible TXT use in future protocols.