IETF Logo Mail Archive

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

Dave Crocker <dhc@dcrocker.net> Tue, 20 August 2013 05:22 UTC

Return-Path: <dhc@dcrocker.net>
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 468B011E8163 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 22:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.577
X-Spam-Level:
X-Spam-Status: No, score=-6.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 gHWXI7uDCqOe for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 22:22:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4C5E511E8101 for <ietf@ietf.org>; Mon, 19 Aug 2013 22:22:22 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7K5MHv9016468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 19 Aug 2013 22:22:21 -0700
Message-ID: <5212FCEF.80701@dcrocker.net>
Date: Mon, 19 Aug 2013 22:21:51 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
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
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org> <m2siy56j0s.wl%randy@psg.com>
In-Reply-To: <m2siy56j0s.wl%randy@psg.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 19 Aug 2013 22:22:21 -0700 (PDT)
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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:22:27 -0000

On 8/19/2013 10:14 PM, Randy Bush 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?


Whether it's what he meant, it's not the correct lesson.  There are 
probably two realistic lessons:

      The first is that there now a number of other apps using TXT 
records, with no problems, because they are stored under scoping nodes 
(underscore-prefaced names).  This approach might be aesthetically 
displeasing, but it works just fine.

      The second is that, unfortunately, deploying a new RR that gains 
widespread, end-to-end support remains problematic, assurances to the 
contrary notwithstanding.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email