[spfbis] Comments on draft-kitterman-4408bis-00

Hector Santos <hsantos@isdg.net> Mon, 26 December 2011 12:39 UTC

Return-Path: <hsantos@isdg.net>
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 D923921F8B8D for <spfbis@ietfa.amsl.com>; Mon, 26 Dec 2011 04:39:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.715
X-Spam-Level:
X-Spam-Status: No, score=-1.715 tagged_above=-999 required=5 tests=[AWL=-0.580, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_71=0.6]
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 oKwCrMhj9H8H for <spfbis@ietfa.amsl.com>; Mon, 26 Dec 2011 04:39:43 -0800 (PST)
Received: from listserv.winserver.com (ftp.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 11EF621F8B9C for <spfbis@ietf.org>; Mon, 26 Dec 2011 04:39:42 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1446; t=1324903180; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=sOeZdXII/RnOQgpXlcqd/c4R9f8=; b=MMSWwPopIGOxt6qFq7to B8/Vw10R7MeDL5G7GjLVT4aAsLhpDEiLgvhWUCQoh5QSHLSr7jL/RdJvJJ/NEKv0 cM7Z3Apx+AG1tqjpsbRl/LgNZKOCVuygNIjqDiP/ZjA59SXg6afmBykn9awS6tgc c3AAbpQEIuwFWPfpj7QAEYY=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for spfbis@ietf.org; Mon, 26 Dec 2011 07:39:40 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2400049955.20344.1700; Mon, 26 Dec 2011 07:39:40 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1446; t=1324903032; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=9/N74ZT 0tCpfQKCYvXOFkPPfYatI2f1uEtIGdmWfUY0=; b=pgF6y82sKWUn6I5raBQQIKa 785j8tXBRqeCa+yKVzPmFN/pD/nikIewtjnAC6ShAQjYCVCiRfEbdZVCXz3lx2LB xYF3SOMGIX2a+EybsytqNptNNwDG/AcNY6I5cYyDZYYEikERCIHF56Vldmcv1dMG nP1qUcqRBuMzM4c67H0M=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for spfbis@ietf.org; Mon, 26 Dec 2011 07:37:12 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2999022282.1063.7252; Mon, 26 Dec 2011 07:37:11 -0500
Message-ID: <4EF86B09.2090608@isdg.net>
Date: Mon, 26 Dec 2011 07:39:37 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: spfbis@ietf.org
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [spfbis] Comments on draft-kitterman-4408bis-00
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, 26 Dec 2011 12:39:44 -0000

[Resubmitted from the proper membership address]

Other than the following extremely minor comment, I saw no substantial 
change to this SPF-BIS draft in regards to the SPF protocol.

Maybe its just me, but I see too much usage of the term MEMO for what 
is otherwise a RFC update for a proposed technical specification.   In 
1.1, it says::

     The protocol was originally documented in [RFC4408], which this
     memo replaces.

As far as I am concern, SPF-BIS I-D is not a MEMO A.K.A. Memorandum. 
It is an
technical and/or functional specification depending on your 
discipline. I suggest text change to strengthen what this document 
really is:

    The protocol was originally documented in [RFC4408], which this
    [new] specification (or document) updates and replaces.

Perhaps a correction or errata to SPF-BIF might be described as a MEMO 
or perhaps an Informational RFC, but this is a complete draft standard 
update for a proposed protocol specification - not a piece of a MEMO 
per se.  Other than this nit, I did a complete compare and saw nothing 
that is of substance to write about.

However, IMO, there are plenty of practical SPF-BIS material that 
should be considered that was learned over the decade.  As an early 
adopter,I would like the opportunity to describe and outline these 
SPF-BIS material suggestions if there is interest.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com