Re: RFC 5378 "contributions"

Simon Josefsson <simon@josefsson.org> Wed, 21 January 2009 20:57 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 3001B3A6A2E; Wed, 21 Jan 2009 12:57:25 -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 28BA43A6A2E for <ietf@core3.amsl.com>; Wed, 21 Jan 2009 12:57:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level:
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599]
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 RDcl8APgVT8B for <ietf@core3.amsl.com>; Wed, 21 Jan 2009 12:57:23 -0800 (PST)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id F39CB3A69ED for <ietf@ietf.org>; Wed, 21 Jan 2009 12:57:22 -0800 (PST)
Received: from c80-216-29-127.bredband.comhem.se ([80.216.29.127] helo=mocca.josefsson.org) by yxa-v.extundo.com with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from <simon@josefsson.org>) id 1LPk8D-0002hQ-Er; Wed, 21 Jan 2009 21:57:02 +0100
From: Simon Josefsson <simon@josefsson.org>
To: Theodore Tso <tytso@mit.edu>
Subject: Re: RFC 5378 "contributions"
References: <87zlhr9plo.fsf@mocca.josefsson.org> <000201c97ba9$394ff280$0601a8c0@allison> <20090121144451.GG31253@mit.edu> <87k58o8z6b.fsf@mocca.josefsson.org> <20090121171052.GK31253@mit.edu>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090121:ietf@ietf.org::pgToowmOPJW8dr63:ABEW
X-Hashcash: 1:22:090121:tytso@mit.edu::eeZ39O5K0UjqhIzS:bBVQ
Date: Wed, 21 Jan 2009 21:56:56 +0100
In-Reply-To: <20090121171052.GK31253@mit.edu> (Theodore Tso's message of "Wed, 21 Jan 2009 12:10:52 -0500")
Message-ID: <87prig5qef.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux)
MIME-Version: 1.0
Cc: 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 Theodore Tso <tytso@mit.edu> writes:

> On Wed, Jan 21, 2009 at 04:19:08PM +0100, Simon Josefsson wrote:
>> 
>> However, the theme were present in several discussions about simplifying
>> the procedures.  One link (but probably not the best one) would be:
>> 
>> http://thread.gmane.org/gmane.ietf.ipr/3738
>> 
>> Implicit in that argument is that contributors release their own
>> contribution under a license, and do not vouch for anyone else's
>> contribution, and that others can re-use the material under that
>> license.  This is the normal procedure in the free software community.
>
> Um, I just looked at that thread, and it was talking more about
> whether or not SDO's should be allowed to "fork" an RFC specification
> without getting prior permission from the IETF or not, and worries
> about "fake" RFC's.  That has nothing to do with shoving all of the
> liabilities associating with assuring that all contributions following
> the IPR responsibilities onto the I-D author/editors.
>
> Maybe you thought it was implicit in the argument, but it certainly
> wasn't obvious to me.  So if your goal was to advance that point of
> view, it probably wasn't the best strategy as an advocate.

I didn't mean to imply that I were aware of the transition issue at the
time.  Sorry for the confusion.  My point was to suggest that we reduce
complexity and re-use something that has been proven to work for many
years.  The current problem appear to stem from a complex solution and
too little review.

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