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 16:54 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 3269E11E8123 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 09:54:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level:
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062, 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 1rzFVYbwW5xK for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 09:54:17 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id B9CDD21F9BC3 for <ietf@ietf.org>; Wed, 21 Aug 2013 09:54:15 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 2DADC20E40FD; Wed, 21 Aug 2013 12:54:13 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377104053; bh=vpHZgcx1YgzsgWHNbkjkyidz5z6R/IhDnRLy4nBGiBI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Jck746uYn+cMNFx/USjWyVdPXka/Qzk3YZMY4XMQkM7xE6yDy/tRLpV1Q1FHC+oE/ FdWekUFgnEkXT0UqkA6VXlHzUSay3HpH1gq9r7AUDG+4ziChmvB6jxhXPBigJzKrej 4S8Zmdq/iYMDGmQJoNCvqD0w1NVm41bkF2B7BvGE=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id DB3E520E40C2; Wed, 21 Aug 2013 12:54:12 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
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
Date: Wed, 21 Aug 2013 12:54:11 -0400
Message-ID: <2298307.uzZxXYiUrK@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-29-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <20130821133928.GA27579@crankycanuck.ca>
References: <20130819150521.GB21088@besserwisser.org> <521495EB.7060207@cisco.com> <20130821133928.GA27579@crankycanuck.ca>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
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 16:54:37 -0000

On Wednesday, August 21, 2013 09:39:28 Andrew Sullivan wrote:
...
> >   * To what extent has that happened?
> 
> I'm not the shepherd, but it is undeniable that most current-era
> shipping DNS servers support RRTYPE 99.

The operational issues I've encountered with actually trying to use RRTYPE99 
in the wild weren't caused by a lack of support in current-era shipping DNS 
servers.  Sometimes it's not even anything directly related to the DNS.  I 
recall cases where it appeared that firewalls were the root of the problem (I 
don't recall details, sorry).  Solving the DNS servers must support unknown 
RRTYPE/SPF type problem only gets you started.

Scott K