Re: [spfbis] Meaning of SPF and domain authentication in general, was #12

Hector Santos <hsantos@isdg.net> Sun, 22 April 2012 20:46 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 6E76121F84E7 for <spfbis@ietfa.amsl.com>; Sun, 22 Apr 2012 13:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.245
X-Spam-Level:
X-Spam-Status: No, score=-2.245 tagged_above=-999 required=5 tests=[AWL=0.354, 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 JH2qdTluA22u for <spfbis@ietfa.amsl.com>; Sun, 22 Apr 2012 13:46:12 -0700 (PDT)
Received: from pop3.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6762721F84DF for <spfbis@ietf.org>; Sun, 22 Apr 2012 13:46:12 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1138; t=1335127565; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=x8cFkZVJJ+1dUP2o+Qrf2oAZtKs=; b=JdEyQfksZS1lKbPGUkwr kUpWzCzAV2PFdo7gOyUK9nfzTfR/kfZEylOKDAJopGL1E+8LthxfjiREzG63lijF H23WHPHYKow5UCz8zwqhTaJWOz0TfFlMoAz42sXquMQJTDIuFWYZZuNgspX8SjPQ zFAKt6HKspUwzRkssZSUGWw=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for spfbis@ietf.org; Sun, 22 Apr 2012 16:46:05 -0400
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 beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 4034383778.34182.4876; Sun, 22 Apr 2012 16:46:04 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1138; t=1335127227; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=DGosUdh XtjVYrB9KPBy1KleGhMJwIr9+cAlLIhCQV8g=; b=YYiAuX4KcSClB9LkXaGTP3U YbxwSQ7zM/Zypb7e38uf3zd6174AMOJ38VaEVB6eXiEsdHm5GvnV9MUt0dAej6em uV57J57XzrB3wSWqukq7mZl9OB+XILUQN468btpNaxw4Ey3WNMx16u4+LeWIjExi +puU+WaduCquP8hnFJOM=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for spfbis@ietf.org; Sun, 22 Apr 2012 16:40:27 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 338315441.2872.7104; Sun, 22 Apr 2012 16:40:26 -0400
Message-ID: <4F947BEF.8010208@isdg.net>
Date: Sun, 22 Apr 2012 17:45:19 -0400
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
References: <20120416230031.12409.qmail@joyce.lan> <4F8CABE8.10007@isdg.net> <CAC4RtVDoJt2WRAvWZt_CwaqnQGDnaK_Y1gggsAGem1mQxZmUXA@mail.gmail.com> <4F94662A.6070909@isdg.net>
In-Reply-To: <4F94662A.6070909@isdg.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [spfbis] Meaning of SPF and domain authentication in general, was #12
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: Sun, 22 Apr 2012 20:46:13 -0000

Folks,

Obviously, the intent was a private communication with Barry.  I wish 
to apologize to all, especially Murray.  While we do have conflicts, I 
honestly admire his dedication and work effort within the IETF. I hope 
we can resolve our differences.   For the record, I was open to 
dealing with the SIDF issue and possibly replace it with some 
SPF/DKIM/ADSP/ATPS combined manner since after all, we have 
implemented SPF, PRA/SUBMITTER, DKIM, ADSP, ATPS and VBR and 
streamlining all this is a high interest.  So I was not against the 
consideration if it could be done without negative repercussions.  I 
simply didn't believe the "usage" angle was the correct approach to 
justify the idea, it is a more complex issue.

Sincerely,

-- 
Hector Santos

Hector Santos wrote:
> (offlist)
> 
> Hi Barry,
> 
> What bothers me that statements were written with a principle focus to 
> replace SIDF with DKIM and there obvious issues that I believed where 
> simply wrong from many angles I don't wish to repeat, but it took me to 
> highlight issues because no else was.  Why did it even have get to this 
> level is vexing to me.