IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Mon, 22 April 2013 14:54 UTC

Return-Path: <johnl@iecc.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 840BF21F8BDE for <spfbis@ietfa.amsl.com>; Mon, 22 Apr 2013 07:54:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level:
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, 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 bW5ZF4fZ29Gf for <spfbis@ietfa.amsl.com>; Mon, 22 Apr 2013 07:54:51 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id A62C421F8EE1 for <spfbis@ietf.org>; Mon, 22 Apr 2013 07:54:50 -0700 (PDT)
Received: (qmail 59406 invoked from network); 22 Apr 2013 14:56:31 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 22 Apr 2013 14:56:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51754f37.xn--yuvv84g.k1304; i=johnl@user.iecc.com; bh=6/F7jXQcTdrWvMGAUxmDnqDrHSsm9kFLRiwZ9EIOZBY=; b=Ex3XQmi07YZKndlne67Mhm06AnCCV76qTqMWVK4Ffj6AC74nmoqbbPmPXc9lzA51EFm7XPSYW5ah80xLAvWKMuOBtXGHy8TwPBCQfI3jKDQZTObSxEtEeAPzxS3JyLERlko5vLlWdA+jo2h9MUQ7VaN9QaT0HDXNhkBBbcZFxuY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51754f37.xn--yuvv84g.k1304; olt=johnl@user.iecc.com; bh=6/F7jXQcTdrWvMGAUxmDnqDrHSsm9kFLRiwZ9EIOZBY=; b=lvQvEAK/lOl+dz/HSq4UhotFtSTpcHaaWPlDtqIPrbaY2AXfg5B2snURxk6Fr6B6c0w9KsLRaWpZgTU+RWCYGFkCsrODL+EOVYzCDeZIlx1JcwdruQYIe+5Pd+jRjc/3p0r3AOlEYII1gjs+8xzesl+CZ/nTP+z5H7XvmxNvJjM=
Date: Mon, 22 Apr 2013 14:54:25 -0000
Message-ID: <20130422145425.18526.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: spfbis@ietf.org
In-Reply-To: <CABuGu1pebsfi+1JHRYoOmm1Q3xft2paOGi3zwXbxHjbR3tmnKw@mail.gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 7bit
Cc: kboth@drkurt.com
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: Mon, 22 Apr 2013 14:54:51 -0000

In article <CABuGu1pebsfi+1JHRYoOmm1Q3xft2paOGi3zwXbxHjbR3tmnKw@mail.gmail.com> you write:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>That leaves the ambiguity of handling -all in embedded (include:) records.
>What should be done if the sample foobar mechanism is being referenced in
>an included record?

At this point, I think we have to say that stuff like that is
undefined, since in reality it does whatever the code does, and it
happens so rarely that nobody cares.

Remember that a standard needs to tell people what to do to interoperate, but
it doesn't have to tell you want to do if someone else screws up.

R's,
John

v2.23.0 | Report a Bug | By Email