IETF Logo Mail Archive

Re: [Asrg] [Fwd: Yahoo! Mail Publishes Specification for DomainKeys]

Matthew Elvey <matthew@elvey.com> Thu, 20 May 2004 22:38 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03009 for <asrg-archive@odin.ietf.org>; Thu, 20 May 2004 18:38:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQw71-000170-Df for asrg-archive@odin.ietf.org; Thu, 20 May 2004 18:34:03 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KMY3dj004274 for asrg-archive@odin.ietf.org; Thu, 20 May 2004 18:34:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQw1D-0008CK-4s for asrg-web-archive@optimus.ietf.org; Thu, 20 May 2004 18:28:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02282 for <asrg-web-archive@ietf.org>; Thu, 20 May 2004 18:27:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQw1A-0005sM-CP for asrg-web-archive@ietf.org; Thu, 20 May 2004 18:28:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQw0E-0005oC-00 for asrg-web-archive@ietf.org; Thu, 20 May 2004 18:27:03 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQvzH-0005lW-00 for asrg-web-archive@ietf.org; Thu, 20 May 2004 18:26:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvnd-0002Rv-19; Thu, 20 May 2004 18:14:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQvfz-00069w-NC for asrg@optimus.ietf.org; Thu, 20 May 2004 18:06:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29961 for <asrg@ietf.org>; Thu, 20 May 2004 18:06:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQvfw-0004SC-VN for asrg@ietf.org; Thu, 20 May 2004 18:06:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQvew-0004La-00 for asrg@ietf.org; Thu, 20 May 2004 18:05:03 -0400
Received: from out2.smtp.messagingengine.com ([66.111.4.26]) by ietf-mx with esmtp (Exim 4.12) id 1BQveA-0004Ik-00 for asrg@ietf.org; Thu, 20 May 2004 18:04:14 -0400
X-Sasl-enc: qehBamaQ3XI28g+NYYXPBg 1085090652
Received: from [10.30.13.78] (pat_11.qualcomm.com [192.35.156.11]) by mail.messagingengine.com (Postfix) with ESMTP id D0F8FBB03A4; Thu, 20 May 2004 18:04:11 -0400 (EDT)
Message-ID: <40AD2B5F.9060105@elvey.com>
From: Matthew Elvey <matthew@elvey.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yakov Shafranovich <research@solidmatrix.com>, ASRG <asrg@ietf.org>
Subject: Re: [Asrg] [Fwd: Yahoo! Mail Publishes Specification for DomainKeys]
References: <40AAB82D.3090004@solidmatrix.com> <40AC314F.9030501@elvey.com> <40AD115E.7030500@solidmatrix.com>
In-Reply-To: <40AD115E.7030500@solidmatrix.com>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/mail-archive/working-groups/asrg/>
Date: Thu, 20 May 2004 15:04:15 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-8.0 required=5.0 tests=HABEAS_SWE autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

My statement is based on http://www.ietf.org/ietf/1id-guidelines.txt :

Mandatory Statements
====================

All Internet-Drafts must begin with ONE of the following three
statements:

         This document is an Internet-Draft and is subject to
         all provisions of Section 10 of RFC2026.

         This document is an Internet-Draft and is subject to
         all provisions of Section 10 of RFC2026 except that the
         right to produce derivative works is not granted.

         This document is an Internet-Draft and is NOT offered in
         accordance with Section 10 of RFC2026, and the author does not
         provide the IETF with any rights other than to publish as an
         Internet-Draft


On 5/20/04 1:13 PM, Yakov Shafranovich sent forth electrons to convey:

> Matthew Elvey wrote:
>
>> Apropos Yahoo's DK I-D wannabe-
>> http://antispam.yahoo.com/domainkeys/draft-delany-domainkeys-base-00.txt 
>> posted to this thread:
>> It fails to meet IETF requirements for publication as an I-D, or for 
>> serious consideration by this group.
>>
>> This text is not allowed:
>> "This document may not be modified, and derivative works of it may not
>> be created. This document may only be posted in an Internet-Draft."
>>
>
> Slight correction: it meets the IETF requirements for publication as 
> an ID. HOWEVER, it does not meet the IETF requirements for a standards 
> track ID. There is a slight difference.
>
> I am not involved with the DK/IETF discussions but my hunch is that 
> the Yahoo guys are waiting to see if they can proceed in the IETF 
> Standards process before modifing the ID. Same as what took place with 
> the SPF ID - the -00 draft has the same problem, the current -01 draft 
> does not. I would assume that they are probably discussing things with 
> the ADs at the IETF.
>
> Yakov
> -- 
> Yakov Shafranovich / asrg <at> shaftek.org
> SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
> "And this too shall come to pass" (Unknown)



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

v2.23.0 | Report a Bug | By Email