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:32 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 1EkkEa-0001gC-3x; Fri, 09 Dec 2005 10:32:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkkEX-0001dU-D0 for ietf@megatron.ietf.org; Fri, 09 Dec 2005 10:32:30 -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 KAA19672 for <ietf@ietf.org>; Fri, 9 Dec 2005 10:31:35 -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 1EkkEi-0007yo-GY for ietf@ietf.org; Fri, 09 Dec 2005 10:32:42 -0500
Received: from root by ciao.gmane.org with local (Exim 4.43) id 1EkkDn-0003Gt-5f for ietf@ietf.org; Fri, 09 Dec 2005 16:31:45 +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:31:43 +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:31:43 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: wayne <wayne@schlitt.net>
Date: Fri, 09 Dec 2005 09:19:21 -0600
Lines: 38
Message-ID: <x4pso6nvra.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:hi5pAx4e7hj5pScQrUpTTYTmPss=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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
> [...]


I know you have worked quite a bit on Sendmail Inc.'s sid-milter for
them.  Perhaps you can answer some questions:


The draft-lyon-senderid-core-01 document is fairly long, some 17
pages.  This is the document that references the SPF-classic spec and
modifies the semantics for use by SenderID.  (There are two other
SenderID documents to describe the PRA and the SMTP SUBMITTER
extention.)

Can you list the semantic differences between SPF-classic and SenderID
that need to show up in implementations that support both?

Are they any at all?

If not, why does the senderid-core document need to be 17 pages long?

If there are, how many of them are correctly implemented by Sendmail
Inc's sid-milter?


Do you know if Sendmail Inc. is committed to conforming to the RFCs
and will change if the RFCs change?


-wayne



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