RE: clarification of blanket statement text

"Contreras, Jorge" <Jorge.Contreras@wilmerhale.com> Sat, 19 February 2005 00:05 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 TAA28607 for <ipr-wg-web-archive@ietf.org>; Fri, 18 Feb 2005 19:05:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2ITl-0000Ab-AP for ipr-wg-web-archive@ietf.org; Fri, 18 Feb 2005 19:28:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2Hi1-0007PX-Mx; Fri, 18 Feb 2005 18:38:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2HF9-0000TU-3O for ipr-wg@megatron.ietf.org; Fri, 18 Feb 2005 18:09:03 -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 SAA16961 for <ipr-wg@ietf.org>; Fri, 18 Feb 2005 18:09:00 -0500 (EST)
Received: from mail109.messagelabs.com ([216.82.255.131]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D2Has-0004sg-Hz for ipr-wg@ietf.org; Fri, 18 Feb 2005 18:31:31 -0500
X-VirusChecked: Checked
X-Env-Sender: Jorge.Contreras@wilmerhale.com
X-Msg-Ref: server-11.tower-109.messagelabs.com!1108768054!11885146!5
X-StarScan-Version: 5.4.11; banners=-,-,-
X-Originating-IP: [148.139.190.21]
Received: (qmail 22862 invoked from network); 18 Feb 2005 23:08:28 -0000
Received: from hdbosdmz2.haleanddorr.com (148.139.190.21) by server-11.tower-109.messagelabs.com with SMTP; 18 Feb 2005 23:08:28 -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 18:07:17 -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 18:07:16 -0500
Message-ID: <93DB9233B42C2844B0A1B7E8B94D99C301C862AD@HDBOSMX.haleanddorr.com>
Thread-Topic: clarification of blanket statement text
Thread-Index: AcUV7zhO48enS2i9RiawTlczDLhRuwAHuCSg
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: 18 Feb 2005 23:07:17.0849 (UTC) FILETIME=[97964C90:01C5160E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
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: b5d20af10c334b36874c0264b10f59f1
Content-Transfer-Encoding: quoted-printable

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