mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Perry The Cynic <perry@cynic.org>
To: Nicholas Knight <nknight@pocketinet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: business models [was patent stuff]
Date: Fri, 31 May 2002 13:17:09 -0700	[thread overview]
Message-ID: <20020531131709.A26493@sutr.cynic.org> (raw)
In-Reply-To: <1022678126.9255.182.camel@irongate.swansea.linux.org.uk> <20020529141300.30309.qmail@eklektix.com> <20020529171524.A5554@kushida.apsleyroad.org> <00a501c20736$6a3e6e60$6407070a@blue>

On Wed, May 29, 2002 at 10:29:40AM -0700, Nicholas Knight wrote:
> The definition of "defensive patent" could do with some reassesment.
> 
> The only way I can see a software patent as truely defensive, is if it's
> explicitly
> licensed for use by anyone, anywhere, for anything, under any software
> license.
> The only thing it should be used to defend against is someone else patenting
> it
> and denying Red Hat the right to use it, it shouldn't be used to prevent
> others,
> no matter who they are, from using it.

There is a much more aggressive use that arguably is still defensive. It's
a formal codification of the way patents are often used by corporations
these days. It goes like this:

"You have a license to use this patent, without fees or restrictions, in
any of your products as long as you do not raise any claims from any of
*your* patents, of any form, against any of our products, except when
such patent includes license terms that are no worse than this license."

In real life, this is hellaciously hard to express in such a way that it
can't be worked around. (One obvious attack is to fork off an "independent"
subsidiary that raises patent claims on your behalf.) Which is why this kind
of strategy is usually implemented by staff lawyers playing "tit for tat"
with the other guy's staff lawyers.

Cheers
  -- perry
---------------------------------------------------------------------------
Perry The Cynic                                             perry@cynic.org
To a blind optimist, an optimistic realist must seem like an Accursed Cynic.
---------------------------------------------------------------------------

  reply	other threads:[~2002-05-31 20:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29  3:21 Adam J. Richter
2002-05-29 13:15 ` Alan Cox
2002-05-29 14:13   ` Jonathan Corbet
2002-05-29 16:15     ` Jamie Lokier
2002-05-29 17:29       ` Nicholas Knight
2002-05-31 20:17         ` Perry The Cynic [this message]
2002-06-03 10:49   ` Rob Landley
  -- strict thread matches above, loose matches on Subject: below --
2002-05-29 19:13 Adam J. Richter
2002-05-28 17:13 Adam J. Richter
2002-05-28 17:52 ` Daniel Phillips
2002-05-28 18:22 ` Alan Cox
2002-05-28 17:23   ` Andre Hedrick
2002-05-29 21:44   ` David Weinehall
2002-05-30  4:51     ` Greg KH
     [not found] <50.c105234.2a24c92d@aol.com>
2002-05-28 13:42 ` Gilad Ben-Yossef
2002-05-27 21:52 patent on O_ATOMICLOOKUP [Re: [PATCH] loopable tmpfs (2.4.17)] Adam J. Richter
2002-05-27 22:24 ` business models [was patent stuff] Larry McVoy
2002-05-27 23:15   ` Karim Yaghmour
2002-05-27 23:31     ` Austin Gonyou
2002-05-28  9:29     ` Peter Wächtler
2002-05-28 13:46       ` Mark Mielke
2002-05-29  8:34         ` Peter Wächtler
2002-05-28  7:53   ` Gilad Ben-Yossef
2002-05-28  8:57     ` Daniel Phillips
2002-05-28 11:30       ` Alan Cox
2002-05-28 10:32   ` Ingo Oeser
2002-05-28 12:28   ` Jonathan Corbet
2002-05-28 18:35   ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020531131709.A26493@sutr.cynic.org \
    --to=perry@cynic.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nknight@pocketinet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®