Re: [spfbis] WGLC: draft-ietf-spfbis-4408bis-14 - Fully parse record *first*

Alessandro Vesely <vesely@tana.it> Tue, 23 April 2013 07:59 UTC

Return-Path: <vesely@tana.it>
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 BC48821F8771 for <spfbis@ietfa.amsl.com>; Tue, 23 Apr 2013 00:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level:
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
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 WrBNBWHGJDd5 for <spfbis@ietfa.amsl.com>; Tue, 23 Apr 2013 00:59:26 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 1897E21F871C for <spfbis@ietf.org>; Tue, 23 Apr 2013 00:59:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1366703965; bh=/XSghUWbRIYcbHeM7eWYY3/WBNU9C1uxDU2ZWRApq+0=; l=1512; h=Date:From:To:References:In-Reply-To; b=a5kRX0r1PLX51G4NTLsQeIRG4f7rjsi75W8YrrTZfa+ubVyNV5AypuQc1RWjqSrZF UvbI34jTD1aNmXOr+lfXT0wk1hoqoNHMWDocet6a/wu7a+tuIPgY3gj0r4rDUx5wDV Bs9BPmC+MD+otcPN26lQyE3je/7FZHYHsUt47e6Q=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.101] (pcale.tana [172.25.197.101]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Tue, 23 Apr 2013 09:59:25 +0200 id 00000000005DC039.0000000051763F5D.00002926
Message-ID: <51763F5D.3080004@tana.it>
Date: Tue, 23 Apr 2013 09:59:25 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: spfbis@ietf.org
References: <20130409062431.GK24624@mx1.yitter.info> <1890223.gRaPZiil6c@scott-latitude-e6320> <51756764.6030104@tana.it> <2528747.v4GPD3HTbD@scott-latitude-e6320>
In-Reply-To: <2528747.v4GPD3HTbD@scott-latitude-e6320>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: [spfbis] WGLC: draft-ietf-spfbis-4408bis-14 - Fully parse record *first*
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: Tue, 23 Apr 2013 07:59:26 -0000

On Mon 22/Apr/2013 19:18:58 +0200 Scott Kitterman wrote:
> On Monday, April 22, 2013 06:37:56 PM Alessandro Vesely wrote:
>> On Mon 22/Apr/2013 18:06:41 +0200 Scott Kitterman wrote:
>>> On Monday, April 22, 2013 05:48:33 PM Alessandro Vesely wrote:
>>>> On Mon 22/Apr/2013 16:04:11 +0200 Scott Kitterman wrote:
>>>>>> Mechanisms after "all" will never be tested.  Mechanisms listed after
>>>>>> "all" MUST be ignored.
>>>>> 
>>>>> Perhaps if we combine those it helps:
>>>>>> Mechanisms after "all" MUST not be tested.  Mechanisms listed after
>>>>>> "all" will be ignored for all purposes except syntax error evaluation.
>>>>> 
>>>>> Does that help?
>>>> 
>>>> Nope, IMHO it's better as is now.  That is:
>>>> 
>>>> CURRENT
>>>> 
>>>>    If there are any syntax errors
>>>> 
>>>> EQUIVALENT-FROM-A-PRAGMATIC-POV
>>>> 
>>>>    If any syntax errors are found
>>>>    
>>>>    anywhere in the record, check_host() returns immediately with the
>>>>    result "permerror", without further interpretation.
>>>> 
>>>> See also http://tools.ietf.org/wg/spfbis/trac/ticket/26
>>>> and http://www.ietf.org/mail-archive/web/spfbis/current/msg02765.html
>>> 
>>> Right, but how can you find a syntax error in something you MUST ignore?
>> 
>> You have to parse it anyway, as it might be a modifier, e.g.
>> 
>>    "v=spf1 a -all ra=rfc6652"
> 
> That's true, but as soon as I determine it's a mechanism, I ignore it, so the 
> ambiguity still exists.

If you determine it's a valid something, there's no syntax error.