Re: Issue found in RFC 3667 text

"todd glassey" <todd.glassey@worldnet.att.net> Wed, 28 April 2004 18:10 UTC

Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04740 for <ipr-wg-archive@odin.ietf.org>; Wed, 28 Apr 2004 14:10:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BItOM-0006FW-0j for ipr-wg-archive@odin.ietf.org; Wed, 28 Apr 2004 14:02:42 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3SI2fSG024023 for ipr-wg-archive@odin.ietf.org; Wed, 28 Apr 2004 14:02:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BItAW-0003lK-2f for ipr-wg-web-archive@optimus.ietf.org; Wed, 28 Apr 2004 13:48:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02955 for <ipr-wg-web-archive@ietf.org>; Wed, 28 Apr 2004 13:48:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BItAS-0002sc-Gz for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 13:48:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIt9T-0002mh-00 for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 13:47:20 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BIt8U-0002gN-00 for ipr-wg-web-archive@ietf.org; Wed, 28 Apr 2004 13:46:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIsxd-0000eu-6k; Wed, 28 Apr 2004 13:35:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIsrB-0007HF-0F for ipr-wg@optimus.ietf.org; Wed, 28 Apr 2004 13:28:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01110 for <ipr-wg@ietf.org>; Wed, 28 Apr 2004 13:28:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIsr7-0001Dr-P0 for ipr-wg@ietf.org; Wed, 28 Apr 2004 13:28:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIsqD-000184-00 for ipr-wg@ietf.org; Wed, 28 Apr 2004 13:27:26 -0400
Received: from mtiwmhc13.worldnet.att.net ([204.127.131.117]) by ietf-mx with esmtp (Exim 4.12) id 1BIspN-0000yp-00 for ipr-wg@ietf.org; Wed, 28 Apr 2004 13:26:33 -0400
Received: from gw (29.san-jose-09-10rs.ca.dial-access.att.net[12.72.195.29]) by worldnet.att.net (mtiwmhc13) with SMTP id <2004042817255511300mrh3ge>; Wed, 28 Apr 2004 17:25:56 +0000
Message-ID: <013c01c42d45$c47371f0$010aff0a@gw>
From: todd glassey <todd.glassey@worldnet.att.net>
To: "Contreras, Jorge" <Jorge.Contreras@haledorr.com>, Fred Baker <fred@cisco.com>
Cc: sob@harvard.edu, ipr-wg@ietf.org, rbarr@cisco.com
References: <93DB9233B42C2844B0A1B7E8B94D99C30148F888@HDBOSMX.haleanddorr.com> <6.1.0.6.2.20040428062836.0623f328@mira-sjc5-b.cisco.com>
Subject: Re: Issue found in RFC 3667 text
Date: Wed, 28 Apr 2004 10:24:36 -0700
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.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: ipr-wg-admin@ietf.org
Errors-To: ipr-wg-admin@ietf.org
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Id: IPR-WG <ipr-wg.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Fred - let me crystallize this if I can - scary thought eh?

Perhaps what is really being said here is actually "that the person
submitting the draft may not have IPR therein" ... which could work for the
purpose of giving the IETF an arms-length from the IPR issues when it
publishes the drafts or workproduct.

It works to protect the IETF, since it is the "release" in effect I have
been talking about for a year or so now,  but even this step does not set
aside that others may have IPR against that IP, so its still prudent for all
concerned to do "full sweeps" of the available IP Databases when they pickup
or assume a role in some development effort.

Hey - Mssr Barr - what do you think of this one ? - That for people doing IP
Scans or Sweeps, that its also probably worth getting a Lexis Account to
search for litigation on certain issues as well...

Todd

----- Original Message ----- 
From: "Fred Baker" <fred@cisco.com>
To: "Contreras, Jorge" <Jorge.Contreras@haledorr.com>
Cc: <sob@harvard.edu>; <ipr-wg@ietf.org>; <rbarr@cisco.com>
Sent: Wednesday, April 28, 2004 6:47 AM
Subject: RE: Issue found in RFC 3667 text


> At 07:49 AM 04/28/04 -0400, Contreras, Jorge wrote:
> >As far as the second issue raised by Fred, that was an intentional
> >feature.  If a patent application has not been published and the
applicant
> >wishes to maintain the confidentiality of its contents, then he/she
should
> >not submit an ID covered by the application's claims unless willing to
> >disclose enough to satisfy the 3668 requirements.
>
> IANAL, and Todd Glassey advises me that there is some recent case law that
> sets aside what I'm about to say. Legal comment would be instructive to
the
> discussion.
>
> My understanding is that the confidentiality of the filing is not at his
> option. Since the claims have been neither supported or denied, he cannot
> say what IPR claims he might have. At most, he can say that he "may have
> IPR" related to the draft.
>
> To say that he should not submit a draft in such a case is to say that the
> IETF should stop its work. Generally, invention happens in the course of
> solving a problem. I can solve a problem for my customer and in so doing
> generate potential IPR. If I can't talk about that in the course of
> standardization, the standard will therefore likely not meet my customer's
> needs. Voila, the internet runs on proprietary protocols and procedures,
> and standards lag. It is also to say that vendors are forced to develop
> early proprietary solutions, and their customers are forced to buy them,
in
> addition to later standardized solutions, where what the customer is
> requesting is standardized solutions in the first place. Vendors today
> frequently contribute IPR to standardization discussions and solve their
> customers' issues in the context of the standard.
>
> I really need to be able to say that I have filed a defensive patent
> without going into the details of the patent, as I myself don't know more
> than that I have filed it. If the argument is that I should not have filed
> the patent, I can point to a case currently being litigated in which
>   - I wrote some code (for a prior employer)
>   - I didn't patent it as I had pulled the algorithm out of the research
> literature,
>   - An employee of a related company wrote a patent on the algorithm,
>   - Now Cisco and said other company are locked in a legal battle.
>
> Corporate policy requires me to write defensive patent applications to
> prevent such situations. So not filing the patent application, however
much
> I might prefer it, is a violation of my company's policy. (I do push back
> when IMNSHO it gets to the point of being ridiculous, as rbarr will
attest...)
>
> It seems that in a case where the license is free and is extended in any
> case except if the licensing company sues mine (Cisco's practice on such
> things), this should be sufficient.
>
>
> _______________________________________________
> 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