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

David Conrad <drc@virtualized.org> Tue, 20 August 2013 05:27 UTC

Return-Path: <drc@virtualized.org>
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 B45FF11E80FD for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 22:27:25 -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 DuGsTBYBI3G7 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 22:27:20 -0700 (PDT)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id B3AFD11E80F3 for <ietf@ietf.org>; Mon, 19 Aug 2013 22:27:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id E8D138712A; Tue, 20 Aug 2013 01:27:17 -0400 (EDT)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 01793-10; Tue, 20 Aug 2013 01:27:16 -0400 (EDT)
Received: from [10.0.1.6] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 32BF687128; Tue, 20 Aug 2013 01:27:14 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
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: David Conrad <drc@virtualized.org>
In-Reply-To: <m2siy56j0s.wl%randy@psg.com>
Date: Mon, 19 Aug 2013 22:27:12 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4FC3784-EA30-4927-A1D2-62B12E15196F@virtualized.org>
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org> <m2siy56j0s.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1508)
Cc: IETF Disgust <ietf@ietf.org>
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: Tue, 20 Aug 2013 05:27:26 -0000

On Aug 19, 2013, at 10:14 PM, Randy Bush <randy@psg.com> wrote:
> so, according to your message, one lesson i might take from this is, if
> i want to deploy a new hack which needs an rrtype, not to use txt in the
> interim.  i will be caught in a mess which will appear to be of my own
> making.  is that somewhat correct?

Not exactly. 

Given the situation at the time (specifically, the difficulty getting new RR types -- a problem since fixed), I believe the use of TXT was appropriate. Unfortunately, the migration strategy away from TXT was flawed. My personal belief is that the rationale to migrate away from TXT remains valid and the appropriate course of action is to fix the migration strategy, not permanently encode what everyone agrees is a hack into a proposed standard.

Regards,
-drc