Re: clarification of blanket statement text

"todd glassey" <todd.glassey@worldnet.att.net> Tue, 15 February 2005 21:46 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 QAA16233 for <ipr-wg-web-archive@ietf.org>; Tue, 15 Feb 2005 16:46:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1Arv-0002k6-G5 for ipr-wg-web-archive@ietf.org; Tue, 15 Feb 2005 17:08:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1AVX-0007Jv-AH; Tue, 15 Feb 2005 16:45:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1AUP-0006bb-6N for ipr-wg@megatron.ietf.org; Tue, 15 Feb 2005 16:44:16 -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 QAA15920 for <ipr-wg@ietf.org>; Tue, 15 Feb 2005 16:44:10 -0500 (EST)
Received: from mtiwmhc12.worldnet.att.net ([204.127.131.116]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1ApV-0002fn-Mo for ipr-wg@ietf.org; Tue, 15 Feb 2005 17:06:02 -0500
Received: from gw (213.san-jose-01-03rs.ca.dial-access.att.net[12.72.192.213]) by worldnet.att.net (mtiwmhc12) with SMTP id <2005021521433711200264pfe>; Tue, 15 Feb 2005 21:43:38 +0000
Message-ID: <043a01c513a7$68a558e0$010aff0a@gw>
From: todd glassey <todd.glassey@worldnet.att.net>
To: rbarr@cisco.com, 'Scott W Brim' <sbrim@cisco.com>, ipr-wg@ietf.org
References: <200502152126.j1FLQ9YP027488@sj-core-4.cisco.com>
Date: Tue, 15 Feb 2005 13:43:34 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
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
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.1 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: 7bit

Robert - you speak for Cisco here dont you? So what is it that Cisco feels
in important about the control and release of the copyright in this
standards process.

Also - the documents are really toothless and the IESG may want to address
that. I am referring to what happens to something what the fish starts to
smell foul as it were.

Todd

----- Original Message ----- 
From: "Robert Barr" <rbarr@cisco.com>
To: "'Scott W Brim'" <sbrim@cisco.com>; <ipr-wg@ietf.org>
Sent: Tuesday, February 15, 2005 1:26 PM
Subject: RE: clarification of blanket statement text


> 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


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