IETF Logo Mail Archive

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

wayne <wayne@schlitt.net> Fri, 09 December 2005 15:14 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 1Ekjwr-0003ys-3M; Fri, 09 Dec 2005 10:14:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ekjwl-0003yd-0j for ietf@megatron.ietf.org; Fri, 09 Dec 2005 10:14:11 -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 KAA17818 for <ietf@ietf.org>; Fri, 9 Dec 2005 10:13:09 -0500 (EST)
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ekjws-0007Nz-Co for ietf@ietf.org; Fri, 09 Dec 2005 10:14:15 -0500
Received: from root by ciao.gmane.org with local (Exim 4.43) id 1EkjuX-000414-Je for ietf@ietf.org; Fri, 09 Dec 2005 16:11:49 +0100
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, 09 Dec 2005 16:11:49 +0100
Received: from wayne by footbone.schlitt.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Fri, 09 Dec 2005 16:11:49 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: wayne <wayne@schlitt.net>
Date: Fri, 09 Dec 2005 09:02:25 -0600
Lines: 19
Message-ID: <x4u0dinwji.fsf@footbone.schlitt.net>
References: <200512081104.09113.julian@mehnle.net> <4398AE3D.512D@xyzzy.claranet.de> <Pine.LNX.4.64.0512090838400.13902@netcore.fi> <200512091303.37502.julian@mehnle.net> <17305.36224.584090.853821@saint.heaven.net>
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:n5t5mv2F0CNdCnn3qVRuMK3XSV8=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: 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 <17305.36224.584090.853821@saint.heaven.net> "Dick St.Peters" <stpeters@NetHeaven.com> writes:

> Julian Mehnle writes:
>> As my appeal[1] pointed out, at the time draft-lyon-senderid-core-00 was 
>> submitted for experimental status, there was no "running code" that 
>> actually interpreted "v=spf1" as "spf2.0/mfrom,pra".
>
> Perhaps you shouldn't have said that.  Sendmail's sid-milter has used
> v=spf1 records for PRA checks since its initial release in August
> 2004.  I don't know the date for draft-lyon-senderid-core-00, but I
> believe it was well after August.

draft-ietf-marid-protocol-03 was released on Sept 15th 2004, after the
consensus of the working group was that the SPFv1 records should not
be reused for SenderID.  So, yeah, there was a few weeks where the
Sendmail milter was within spec.


-wayne


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

v2.23.0 | Report a Bug | By Email