Re: [dnsext] [spfbis] Obsoleting SPF RRTYPE

Warren Kumari <warren@kumari.net> Thu, 25 April 2013 18:16 UTC

Return-Path: <warren@kumari.net>
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 91F3721F9642; Thu, 25 Apr 2013 11:16:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.368
X-Spam-Level:
X-Spam-Status: No, score=-102.368 tagged_above=-999 required=5 tests=[AWL=0.231, BAYES_00=-2.599, 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 93XLqTskaQbR; Thu, 25 Apr 2013 11:16:19 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B25821F9692; Thu, 25 Apr 2013 11:16:18 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.117]) by vimes.kumari.net (Postfix) with ESMTPSA id 7DA0F1B405F4; Thu, 25 Apr 2013 14:16:17 -0400 (EDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <4F78BF49-73D6-4716-A3AA-CA94FA3BD310@kumari.net>
Date: Thu, 25 Apr 2013 14:16:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <83A5592A-44F5-40AD-BA2C-05A5F0EBD100@kumari.net>
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> <5179691B.50602@qti.qualcomm.com> <4F78BF49-73D6-4716-A3AA-CA94FA3BD310@kumari.net>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1503)
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 18:16:20 -0000

[ Whee, replying to my own message. Always a good sign…] 
On Apr 25, 2013, at 2:03 PM, Warren Kumari <warren@kumari.net> wrote:

> 
> On Apr 25, 2013, at 1:34 PM, Pete Resnick <presnick@qti.qualcomm.com> wrote:
> 
>> 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.
> 
> I would also recommend that folk actually go and read RFC6686 [0] - I know that having actual measurements interferes with one's ability to have a fun little rant, but, if you do, maybe you can avoid looking silly (like I did with the RFC5507 discussion :-)).
> 
> Maybe stuffing stuff in a TXT record was a poor decision. Maybe it wasn't. There are heaps more SPF in TXT than SPF in SPF, kvetcing won't change that, and I'm sure we can find something else more fun to kvetch about…
> 

Ever have one of those days when you just wake up ornery? Those are probably the days when you shouldn't be responding to mail (or interacting with people at all) :-P

W


> 
> W
> 
> [0]: Yes, I know finding the documents can be hard. Here is a link: http://tools.ietf.org/html/rfc6686
> 
> 
> 
>> pr
>> 
>> -- 
>> Pete Resnick<http://www.qualcomm.com/~presnick/>
>> Qualcomm Technologies, Inc. - +1 (858)651-4478
>> 
>> _______________________________________________
>> dnsext mailing list
>> dnsext@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsext
>> 
> 
> --
> "When it comes to glittering objects, wizards have all the taste and self-control of a deranged magpie."
> -- Terry Pratchett
> 
> 
> 
> 

-- 
A. No
Q. Is it sensible to top-post?