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

Harald Tveit Alvestrand <harald@alvestrand.no> Thu, 25 August 2005 17:27 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8LVT-0000IM-5r; Thu, 25 Aug 2005 13:27:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8LVO-0000Hk-5T; Thu, 25 Aug 2005 13:27:12 -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 NAA01366; Thu, 25 Aug 2005 13:27:07 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E8LVw-0002Fw-6R; Thu, 25 Aug 2005 13:27:45 -0400
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id A3A9232008F; Thu, 25 Aug 2005 19:26:45 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15941-03; Thu, 25 Aug 2005 19:26:41 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 69A8632008A; Thu, 25 Aug 2005 19:26:38 +0200 (CEST)
Date: Thu, 25 Aug 2005 10:14:39 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Julian Mehnle <julian@mehnle.net>, Brian Carpenter <brc@zurich.ibm.com>
Message-ID: <B5BB79FFA1CF09E73E64D992@B50854F0A9192E8EC6CDA126>
X-Mailer: Mulberry/4.0.2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: Ted Hardie <hardie@qualcomm.com>, iesg@ietf.org, SPF Council <spf-council@v2.listbox.com>, MARID <ietf-mxcomp@imc.org>, SPF Discussion <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

Julian,

not speaking for anyone but myself.....

one matter of principle:

are you of the opinion that the IESG should try to police which experiments 
get run on the Internet by refusing to publish RFCs documenting 
possibly-conflicting experments?

Both of these documents were published at the request of their authors. I 
know that ways in which they could cause conflict were pointed out to the 
authors, and that both authors upheld their requests to publish.

If you ask the IESG to assert the power to police this kind of experiment, 
please make sure you will be happy with the result if they agree with 
you.....

                  Harald

--On 25. august 2005 00:45 +0200 Julian Mehnle <julian@mehnle.net> wrote:

> I believe that draft-lyon-senderid-core-01 conflicts in a significant
> aspect with draft-schlitt-spf-classic-02, on which the former depends, and
> which has also been approved by the IESG to be published as an
> Experimental RFC.[2]  The conflicting part of the Sender-ID specification
> disrespects the substantial history the SPF specification has outside the
> IETF. Through its decision, the IESG also ignores SPF's deployed base.[3]
> And even if the IESG intends to run both of the specifications as an
> experiment before deciding any further on how to proceed with them, the
> publication of conflicting specifications is bound to disrupt these
> experiments.





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