[spfbis] Proposed spf TXT record change

"Roy A. Gilmore" <rag@ragged-software.com> Tue, 09 February 2016 23:33 UTC

Return-Path: <rag@ragged-software.com>
X-Original-To: spfbis@ietfa.amsl.com
Delivered-To: spfbis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 33A541B2E37 for <spfbis@ietfa.amsl.com>; Tue, 9 Feb 2016 15:33:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id pwT0D_FocmZ5 for <spfbis@ietfa.amsl.com>; Tue, 9 Feb 2016 15:33:49 -0800 (PST)
Received: from atl4mhob01.myregisteredsite.com (atl4mhob01.myregisteredsite.com []) by ietfa.amsl.com (Postfix) with ESMTP id C13161B2E35 for <spfbis@ietf.org>; Tue, 9 Feb 2016 15:33:49 -0800 (PST)
Received: from mailpod.hostingplatform.com ([]) by atl4mhob01.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u19NXmYT013510 for <spfbis@ietf.org>; Tue, 9 Feb 2016 18:33:48 -0500
Received: (qmail 11214 invoked by uid 0); 9 Feb 2016 23:33:48 -0000
X-Authenticated-UID: rag@ragged-software.com
Received: from unknown (HELO thor.internal.ragged-software.com) (rag@ragged-software.com@ by 0 with ESMTPA; 9 Feb 2016 23:33:48 -0000
To: spfbis@ietf.org
From: "Roy A. Gilmore" <rag@ragged-software.com>
X-Enigmail-Draft-Status: N1110
Organization: RAGged Software
Message-ID: <56BA775B.9050109@ragged-software.com>
Date: Tue, 9 Feb 2016 15:33:47 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/spfbis/cgk_bkf5ltyZuUzujsuGArHnYo4>
Subject: [spfbis] Proposed spf TXT record change
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SPFbis discussion list <spfbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spfbis>, <mailto:spfbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spfbis/>
List-Post: <mailto:spfbis@ietf.org>
List-Help: <mailto:spfbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spfbis>, <mailto:spfbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 00:10:28 -0000

I'm not sure how to go about this, but, I'll start here and maybe
somebody could point me in the right direction. I think placing the spf
information in a TXT record directly attached to the domain is a
mistake. I think the spf information should be placed in a TXT record
attached to a _spf selector (e.g. _spf.example.com). This behavior
already has a history of being used by other services (i.e.
_kerberos.example.com, _dmarc.example.com, etc.), and would make
retrieving the spf information much easier and much more robust. This
would also be a trivial change to implement. Any thoughts?