Re: [dnsext] SPF, a cautionary tale

"Murray S. Kucherawy" <superuser@gmail.com> Mon, 06 May 2013 14:04 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 61C7621F9154 for <dnsext@ietfa.amsl.com>; Mon, 6 May 2013 07:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.379
X-Spam-Level:
X-Spam-Status: No, score=-2.379 tagged_above=-999 required=5 tests=[AWL=0.220, 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 Tr2DSXcEJ-Kn for <dnsext@ietfa.amsl.com>; Mon, 6 May 2013 07:04:24 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id A09A221F9223 for <dnsext@ietf.org>; Mon, 6 May 2013 07:04:17 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id c11so3586035wgh.22 for <dnsext@ietf.org>; Mon, 06 May 2013 07:04:16 -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=HCZ4YYVy6jZrIizPEBaZcJqkU4LYyzaKk1PGQtLwREE=; b=FYut/5NpPg2bCu/qabWlQCN0Q8N6r5/SrPKIpPaKTU+Fl1NRuTSRLBkJbeHpRb+Pmc PyyeQNEuPXGbC4Q9196QJ+DmrJTE9UAxPLzV0Z6mjAtC2RiSYQBuGRjbi82aKlfBh4+9 EROAV0jBKAEbtMIux4jXKTsLzYCeH9FWN5gF/Hi0Im47QzVKQXy5mzfnfTgsT2hBpr5X 1yEEoYNs590FUznS08n11GSpVt48kSO9FhnoYqd9nRFFJomfTU/OdiUuMZ68xDAcqwwG 2/tkYRDiEwSY852vriSqUilNCZuFWbYVgine86C1N3ciSl6Lmi7Pepv3LaYZQsg1Sm/x dyVw==
MIME-Version: 1.0
X-Received: by 10.195.12.228 with SMTP id et4mr20875834wjd.59.1367849056809; Mon, 06 May 2013 07:04:16 -0700 (PDT)
Received: by 10.180.14.34 with HTTP; Mon, 6 May 2013 07:04:16 -0700 (PDT)
In-Reply-To: <5187a8f9.852acd0a.12c2.7d46SMTPIN_ADDED_BROKEN@mx.google.com>
References: <8D23D4052ABE7A4490E77B1A012B63077516EA82@mbx-01.win.nominum.com> <20130503171843.39672.qmail@joyce.lan> <20130504133312.GA27772@vacation.karoshi.com.> <alpine.BSF.2.00.1305041103360.8602@joyce.lan> <20130505012216.GA29079@vacation.karoshi.com.> <alpine.BSF.2.00.1305042223280.10848@joyce.lan> <20130505032549.GA30757@vacation.karoshi.com.> <alpine.BSF.2.00.1305042327490.11044@joyce.lan> <51861e2f.62a3420a.11ed.ffffc5c1SMTPIN_ADDED_BROKEN@mx.google.com> <CAL0qLwY2t3Hgb85yOuqhNLRW5rcZkMt5dKNoWnLmSkKES391Ug@mail.gmail.com> <5187a8f9.852acd0a.12c2.7d46SMTPIN_ADDED_BROKEN@mx.google.com>
Date: Mon, 06 May 2013 07:04:16 -0700
Message-ID: <CAL0qLwZyggdyf_k1--m=tFGqM3kt01wJocQRBwkRXLNmqZiOsg@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: bmanning@vacation.karoshi.com
Content-Type: multipart/alternative; boundary="047d7bb04ad8233d1a04dc0d2dca"
Cc: "dnsext@ietf.org Group" <dnsext@ietf.org>
Subject: Re: [dnsext] SPF, a cautionary tale
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: Mon, 06 May 2013 14:04:25 -0000

On Mon, May 6, 2013 at 5:58 AM, <bmanning@vacation.karoshi.com> wrote:

>         there is this wonderful thing called "O'Dells Law" which,
> paraphrased
>         is:  "The installed based doesn't matter".   However, there is
> nothing
>         preventing the SPF community from using TXT to store thier
> particularly
>         unique stuff.  But there can be zero whining when other folks use
> TXT for
>         their own purposes and confuse the heck out of SPF processors
> which get
>         (for thier purposes) malformed SPF data...
>

Numerous such cases exist (I gave ut.edu as an example) and nobody is doing
any of the aforementioned whining.  Establishing a loop across a set of
strings looking for the one that starts "v=spf1" is hardly rocket science.
If that's the primary concern, I think we're good to go from here.

-MSK