Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02

wayne <wayne@schlitt.net> Fri, 26 August 2005 18:31 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8iz4-0001s9-3R; Fri, 26 Aug 2005 14:31:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8iz2-0001rD-0w for ietf@megatron.ietf.org; Fri, 26 Aug 2005 14:31:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05447 for <ietf@ietf.org>; Fri, 26 Aug 2005 14:31:18 -0400 (EDT)
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E8izl-00080D-Qa for ietf@ietf.org; Fri, 26 Aug 2005 14:32:08 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1E8ixG-00080R-9B for ietf@ietf.org; Fri, 26 Aug 2005 20:29:30 +0200
Received: from footbone.schlitt.net ([67.52.51.37]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Fri, 26 Aug 2005 20:29:30 +0200
Received: from wayne by footbone.schlitt.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Fri, 26 Aug 2005 20:29:30 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: wayne <wayne@schlitt.net>
Date: Fri, 26 Aug 2005 13:27:12 -0500
Lines: 39
Message-ID: <x4d5o0o8ov.fsf@footbone.schlitt.net>
References: <198A730C2044DE4A96749D13E167AD375A2AB8@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: footbone.schlitt.net
User-Agent: Gnus/5.110004 (No Gnus v0.4) XEmacs/21.4.17 (linux)
Cancel-Lock: sha1:lRtKuk+mGF89+t3jmtzOBqN0anc=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: ietf-mxcomp@imc.org, spf-discuss@v2.listbox.com
Subject: Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

In <198A730C2044DE4A96749D13E167AD375A2AB8@MOU1WNEXMB04.vcorp.ad.vrsn.com> "Hallam-Baker, Phillip" <pbaker@verisign.com> writes:

> I do not think that the IESG should block a proposal citing a conflict
> when the real animus here is entirely due to the IPR issue.

There are certainly people who have problems with introducing
technology into a core Internet protocol such as SMTP that has a
license that conflicts with with a significant number of deployed
servers.

That is by no means the only thing that people object to.  Even if the
license problems went away, there would still be people that have
objections to the conflicting use of SPFv1 records, and, I'm sure,
people who object to the basic techniques to that both SPF and
SenderID use.


> All SPF does is provide a mechanism whereby sending parties can describe
> their outgoing edge mail servers. The recipient has the absolute right
> to interpret that data in any way they see fit. That is the entire point
> of a spam filtering scheme.

You have long advocated this position, but unfortunately the
definition of "outgoing edge mail servers" is not a nice, clean, crisp
concept.  It sounds good, but unfortunately, it doesn't work.

If this was the case, then there wouldn't be cases where SenderID gaves
incorrect results when using SPFv1 records.


> Nobody has ever demonstrated a conflict as far as I am concerned, all
> attempts to allege a conflict begin, "the sender intends" which is
> utterly irrelevant.

There are several known conflicts, as outlined in the appeal, and they
don't begin with "the sender intends".


-wayne


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf