IETF Logo Mail Archive

Re: archives (was The other parts of the report....

sob@harvard.edu (scott bradner) Fri, 10 September 2004 19:04 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22147; Fri, 10 Sep 2004 15:04:33 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5qlN-0005EY-Qo; Fri, 10 Sep 2004 15:08:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5qRS-0006Id-Pa; Fri, 10 Sep 2004 14:48:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5qN1-0004OX-F7 for ietf@megatron.ietf.org; Fri, 10 Sep 2004 14:43:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20194 for <ietf@ietf.org>; Fri, 10 Sep 2004 14:43:37 -0400 (EDT)
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5qR8-0004fn-0j for ietf@ietf.org; Fri, 10 Sep 2004 14:47:55 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501) id 5091586F41; Fri, 10 Sep 2004 14:43:07 -0400 (EDT)
To: ietf@ietf.org
Message-Id: <20040910184307.5091586F41@newdev.harvard.edu>
Date: Fri, 10 Sep 2004 14:43:07 -0400
From: sob@harvard.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: Re: archives (was The other parts of the report....
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007

bil sez:
        ah... but said RFC did not exist at the time my IDs 
        went out. and my cursory perusal of said RFC seems
        to indicate that it is mute on materials submitted
        into the IETF process in times that pre-date said 
        RFC existance.

fully agree - that was not my purpose in providing teh pointer - I
just wanted you (and others) to know what today's rules are

        that said, it could be that the 40,000 or so legacy
        draft authors won't care, but it would be sound hygiene
        to ask them if they mind if RFC 3667 rules would apply
        to their contributions.  

you are kidding - right?

Scott

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

v2.23.0 | Report a Bug | By Email