Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard

Patrik Fältström <paf@frobbit.se> Tue, 20 August 2013 07:43 UTC

Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39EE421F9D55 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 00:43:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, MIME_8BIT_HEADER=0.3, 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 6-kbm3m0fZmd for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 00:43:20 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id BA00221F9C22 for <ietf@ietf.org>; Tue, 20 Aug 2013 00:43:20 -0700 (PDT)
Received: from [IPv6:2a01:3f0:1::85d3:8d58:735a:e251] (unknown [IPv6:2a01:3f0:1:0:85d3:8d58:735a:e251]) by mail.frobbit.se (Postfix) with ESMTPSA id 597C621F7E; Tue, 20 Aug 2013 09:43:19 +0200 (CEST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: Patrik Fältström <paf@frobbit.se>
In-Reply-To: <5213174D.7080504@dcrocker.net>
Date: Tue, 20 Aug 2013 09:43:18 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D2148A40-2673-40C7-8349-0A65D0D01794@frobbit.se>
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org> <m2siy56j0s.wl%randy@psg.com> <5212FCEF.80701@dcrocker.net> <55459829-933F-4157-893A-F90552D4441A@frobbit.se> <5213174D.7080504@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1508)
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 07:43:21 -0000

On 20 aug 2013, at 09:14, Dave Crocker <dhc@dcrocker.net> wrote:

> On 8/19/2013 11:33 PM, Patrik Fältström wrote:
>> Reason for this is that the RR with an underscored prefix MIGHT end up in a different zone than the record without.
> 
> Patrik,
> 
> Please clarify.  I don't know what you mean by the 'with' and 'without' references.

The two following records MUST be in the same zone:

foo.example. IN X RDATAX
foo.example. IN Y RDATAY

The two following MIGHT NOT be in the same zone:

foo.example. IN X RDATAX
_bar.foo.example. IN TXT RDATAY

> And as long as I'm asking for more explanation, given the number of years of use the construct has had and for the number of different applications, where has the problem (whatever you mean specifically) been seen?

When using DNSSEC if the _bar.foo.example record in the 2nd example above is unsigned, while the foo.example in the first example is.

   Patrik