Re: [spfbis] Revisit: Issue #36: RFC 2119 key words
Scott Kitterman <spf2@kitterman.com> Sat, 09 February 2013 00:51 UTC
Return-Path: <spf2@kitterman.com>
X-Original-To: spfbis@ietfa.amsl.com
Delivered-To: spfbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD3FC21F8C3E for <spfbis@ietfa.amsl.com>; Fri, 8 Feb 2013 16:51:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level:
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RRCQKkXA3SrA for <spfbis@ietfa.amsl.com>; Fri, 8 Feb 2013 16:51:25 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 2779621F8C32 for <spfbis@ietf.org>; Fri, 8 Feb 2013 16:51:25 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id A26D520E40C9; Fri, 8 Feb 2013 19:51:24 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1360371084; bh=nCM2NFB+Rgc/51EDMkEP/wzDWwrh7m3T/HvGoBZ6lwY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Ri+rCg019DsmRzfFKnkNfh2duBt4B3TR9StmmazatHaln6bcuFbjNKqAgZNdI+IIS tdu+h95rTjOmjttUhdMy2RKkAxdhRUL9rw7gUTrLRmPBHKJ5Y1PeXtoHZIgMyL8wkS ub5Tr3lXAuexDA1jd+qHOx0fCKbRKCd3eQ6kSAd4=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 849E020E40BE; Fri, 8 Feb 2013 19:51:24 -0500 (EST)
From: Scott Kitterman <spf2@kitterman.com>
To: "spfbis@ietf.org" <spfbis@ietf.org>
Date: Fri, 08 Feb 2013 19:51:23 -0500
Message-ID: <3176279.ZD4dlLcq5n@scott-latitude-e6320>
User-Agent: KMail/4.9.4 (Linux/3.5.0-23-generic; KDE/4.9.4; i686; ; )
In-Reply-To: <CAC4RtVCay_FdzdUS9fo0E=rmwXeFHQDsaJ1UFvm=Y-CuDfuxWQ@mail.gmail.com>
References: <CAL0qLwYvJaZ2NZV+xUkCSfbm6Wsy=4AkEGLqkNOxQrwdaUQqfg@mail.gmail.com> <21604708.4WkHlj1qTs@scott-latitude-e6320> <CAC4RtVCay_FdzdUS9fo0E=rmwXeFHQDsaJ1UFvm=Y-CuDfuxWQ@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
Subject: Re: [spfbis] Revisit: Issue #36: RFC 2119 key words
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SPFbis discussion list <spfbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spfbis>, <mailto:spfbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spfbis>
List-Post: <mailto:spfbis@ietf.org>
List-Help: <mailto:spfbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spfbis>, <mailto:spfbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 00:51:25 -0000
On Friday, February 08, 2013 04:57:05 PM Barry Leiba wrote: > >> -- Section 4.6.4 -- > >> In the second paragraph, why are you mixing "MX resource records" in > >> the first sentence with "A resource records" in the second sentence? > >> Is this a typo, or intentional? If it's intentional, I would re-word > >> it, which will probably correct the odd "MUST". > > > > What I was trying to communicate there is something like the following > > > > sequence: > > - Do mx lookup for the domain. > > - One or more a records returned > > - If the number of a records is =< 10, then do a lookups to find the > >relevant> > > IP addresses > > > > - If the number of a records is > 10, don't do any lookups and return a > > > > permerror. > > > > When I look at it, I think it says that, but obviously it's not clear. > > Wording suggestions appreciated. > > Right, but you start by talking about how many MX lookups there are. > What you say in your explanation above is that there's one, and the > issue is how many A records that expands to. > > As written, it seems to say that you can do up to 10 MX lookups, and > each of those can result in up to 10 A lookups, for a total of 110 DNS > lookups. Is that what you mean? Yes. This is the basis for the infamous 111 DNS lookups. > Are you trying to limit the total number of lookups in an SPF-record > evaluation? Or just the total number from any one clause? For a single term (clause). > Maybe this is enough to help you with wording... or maybe when you > answer the questions above, I can take a stab. Please do. Scott K
- [spfbis] Revisit: Issue #36: RFC 2119 key words Murray S. Kucherawy
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Scott Kitterman
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Barry Leiba
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Scott Kitterman
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… SM
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Scott Kitterman
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Barry Leiba
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… SM
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Scott Kitterman
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Scott Kitterman
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Barry Leiba
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… SM
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Scott Kitterman
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Scott Kitterman
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… SM
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… S Moonesamy
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Alessandro Vesely
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Scott Kitterman
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Scott Kitterman
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Barry Leiba
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Scott Kitterman
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… SM
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Scott Kitterman
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Scott Kitterman
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Scott Kitterman
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Alessandro Vesely
- Re: [spfbis] Revisit: Issue #36: RFC 2119 key wor… Murray S. Kucherawy