Re: IETF Last Call for two IPR WG Dcouments

Ray Pelletier <rpelletier@isoc.org> Sat, 05 April 2008 09:42 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 core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A65D53A6BDA; Sat, 5 Apr 2008 02:42:11 -0700 (PDT)
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 53AB83A6B67 for <ietf@core3.amsl.com>; Sat, 5 Apr 2008 02:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.41
X-Spam-Level:
X-Spam-Status: No, score=-2.41 tagged_above=-999 required=5 tests=[AWL=0.188, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 FdkO56SxhkkD for <ietf@core3.amsl.com>; Sat, 5 Apr 2008 02:42:09 -0700 (PDT)
Received: from smtp207.sat.emailsrvr.com (smtp207.sat.emailsrvr.com [66.216.121.207]) by core3.amsl.com (Postfix) with ESMTP id 2ECD53A6B4E for <ietf@ietf.org>; Sat, 5 Apr 2008 02:42:09 -0700 (PDT)
Received: from relay10.relay.sat.mlsrvr.com (localhost [127.0.0.1]) by relay10.relay.sat.mlsrvr.com (SMTP Server) with ESMTP id CC8681B4014; Sat, 5 Apr 2008 05:42:16 -0400 (EDT)
Received: by relay10.relay.sat.mlsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTP id 37AAE1B4010; Sat, 5 Apr 2008 05:42:16 -0400 (EDT)
Message-ID: <47F74969.4030100@isoc.org>
Date: Sat, 05 Apr 2008 05:42:01 -0400
From: Ray Pelletier <rpelletier@isoc.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, zh, zh-cn, zh-hk, zh-sg, zh-tw, ja
MIME-Version: 1.0
To: Ted Hardie <hardie@qualcomm.com>
Subject: Re: IETF Last Call for two IPR WG Dcouments
References: <20080324200545.D6E6328C3AE@core3.amsl.com> <87myoji2ut.fsf@mocca.josefsson.org> <47ECFEF8.6050400@joelhalpern.com> <877ifmq3oc.fsf@mocca.josefsson.org> <47ED19B2.1060006@joelhalpern.com> <873aq8ftrz.fsf@mocca.josefsson.org> <2B752728-CE81-40B5-8E66-230D5E504D4F@thingmagic.com> <BB56240F3A190F469C52A57138047A032BCAC0@xmb-rtp-211.amer.cisco.com> <87r6dtopy9.fsf@mocca.josefsson.org> <47EE921B.8060509@gmail.com> <877ifkfu86.fsf@mocca.josefsson.org> <p06240806c41561285785@[10.20.30.162]> <8763v4dsr5.fsf@mocca.josefsson.org> <p0624080dc41586bc25a3@[10.20.30.162]> <87zlsgcbvy.fsf@mocca.josefsson.org> <47EFE5FD.1070007@joelhalpern.com> <p06240602c415db1c464b@[24.4.239.115]> <87ve335i9x.fsf@mocca.josefsson.org> <p06240600c416abe437bb@[24.4.239.115]>
In-Reply-To: <p06240600c416abe437bb@[24.4.239.115]>
Cc: Simon Josefsson <simon@josefsson.org>, "Joel M. Halpern" <jmh@joelhalpern.com>, "ietf@ietf.org" <ietf@ietf.org>, ipr-wg@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: multipart/mixed; boundary="===============1374510560=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

In their April 3, 2008 meeting, the IETF Trustees discussed the
outbound-IPR document, and found no issues with the advice given in
the document. 

More specifically, the Trustees intend to invite comments
from the community, via the ietf discussion list, prior to issuing any
new licenses.  The comment period(s) will begin as soon as proposed text
for licenses have been drafted or selected. 

The Trustees will not make any final decisions on licenses stemming from 
the
outbound-IPR document until after taking the communities' feedback into 
account.

For the Trustees,
Ray Pelletier
Trustee

Ted Hardie wrote:

>>>I agree with Joel.  We're trying to give instructions to the Trust that
>>>cover the broadest possible user base; calling out specific licenses
>>>or user bases either appears to privilege them or adds no value at
>>>all.  Suggesting to the Trustees that they consider specific licenses
>>>or, even better, pointing their lawyers at the potholes others have
>>>hit would be very useful.  But this draft is not the place to do it.
>>>      
>>>
>>I believe the document is the place to do it.  This is the only document
>>were the IETF explains how the Trust should write its outgoing software
>>license for code in RFCs.  Useful considerations for that process should
>>go into the document.
>>
>>My proposed text does not suggest specific licenses.  That is a
>>misunderstanding.
>>    
>>
>
>Simon,
>	The list of potentially useful considerations in this arena is both long
>and ever-changing.  Imagine, for a moment, that I suggested that the Trust
>survey the legal departments of every organization which had sponsored
>a nomcom-eligible participant in the IETF over the past 3 years asking, if the proposed
>license was usable by their organization.  In some lights, this is a pretty reasonable
>suggestion.   These are organizations with a demonstrated interest in our
>output, and surveys can be a useful tool even when response rates are low.
>Why not confirm that we are meeting the needs of core participants?
>	The answer, basically, is that we want the output to be usable by
>anyone, and privileging the people who pay kind of misses the point.  We
>are giving instructions to the Trust to do the best job they can in making
>sure that the output is usable by anyone for any purpose, no matter whether
>they belong to group A, group B, or won't know for many years that they'll
>have an interest at all.
>	As for how to get in touch with them, trustees of the trust are the
>IAOC.  The IAOC's membership is listed here:
>
>http://iaoc.ietf.org/members_detail.html
>
>I am sure they will listen carefully to your concerns and will consider the
>issues you raise.
>			regards,
>				Ted
>_______________________________________________
>IETF mailing list
>IETF@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf
>
>
>  
>
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf