Re: IETF Last Call for two IPR WG Dcouments

Simon Josefsson <simon@josefsson.org> Tue, 08 April 2008 21:50 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 AA69E28C245; Tue, 8 Apr 2008 14:50:57 -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 6CF733A6839; Tue, 8 Apr 2008 14:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.734
X-Spam-Level:
X-Spam-Status: No, score=-1.734 tagged_above=-999 required=5 tests=[AWL=0.865, 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 kZ-Rwg1Lrd97; Tue, 8 Apr 2008 14:50:55 -0700 (PDT)
Received: from yxa.extundo.com (yxa.extundo.com [83.241.177.38]) by core3.amsl.com (Postfix) with ESMTP id 9920128C1AE; Tue, 8 Apr 2008 14:50:18 -0700 (PDT)
Received: from mocca.josefsson.org (yxa.extundo.com [83.241.177.38]) (authenticated bits=0) by yxa.extundo.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id m38LoULM015804 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Apr 2008 23:50:31 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Ray Pelletier <rpelletier@isoc.org>
Subject: Re: IETF Last Call for two IPR WG Dcouments
In-Reply-To: <47F74969.4030100@isoc.org> (Ray Pelletier's message of "Sat, 05 Apr 2008 05:42:01 -0400")
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]> <47F74969.4030100@isoc.org>
User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (gnu/linux)
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:080408:ietf@ietf.org::ywJSFi5YHte1+9sA:iC4
X-Hashcash: 1:22:080408:jmh@joelhalpern.com::ODV7gi8tv47QpEvg:4Omp
X-Hashcash: 1:22:080408:rpelletier@isoc.org::43Or/k+6SGoWJzp9:9w8l
X-Hashcash: 1:22:080408:ipr-wg@ietf.org::BMfNOxt+6p5G+ohO:F606
X-Hashcash: 1:22:080408:hardie@qualcomm.com::7dRJqxmHDcxOxKZV:gHTF
Date: Tue, 08 Apr 2008 23:50:30 +0200
Message-ID: <878wzoc8yh.fsf@mocca.josefsson.org>
MIME-Version: 1.0
X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on yxa.extundo.com
X-Virus-Status: Clean
Cc: Ted Hardie <hardie@qualcomm.com>, "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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Thanks Ray, that is reassuring.

I don't think this decreases the need for the -outbound document to be
as clear as possible about what the IETF needs are, though.

/Simon

Ray Pelletier <rpelletier@isoc.org> writes:

> 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
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf