Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard

Scott Kitterman <scott@kitterman.com> Wed, 21 August 2013 23:07 UTC

Return-Path: <scott@kitterman.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 41C9321F8C7C for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 16:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 IKfUlCGTMsD9 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 16:07:37 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) by ietfa.amsl.com (Postfix) with ESMTP id AF44321F8C65 for <ietf@ietf.org>; Wed, 21 Aug 2013 16:07:25 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id D3E27D04085; Wed, 21 Aug 2013 19:07:23 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377126443; bh=+dBoUx2Wd6GRsP15rGG6hQtu0o1FqVvuIRMb+17sQjk=; h=In-Reply-To:References:Subject:From:Date:To:From; b=jwG0Q4Z58sk8AaDaijgYvY4NoohDrTuyqryhFJy21+ciXByRQZh6x57opZU1Xcy5t 5eyY6Ej74IPBs8nAUUIzo6lndR0VrD1ax5sDqiG7HxMZZIx4Ft2xB6YOANfucFABr6 4W66iGC8NASe5z4TaYdQ1VEEHX3M88WRLGpXMEwM=
Received: from [IPV6:2600:1003:b10f:dd68:4953:6750:ff67:6451] (unknown [IPv6:2600:1003:b10f:dd68:4953:6750:ff67:6451]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 4DF5ED0405B; Wed, 21 Aug 2013 19:07:22 -0400 (EDT)
User-Agent: K-9 Mail for Android
In-Reply-To: <20130821222514.A617138C05EC@drugs.dv.isc.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <13637683.gDTVOaM8nE@scott-latitude-e6320> <20130821133233.D0A6B38BE02F@drugs.dv.isc.org> <7917527.VmCQD3a6Q3@scott-latitude-e6320> <20130821214832.1C92538C0230@drugs.dv.isc.org> <20130821222514.A617138C05EC@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: Scott Kitterman <scott@kitterman.com>
Date: Wed, 21 Aug 2013 19:07:25 -0400
To: ietf@ietf.org
Message-ID: <0c3746c3-dac1-471f-bd07-8faf20481337@email.android.com>
X-AV-Checked: ClamAV using ClamSMTP
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 23:07:38 -0000

Mark Andrews <marka@isc.org> wrote:
>
>In message <20130821214832.1C92538C0230@drugs.dv.isc.org>, Mark Andrews
>writes:
>> > It's primarily an issue for applications.  To the DNS, it's exactly
>what it 
>> > is, a TXT record.
>
>I can hand update of A and AAAA records to the machine.
>I can hand update of MX records to the mail adminstrator.
>I can hand update of SPF records to the mail adminstrator.
>I can hand update of TXT records to ??????

No one because it has multiple uses.  This is true whether SPF exists or not.  SPF use of RRTYPE TXT for SPF records makes that neither better nor worse.

You could publish:

example.com IN TXT v=spf1 redirect=_spf.example.com
_spf.example. com IN TXT v=spf1 [actual content here]

Then delegate _spf.example.com to the mail administrator.  Problem solved.

Scott K