Re: RFC 5378 "contributions"

Theodore Tso <tytso@mit.edu> Wed, 21 January 2009 14:45 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 DEF663A67F8; Wed, 21 Jan 2009 06:45:15 -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 DC44C28C13F for <ietf@core3.amsl.com>; Wed, 21 Jan 2009 06:45:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.829
X-Spam-Level:
X-Spam-Status: No, score=-1.829 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, 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 8RJGz+okMYJu for <ietf@core3.amsl.com>; Wed, 21 Jan 2009 06:45:13 -0800 (PST)
Received: from thunker.thunk.org (THUNK.ORG [69.25.196.29]) by core3.amsl.com (Postfix) with ESMTP id 37E3C3A67A1 for <ietf@ietf.org>; Wed, 21 Jan 2009 06:45:13 -0800 (PST)
Received: from root (helo=closure.thunk.org) by thunker.thunk.org with local-esmtp (Exim 4.50 #1 (Debian)) id 1LPeK3-0000iD-VF; Wed, 21 Jan 2009 09:44:52 -0500
Received: from tytso by closure.thunk.org with local (Exim 4.69) (envelope-from <tytso@mit.edu>) id 1LPeK3-0001Sy-5M; Wed, 21 Jan 2009 09:44:51 -0500
Date: Wed, 21 Jan 2009 09:44:51 -0500
From: Theodore Tso <tytso@mit.edu>
To: "Tom.Petch" <sisyphus@dial.pipex.com>
Subject: Re: RFC 5378 "contributions"
Message-ID: <20090121144451.GG31253@mit.edu>
References: <87zlhr9plo.fsf@mocca.josefsson.org> <000201c97ba9$394ff280$0601a8c0@allison>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <000201c97ba9$394ff280$0601a8c0@allison>
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: Simon Josefsson <simon@josefsson.org>, 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 Tue, Jan 20, 2009 at 03:20:20PM +0100, Tom.Petch wrote:

> 
> Underlying this, I believe that if only the IPR WG had not had to
> spend so much time discussing and re-discussing and re-re-discussing
> ... this issue, then may be, just may be, we would have had more
> time to focus on the transition arrangements that we identified the
> need for in RFC5377 s.3.  In which case, this thread and all the
> other related ones would never have occurred.

So I wasn't on the IPR working group, but it seems to me that there
are two separable issues.  There is the question of *which* license to
use for contributions (which might or might not vary based on type of
contribution, i.e., text vs. code), and then there is the question of
whether we are sticking the entire legal liability and respponsibility
onto the I-D editors/authors to guarantee/warant that the entire
document can be released under the the new licensing requirements, and
that relates quite strongly to the transition issue.

Was that second issue discussed by the IPR wg?

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