IETF Logo Mail Archive

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

Bill Manning <bmanning@ISI.EDU> Fri, 10 September 2004 23:06 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 TAA18381; Fri, 10 Sep 2004 19:06:39 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5uXl-0004O1-Gy; Fri, 10 Sep 2004 19:11:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5uJX-00047c-0e; Fri, 10 Sep 2004 18:56:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5uJC-0003uN-1e for ietf@megatron.ietf.org; Fri, 10 Sep 2004 18:55:58 -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 SAA17740 for <ietf@ietf.org>; Fri, 10 Sep 2004 18:55:54 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5uNK-0004Av-PE for ietf@ietf.org; Fri, 10 Sep 2004 19:00:16 -0400
Received: (from bmanning@localhost) by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i8AMseR21196; Fri, 10 Sep 2004 15:54:40 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200409102254.i8AMseR21196@boreas.isi.edu>
To: sob@harvard.edu
Date: Fri, 10 Sep 2004 15:54:40 -0700
In-Reply-To: <20040910184307.5091586F41@newdev.harvard.edu> from "scott bradner" at Sep 10, 2004 02:43:07 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: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc: 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>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit

%         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

	nope. not kidding any more than you are.

	In movie production, they have a team of folks ensure that
	all music used is properly credited and appropriate licenses
	aquired.  Disney did not perform due diligence and is facing 
	loss of all its trademark protection in South Africa for failing
	to properly clear some of the music it used in "Lion King".

	-IF- ISOC/IETF is going to attempt to retroactively assert
	a right to publish works under different rules than were originally
	granted -WITHOUT the Authors Permission-, then there will be a
	(perhaps) small number of legal challanges.  I think it would 
	be ethically more sound to ask permission first.

--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

v2.46.0 | Report a Bug | By Email | System Status