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

"william(at)elan.net" <william@elan.net> Fri, 09 December 2005 19:39 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eko5Z-0005rq-8a; Fri, 09 Dec 2005 14:39:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eko5X-0005rb-2s for ietf@megatron.ietf.org; Fri, 09 Dec 2005 14:39:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20491 for <ietf@ietf.org>; Fri, 9 Dec 2005 14:38:32 -0500 (EST)
Received: from sokol.elan.net ([216.151.192.200]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eko5l-0000GM-D3 for ietf@ietf.org; Fri, 09 Dec 2005 14:39:42 -0500
Received: from sokol.elan.net (sokol [127.0.0.1]) by sokol.elan.net (8.13.1/8.13.1) with ESMTP id jB9JdN85022623; Fri, 9 Dec 2005 11:39:24 -0800
Received: from localhost (william@localhost) by sokol.elan.net (8.13.1/8.13.1/Submit) with ESMTP id jB9JdNZU022620; Fri, 9 Dec 2005 11:39:23 -0800
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Fri, 09 Dec 2005 11:39:23 -0800
From: "william(at)elan.net" <william@elan.net>
To: SPF discussions <spf-discuss@v2.listbox.com>
In-Reply-To: <tslvexyhy57.fsf@cz.mit.edu>
Message-ID: <Pine.LNX.4.62.0512091136230.6721@sokol.elan.net>
References: <200512081104.09113.julian@mehnle.net> <4398AE3D.512D@xyzzy.claranet.de> <Pine.LNX.4.64.0512090838400.13902@netcore.fi> <Pine.LNX.4.62.0512090426220.6721@sokol.elan.net> <x4y82uo041.fsf@footbone.schlitt.net> <tslvexyhy57.fsf@cz.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ietf@ietf.org
Subject: Re: [spf-discuss] 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

On Fri, 9 Dec 2005, Sam Hartman wrote:

>>>>>> "wayne" == wayne  <wayne@schlitt.net> writes:
>
>    wayne> Isn't the time to fix the problem now?  Before the
>    wayne> experiment is run?
>
> Can you convince the sender ID authors to do so and to change their
> implementations?
>
> I don't think the IETF or IESG could accomplish that.  If you can then
> I agree we will have a better Internet.

You might not be able to accomplish that, but you need not support its
publication as RFC either. Tell them clearly that if they want their
docs published as RFC, the experiment needs to be defined so that it
does not cause interoperability problems with other experiments and
does not violate existing standards.

-- 
William Leibzon
Elan Networks
william@elan.net

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