RE: clarification of blanket statement text

"Contreras, Jorge" <Jorge.Contreras@wilmerhale.com> Sat, 19 February 2005 01:57 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 UAA09988 for <ipr-wg-web-archive@ietf.org>; Fri, 18 Feb 2005 20:57:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2KDs-00049j-Vm for ipr-wg-web-archive@ietf.org; Fri, 18 Feb 2005 21:19:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2JnF-0000Mi-Hd; Fri, 18 Feb 2005 20:52:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2JSz-0008Ua-Pd for ipr-wg@megatron.ietf.org; Fri, 18 Feb 2005 20:31:30 -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 UAA08027 for <ipr-wg@ietf.org>; Fri, 18 Feb 2005 20:31:28 -0500 (EST)
Received: from mail95.messagelabs.com ([216.82.241.67]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D2Jok-0003Th-GA for ipr-wg@ietf.org; Fri, 18 Feb 2005 20:53:59 -0500
X-VirusChecked: Checked
X-Env-Sender: Jorge.Contreras@wilmerhale.com
X-Msg-Ref: server-15.tower-95.messagelabs.com!1108776656!8616262!1
X-StarScan-Version: 5.4.11; banners=-,-,-
X-Originating-IP: [148.139.190.21]
Received: (qmail 7948 invoked from network); 19 Feb 2005 01:30:56 -0000
Received: from hdbosdmz2.haleanddorr.com (148.139.190.21) by server-15.tower-95.messagelabs.com with SMTP; 19 Feb 2005 01:30:56 -0000
Received: from hdbosmx.haleanddorr.com ([148.139.4.241]) by hdbosdmz2.haleanddorr.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 18 Feb 2005 20:29:45 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
Date: Fri, 18 Feb 2005 20:29:44 -0500
Message-ID: <93DB9233B42C2844B0A1B7E8B94D99C301C862B1@HDBOSMX.haleanddorr.com>
Thread-Topic: clarification of blanket statement text
Thread-Index: AcUV7zhO48enS2i9RiawTlczDLhRuwAHuCSgAAS3P7A=
From: "Contreras, Jorge" <Jorge.Contreras@wilmerhale.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>, rbarr@cisco.com, "George T. Willingmyre" <gtw@gtwassociates.com>, Scott W Brim <sbrim@cisco.com>, ipr-wg@ietf.org
X-OriginalArrivalTime: 19 Feb 2005 01:29:45.0154 (UTC) FILETIME=[7E2D8A20:01C51622]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Content-Transfer-Encoding: quoted-printable
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.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Content-Transfer-Encoding: quoted-printable

I've been asked to clarify, so here's my 
interpretation of the rules (sorry for repeating
what's been said by others in slightly different
words):

Under 6.4.3, a participant can satisfy its disclosure
obligations by making a "blanket" statement
that it is willing to license all of its potential
IPR covering an IETF specification ONLY if 
	
	(a) the license will be royalty-free, AND

	(b) any other terms and conditions of the
license are disclosed in an IPR disclosure statement.

No other "blanket" statements of licensing intention
satisfy the participant's disclosure obligations under 3668.  
Thus, if a participant states that it is willing to
license all of its IPR on a RAND basis, the statement
is not compliant.  

The participant who wants to grant RAND licenses 
must comply with the
specific disclosure rules in 6.4.1 and elsewhere.

If that was the intention, then the language works
as written.  If not, then it can be fixed.
However, I'm not sure I understand the problem that's
being identified.

Jorge

-----Original Message-----
From: ipr-wg-bounces@ietf.org [mailto:ipr-wg-bounces@ietf.org]On Behalf
Of Contreras, Jorge
Sent: Friday, February 18, 2005 6:07 PM
To: Harald Tveit Alvestrand; rbarr@cisco.com; George T. Willingmyre;
Scott W Brim; ipr-wg@ietf.org
Subject: RE: clarification of blanket statement text


I agree with Robert -- this type of 
disclosure is not compliant.  This was 
actually discussed within the IP-WG when
the rules were being drafted -- it is 
not just an oversight.  A change may
be desirable, but it would be more
than a simple correction of something
inadvertent.

-----Original Message-----
From: ipr-wg-bounces@ietf.org [mailto:ipr-wg-bounces@ietf.org]On Behalf
Of Harald Tveit Alvestrand
Sent: Friday, February 18, 2005 1:52 PM
To: rbarr@cisco.com; 'George T. Willingmyre'; 'Scott W Brim';
ipr-wg@ietf.org
Subject: RE: clarification of blanket statement text


You're right.

I think this proves that we were not reading RFC 3668 when we wrote it.

What do you suggest that we do about it?

--On fredag, februar 18, 2005 10:45:29 -0800 Robert Barr <rbarr@cisco.com> 
wrote:

>
>
>> -----Original Message-----
>> From: ipr-wg-bounces@ietf.org
>> [mailto:ipr-wg-bounces@ietf.org] On Behalf Of Harald Tveit Alvestrand
>> Sent: Friday, February 18, 2005 9:05 AM
>> To: rbarr@cisco.com; 'George T. Willingmyre'; 'Scott W Brim';
>> ipr-wg@ietf.org
>> Subject: RE: clarification of blanket statement text
>>
>>
>>
>> --On fredag, februar 18, 2005 08:32:33 -0800 Robert Barr
>> <rbarr@cisco.com>
>> wrote:
>>
>> >> Agreed - these companies will have to continue to make specific IPR
>> >> statements. Making such statements is consistent with the
>> >> RFC, and provides
>> >> information to the IETF community - which I think is a Good
>> >> Thing - but
>> >> they do not lessen the requirement on the companies that make them.
>> >>
>> >>                            Harald
>> > They should be marked non-compliant, as is done with other types of
>> > statements. Why is it consistent w RFC?? The excerpt above says
>> > "requirement not satisfied"
>>
>> As I interpret it, they satisfy the formal requirements for a
>> disclosure,
>> but do not satisfy the (more strict) requirement for a
>> disclosure that
>> allows the filer to not file any more disclosures.
>>
>> Scott and Jorge will probably chime in if I got that one wrong.
>
>
> they don't satisfy this formal requirement:
>
> 6.4.  What must be in a disclosure?
>
> 6.4.1.  .... The disclosure must also list the
>    specific IETF or RFC Editor Document(s) or activity affected.  If the
>    IETF Document is an Internet-Draft, it must be referenced by specific
>    version number. ..
>





_______________________________________________
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