Re: Proposal to create IETF IPR Advisory Board

TSG <tglassey@earthlink.net> Thu, 19 February 2009 02:16 UTC

Return-Path: <tglassey@earthlink.net>
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 6D2553A69C1 for <ietf@core3.amsl.com>; Wed, 18 Feb 2009 18:16:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.76
X-Spam-Level:
X-Spam-Status: No, score=-2.76 tagged_above=-999 required=5 tests=[AWL=-0.161, 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 W3BWFfESseCf for <ietf@core3.amsl.com>; Wed, 18 Feb 2009 18:16:39 -0800 (PST)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by core3.amsl.com (Postfix) with ESMTP id 7A1183A69AF for <ietf@ietf.org>; Wed, 18 Feb 2009 18:16:39 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=bIHxl3YGZB9oKR8X82eUy9mGOqdo4r7vhp7EMIU9/3Vf8jgz7MjsWaCtxpWT+WBo; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.66] (helo=[192.168.1.101]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1LZyT5-0006zl-7n; Wed, 18 Feb 2009 21:16:51 -0500
Message-ID: <499CC115.2000500@earthlink.net>
Date: Wed, 18 Feb 2009 18:16:53 -0800
From: TSG <tglassey@earthlink.net>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Michael Dillon <wavetossed@googlemail.com>
Subject: Re: Proposal to create IETF IPR Advisory Board
References: <20090213190630.56CF76BE54F@mercury.lcs.mit.edu> <2963ECA56B01F94B9964469DCB8A2B5A05610EF6@de01exm69.ds.mot.com> <265AEFC9577741F5A6B36FACDD757673@LROSENTOSHIBA> <499965B7.9050702@alvestrand.no> <3BEE4CFFA90F43B5917F328AE8BDF0EE@LROSENTOSHIBA> <p06240839c5bfa3544666@10.20.30.158> <F4E3B51C33F640CDBBCF1C317EDF6817@LROSENTOSHIBA> <p06240856c5bfbe3793c2@10.20.30.158> <877585b00902170714v455313dpb5f0982d5a13eaf2@mail.gmail.com> <6846CCF9-0C56-4EBD-8FCE-76B31DA17370@cisco.com> <877585b00902181407t5b5f3bd3u21b0ed7f9fd2b601@mail.gmail.com>
In-Reply-To: <877585b00902181407t5b5f3bd3u21b0ed7f9fd2b601@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec791caf1130edf538e116b88c3935721238350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.66
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-Archive: <http://www.ietf.org/mail-archive/web/ietf>
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>
X-List-Received-Date: Thu, 19 Feb 2009 02:16:40 -0000

Michael Dillon wrote:
>> FSF is very well intentioned; don't understand me to say otherwise. That
>> said, I think their view on IPR is pretty extreme - "no IPR is acceptable".
>>     
>
> Perhaps that is their view as an organization, but if the IETF engages
> with the FSF to get individuals involved in the IPR discussions, I
> think you will find more flexibility of viewpoint.
>   
Yes but their control is narrow so derivatives are freely made. That's 
not the license everyone wants for their standard but it serves FSF 
users. So we should do something that allows any type of standard (open 
use, open-source, proprietary/controlled use) to be done with the same 
standards development and validation framework. To do that maybe the 
licensing needs to be rethought...
> If the IETF chooses to ignore the FSF, I don't think that strategy will work.
>   
Which brings us back to the idea that the party managing the standard 
development effort should define the licensing model rather than the 
model being uniform to the IETF. Seriously think this through - how 
about we modify the standards process so that the WIG Development effort 
selects the specific licensing model for that effort. In fact you may 
have several efforts implementing the same services side by side, except 
with separate licensing's.

I think that the licensing model should be totally linked to the 
standard effort so everyone gets what they want...

You guys want ultimate control - so take it - move the licensing process 
into the Project Definition and allow people to select those models 
already in place or specify something different. This means that the 
issue of negotiating this goes away and we can get back to more 
important topics.

We also will in one fell swoop open the IETF to totally open-sourced 
standards models and proprietary ones too. Imagine that - if the 
licensing model is just moved into the standard itself from the boiler 
plate housed in the BCP's.

Todd Glassey
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>