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

Joe Touch <touch@ISI.EDU> Fri, 10 September 2004 21:25 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 RAA10370; Fri, 10 Sep 2004 17:25:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5sy5-0002aC-4T; Fri, 10 Sep 2004 17:30:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5sdQ-0007Wq-OI; Fri, 10 Sep 2004 17:08:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5ryH-0005XI-4Q for ietf@megatron.ietf.org; Fri, 10 Sep 2004 16:26:13 -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 QAA01218 for <ietf@ietf.org>; Fri, 10 Sep 2004 16:26:10 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5s2P-0007n6-EN for ietf@ietf.org; Fri, 10 Sep 2004 16:30:29 -0400
Received: from [128.9.168.55] (upn.isi.edu [128.9.168.55]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i8AKOnJ06802; Fri, 10 Sep 2004 13:24:49 -0700 (PDT)
Message-ID: <41420D15.4090700@isi.edu>
Date: Fri, 10 Sep 2004 13:22:45 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Carl Malamud <carl@media.org>
References: <200409101916.i8AJGahi004154@bulk.resource.org>
In-Reply-To: <200409101916.i8AJGahi004154@bulk.resource.org>
X-Enigmail-Version: 0.84.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: scott bradner <sob@harvard.edu>, ietf@ietf.org
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>
Content-Type: multipart/mixed; boundary="===============0307051785=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0


Carl Malamud wrote:

> You could do an opt-out period, say 6 months, before publishing
> the database.  With sufficient publicity, say periodic reposting
> of the opt-out announcement on the ietf list, this seems to
> strike a balance between the unspecified policy of the past
> and a new policy for the future.  
> 
> This seems like a more-than-sufficient amount of care given
> the fact that the data is already available in numerous
> locations on the network.  
> 
> However, I don't think you even need to do an opt-out 
> requirement.  Times change.  The data exists on the net.  

There are those of us who actively pursue this when it happens. It 
usually takes a few emails.

Just because someone usurps your copyright doesn't mean you've lost 
copyright per se, or should.

> The IETF needs to keep a full archive for legal reasons
> even if it doesn't allow FTP access by the public.  Why
> should lawyers with subpoenas get access to the database
> and members of the community can't? 

Let's see all your legal and medical records, if you're in such a mood 
for sharing. ;-) There are plenty of things that can be accessed only 
with due process, and (IMO) should require such.

> We should simply
> remove the access control.

In case it isn't clear, I disagree ;-)

Joe

> 
> Regards,
> 
> Carl
> 
> 
>>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
>>
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on what to pass are made solely by IETF_CENSORED ML Administrator (ietf_admin@ngnet.it)
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf