Re: [dnsext] [spfbis] Obsoleting SPF RRTYPE

"Murray S. Kucherawy" <superuser@gmail.com> Fri, 26 April 2013 06:30 UTC

Return-Path: <superuser@gmail.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 11AB621F91A2; Thu, 25 Apr 2013 23:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level:
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 JxMwzbcy2enj; Thu, 25 Apr 2013 23:30:15 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) by ietfa.amsl.com (Postfix) with ESMTP id C854C21F91B7; Thu, 25 Apr 2013 23:30:14 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id hm14so213877wib.5 for <multiple recipients>; Thu, 25 Apr 2013 23:30:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=qkKxxbS61c+29IzFzh2ux1pgevJn908JuLVXQ7A2hXg=; b=MbUqrqf1wE9/nNlZ08qaiyjcKrz1Ndwz0Qr8hZ2dmQcRG+5IbUl1IWQEAkqTw4xWbD u5kBnRR8RIqoQ2U91XUEeXyJtKz9V4Z7Eobj/P6knOSTO2aQ4vOKC0hrSIwK2pDRQ4Xe OQdysmlAvMPJHktVyNF+oQm+GcyR75jluMFcp5+fv9MjpeZoYp/SsOoxn+nKD2dC0Bio lYjqjZFAAtLApnHZvkiL75CiXl0TWGaExJJKhDT6SSfSebTnzN0W74T6k3ouagymeJAc vMtFGNknpP4QG4XRjCb1NW0NxA5bxdMFgSbogGhHY0bpQd+5Vomxvyb7eZld6K+AQkIB /m+A==
MIME-Version: 1.0
X-Received: by 10.180.37.101 with SMTP id x5mr2317657wij.0.1366957813404; Thu, 25 Apr 2013 23:30:13 -0700 (PDT)
Received: by 10.180.36.176 with HTTP; Thu, 25 Apr 2013 23:30:13 -0700 (PDT)
In-Reply-To: <8CD461F5-2A96-4BC5-8934-1181CB134F7E@virtualized.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> <5179691B.50602@qti.qualcomm.com> <5179980F.9090606@dougbarton.us> <5179B10E.705@qti.qualcomm.com> <5179BC32.8050205@dougbarton.us> <CAL0qLwYzKnfRArQAVD1M=ccnV079j-D9PHDaB-tLaUwG4vm_BQ@mail.gmail.com> <8CD461F5-2A96-4BC5-8934-1181CB134F7E@virtualized.org>
Date: Thu, 25 Apr 2013 23:30:13 -0700
Message-ID: <CAL0qLwYHtYmCpLco86u5Loc1SuG9OpWyHZVPySZp8XOF2ypyxg@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: David Conrad <drc@virtualized.org>
Content-Type: multipart/alternative; boundary="e89a8f646ff3e4184a04db3daa27"
Cc: "spfbis@ietf.org" <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: Fri, 26 Apr 2013 06:30:16 -0000

On Thu, Apr 25, 2013 at 11:05 PM, David Conrad <drc@virtualized.org> wrote:

> > So how much energy are the DNS experts going to put into cleaning up
> their house while demanding the mail people clean up theirs?
>
> So, this is about revenge because it used to be hard to get RRtypes?
>

Did I really come across as that petty?

No, what I'm saying is that the way things were ten years ago pushed the
SPF community to the place it's in now, ugly as it is.  SPF, in the
interim, has become very widely deployed.  Suddenly now we have a few
voices from the ivory tower asserting that the same community needs to go
out and re-do things the way they should have been done in the first place,
now that we finally have a somewhat more reasonable perspective, even
though some of the vestiges of ten years ago are in fact still around.  My
reaction to that is "You can't be serious."  That doesn't sound like
revenge at all to me, just pragmatism.


> > The deployed SPF base probably won't give a damn if the IETF suddenly
> releases an RFC that exclaims "Everybody migrate to type 99!"
>
> Yep.  This gets into projections about the future.  If SPF has topped out,
> it simply doesn't matter.  If SPF is going to continue to grow, then it
> probably does matter.
>

I think it's much closer to the former.


> The point is that it isn't just fine.  It does have operational impacts,
> from potentially increased fragmentation/fallback to TCP to increased
> complexity in TXT RR parsers that have to distinguish between the myriad of
> crap that's residing at the zone apex TXT RR, etc.  Of course, most of
> these negative impacts are hidden to the folks who are putting the TXT RRs
> in the zone, so it's all good, right?
>
> > Thus, I maintain that we take our licks on this one and just take steps
> to ensure that nobody follows this path again.
>
> And how do you propose that exactly, particularly given the precedent set
> by SPFBIS?
>

Someone else (Joe, I think) has already referred to other RFCs that talk
about things like IAB advice about how [not] to put application data into
the DNS.  Seems to me this is a perfectly good subject for another such
project.  One may counter that by saying nobody will pay attention to such
a document, but I submit that it's our primary mechanism for making sure
mistakes aren't re-made, so that's the tool we have to use or not use.

If we do the opposite and somehow compel SPFBIS to favour type 99 over TXT,
then I still think we'll be shouting that to an audience that will think
we're nuts and simply go about their business.

-MSK