Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your reviewand comments on a proposed Work-Around to the Pre-5378 Problem

Theodore Tso <tytso@mit.edu> Sat, 10 January 2009 04:14 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F2093A6971; Fri, 9 Jan 2009 20:14:36 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 642073A6978 for <ietf@core3.amsl.com>; Fri, 9 Jan 2009 20:14:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.182
X-Spam-Level:
X-Spam-Status: No, score=-2.182 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GAGjv9beQYLp for <ietf@core3.amsl.com>; Fri, 9 Jan 2009 20:14:34 -0800 (PST)
Received: from thunker.thunk.org (thunk.org [69.25.196.29]) by core3.amsl.com (Postfix) with ESMTP id CF0173A6971 for <ietf@ietf.org>; Fri, 9 Jan 2009 20:14:33 -0800 (PST)
Received: from root (helo=closure.thunk.org) by thunker.thunk.org with local-esmtp (Exim 4.50 #1 (Debian)) id 1LLVEn-0000Kz-FE; Fri, 09 Jan 2009 23:14:17 -0500
Received: from tytso by closure.thunk.org with local (Exim 4.69) (envelope-from <tytso@mit.edu>) id 1LLVEm-00052I-TW; Fri, 09 Jan 2009 23:14:16 -0500
Date: Fri, 09 Jan 2009 23:14:16 -0500
From: Theodore Tso <tytso@mit.edu>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your reviewand comments on a proposed Work-Around to the Pre-5378 Problem
Message-ID: <20090110041416.GM23869@mit.edu>
References: <70873A2B7F744826B0507D4B84903E60@noisy> <FB8A848E-E415-4CDE-9E3F-5C74A5614F18@cisco.com> <49678B2A.8000100@dcrocker.net> <20090109181503.GP24908@verdi> <6E372F257B0C42E7AB9B7DA6231FF4E4@LROSENTOSHIBA> <p06240800c58d5466241b@[10.227.48.131]> <DBAA71AA401E5398212B1E03@PST.jck.com> <4967CAA1.9020608@gmail.com> <B2385D8E5F5BA599A174BD43@PST.jck.com> <4967E348.7050300@joelhalpern.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <4967E348.7050300@joelhalpern.com>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@mit.edu
X-SA-Exim-Scanned: No (on thunker.thunk.org); SAEximRunCond expanded to false
Cc: 'IETF Discussion' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.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://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Fri, Jan 09, 2009 at 06:52:40PM -0500, Joel M. Halpern wrote:
> My own take has been that the code reuse problem is the dominant  
> problem.  Document transfer outside the IETF is sufficiently rare that I  
> would agree with Fred that not solving that is fine.

If it really is the case that the *only* two problems was document
transferoutside of the IETF (rare) and code reuse problem (what
percentage of documents are are actual code that would require special
case licensing --- small) it's actually pretty amazing that the
problem was allowed to balloon to cover **all** text for **all I-D's
and RFC's**.

There's the old saying --- an engineer takes a large problem and break
it up into several smaller problems, and having solved each of the
small problems, solves the overall problem; a bureaucrat takes several
small programs, and tangles them all together into one, gigantic,
intractable problem.

> This also means that from my personal perspective, a solution that says  
> (loosely based on a suggestion from someone else in a side conversation)  
> that
> 1) If you can, you grant 5378 rights
> 2) If you can't, you grant the old rights, as long as there is no code  
> in the document
> 3) If there is code, get the rights to the code so people can actually  
> use the code in the RFC to implement the RFC.  (MIBs are already  
> covered, but we have lots of other kinds of code.)

We do have precedent for include code that has explicit open source
licensing rights.  For example, the MD5 implementation in RFC 1321 has
an explicit BSD-style license.  How much code is there, really?  I
suppose pseudo-code might be a gray area tht will depend on how
paranoid of a lawyer you are dealing with.  One who uses the argument
that "copyright can not protect ideas, just the expression of the
idea", will probably say that it's OK.  One who tries to draw a
parallel to translations as derived works might be more concerned.

	    		    	    	  	- Ted
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf