Re: [secdir] [spfbis] SECDIR Review of draft-ietf-spfbis-4408bis-19

Dave Crocker <dhc@dcrocker.net> Wed, 11 September 2013 14:51 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D715621E80B6; Wed, 11 Sep 2013 07:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 7L+pAmVMZyHg; Wed, 11 Sep 2013 07:51:36 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7E6F521F9EE9; Wed, 11 Sep 2013 07:51:36 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r8BEpJeo018418 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 11 Sep 2013 07:51:22 -0700
Message-ID: <52308352.2060902@dcrocker.net>
Date: Wed, 11 Sep 2013 07:50:58 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
References: <CAMm+Lwg4hcnk+uPQZizeRM++tic4utQ4P4mFFeKoq=Dx=0nvJw@mail.gmail.com> <6.2.5.6.2.20130911060419.0ddb37c8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130911060419.0ddb37c8@elandnews.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 11 Sep 2013 07:51:22 -0700 (PDT)
X-Mailman-Approved-At: Wed, 11 Sep 2013 11:19:22 -0700
Cc: spfbis@ietf.org, draft-ietf-spfbis-4408bis.all@tools.ietf.org, iesg@ietf.org, secdir@ietf.org
Subject: Re: [secdir] [spfbis] SECDIR Review of draft-ietf-spfbis-4408bis-19
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2013 14:51:41 -0000

On 9/11/2013 6:22 AM, S Moonesamy wrote:
> I am commenting on the following paragraph only:
>
>> The Security Considerations section is adequate for the purpose except
>> that no mention is made anywhere in the specification about DKIM and
>> how a mail receiver should interpret presence of DKIM and SPF policy
>> at the same time. This is a legitimate concern since DKIM is already a
>> standards track proposal and SPF is only now being promoted to
>> Standards Track. Thus the SPF document should address the question of
>> dual use.
>
> There was a BoF at the last IETF meeting to discuss proposals about how
> to interpret the presence of DKIM and/or SPF policy at the same time (
> http://www.ietf.org/proceedings/87/minutes/minutes-87-dmarc ).  The dual
> use can be addressed as part of the DMARC effort.


At the level of a fully-integrated email anti-abuse system, concern 
about possible SPF and DKIM presence and interaction effects is, of 
course, essential.

However SPF is only a component technology.  It's specification is not 
the place for discussing higher-level interaction effects.

By way of example, imagine the specification for an automobile tire 
being expected to talk about design and operations issues when the tire 
is linked to 3 siblings and a suspension system, and a motor and... 
That's an important topic, but the tire spec is wrong venue.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net