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

Frank Ellermann <nobody@xyzzy.claranet.de> Sat, 27 August 2005 02:30 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8qT5-0007aj-3x; Fri, 26 Aug 2005 22:30:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8qT2-0007ZR-QP for ietf@megatron.ietf.org; Fri, 26 Aug 2005 22:30:49 -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 WAA06557 for <ietf@ietf.org>; Fri, 26 Aug 2005 22:30:46 -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 1E8qTs-0008Fq-T6 for ietf@ietf.org; Fri, 26 Aug 2005 22:31:41 -0400
Received: from root by ciao.gmane.org with local (Exim 4.43) id 1E8qSt-0001j1-H7 for ietf@ietf.org; Sat, 27 Aug 2005 04:30:39 +0200
Received: from 62.80.58.221 ([62.80.58.221]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Sat, 27 Aug 2005 04:30:39 +0200
Received: from nobody by 62.80.58.221 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Sat, 27 Aug 2005 04:30:39 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Sat, 27 Aug 2005 03:53:43 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 34
Message-ID: <430FC7A7.6311@xyzzy.claranet.de>
References: <B5BB79FFA1CF09E73E64D992@B50854F0A9192E8EC6CDA126> <1124993318.13993.123.camel@thunk> <09E57A88-3A53-4A78-99D9-67E95B93E9C5@hxr.us> <x43bowpzni.fsf@footbone.schlitt.net> <7E876E12-3D43-4BFB-8F5B-76C3E985A610@hxr.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: 62.80.58.221
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Cc: ietf-mxcomp@imc.org, spf-discuss@v2.listbox.com, ietf@ietf.org
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

Andrew Newton wrote:

> I stated that the SPF and Sender ID experiments should not
> use the v=spf1 records to avoid conflict.

Yes, you are a prominent part of this "embrace and extend"
strategy also known as "steal or destroy".

> if you (the author of the document) do not consider this to
> be an experiment, then perhaps the IETF should not publish
> SPF as an Experimental RFC.

Perhaps the IETF should choose its leadership more carefully.

It didn't work, this trick to get rid of the critical "NOT
RECOMMENDED" in draft-schlitt by a note to the RfC editor.

It didn't work, this trick to close MARID when it was clear
that abusing v=spf1 for PRA is a non-starter.

Hopefully it also won't work by the infamous "SHOULD abuse
v=spf1" in senderid-core-01.

The persons listed on...
http://www.ietf.org/u/ietfchair/dea-directorate.html
as well as all "no objections" on http://tinyurl.com/ayaun
will have a hard time to redeem themselves in my eyes, and
so far only one managed this.

When Keith said here that all this was only an error, not
intentional, I fear that isn't the case for some of these
persons.
                         No paseran



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