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

Bill Manning <bmanning@ISI.EDU> Fri, 10 September 2004 18:50 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 OAA20921; Fri, 10 Sep 2004 14:50:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5qXi-0004t1-7b; Fri, 10 Sep 2004 14:54:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5qP2-0005aB-Qm; Fri, 10 Sep 2004 14:45:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5q9L-0000nV-Sk for ietf@megatron.ietf.org; Fri, 10 Sep 2004 14:29:31 -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 OAA19095 for <ietf@ietf.org>; Fri, 10 Sep 2004 14:29:29 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5qDS-0004Mc-2m for ietf@ietf.org; Fri, 10 Sep 2004 14:33:47 -0400
Received: (from bmanning@localhost) by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i8AIQil29335; Fri, 10 Sep 2004 11:26:44 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200409101826.i8AIQil29335@boreas.isi.edu>
To: sob@harvard.edu
Date: Fri, 10 Sep 2004 11:26:44 -0700
In-Reply-To: <20040910181324.51A7D86DEC@newdev.harvard.edu> from "scott bradner" at Sep 10, 2004 02:13:24 PM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: bmanning
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Cc: harald@alvestrand.no, cdel@firsthand.net, ietf@ietf.org, sob@harvard.edu, bmanning@ISI.EDU
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: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit

% 
% Bill - as I said in a previous posting - it would be quite fine
% for you to say 'IETF- you do not have permission to post my expired ID' 
% and the IETF should then remove your ID from the IETF's public archive
% but just because you might want to do that shoudl not (imo) keep the
% IETF from posting the 40,000 or so IDs from others, most of whom I
% expect would not object
% 
% 
% Scott

	perhaps true.
	but retro-actively changing the term of a contract,
	esp when no such escape clause was in effect at the
	time the contract was in force, is fraught w/ potential
	liabilities.
	
	not saying it could not happen, just that not all that
	sure of the value proposition of this particular line
	item makes it worthwhile going after the collective
	at this time.  

	it would be worth some cycles to modify the BP used
	to indicate, for the general case, that ISOC or its duly
	authorized agents(blablabla) reserves the right to maintain
	any ID published with this clause intact in the ISOC archives.

	as usual, ymmv.

--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).

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