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

Yakov Shafranovich <research@solidmatrix.com> Fri, 21 May 2004 00:00 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 UAA07125 for <asrg-archive@odin.ietf.org>; Thu, 20 May 2004 20:00:53 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQxLd-0003Zo-44 for asrg-archive@odin.ietf.org; Thu, 20 May 2004 19:53:13 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KNrDDC013743 for asrg-archive@odin.ietf.org; Thu, 20 May 2004 19:53:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQxJi-000318-Md for asrg-web-archive@optimus.ietf.org; Thu, 20 May 2004 19:51:14 -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 TAA06834 for <asrg-web-archive@ietf.org>; Thu, 20 May 2004 19:51:12 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQxJh-0003tV-04 for asrg-web-archive@ietf.org; Thu, 20 May 2004 19:51:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQxIm-0003pf-00 for asrg-web-archive@ietf.org; Thu, 20 May 2004 19:50:17 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQxIO-0003lb-00 for asrg-web-archive@ietf.org; Thu, 20 May 2004 19:49:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQx9q-00011x-0A; Thu, 20 May 2004 19:41:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQx67-00088Y-4d for asrg@optimus.ietf.org; Thu, 20 May 2004 19:37:11 -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 TAA06148 for <asrg@ietf.org>; Thu, 20 May 2004 19:37:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQx65-0002uv-AW for asrg@ietf.org; Thu, 20 May 2004 19:37:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQx5C-0002r3-00 for asrg@ietf.org; Thu, 20 May 2004 19:36:14 -0400
Received: from mout.perfora.net ([217.160.230.40]) by ietf-mx with esmtp (Exim 4.12) id 1BQx4g-0002nD-00 for asrg@ietf.org; Thu, 20 May 2004 19:35:42 -0400
Received: from 000-095-757.area3.spcsdns.net[68.245.116.154] (helo=solidmatrix.com) by mrelay.perfora.net with ESMTP (Nemesis), id 1BQx4X-3MIg-0MKz5u-0002Do; Thu, 20 May 2004 19:35:33 -0400
Message-ID: <40AD40B2.50409@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Matthew Elvey <matthew@elvey.com>
CC: 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> <40AD2B5F.9060105@elvey.com>
In-Reply-To: <40AD2B5F.9060105@elvey.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
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 19:35:14 -0400
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

See RFC 3667, section 5.2(b) which changed that. It seems that the 
secretariat did not yet update the ID guidelines to match RFC 3667.

Yakov

Matthew Elvey wrote:
> 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