RE: clarification of blanket statement text

"Robert Barr" <rbarr@cisco.com> Tue, 15 February 2005 21:35 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15287 for <ipr-wg-web-archive@ietf.org>; Tue, 15 Feb 2005 16:35:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1Ah1-0002UT-T0 for ipr-wg-web-archive@ietf.org; Tue, 15 Feb 2005 16:57:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1AHV-0003Ea-Qc; Tue, 15 Feb 2005 16:30:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1ADg-0001pR-FY for ipr-wg@megatron.ietf.org; Tue, 15 Feb 2005 16:26:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14503 for <ipr-wg@ietf.org>; Tue, 15 Feb 2005 16:26:54 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1AYk-0002H7-13 for ipr-wg@ietf.org; Tue, 15 Feb 2005 16:48:43 -0500
Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-4.cisco.com with ESMTP; 15 Feb 2005 13:26:43 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from rbarrw2k01 ([10.32.226.37]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j1FLQ9YP027488; Tue, 15 Feb 2005 13:26:18 -0800 (PST)
Message-Id: <200502152126.j1FLQ9YP027488@sj-core-4.cisco.com>
From: Robert Barr <rbarr@cisco.com>
To: 'Scott W Brim' <sbrim@cisco.com>, ipr-wg@ietf.org
Date: Tue, 15 Feb 2005 13:26:09 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
Thread-Index: AcUTo0UcG4HYKzqES0yaH2MLuAlKugAAQCYw
In-Reply-To: <20050215205902.GY1088@sbrim-w2k02>
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.226.37]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Subject: RE: clarification of blanket statement text
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: rbarr@cisco.com
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=subscribe>
Sender: ipr-wg-bounces@ietf.org
Errors-To: ipr-wg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit

I think this would be a useful discussion -- it provides more structure and
purpose to the proposed discussion of "acceptable" defensive clauses. If a
defensive clause in  a free license is "acceptable" then a blanket statement
should be acceptable.
rbarr, zealot 

> -----Original Message-----
> From: ipr-wg-bounces@ietf.org 
> [mailto:ipr-wg-bounces@ietf.org] On Behalf Of Scott W Brim
> Sent: Tuesday, February 15, 2005 12:59 PM
> To: ipr-wg@ietf.org
> Subject: clarification of blanket statement text
> 
> I'd like to discuss this at the meeting.  If necessary I can write up
> a small draft based on the results of discussion.  It's within scope
> of the current charter.
> 
> In RFC 3668 6.4.3, it says:
> 
>    However, the requirement for an IPR disclosure is satisfied by a
>    blanket statement of the IPR discloser's willingness to license all
>    of its potential IPR meeting the requirements of Section 6.6 (and
>    either Section 6.1.1 or 6.1.2) to implementers of an IETF
>    specification on a royalty-free basis as long as any other terms
>    and conditions are disclosed in the IPR disclosure statement.
> 
> RFC 3668 explicitly says "royalty-free".
> http://www.ietf.org/ietf/IPR/DYNAMICSOFT-SIMPLE.txt uses that term,
> but consider
> http://www.ietf.org/ietf/IPR/cisco-ipr-draft-salowey-tls-ticket.txt,
> http://www.ietf.org/ietf/IPR/hp-mib, and the classic RFC 1822 as
> examples that do not say "royalty-free" -- they say the discloser will
> "not assert" its patent except under certain specified conditions.
> 
> Could the "not assert" terms in those be used in a blanket statement
> legitimately according to RFC 3668?  
> 
> Thanks ... Scott (Brim)
> 
> _______________________________________________
> Ipr-wg mailing list
> Ipr-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipr-wg
> 

_______________________________________________
Ipr-wg mailing list
Ipr-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/ipr-wg