Re: [spfbis] WGLC: draft-ietf-spfbis-4408bis-14

Scott Kitterman <spf2@kitterman.com> Fri, 19 April 2013 04:18 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 4562B1F0D12 for <spfbis@ietfa.amsl.com>; Thu, 18 Apr 2013 21:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 SjFLWzFGl-75 for <spfbis@ietfa.amsl.com>; Thu, 18 Apr 2013 21:18:54 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF261F0D11 for <spfbis@ietf.org>; Thu, 18 Apr 2013 21:18:54 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 6FFB320E40D4; Fri, 19 Apr 2013 00:18:53 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1366345133; bh=ISmlDBZ+I9E1rHXFqJsgUNL8I6Knp1iCZ/KvUfqYaY8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=lECXXAHT9+TuvYnzICHPTguLGbMZLcIK88mGLTILZ0joughgi8eY/GCJvHrTaIAAd AjVfzFtqdVhU7+trN0kjQPxLhLGky14K+B/YOvgOhvapngOLfwiVdqP2DLBAi1FH7Y mkuMRs4uOAtRdGEIs8ctFl8ohzxXZifkx6LxY2ow=
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 557B420E4090; Fri, 19 Apr 2013 00:18:52 -0400 (EDT)
From: Scott Kitterman <spf2@kitterman.com>
To: spfbis@ietf.org
Date: Fri, 19 Apr 2013 00:18:52 -0400
Message-ID: <3819226.HNrkiDGy6d@scott-latitude-e6320>
User-Agent: KMail/4.9.5 (Linux/3.5.0-27-generic; KDE/4.9.5; i686; ; )
In-Reply-To: <CAJ4XoYd2r7=Vd3Ge4JZie=Hz6+JupDR-OkuSRzRkyuk+5KHrKA@mail.gmail.com>
References: <20130409062431.GK24624@mx1.yitter.info> <CAJ4XoYd2r7=Vd3Ge4JZie=Hz6+JupDR-OkuSRzRkyuk+5KHrKA@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] WGLC: draft-ietf-spfbis-4408bis-14
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: Fri, 19 Apr 2013 04:18:55 -0000

On Tuesday, April 16, 2013 10:08:12 PM Dotzero wrote:
> I've reviewed the draft and have one "nit" and one question/comment:
> 
> In the Abstract the use of ADMD should be followed with
> (ADministrative Management Domains)
> 
>    Email on the Internet can be forged in a number of ways.  In
>    particular, existing protocols place no restriction on what a sending
>    host can use as the "MAIL FROM" of a message or the domain given on
>    the SMTP HELO/EHLO commands.  This document describes version 1 of
>    the Sender Policy Framework (SPF) protocol, whereby an ADMD can
>    explicitly authorize the hosts that are allowed to use its domain
>    names, and a receiving host can check such authorization.

Fixed locally.  I moved it up from the next paragraph to this one.

> 
> For section 2.6.7.  Permerror
> 
>    A "permerror" result means the domain's published records could not
>    be correctly interpreted.  This signals an error condition that
>    definitely requires manual intervention to be resolved.
> 
> Manual intervention by whom? Does this need to be clarified?

Since it's an error in the record, I think it's not something that needs to be 
changed.  Anyone else?

> Other than these two relatively minor details, nothing jumped out at me.
>
> Mike
>
Thanks for the review.

Scott K