Re: [dnsext] [spfbis] Obsoleting SPF RRTYPE

Pete Resnick <presnick@qti.qualcomm.com> Thu, 25 April 2013 17:34 UTC

Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35B6521F881C; Thu, 25 Apr 2013 10:34:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.293
X-Spam-Level:
X-Spam-Status: No, score=-102.293 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 CjG0ob3fpVOH; Thu, 25 Apr 2013 10:34:27 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id EF07121F84B7; Thu, 25 Apr 2013 10:34:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1366911263; x=1398447263; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=UUj3Q3VaadkoiSop6s1H9kEW06YTCTIgMEyBMHqTIjE=; b=r9E2V+qST9RvAduSI3DVAFO25+L9s47EwftX0U6MHCs5RAmMa9Az99Fd 0qqBdLuFq0bCbG6QDBUGUS5vft0HxjlMFFXcxykRfZHKXp0QviqE8fH3Y 6pJ5ZlpcIr6+2uCB8i9Mi/FD8Te9q4X+8PBK9QomR3dSCViE9SCLdTSDm E=;
X-IronPort-AV: E=Sophos;i="4.87,551,1363158000"; d="scan'208";a="36633237"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth01.qualcomm.com with ESMTP; 25 Apr 2013 10:34:21 -0700
X-IronPort-AV: E=Sophos;i="4.87,551,1363158000"; d="scan'208";a="438587763"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 25 Apr 2013 10:34:21 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.318.4; Thu, 25 Apr 2013 10:34:21 -0700
Message-ID: <5179691B.50602@qti.qualcomm.com>
Date: Thu, 25 Apr 2013 12:34:19 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Måns Nilsson <mansaxel@besserwisser.org>
References: <20130425013317.36729.qmail@joyce.lan> <80ADB3EE-17FD-4628-B818-801CB71BCBFE@virtualized.org> <BB8C643A-FC46-4B2F-B677-F1B7CAB0E79F@frobbit.se> <alpine.BSF.2.00.1304251030380.65043@joyce.lan> <14A728AE-83DC-4C1F-A88A-6F988D37F2C7@frobbit.se> <20130425154235.GP23770@besserwisser.org>
In-Reply-To: <20130425154235.GP23770@besserwisser.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [172.30.39.5]
Cc: spfbis@ietf.org, "dnsext@ietf.org Group" <dnsext@ietf.org>
Subject: Re: [dnsext] [spfbis] Obsoleting SPF RRTYPE
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2013 17:34:28 -0000

On 4/25/13 10:42 AM, Måns Nilsson wrote:
> And IMNSHO spfbis is out of scope prescribing TXT records, just because
> of this contagiousness.
>
> For the record: I think that the spfbis draft is unfit for publication
> as RFC unless TXT records are deprectaed as only carrier of data.
>    

SPFBIS AD hat on for this:

We are *long* past this discussion. This discussion should have happened 
at SPFBIS *chartering* time, as it is crystal clear from the charter 
that existing features currently in use in SPF are not going away. 
Indeed, the TXT record was specifically mentioned in the charter.

I certainly have the same heartburn as everyone else about having used 
TXT in this manner, but that ship has long sailed. This is running and 
interoperable code and it is being documented on the standards track. 
Unless you think there is a piece of information I missed in my 
assessment that we had consensus to go forward with this work in the 
first place, you are going to have a hard time convincing me that this 
is not in the rough part of the consensus now.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478