Re: IETF Last Call for two IPR WG Dcouments

David Morris <dwm@xpasc.com> Mon, 31 March 2008 02:11 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 BE7623A6E13; Sun, 30 Mar 2008 19:11:39 -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 6EA3F3A6E1A for <ietf@core3.amsl.com>; Sun, 30 Mar 2008 19:11:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.052
X-Spam-Level:
X-Spam-Status: No, score=0.052 tagged_above=-999 required=5 tests=[AWL=0.482, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_SORBS_DUL=0.877]
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 DLH2Xi6JkcR8 for <ietf@core3.amsl.com>; Sun, 30 Mar 2008 19:11:37 -0700 (PDT)
Received: from email.xpasc.com (email.xpasc.com [65.85.17.142]) by core3.amsl.com (Postfix) with ESMTP id 620413A6E13 for <ietf@ietf.org>; Sun, 30 Mar 2008 19:11:36 -0700 (PDT)
Received: from bslepgate.xpasc.com (localhost.localdomain [127.0.0.1]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id B9FF0101834 for <ietf@ietf.org>; Sun, 30 Mar 2008 19:11:34 -0700 (PDT)
X-Propel-Return-Path: <dwm@xpasc.com>
Received: from email.xpasc.com ([10.1.2.88]) by [127.0.0.1] ([127.0.0.1]) (port 7027) (Abaca EPG outproxy filter 2.1.7.8167-src $Rev: 8148 $) id iz6Ur83v2bx0; Sun, 30 Mar 2008 19:11:34 -0700
Received: from xpasc.com (egate.xpasc.com [10.1.2.49]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id 4696E10058A for <ietf@ietf.org>; Sun, 30 Mar 2008 19:11:33 -0700 (PDT)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.11.2/8.11.2) with ESMTP id m2V2BWB04765 for <ietf@ietf.org>; Sun, 30 Mar 2008 18:11:32 -0800
Date: Sun, 30 Mar 2008 18:11:32 -0800
From: David Morris <dwm@xpasc.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF Last Call for two IPR WG Dcouments
In-Reply-To: <p06240602c415db1c464b@[24.4.239.115]>
Message-ID: <Pine.LNX.4.33.0803301807590.4647-100000@egate.xpasc.com>
MIME-Version: 1.0
X-Propel-ID: iz6Ur83v2bx0
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

I think more important is that the cited intent when this thread was
warming up was that we were asking the Trust to NOT IMPOSE any
restrictions on code examples WHICH WEREN'T already present from
the contributor of the example. ANY license imposed by the Trust
would likley conflict with that intent.



On Sun, 30 Mar 2008, Ted Hardie wrote:

> At 12:11 PM -0700 3/30/08, Joel M. Halpern wrote:
> >I am still left with the impression that adding references to specific
> >licenses to the draft is going to be confusing, not helpful.
> >If we started saying "needs to be compatible with license X, Y, and Z"
> >then we have at least two problems.  We would have to confirm that X, Y,
> >and Z all met our goals.  And we would have to figure out why we should
> >point to X, Y, and Z but not Q, W, or any other licenses that may be
> >suitable as models.
> >
> >I have no problem with any individual suggesting to the Trustees that
> >specific existing models may be a good way to achieve the stated goal.
> >But adding references to example licenses, even if we were sure they
> >matched our goals, will not help anyone understand the agreed goals.
> >The existing statement is quite clear English.
> >
> >Yours,
> >Joel M. Halpern
>
> 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.
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf