decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Comparative Charts - IBM Counterclaims and SCO's Answers and Affirmative Defenses
Sunday, March 14 2004 @ 05:15 AM EST

Here are two charts to help us to see exactly what SCO is answering in its new Amended Answer to IBM's Amended Counterclaims, including the recent changes. The left-hand column is IBM's Amended Counterclaims. The middle column is SCO's original Answer. The right column is their Second Amended Answer to IBM's Amended Counterclaims. It's all the same until you come to the Affirmative Defenses, which I made into a second chart, with the original SCO affirmative defenses on the left and the new version on the right. It's two charts, but both the answers and the affirmative defenses are in the same SCO documents. I've separated them only for contrasting them visually clearly. New material is shown in red text and deleted material is in blue.

SCO greatly fleshes out their affirmative defenses with respect to IBM's patent counterclaims. The second chart shows those changes. Keep in mind that they are trying hard to answer what IBM raised as a Motion to Strike. The Memorandum in Support of Motion to Strike explains the grounds IBM raised as to why three of SCO's affirmative defenses should be stricken. You could sum up IBM's reasons by quoting their Preliminary Statement in the memorandum:

"In response to IBM's counterclaims, SCO asserts three affirmative defenses based on fraud--SCO's Fifth, Fifteenth, and Nineteenth Affirmative Defenses. In disregard of Rule 9(b) of the Federal Rules of Civil Procedure, however, SCO pleads no supporting facts whatsoever. That is insufficient pleading, and SCO's affirmative defenses should be stricken."

SCO is now, in its amended answers, trying to supply some supporting facts quick.

This motion to strike is the one in which Judge Wells in her order of March 3, 2004, asked both sides to provide a memorandum explaining to her how SCO's amended pleadings and IBM's answer to it would affect IBM's motion to strike. IBM is to file theirs first, within 60 days of the order, and then SCO will answer, followed by IBM's final say, followed by a court hearing. Here is exactly what the order said on this point:

"In light of the Court's order granting SCO's motion to file an amended complaint, and IBM's answer to SCO's second amended complaint, the Court hereby orders:Both SCO and IBM are to file additional memoranda with the Court addressing the impact, if any, of the second amended complaint and IBM's subsequent answer on IBM's Motion to Strike the 5th, 15th, and 19th Affirmative Defenses asserted by the SCO Group in its Answers to IBM's Amended Counterclaims. Because this is IBM's motion, IBM is to file its intial memoranda with the Court within 60 days of the entry of this order. SCO will then have 15 days to respond to IBM's filing. IBM will have 7 days following SCO's response to file a reply. Following the additional briefing, the Court will contact the parties to schedule a hearing regarding IBM's motion to strike SCO's affirmative defenses."

Here are the affirmative defenses that IBM asked to be stricken:

  • FIFTH AFFIRMATIVE DEFENSE -IBM's claims are barred by fraud, illegality, collusion, conspiracy and/or lack of clean hands.
  • FIFTEENTH AFFIRMATIVE DEFENSE -On information and belief, one or more of the copyrights at issue is, or may be, unenforceable by reason of IBM's inequitable conduct, acts or omissions before the United States Patent and Trademark Office.
  • NINETEENTH AFFIRMATIVE DEFENSE - On information and belief, the #746 Patent or one or more of the other patents at issue is, or may be, unenforceable by reason of IBM's inequitable conduct, acts or omissions before the United States Patent and Trademark Office.

The 15th is the affirmative defense that SCO has dropped itself, because it was pled in error. The Nineteenth is now the 18th, and it's the heart of the matter. It's the huge chunk of red text on the right-hand column in the second chart, just so you can find it quickly. As for the 5th Affirmative Defense, that's a kind of overview, and IBM argued that by failing to state with specificity what exactly IBM is accused of doing or saying that would justify barring their claims on the grounds of "fraud, illegality, collusion, conspiracy and/or lack of clean hands", SCO's three affirmative defenses should be stricken. SCO has not amplified its 5th Affirmative Defense with any further specifics in response to IBM's challenge except for the lengthy Eighteenth Affirmative Defense in the new filing.

Whether that proves to be enough depends in large part on whether SCO has produced sufficient grounds to invalidate IBM's patents. You'll see that they allege over and over that IBM failed maliciously to clue the Patent and Trademark Office in to prior art. That's a way to get a patent overturned, of course, which is why they are trying it, and presumably that is the "fraud". I don't know the specific facts, but some of you out there will, so take a look at the prior art examples. I find it hard to believe that IBM did that once, let alone several times. SCO needs to win all four, or IBM will nail SCO to the wall on their patent infringement counterclaims. That's true whether or not IBM wins on this Motion to Strike. IBM, as you will remember, chose four patents which strike at the heart of SCO's products. This same technique is how one might go after new patents that look troubling to the FOSS community, by the way, so it's worth watching this part closely and learning.

SCO filed, on February 4, a Motion, and a Memorandum in support, asking the judge for permission to amend their complaint, attached to the motion as Exhibit A, and also to add claims and affirmative defenses, attached as Exhibit B, which is now this Second Amended Answer to IBM's Amended Counterclaims. IBM didn't object and the judge so ordered, but IBM does get to answer. Then each side gets to explain how all the changes affect IBM's Motion to Strike. This legal forest is getting mighty thick, and it took me hours to piece the steps together, and with the help of an attorney to boot. I must have Spring fever. No wonder the judge asked for explanatory memoranda. Anyway, hopefully this explanation, with the charts, will help you follow along in this complicated legal dance and be an aid to comprehending what to expect next.

*************************************************************************

# IBM Amended Counterclaims Against SCO SCO Answer To IBM'S Amended Counterclaims SCO's Amended Answer to IBM's Amended Counterclaims
1 These counterclaims arise from SCO's efforts wrongly to assert proprietary rights over important, widely-used technology and to impede the use of that technology by the open-source community. SCO has misused, and is misusing, its purported rights to the UNIX operating system developed originally by Bell Laboratories, then a research and development arm of AT&T Corp., to threaten destruction of the competing operating systems known as AIX and Linux, and to extract windfall profits for its unjust enrichment. Admits that the UNIX operating system was originally developed by Bell Laboratories, then a development arm of AT&T Corp., but denies the remaining allegations of ¶ 1.Admits that the UNIX operating system was originally developed by Bell Laboratories, then a development arm of AT&T Corp., but denies the remaining allegations of ¶1.
2 IBM's counterclaims also arise from SCO's infringement of IBM copyrights and patents. Although SCO purports to respect the intellectual property rights of others -- and has instituted litigation against IBM for alleged failures with respect to SCO's purported rights -- SCO itself is infringing a number of IBM copyrights and patents. Admits that it respects the intellectual property rights of others, but denies the remaining allegations of ¶ 2.Admits that it respects the intellectual property rights of others, but denies the remaining allegations of ¶2.
3 This Court has jurisdiction over IBM's counterclaims pursuant to 28 U.S.C. §§ 1331,1332(a)(l), 1338(a) and and (b), 1367, 2201(a) and 2202 and 15 U.S.C. § ll25(a)(l). Admits the allegations of ¶ 3.Admits the allegations of ¶3.
4 The Court has diversity and supplemental jurisdiction over IBM's state law claims. The parties have complete diversity of citizenship, and the amount in controversy exceeds $75,000, exclusive of interest and costs. IBM's Lanham Act, copyright and patent claims arise under federal law. Admits the Court has jurisdiction over the claims, but denies that IBM has any valid claims and denies the remaining allegations of ¶ 4 not specifically admitted herein. Admits the Court has jurisdiction over the claims, but denies that IBM has any valid claims and denies the remaining allegations of ¶4 not specifically admitted herein.
5 Venue is proper in this district, with respect to IBM's counterclaims, pursuant to 28 U.S.C. §§ l391(b), 139l(c), and 1400(a) and (b). Admits the allegations of ¶ 5.Admits the allegations of ¶5.
6 Counterclaim-plaintiff IBM is a New York corporation with its principal place of business in the state of New York. Admits the allegations of ¶ 6.Admits the allegations of ¶6.
7 Counterclaim-defendant SCO is a Delaware corporation with its principal place of business in Utah County, Utah. Admits the allegations of ¶ 7.Admits the allegations of ¶7.
8 Unix is a name used to characterize a family of operating systems that share common characteristics and meet certain well-publicized "UNIX" standards. The earliest Unix operating system was built by software engineers at Bell Laboratories, the research division of AT&T. Admits that the earliest UNIX operating system was built by software engineers at Bell Laboratories, the research division of AT&T, but denies the remaining allegations of ¶ 8 not specifically admitted herein. Admits that the earliest UNIX operating system was built by software engineers at Bell Laboratories, the research division of AT&T, but denies the remaining allegations of ¶8 not specifically admitted herein.
9 Over the years, AT&T Technologies, Inc., a wholly owned subsidiary of AT&T, and its related companies licensed Unix operating systems for widespread enterprise use. AT&T's Unix software has been licensed to many thousands of persons or entities. Admits the allegations of ¶ 9.Admits the allegations of ¶9.
10 In 1993, AT&T sold its Unix assets -- then held by its subsidiary, Unix System Laboratories, Inc. ("USL") -- to Novell, Inc. ("Novell"). In 1995, Novell sold some, not all, of its Unix assets to The Santa Cruz Operation, Inc., now known as Tarantella, Inc. ("Original SCO"), which is not affiliated with counterclaim-defendant SCO. Admits that AT&T sold UNIX assets, through its subsidiary USL, to Novell in 1993, admits that Novell sold UNIX assets to The Santa Cruz Operation, Inc., now known as Tarantella, Inc. ('Tarantella') in 1995, admits that Tarantella is not affiliated with SCO, but denies that Novell sold only part of its UNIX assets and further denies the remaining allegations contained in ¶ 10 not specifically admitted herein.Admits that AT&T sold UNIX assets, through its subsidiary USL, to Novell in 1993, admits that Novell sold UNIX assets to The Santa Cruz Operation, Inc., now know as Tarantella, Inc. ("Tarantella") in 1995, admits that Tarantella is not affiliated with SCO but denies that Novell sold only part of its UNIX assets and further denies the remaining allegations contained in ¶10 not specifically admitted herein.
11 Counterclaim-defendant SCO played no role in the development of Unix. But it purports to have acquired Original SCO's rights to Unix in 2001. Based upon the rights it purports to have acquired from Original SCO, SCO has undertaken the scheme described herein. Denies the allegations of ¶11.Denies the allegations of ¶11.
12 In the mid-1980s, IBM acquired broad rights to use Unix software pursuant to a series of agreements with AT&T Technologies, Inc. These agreements, referred to as the "AT&T Agreements", include the Software Agreement (Agreement Number SOFT-00015) dated February 1, 1985, the Sublicensing Agreement (Agreement Number SUB-00015A) dated February 1, 1985, the Substitution Agreement (Agreement Number XFER-00015B) dated February 1, 1985, the letter agreement dated February 1, 1985, and the Software Agreement Supplement 170, as amended by a letter agreement dated on or about January 25, 1989. Copies of these agreements are attached hereto as Exhibits A - F, respectively. Admits that in 1985 IBM acquired certain UNIX rights pursuant to license with AT&T, and admits that IBM and AT&T entered agreements as referenced in ¶12, but denies that IBM's UNIX-related rights are characterized as 'broad,' denies that IBM has any remaining rights under the referenced agreements and denies the remaining allegations of ¶12 not specifically admitted herein.Admits that in 1985 IBM acquired certain UNIX rights pursuant to license with AT&T, and admits that IBM and AT&T entered agreements as referenced in ¶12, but denies that IBM's UNIX-related rights are characterized as 'broad,' denies that IBM has any remaining rights under the referenced agreements and denies the remaining allegations of ¶12 not specifically admitted herein.
13 In connection with the proper exercise of these and other rights previously obtained by IBM with respect to Unix, IBM began development of its own version of a Unix operating system, called AIX. Over the last two decades, IBM has expended tremendous resources on developing AIX, creating millions of lines of original code, incorporating it into its product lines and licensing the technology to thousands of customers worldwide. IBM continues to do so today. Admits that IBM developed a version of UNIX pursuant to license originally with AT&T and admits that IBM's version of UNIX is called AIX but denies that IBM properly exercised its rights and is without information sufficient to admit or deny the remaining allegations of ¶13 and therefore denies the same.Admits that IBM developed a version of UNIX pursuant to license originally with AT&T and admits that IBM's version of UNIX is called AIX but denies that IBM properly exercised its rights and is without information sufficient to admit or deny the remaining allegations of ¶13, and therefore denies the same.
14 Like IBM, Sequent Computer Systems, Inc. ("Sequent") developed a version of a Unix operating system known as Dynix. IBM acquired Sequent by merger in 1999. Admits that Sequent, like IBM, acquired certain UNIX rights pursuant to its own license agreements with AT&T, all of which IBM failed to attach to the its counterclaim, and admits that IBM acquired the stock of Sequent and denies the remaining allegations of ¶14 not specifically admitted herein.Admits that Sequent, like IBM, acquired certain UNIX rights pursuant to its own license agreements with AT&T, all of which IBM failed to attach to the its [sic] counterclaim, and admits that IBM acquired the stock of Sequent and denies the remaining allegations of ¶14 not specifically admitted herein.
15 On October 17, 1996, after Novell and Original SCO acquired AT&T's rights to Unix, IBM obtained additional rights with respect to Unix software. Pursuant to an agreement known as Amendment X, entered into by IBM, Novell and Original SCO, IBM acquired, for example, the "irrevocable, fully paid-up, perpetual right to exercise all of its rights" under the AT&T Agreements. A copy of this agreement is attached hereto as Exhibit G. Admits that Amendment X was entered into in 1996 by and among IBM, Original SCO and Novell, but denies the remaining allegations in ¶15.Admits that Amendment X was entered into in 1996 by and among IBM, original SCO and Novell, but denies the remaining allegations in ¶15.
16 Linux is an operating system that stems from a rich history of collaborative development. Linux is a dynamic and versatile operating system and is, for many, the operating system of choice. Denies the allegations of ¶16 and alleges that Linux is, in actuality, an unauthorized version of UNIX that is structured, assembled and designed to be technologically indistinguishable from UNIX, and practically is distinguishable only in that Linux is a 'free' version of UNIX designed to destroy proprietary operating system software.Denies the allegations of ¶16 and alleges that Linux is, in actuality, an unauthorized version of UNIX that is structured, assembled and designed to be technologically indistinguishable from UNIX, and is practically distinguishable only in that Linux is a 'free' version of UNIX designed to destroy proprietary operating system software.
17 The development of Linux began when an undergraduate student at the University of Helsinki, by the name of Linus Torvalds, set out to create a new, free operating system. In 1991, Linus Torvalds began developing the Linux kernel, the core of the operating system, and posting news of his project to internet newsgroups, along with a call for volunteers to assist in his efforts. Admits that Linus Torvalds assembled the original Linux kernel but is without information sufficient to admit or deny the remaining allegations of ¶17 not specifically admitted herein, and therefore denies the same.Admits that Linus Torvalds assembled the original Linux kernel but is without information sufficient to admit or deny the remaining allegations of ¶17 not specifically admitted herein, and therefore denies the same.
18 With the internet providing for a distributed collaboration, other programmers joined to create code making up the kernel. Linus Torvalds directed the collaboration to a version 1.0 release of the Linux kernel in 1994. Is without information sufficient to admit or deny the allegations of ¶18, and therefore denies the same. Is without information sufficient to admit or deny the allegations of ¶18, and therefore denies the same.
19 In the years that followed, thousands of developers, including developers at IBM, contributed to the further development of Linux. Version 2.4 of the Linux kernel was released in 2001. IBM owns valid copyrights in its contributions to Linux, as illustrated below. Admits that many developers have contributed software code to the Linux kernel, admits that IBM has contributed software code to the Linux kernel, admits that the first iteration of Version 2.4 of the Linux kernel was released in 2001, but is without information sufficient to admit or deny the remaining allegations of ¶19 not specifically admitted herein, and therefore denies the same.Admits that many developers have contributed software code to the Linux kernel, admits that IBM contributed software code to the Linux kernel, admits that the first iteration of Version 2.4 of the Linux kernel was released in 2001, but is without information sufficient to admit or deny the remaining allegations of ¶19 not specifically admitted herein, and therefore denies the same.
20 The first commercial distribution of Linux was introduced in 1994 by Red Hat. Thereafter, other distributors, including SCO, introduced a number of commercial Linux products, which typically comprise the Linux kernel, the applications that the kernel runs (which, with the kernel, comprise a complete operating system) and whatever else the distributor chooses to combine into an easily installable product. Admits that Red Hat has distributed one or more versions of Linux, which may include one or more versions of the Linux kernel, and admits that other distributors may have done so as well, including SCO, but denies the remaining allegations of ¶20 not specifically admitted herein.Admits that Red Hat has distributed one or more versions of Linux, which may include one or more versions of the Linux kernel, and admits that the other distributors may have done so as well, including SCO, but denies the remaining allegations of ¶20 not specifically admitted herein.
21 Linux is open-source software. Open-source software is free in the sense that it is publicly available, royalty free, and users have the freedom to run, copy, distribute, study, adapt, and improve the software. Admits the allegations of ¶21, but alleges that Linux software contains other additional characteristics not identified in ¶21, and further alleges that Paragraph 21 does not provide a complete definition of Linux.Admits the allegations of ¶21, but alleges that Linux software contains other additional characteristics not identified in ¶21, and further alleges that ¶21 does not provide a complete definition of Linux.
22 Whereas traditional software licenses often reflect legal limitations restricting the use and reproduction of original works, the open-source community has taken a different approach to licensing. The open-source community, including SCO, resolved to license Linux so as to keep the source code publicly available. Due to the open-source nature of Linux, anyone can freely download Linux and many Linux applications and modify and re-distribute them with few restrictions. Admits that software license agreements typically reflect legal limitations restricting the use and reproduction of works, admits that Linux is available for free download, admits that the license presently governing Linux (the General Public License) generally is oriented to keep source code publicly available, but denies the remaining allegations of ¶22 not specifically admitted herein.Admits that software license agreements typically reflect legal limitations restricting the use and reproduction of works, admits that Linux is available for free download, admits that the license presently governing Linux (the General Public License) generally is oriented to keep the source code publically available, but denies the remaining allegations of ¶22 not specifically admitted herein.
23 There are a variety of open-source licenses, but the most popular is the GNU General Public License (the "GPL"), a copy of which is attached hereto as Exhibit H. The Linux kernel, and significant portions of the larger Linux operating system, are distributed under the GPL. Admits the allegations of ¶23 but denies enforceability or applicability of the GPL.Admits the allegations of ¶23, but denies enforceability or applicability of the GPL.
24 In fact, one of the most important decisions Linus Torvalds made was to develop the Linux kernel under the GPL and keep the source code freely distributable so others could build upon, modify, and develop programs for the operating system. Is without information sufficient to admit or deny the allegations of ¶24, and therefore denies the same. Is without information sufficient to admit or deny the allegations of ¶24, and therefore denies the same.
25 Whereas the licenses for most software are programs designed to limit or restrict a licensee's freedom to share and change it, the GPL is intended to guarantee a licensee's freedom to share and change free software -- to make sure the software is free for all its users. The GPL applies to any program whose authors commit to using it. Admits that the GPL purports to guarantee the right to freely share and change free software, but denies that the GPL applies to any program whose authors commit to using it, denies enforceability or applicability of the GPL, and is without information sufficient to admit or deny the remaining allegations of ¶25 not specifically admitted herein, and therefore denies the same.Admits that the GPL purports to guarantee the right to freely share and change free software, but denies that the GPL applies to any program whose authors commit to using it, denies enforceability or applicability of the GPL, and is without information sufficient to admit or deny the remaining allegations of ¶25 not specifically admitted herein, and therefore denies the same.
26 The GPL is designed to make sure that a licensee has the freedom to distribute copies of free software, receives source code or can get it if the licensee wants it, can change the software or use pieces of it in new free programs and knows the licensee can do these things. Admits that the GPL allows a licensee to distribute copies of free software, receive source code and change and use the software in new free programs but is without information sufficient to admit or deny the remaining allegations of ¶26 not specifically admitted herein and therefore denies the same.Admits that the GPL allows a licensee to distribute copies of free software, receive source code and change and use the software in new free programs but is without information sufficient to admit or deny the remaining allegations of ¶26 not specifically admitted herein, and therefore denies the same.
27 The Linux kernel is subject to the GPL as it is comprised of programs and other works that contain notices placed by contributing copyright holders permitting distribution under the terms of the GPL. The Linux developers' public agreement to apply GPL terms expresses in a binding legal form the conscious public covenant that defines the open-source community -- covenant that SCO itself supported as a Linux company for many years. Admits that Linux is licensed under the GPL and admits that Linux contains some notices placed by some copyright holders, but denies enforceability or applicability of the GPL and denies the remaining allegations of ¶27 not specifically admitted herein.Admits that Linux is licensed under the GPL and admits that Linux contains some notices placed by some copyright holders, but denies enforceability or applicability of the GPL and denies the remaining allegations of ¶27 not specifically admitted herein.
28 SCO accepted the terms of the GPL by modifying and distributing Linux products. By distributing Linux products under the GPL, SCO agreed, among other things, not to assert -- indeed, it is prohibited from asserting -- certain proprietary rights over any programs distributed by SCO under the terms of the GPL. SCO also agreed not to restrict further distribution of any programs distributed by SCO under the terms of the GPL. Denies the allegations of ¶28. Denies the allegations of ¶28.
29 SCO was founded as Caldera, Inc. in 1994, approximately 25 years after the beginning of the development of Unix and three years after Linus Torvalds began the development of Linux, to develop Linux-based business solutions. In 1998, Caldera, Inc. sold its assets relating to its business of developing and marketing Linux to Caldera Systems, Inc., a newly formed corporation. Admits that it was originally founded as Caldera, Inc., admits that in 1998 Caldera, Inc. sold certain of its assets to Caldera Systems, Inc., but denies the remaining allegations in ¶29 not specifically admitted herein. Admits that it was originally founded as Caldera, Inc., admits that in 1998 Caldera, Inc. sold certain of its assets to Caldera Systems, Inc., but denies the remaining allegations in ¶29 not specifically admitted herein.
30 SCO began its business as a developer and distributor of the Linux operating system. By 2001, according to SCO, it led the world's largest Linux channel with more than 15,000 resellers worldwide. Admits that it has distributed certain versions of the Linux operating system but denies the remaining allegations of ¶30.Admits that it has distributed certain versions of the Linux operating system but denies the remaining allegations of ¶30.
31 SCO has developed and marketed software based on the Linux operating system and provided related services that enable the development, deployment and management of Linux-specialized servers and internet access devices that simplify computing. According to SCO, it was one of the first companies to tailor Linux open-source code from various sources into sound discrete products. Admits that it previously developed and marketed software based on certain versions of the Linux operating system, and admits that it has provided certain Linux-related services, but denies the remaining allegations of ¶31.Admits that it previously developed and marketed software based on certain versions of the Linux operating system, and admits that it has provided certain Linux-related services, but denies the remaining allegations of ¶31.
32 Specifically, SCO has distributed and/or redistributed a number of Linux products, including SCO Linux server, SCO OpenLinux Server, and SCO OpenLinux Workstation. SCO has also distributed SCO Volution Manager, a web-based management system for managing and maintaining established versions of Linux (as well as Unix operating systems). Although SCO purported to suspend its Linux distribution after the commencement of this action, SCO has continued to make Linux source code available for download through its website. Admits that it previously distributed or re-distributed SCO Linux server, SCO OpenLinux Server, SCO OpenLinux Workstation and SCO Volution Manager, and admits that SCO has suspended its Linux distribution, but denies the remaining allegations contained in ¶32.Admits that it previously distributed or re-distributed SCO Linux server[sic], SCO OpenLinux Server, SCO OpenLinux Workstation and SCO Volution Manager, and admits that SCO has suspended its Linux distribution, but denies the remaining allegations in ¶32.
33 The viability of SCO's product offerings has depended in large measure upon the efforts of the open-source community in enhancing products and making them compatible for use across multiple software and hardware platforms. Indeed, SCO incorporated certain code licensed pursuant to the GPL into its proprietary Unix products. SCO has also relied on independent developers in the open-source community, such as Linus Torvalds, in order to release upgrades of SCO's Linux-based products. Denies the allegations of ¶33. Denies the allegations of ¶33.
34 In addition to distributing Linux products, SCO facilitated the adoption of Linux by providing education programs designed to help its customers to develop, deploy and administer Linux systems. Furthermore, SCO joined with other Linux vendors in UnitedLinux, an initiative to streamline Linux development and certification around a global, uniform distribution of Linux for business. Admits that it previously distributed certain versions of Linux, admits that it previously provided Linux-related educational programs, admits that it joined UnitedLinux. but denies the remaining allegations of ¶34 not specifically admitted herein.Admits that it previously distributed certain versions of Linux, admits that it previously provided Linux-related educational programs, admits that it joined UnitedLinux, but denies the remaining allegations of ¶34 not specifically admitted herein.
35 On May 7, 2001, Caldera Systems was merged into Caldera International, Inc. (described below), which changed its name to The SCO Group, Inc. in May 2003. Admits the allegations of ¶35.Admits the allegations of ¶35.
36 Until it undertook the scheme described herein, SCO supported the open-source community. According to SCO, it fully embraced the open-source model. Admits that it previously supported in some ways the open-source community prior to discovery of violation of its intellectual property rights by IBM and others, but denies the existence of any 'scheme,' and denies the allegations of ¶36 not specifically admitted herein.Admits that it previously supported in some ways the open-source community prior to discovery of violations of its intellectual property rights by IBM and others, but denies the existence of any "scheme," and denies the allegations of ¶36 not specifically admitted herein.
37 SCO Linux products encompass a range of software that uses a number of different licensing schemes, including open-source licenses and, in particular, the GPL. Components of SCO's Linux products (such as OpenLinux), including the Linux kernel, have been developed and made available for licensing under the GPL and similar licenses, which generally allow any person or organization to copy, modify and distribute the software, without royalty, in any form, including source code. Admits that some of its products were previously made available for licensing under the GPL, but denies the remaining allegations of ¶37 not specifically admitted herein. Admits that some of its products were previously made available for licensing under the GPL, but denies the remaining allegations of ¶36 not specifically admitted herein.
38 Due to the open-source nature of many of SCO's software products and the licenses under which it has developed and distributed them, SCO's collection of trademarks constitutes its most important intellectual property. Denies the allegations of ¶38. Denies the allegations of ¶38.
39 At least until it undertook the scheme described herein, SCO contributed tools and technology to the open-source community. For instance, SCO incorporated open-source components in its product offerings to the betterment of its products, and gave away CD-ROMs containing its Linux operating system at trade shows and allowed it to be freely downloaded over the internet to encourage interest. Admits that it previously engaged in certain Linux-related activities, but denies the remaining allegations of ¶39 not specifically admitted herein. Admits that it previously engaged in certain Linux-related activities, but denies the remaining allegations of ¶39 not specifically admitted herein.
40 In addition, SCO fostered, and regularly contributed to, multiple open-source development projects in order to enhance the capability of SCO's products and services. In fact, SCO's business model depended upon incorporating contributions from the open-source community into products that it open sourced. Admits that it has contributed to certain open-source development projects, but denies the remaining allegations of ¶40 not specifically admitted herein. Admits that it has contributed to certain open-source development projects, but denies the remaining allegations of ¶40 not specifically admitted herein.
41 SCO also fostered and supported the development of additional open-source and Linux enhancements through the Open Source Development Lab and through participation as a key member of many industry standard and open-source initiatives. Denies the allegations of ¶41. Denies the allegations of ¶41.
42 IBM is a participant in the open-source movement and has made a substantial investment in Linux business efforts over the last 5 years. IBM participates in a broad range of Linux projects that are important to the company and contribute to the open-source community. Admits the allegations of ¶42, but alleges that SCO was unaware of IBM's Linux-related investment prior to its formal announcements thereof, and further alleges that IBM secretly and improperly failed to disclose to SCO such Linux-related investments and its intentions with respect to Linux before and during Project Monterey. Admits the allegations of ¶42, but alleges that SCO was unaware of IBM's Linux-related investment prior to its formal announcements thereof, and further alleges that IBM secretly and improperly failed to disclose to SCO such Linux-related investments and its intentions with respect to Linux before and during Project Monterey.
43 Today, IBM has many Linux-related offerings: mainframes and servers that run Linux; memory solutions for Linux environments; a broad range of software offerings; services that include deployment of Linux-based e-business environments, migration of database applications and data to Linux systems, support for Linux-based cluster computing, server consolidation, and a 24-hour technical engineering support line. IBM has created a Linux Center of Competency that offers Linux training and support, applications testing, technical advice and a hands-on environment in which to evaluate Linux and Linux-based applications. Admits the allegations of ¶43.Admits the allegations of ¶43.
44 Like thousands of other developers, IBM has properly contributed source code to Linux under the GPL. In fact, SCO has included IBM contributions to Linux in Linux products that SCO has distributed under the GPL. Like all recipients of SCO's Linux distributions, IBM is entitled to the protections of the GPL with respect to the IBM contributions, as well as any other contributions, included in SCO's Linux distributions, of which IBM is a recipient. Admits that IBM has contributed source code to Linux projects under the GPL, but denies that such contributions were proper or legal, and denies the remaining allegations of ¶44 not specifically admitted herein.Admits that IBM has contributed source code to Linux projects under the GPL, but denies that such contributions were proper or legal, and denies the remaining allegations of ¶44 not specifically admitted herein.
45 Although it completed an initial public offering, SCO, unlike IBM, has failed to establish a successful business around Linux. SCO's Linux business has never generated a profit. In fact, the company as a whole did not experience a profitable quarter until after it abandoned its Linux business and undertook its present scheme to extract windfall profits from Unix technology that SCO played no role in developing. Admits that it completed a public offering, admits that IBM has established its business around Linux and that IBM has received a significant amount of revenue and profit related to Linux, admits that SCO has never generated a profit related to Linux, admits that SCO has not generated profit until recently, but denies the remaining allegations of ¶45 not specifically admitted herein and alleges that IBM's Linux-related revenue is from its wrongful conduct in violation of SCO's legal and contractual rights. Admits that it completed a public offering, admits that IBM has established its business around Linux and that IBM has received a significant amount of revenue and profit related to Linux, admits that SCO has never generated a profit related to Linux, admits that SCO has not generated profit until recently, but denies the remaining allegations of ¶45 not specifically admitted herein and alleges that IBM's Linux-related revenue is from its wrongful conduct in violation of SCO's legal and contractual rights.
46 In an attempt to revive its faltering Linux business, SCO acquired rights to the Unix operating system originally developed by Bell Laboratories and undertook the unification of the Unix and Linux operating systems. On May 7, 2001, Caldera Systems was merged into Caldera International, Inc., a holding company formed to acquire the Server Software and Professional Services divisions of Original SCO, including Original SCO's rights to the Unix assets it acquired from Novell and the Unix variant developed by Original SCO. Admits that Caldera Systems, Inc. was merged into Caldera International, Inc., admits that SCO acquired rights to the UNIX operating system originally developed by Bell Laboratories, but denies the remaining allegations of ¶46 not specifically admitted herein. Admits that Caldera Systems, Inc. was merged into Caldera International, Inc., admits that SCO acquired rights to the UNIX operating system originally developed by Bell Laboratories, but denies the remaining allegations of ¶46 not specifically admitted herein.
47 Following its acquisition of Original SCO's Unix assets, SCO described its business plan as being to integrate its Linux-based products and services with its Unix-based products and services as a way of encouraging businesses to adopt the open-source, Linux-based operating systems. Denies the allegations of ¶47. Denies the allegations of ¶47.
48 In pursuit of this strategy, SCO designed SCO Linux to permit existing Unix-based users to migrate to Linux. In addition, SCO marketed and sold a number of Unix products, including UnixWare, SCO OpenServer, Reliant HA, and Merge, and Caldera's Global Professional Services assisted customers in developing and deploying unified Unix and Linux solutions through consulting and custom engineering services. Denies the allegations of ¶48. Denies the allegations of ¶48.
49 Like SCO's original Linux business, however, this enterprise failed. SCO has not been able to operate a successful, legitimate business concerning Linux and/or Unix. With apparently no other prospects, SCO shifted its business model yet again -- this time to litigation and threats of litigation, as is described below. Denies the allegations of ¶49.Denies the allegations of ¶49.
50 SCO devised a scheme to profit from the UNIX rights that it acquired from Original SCO, though those assets were in no way developed by SCO. Although most, if not all, of the AT&T UNIX technology that SCO purports to own is generally known, available without restriction to the general public or readily ascertainable by proper means, SCO undertook to create fear, uncertainty and doubt in the marketplace in regard to SCO's rights in and to that technology. Denies the allegations of ¶50. Denies the allegations of ¶50.
51 Recognizing that there is little value in its UNIX rights, SCO did not limit its scheme to that technology. Rather, SCO devised and executed a plan to create the false perception that SCO holds rights to UNIX that permit it to control not only all UNIX technology, but also Linux -- including those aspects generated through the independent hard work and creativity of thousands of other developers and long distributed by SCO itself under the GPL. Denies the allegations of ¶51. Denies the allegations of ¶51.
52 SCO undertook to carry out its scheme by, among other things, (a) bringing baseless legal claims against IBM and threatening to sue other companies and individuals, (b) conducting a far-reaching publicity campaign to create the false and/or unsubstantiated impression that SCO has rights to UNIX and Linux that it does not have and that IBM and others have violated SCO's rights and (c) otherwise seeking to condition the market to believe that SCO has rights to UNIX and Linux that it does not have and cannot properly enforce. Denies the allegations of ¶52.Denies the allegations of ¶52.
53 On March 7, 2003, without any prior notice or warning that would have allowed IBM to understand SCO's claims and respond to them, SCO sued IBM alleging a host of meritless claims. In particular, SCO alleges that IBM has breached its contractual obligations to SCO by, among other things, incorporating and inducing others to incorporate SCO's intellectual property into Linux. In addition, SCO alleges that IBM has competed unfairly, interfered with SCO's contracts with others, and misappropriated SCO's trade secrets. Admits it alleges that IBM has breached contractual obligations to SCO by, among other things, incorporating and inducing others to incorporate source code in the Linux kernel in violation of SCO's contractual and intellectual property rights, and that IBM has competed unfairly, interfered with SCO's contract rights with others and misappropriated and/or misused trade secrets, but denies the remaining allegations of ¶53 not specifically admitted herein.Admits it alleges that IBM has breached contractual obligations to SCO by, among other things, incorporating and inducing others to incorporate source code in the Linux kernel in violation of SCO's contractual and intellectual property rights, and that IBM has competed unfairly, interfered with SCO's contract rights with others and misappropriated and/or misused trade secrets, but denies the remaining allegations of ¶53 not specifically admitted herein.
54 By its complaint, and the amended complaint it submitted on July 22, 2003, SCO asserts legal theories that are frivolous, such as that SCO has ownership rights with respect to all of the code in AIX. SCO seeks relief to which it is plainly not entitled, such as a permanent injunction terminating IBM's ability to possess and use the software products it licensed from AT&T Technologies. Inc., notwithstanding the fact that those rights are expressly "irrevocable" and "perpetual". Denies the allegations of ¶54. Denies the allegations of ¶54.
55 In addition to instituting litigation against IBM, SCO sent letters to 1500 of the world's largest corporations threatening litigation. In its letters, an example of which is attached hereto as Exhibit I, SCO states, "We believe that Linux infringes on our UNIX intellectual property and other rights". SCO further states, "We intend to aggressively protect and enforce these rights" against not only the companies involved with "the Linux development process" but also "the end user" companies using any Linux technology. SCO has made clear that it intends to bring legal action relating to Linux. For example, in a press conference on July 21, 2003, SCO stated that taking out a license with SCO was the "alternative to legal enforcement against Linux end-users". Admits having sent letters to 1500 of the world's largest corporations, alleges that the letters are the best evidence of the contents thereof, denies that said letters threatened litigation and denies the remaining allegations of ¶55 not specifically admitted herein. Admits having sent letters to 1500 of the world's largest corporations, alleges that the letters are the best evidence of the contents thereof, denies that said letters threatened litigation and denies the remaining allegations of ¶55 not specifically admitted herein.
56 Following the commencement of its lawsuit against IBM and its barrage of letters threatening suit against others, SCO continued its campaign of falsehoods by further misrepresenting to the market the interplay of UNIX, AIX, Dynix and Linux and SCO's and IBM's rights to these products. Denies the allegations of ¶56. Denies the allegations of ¶56.
57 SCO has repeatedly made false public statements to the effect that it has the right and authority to revoke, and has effectively revoked, IBM's right to use AIX, IBM's version of UNIX. For example, on May 12, 2003, Chris Sontag, a Senior Vice President of SCO, stated publicly, SCO has "the right to revoke the AIX license", and on June 16, 2003, SCO announced publicly that it had "terminated IBM's right to use or distribute any software product that is a modification of or based on UNIX System V source code". Indeed, in an interview given by SCO CEO Darl McBride to Peter Williams of vnunet.com on June 25, 2003, SCO falsely represented that its contractual rights to "pull" IBM's contract are "bullet-proof". SCO has made similarly false statements relating to Dynix. Admits that it has made certain public statements regarding IBM's rights to use AIX and Dynix, admits that it claims the legal right and authority to revoke, and has effectively revoked, IBM right to use, license or distribute AIX and that it has so stated in certain statements, admits that it claims the legal right to revoke IBM's use, license or distribution of Dynix and has so stated in certain statements, but denies the remaining allegations of ¶57 not specifically admitted herein. Admits that it has made certain public statements regarding IBM's right to use AIX and Dynix, admits that it claims the legal right and authority to revoke, and has revoked, IBM's right to use, license or distribute AIX and that it has so stated in certain statements, admits that it claims the legal right to revoke IBM's use, license or distribution of Dynix and has so stated in certain statements, but denies the remaining allegations of ¶57 not specifically admitted herein.
58 By way of further example, SCO has falsely stated that it has the right to control the use by IBM of all of UNIX and AIX technology and to control the use by all persons and entities of Linux technology, which SCO contends is an illegal derivative of UNIX. On June 16, 2003, SCO announced in a press release that "AIX is an unauthorized derivative of the UNIX System operating system source code and its users are, as of this date, using AIX without a valid basis to do so". A SCO letter to Linux users, dated May 12, 2003, states, "We believe that Linux is, in material part, an unauthorized derivative of UNIX.... We believe that Linux infringes on our UNIX intellectual property and other rights." Admits it claims that licensing and sublicensing agreements and related agreements with IBM give SCO the right to control certain uses of AIX by IBM, admits it claims that Linux is, in material part, an unauthorized derivative of UNIX and that SCO has so stated, admits it claims that as of and after June 16, 2003 IBM's right to further use, license or distribute AIX was terminated and that SCO has so stated, admits it claims that IBM customers who license AIX following June 16, 2003 are doing so in violation of SCO's rights and that SCO has so stated, admits it claims that certain uses of Linux infringe on SCO's intellectual property rights and that SCO has so stated, but denies the remaining allegations of ¶58 not specifically admitted herein.Admits it claims that licensing and sublicensing agreements and related agreements with IBM give SCO the right to control certain uses of AIX by IBM, admits it claims that Linux is, in material part, an unauthorized derivative of UNIX and that SCO has so stated, admits it claims that as of and after June 16, 2003 IBM's right to further use, license or distribute AIX was terminated and that SCO has so stated, admits it claims that IBM customers who license AIX following June 16, 2003 are doing so in violation of SCO's rights and that SCO has so stated, admits it claims that certain uses of Linux infringe on SCO's intellectual property rights and that SCO has so stated, but denies the remaining allegations of ¶58 not specifically admitted herein.
59 SCO's campaign has not been limited to press releases and public interviews. SCO has also propagated falsehoods about its and IBM's rights in non-public meetings with analysts. SCO has solicited and participated in these meetings to misuse analysts to achieve wider dissemination of SCO's misleading message about UNIX, AIX and Linux and to damage IBM and the open-source movement. In a luncheon hosted by Deutsche Bank analyst Brian Skiba, on or about July 22, 2003, for example, SCO falsely stated that IBM transferred the NUMA code from Sequent to Linux without any legal basis to do so and that IBM's actions were giving rise to about $1 billion in damages per week. In an interview in June 2003 with Client Server News, SCO misrepresented to analysts that IBM has improperly released "truckloads" of code into the open-source community. Admits it claims that IBM has contributed certain Dynix code to Linux in violation of its contractual and legal obligations to SCO and that SCO has so stated, admits it claims that IBM's violation of SCO's rights are giving rise to damages as a result of IBM's improper profit from Linux and improper continued use of AIX, and that SCO has so stated, but denies the remaining allegations of ¶59 not specifically admitted herein. Admits it claims that IBM has contributed certain Dynix code to Linux in violation of its contractual and legal obligations to SCO and that SCO has so stated, admits it claims that IBM's violation of SCO's rights are giving rise to damages as a result of IBM's improper profit from Linux and improper continued use of AIX, and that SCO has so stated, but denies the remaining allegations of ¶59 not specifically admitted herein.
60 On June 9, 2003, in response to SCO's actions, and pursuant to its obligations under Amendment X, Novell stated its belief that SCO has no right to terminate IBM's UNIX License which is perpetual and irrevocable, and Novell exercised its retained rights to UNIX to put a stop to SCO's misconduct. Under Section 4.16(b) of the Asset Purchase Agreement between Novell and Original SCO dated September 19, 1995 ("APA"), attached hereto as Exhibit J, Novell directed SCO to "waive any purported right SCO may claim to terminate IBM's [UNIX] licenses enumerated in Amendment X or to revoke any rights thereunder, including any purported rights to terminate asserted in SCO's letter of March 6, 2003 to IBM". A copy of Novell's June 9, 2003 letter is attached hereto as Exhibit K. Admits the existence of the letter of June 9, 2003 but denies any legal or factual basis for the said letter and denies the remaining allegations of ¶60 not specifically admitted herein. Admits the existence of the letter of June 9, 2003 but denies any legal or factual basis for the said letter and denies the remaining allegations of ¶60 not specifically admitted herein.
61 When SCO failed to take the actions directed by Novell, on June 12, 2003, Novell exercised its rights under Section 4.16(b) of the APA to waive and revoke, in SCO's stead, any purported right SCO claimed to terminate IBM's licenses. A copy of Novell's June 12, 2003 letter is attached hereto as Exhibit L. Admits the existence of the letter of June 12, 2003 but denies any right in Novell to waive or revoke SCO's rights and denies any legal or factual basis for the said letter and denies the remaining allegations of ¶61 not specifically admitted herein.Admits the existence of the letter of June 12, 2003 but denies any right in Novell to waive or revoke SCO's rights and denies any legal or factual basis for the said letter and denies the remaining allegations of ¶61 not specifically admitted herein.
62 Notwithstanding the fact that IBM's rights to UNIX are expressly "irrevocable" and "perpetual" under Amendment X and the fact that Novell has exercised its right to waive, in any event, any contractual rights SCO claims IBM violated, SCO nevertheless purported to terminate IBM's licenses on June 13, 2003. Moreover, even assuming (contrary to fact) that IBM's rights were terminable, at no time prior to SCO's purported termination did SCO comply with its obligations under the AT&T Agreements to identify the specific acts or omissions that SCO alleges constitute IBM's breach, despite IBM's demands that SCO do so. Denies the allegations of ¶62.Denies the allegations of ¶62.
63 Rather, SCO has continued to misrepresent that it can, or will, or has in fact revoked IBM's right to use UNIX, without disclosing that IBM's rights to UNIX are not terminable or that Novell has exercised its right to waive any contractual rights SCO claims IBM violated. In an interview with InformationWeek on or about June 12, 2003, for instance, SCO falsely stated that it has the right to revoke IBM's license and order the destruction of every copy of AIX. Admits it has revoked IBM's right to further use, license or distribute AIX, pursuant to the express terms of the Software Agreement and related documents, and that it has so stated, but denies the remaining allegations of ¶63 not specifically admitted herein. Admits it has revoked IBM's right to further use, license, or distribute AIX, pursuant to the express terms of the Software Agreement and related documents, and that it has so stated, but denies the remaining allegations of ¶63 not specifically admitted herein.
64 Rather than particularize its allegations of misconduct by IBM and others, SCO has obfuscated and altered its claims to foster fear, uncertainty and doubt about its rights and the rights of others. In letters dated April 2, 2003, and May 5, 2003, attached hereto as Exhibits M and N, respectively, IBM expressly asked SCO to advise IBM as to what SCO contends IBM has done in violation of any of its agreements, and what SCO contends IBM should do to cure such violations. SCO refused. In fact, SCO's counsel stated, in an interview with Maureen O'Gara of LinuxGram, that it "doesn't want IBM to know what they [SCO's substantive claims] are". Admits that IBM sent letters dated April 2, 2003 and May 5, 2003 but denies the remaining allegations of ¶64 not specifically admitted herein. Admits that IBM sent letters dated April 2, 2003 and May 5, 2003 but denies the remaining allegations of ¶64 not specifically admitted herein.
65 SCO has obfuscated its claims and has hidden its supposed evidence because the evidence does not demonstrate the breaches and violations that SCO has alleged. Moreover, key developers and influence leaders in the open-source community, including leaders of Linux kernel development, have stated publicly that they are prepared immediately to remove any allegedly offending material from the Linux kernel. Rather than permit remediation or mitigation of its alleged injuries (which are non-existent), SCO has declined to reveal the particulars of the alleged violations in order to artificially and improperly inflate the price of its stock. Denies the allegations of ¶65.Denies the allegations of ¶65.
66 While refusing to supply IBM with meaningful specifics regarding the alleged breaches, SCO has shown its purported evidence to analysts, journalists and others who are interested in seeing it. For example, at a forum held in Las Vegas on August 17-19, 2003, SCO made a false and misleading presentation concerning its claims against IBM, in which SCO purported to disclose examples of its evidence of alleged misconduct by IBM. Denies the allegations of ¶66.Denies the allegations of ¶66.
67 In addition to purporting to terminate IBM's rights to use AIX, SCO has disparaged AIX as "unauthorized". In a press release dated June 16, 2003, SCO's counsel stated that "SCO has the right to terminate IBM's right to use and distribute AIX. Today AIX is an unauthorized derivative of the UNIX operating system source code and its users are, as of this date, using AIX without a valid license to do so". In the same press release, Darl McBride, SCO's Chief Executive Officer, stated that "IBM no longer has the authority to sell or distribute AIX and customers no longer have the right to use AIX software". SCO has made similarly false and disparaging statements relating to Dynix. Admits that IBM is currently without legal or contractual authority to use, license or distribute AIX or Dynix, based on its breach of agreement with SCO and SCO's resulting termination of IBM's AIX software agreement and related agreements and Sequent's Dynix software agreement and related agreements, and admits that SCO has so stated, but denies the remaining allegations of ¶67 not specifically admitted herein. Admits that IBM is currently without legal or contractual authority to use, license or distribute AIX or Dynix, based on its breach of agreement with SCO and SCO's resulting termination of IBM's AIX software agreement and related agreements and Sequent's Dynix software agreement and related agreements, and admits that SCO has so stated, but denies the remaining allegations of ¶67 not specifically admitted herein.
68 Here again, SCO's false and misleading statements have not been limited to AIX. In recognition of the fact that its claims against IBM are baseless, and in flat contradiction of the allegation of its original complaint (i.e., that this case is not about the relative merits of proprietary versus open-source software), SCO has now falsely stated, in effect, it owns and is entitled to collect royalties regarding Linux. For example, on July 21, 2003, McBride stated, on behalf of SCO, Linux infringes SCO's rights and as "a viable alternative to legal enforcement" SCO is prepared to offer a license to SCO's UNIX products that would, SCO says, permit lawful use of Linux. Admits that SCO has offered a license to Fortune 1000 and Global 500 Linux users as a means of permitting lawful use of certain Linux products and that SCO has so stated, but denies the remaining allegations of ¶68 not specifically admitted herein.Admits that SCO has offered a license to Fortune 1000 and Global 500 Linux users as a means of permitting lawful use of certain Linux products and that SCO has so stated, but denies the remaining allegations of ¶68 not specifically admitted herein.
69 SCO has misrepresented that IBM has infringed SCO's copyrights, and has threatened to sue IBM for copyright infringement, with respect to Linux. For example, at its 2003 SCO Forum, SCO represented that Linux is an unauthorized derivative of Unix, that IBM has infringed its rights in Linux and that SCO is entitled to damages and injunctive relief against IBM. Denies the allegations of ¶69.Denies the allegations of ¶69.
70 SCO's false and misleading statements have also damaged the reputation and prospects of the entire open-source community. SCO's misconduct undermines the substantial public interest in the provision of software that is reliable, inexpensive, and accessible by the general public. Denies the allegations of ¶70. Denies the allegations of ¶70.
71 As stated, IBM has made contributions of source code to Linux under the GPL, some of which are identified below. IBM owns valid copyrights in these contributions, as illustrated below, and has identified them with appropriate copyright notices. Admits that IBM has made contributions of source code to Linux 2.4 and 2.5 kernels under the GPL, but denies the applicability or enforceability of the GPL and denies the remaining allegations of ¶71 not specifically admitted herein. Admits that IBM has made contributions of source code to Linux 2.4 and 2.5 kernels under the GPL, but denies the applicability or enforceability of the GPL and denies the remaining allegations of ¶71 not specifically admitted herein.
72 Notwithstanding SCO's allegations that IBM and others have breached SCO's intellectual property rights, SCO has infringed and is infringing IBM's copyrights in its Linux contributions. Admits that IBM and others have breached SCO's intellectual property rights, but denies the remaining allegations of ¶72. Admits that IBM and others have breached SCO's intellectual property rights, but denies the remaining allegations of ¶72.
73 IBM granted SCO and others a non-exclusive license to these copyrighted contributions on the terms set out in the GPL and only on the terms set out in the GPL. SCO breached its obligations under the GPL, however, and therefore its rights under the GPL terminated. Denies the allegations of ¶73 and denies the enforceability or applicability of the GPL. Denies the allegations of ¶73 and denies the enforceability or applicability of the GPL.
74 SCO has infringed and is infringing IBM's copyrights by copying, modifying, sublicensing and/or distributing Linux products after its rights under the GPL terminated. SCO has taken copyrighted source code made available by IBM under the GPL, included that code in SCO's Linux products, and copied, modified, sublicensed and/or distributed those products other than as permitted under the GPL. Denies the allegations of ¶74. Denies the allegations of ¶74.
75 In addition to infringing IBM's copyrights, SCO is engaged in pervasive acts of infringement of no fewer than four of IBM's patents, by making, using, selling and/or offering to sell a variety of products, including but not limited to: "UnixWare", a Unix operating system for Intel and AMD processor-based computer systems; "Open Server", an operating system platform; "SCO Manager", a web-based remote systems management solution for management of Linux and SCO Unix systems; and "Reliant HA", "clustering" software that permits interconnection of multiple servers to achieve redundancy. Admits that SCO licenses and distributes UnixWare, 'OpenServer,' 'SCO Manager,' and 'Reliant HA,' but denies infringement and denies the remaining allegations of ¶75. Admits that SCO licenses and distributes UnixWare, "OpenServer," "SCO Manager," and "Reliant HA," but denies infringement and denies the remaining allegations of ¶75.
76 As a result of the misconduct described above, SCO has not only artificially inflated its stock price and been unjustly enriched, but also it has injured IBM and, more broadly, the open-source movement. SCO's misconduct has resulted in damage to IBM's business, including its reputation and goodwill, has interfered with its prospective economic relations and has required it unduly to divert resources to respond to SCO's baseless allegations. SCO has injured the open-source movement, of which it was once a part, by fostering fear, uncertainty and doubt about its and others' rights to use UNIX, AIX, Dynix and Linux. Denies the allegations of ¶76. Denies the allegations of ¶76.
77 SCO's misconduct is especially egregious because SCO has implemented its scheme with actual knowledge or in reckless disregard of the fact that it does not have the rights that it seeks to assert (e.g. the right to terminate IBM's irrevocable and perpetual UNIX rights). Moreover, SCO committed not to assert certain proprietary rights over or to restrict further distribution of any program distributed by SCO under the terms of the GPL. Denies the allegations of ¶77. Denies the allegations of ¶77.
78 First Counterclaim: Breach of Contract
IBM repeats and realleges the averments in paragraphs 1 through 77, with the same force and effect as though they were set forth fully herein.
Repeats and realleges ¶¶ 1-77, above.Repeats and realleges ¶¶ 1-77, above.
79 SCO is licensor and IBM licensee of the right to use and sublicense the UNIX software, as specified in the AT&T Agreements, Amendment X and other similar agreements, all of which are valid contracts. Admits that IBM continues to be obligated to SCO by confidentiality requirements and other provisions in the AT&T Agreements and Amendment X that, by their terms, specifically continue beyond termination, but alleges that IBM's right to use, license and distribute under the said agreements has been lawfully and properly terminated, and therefore denies that IBM has any right under the said agreements and denies the remaining allegations of ¶79 not specifically admitted herein. Admits that IBM continues to be obligated to SCO by confidentiality requirements and other provisions in the AT&T Agreements and Amendment X that, by their terms, specifically continue beyond termination, but alleges that IBM's rights to use, license and distribute under the said agreements has been lawfully and properly terminated, and therefore denies that IBM has any right under the said agreements and denies the remaining allegations of ¶79 not specifically admitted herein.
80 IBM has performed all its duties and obligations under the AT&T Agreements, Amendment X and other similar agreements. Denies the allegations of ¶80. Denies the allegations of ¶80.
81 SCO has breached its express duties and obligations under the AT&T Agreements, Amendment X and other similar agreements by, among other things, purporting to terminate IBM's irrevocable and perpetual UNIX rights and/or refusing to provide IBM adequate notice and opportunity to cure its alleged misconduct. Denies the allegations of ¶81.Denies the allegations of ¶81.
82 SCO has also breached the implied covenant of good faith and fair dealing under the AT&T Agreements, Amendment X and other similar agreements by affirmatively seeking to deprive IBM of the benefits to which it is entitled under those contracts through numerous acts of bad faith, including, among other things, making false and misleading statements to the public about SCO's and IBM's rights under the same. Denies the allegations of ¶82. Denies the allegations of ¶82.
83 IBM has suffered damages from SCO's breaches of contract in an amount to be determined at trial. Denies the allegations of ¶83. Denies the allegations of ¶83.
84 Second Counterclaim: Lanham Act Violation
IBM repeats and realleges the averments in paragraphs 1 through 83, with the same force and effect as though they were set forth fully herein.
Repeats and realleges ¶¶ 1-83, above. Repeats and realleges ¶¶ 1-83, above.
85 IBM sells and distributes AIX and Linux-related products and services in interstate commerce, and IBM sold and distributed Dynix in interstate commerce. Admits that IBM sells Linux-related services in interstate commerce, but denies that IBM has or had authority to sell, license or distribute AIX in interstate commerce from and after June 16, 2003, and denies that IBM has or had authority to license, sell or distribute Dynix in interstate commerce from and after September 2. 2003, alleges that IBM's rights in AIX and Dynix have been lawfully and properly terminated, and denies the remaining the allegations of ¶85 not specifically admitted herein. Admits that IBM sells Linux-related services in interstate commerce, but denies that IBM has or had authority to sell, license or distribute AIX in interstate commerce from and after June 16, 2003 , and denies that IBM has or had authority to license, sell or distribute Dynix in interstate commerce from and after September 2, 2003, alleges that IBM's rights in AIX and Dynix have been lawfully and properly terminated, and denies the remaining allegations of ¶85 not specifically admitted herein.
86 SCO has made material false representations regarding AIX, Dynix and IBM's Linux-related products and services, which affect a customer's decision whether to purchase these products and services. Specifically, SCO has publicly misrepresented the legitimacy of these products and services by falsely representing that IBM no longer has the right, authority and license to use, produce and distribute these products and by misrepresenting SCO's own rights in and to UNIX, AIX, Dynix and Linux. Denies the allegations of ¶86. Denies the allegations of ¶86.
87 SCO has published its false statements in a series of widely-distributed press releases, press interviews and other streams of commerce, as part of its bad faith campaign to discredit IBM's products and services in the marketplace, to increase the perceived value of SCO's limited rights to UNIX and to promote SCO's own UNIX operating systems, UnixWare and Open Server. Denies the allegations of ¶87.Denies the allegations of ¶87.
88 These statements are likely to cause confusion and mistake and have in fact caused confusion and mistake as to the characteristics of IBM's goods, products and/or services. Denies the allegations of ¶88.Denies the allegations of ¶88.
89 As a direct result of SCO's false representations, all of which are in violation of 15 U.S.C. § 1125, IBM has suffered damages in an amount to be determined at trial. IBM is also entitled to damages and attorneys' fees pursuant to 15 U.S.C. § 1117(a). Denies the allegations of ¶89. Denies the allegations of ¶89.
90 Third Counterclaim: Unfair Competition
IBM repeats and realleges the averments in paragraphs 1 through 89, with the same force and effect as though they were set forth fully herein.
Repeats and realleges ¶¶ 1-89, above. Repeats and alleges ¶¶ 1-89, above.
91 IBM has invested over two decades and hundreds of millions of dollars in the creation and development of AIX. Through IBM's efforts, innovation and hard work, AIX has become one of the leading UNIX operating systems, and IBM's products and services are sold and used throughout the United States. Similarly, IBM has invested substantial time and effort in developing its Linux-related products and services. Admits that IBM has expended a substantial investment of time, effort, and money in development of AIX pursuant to the terms of its license with SCO and SCO's predecessors in interest, admits that AIX has become one of the world's leading UNIX operating systems, admits that IBM's products and services are sold and used throughout the United States, admits that IBM acquired Sequent and thereby acquired Sequent's interest in Dynix, subject to the terms and conditions of Sequent's agreements with SCO and/or its predecessors, but denies the remaining allegations of ¶91 not specifically admitted herein. Admits that IBM has expended a substantial investment of time, effort, and money in development o f AIX pursuant to the terms of its license with SCO and SCO's predecessors in interest, admits that AIX has become one of the world's leading UNIX operating systems, admits that IBM's products and services are sold and used throughout the United States, admits that IBM acquired Sequent and thereby acquired Sequent's interest in Dynix, subject to the terms and conditions of Sequent's agreements with SCO and/or its predecessors, but denies the remaining allegations of ¶91 not specifically admitted herein.
92 SCO has intentionally, knowingly, wrongfully and in bad faith engaged in a public pattern of conduct aimed at depriving IBM of the value of its AIX, Dynix and Linux-related products and services and misappropriating the same for the benefit of SCO's Unix licensing business as well as SCO's competing Unix operating systems. SCO's misconduct is likely to result in confusion in the marketplace and has in fact resulted in confusion concerning AIX, Dynix and Linux. Denies the allegations of ¶92. Denies the allegations of ¶92.
93 SCO has engaged in unfair competition by falsely claiming ownership of IBM's intellectual property as well as the intellectual property created by the open-source community; publishing false and disparaging statements about AIX and Dynix; making bad faith misrepresentations concerning IBM's rights to Unix, AIX and Dynix; misusing and misrepresenting SCO's limited rights in Unix to injure IBM; and falsely accusing IBM of theft of SCO's intellectual property. Denies the allegations of ¶93. Denies the allegations of ¶93.
94 As a direct result of SCO's unfair competition, IBM has and will continue to suffer damage to its reputation, goodwill, and business in an amount to be determined at trial. Because SCO's acts of unfair competition were and are willful and malicious, IBM is also entitled to punitive damages. Denies the allegations of ¶94.Denies the allegations of ¶94.
95 Fourth Counterclaim: Intentional Interference with Prospective Economic Relations
IBM repeats and realleges the averments in paragraphs 1 through 94, with the same force and effect as though they were set forth fully herein.
Repeats and realleges ¶¶ 1-94, above. Repeats and realleges ¶¶ 1-94, above.
96 IBM is actively engaged in the development, manufacture and sale of AIX and products and services relating to Linux, and IBM has sold and distributed Dynix. IBM has prospective business relationships with numerous companies and individuals to whom IBM has sold and/or licensed these products and services and/or to whom IBM seeks to sell and/or license these products and services. IBM also has prospective business relationships with business and individual members of the Linux and open-source software development, distribution, service and computing communities with whom IBM seeks to do business in various capacities, including through research and development efforts. Admits the allegations of ¶96. Admits the allegations of ¶96.
97 SCO is fully aware of these prospective business relationships and the importance of the relationships to IBM's continued commercial success. Admits it is generally aware that IBM has or may have certain prospective business relationships that IBM deems important, but denies the remaining allegations of ¶97 not specifically admitted herein. Admits it is generally aware that IBM has or may have certain prospective business relationships that IBM deems important, but denies the remaining allegations of ¶97 not specifically admitted herein.
98 SCO has intentionally interfered with these relationships through improper means, including by making false and misleading statements to IBM's prospective customers that IBM no longer has the right, authority and license to use, produce and distribute AIX, Dynix and Linux-related products. SCO has also misrepresented its own rights relating to these operating systems. The purpose of SCO's unlawful conduct is to injure IBM by driving prospective customers of AIX, Dynix and IBM's Linux-related products and services away from purchasing and licensing the same from IBM. Denies the allegations of ¶98.Denies the allegations of ¶98.
99 Furthermore, SCO has intentionally interfered with IBM's valuable economic relationships with business and individual members of the Linux and open-source software communities by falsely and publicly accusing IBM of inserting "truckloads" of SCO's intellectual property into the Linux kernel and related software. Again, the purpose of SCO's unlawful conduct is to injure IBM by driving away these businesses and individuals from future open-source collaborations with IBM. Denies the allegations of ¶99. Denies the allegations of ¶99.
100 IBM has suffered damages from SCO's tortious interference with its economic relations in an amount to be determined at trial. Because SCO's tortious interference with IBM's prospective economic relations was and is willful and malicious, IBM is entitled to punitive damages. Denies the allegations of ¶100. Denies the allegations of ¶100.
101 Fifth Counterclaim: Unfair and Deceptive Trade Practices
IBM repeats and realleges the averments in paragraphs 1 through 100, with the same force and effect as though they were set forth fully herein.
Repeats and realleges ¶¶ 1-100, above. Repeats and realleges ¶¶ 1-100, above.
102 SCO has engaged in unfair and deceptive trade practices by, among other things, falsely representing that IBM no longer has the right, authority and/or license to use, produce and/or distribute AIX, Dynix and Linux-related products; misrepresenting SCO's and IBM's rights relating to these operating systems; and publishing false and disparaging statements about AIX and Linux. Denies the allegations of ¶ 102. Denies the allegations of ¶102.
103 SCO's false statements and misrepresentations were made in connection with SCO's solicitation of business, and in order to induce IBM and others to purchase products and licenses from SCO. SCO's statements and misrepresentations are likely to cause confusion and misunderstanding as to the qualities, benefits and characteristics of AIX, Dynix and Linux. SCO has misrepresented the qualities, benefits and/or characteristics of these products. Denies the allegations of ¶ 103.Denies the allegations of ¶103.
104 SCO's misconduct was undertaken for the purpose of deceiving the marketplace and defaming IBM and has deceived and misled the public and IBM's customers; disparaged the goods, services, and business of IBM; and otherwise injured IBM's business in violation of N.Y. Gen. Bus. Law § 349 and the laws of other states. Denies the allegations of ¶104.Denies the allegations of ¶104.
105 IBM has provided SCO with notice of its false and misleading statements, and has given SCO an opportunity to correct those statements. SCO has refused and has instead opted to make more false and misleading statements. Denies the allegations of ¶105.Denies the allegations of ¶105.
106 As a direct result of SCO's unfair and deceptive trade practices, the public at large, including AIX, Dynix and Linux users, has been harmed by SCO's campaign to foster fear, uncertainty and doubt about AIX, Dynix and Linux. Moreover, IBM has suffered damages in an amount to be determined at trial. Because SCO's acts of unfair and deceptive trade practices were and are willful, knowing and malicious, IBM is also entitled to treble damages and/or fees pursuant to N.Y. Gen. Bus. Law § 349(h). Denies the allegations of ¶106. Denies the allegations of ¶106.
107 Sixth Counterclaim: Breach of GNU General Public License
IBM repeats and realleges the averments in paragraphs 1 through 106, with the same force and effect as though they were set forth fully herein.
Repeats and realleges ¶¶ 1-106, above. Repeats and realleges ¶¶ 1-106, above.
108 IBM has made contributions of source code to Linux under the GPL on the condition that users and distributors of such code, including SCO, abide by the terms of the GPL in modifying and distributing Linux products, including, for example, the requirement that they distribute all versions of GPL'd software (original or derivative) under the GPL and only the GPL. Admits that IBM has made contributions of source code to Linux under the GPL, but denies the applicability or enforceability of the GPL and denies the remaining allegations of ¶108 not specifically admitted herein. Admits that IBM has made contributions of source code to Linux under the GPL, but denies the applicability or enforceability of the GPL and denies the remaining allegations of ¶108 not specifically admitted herein.
109 SCO has taken source code made available by IBM under the GPL, included that code in SCO's Linux products, and distributed significant portions of those products under the GPL. By so doing, SCO accepted the terms of the GPL (pursuant to GPL § 5), both with respect to source code made available by IBM under the GPL and with respect to SCO's own Linux distributions. Denies the allegations of ¶109. Denies the allegations of ¶109.
110 SCO has breached the GPL by, among other things, copying, modifying, sublicensing or distributing programs licensed under the GPL, including IBM contributions, on terms inconsistent with those set out in the GPL; and seeking to impose additional restrictions on the recipients of programs licensed under the GPL, including IBM contributions, distributed by SCO. Denies the allegations of ¶110. Denies the allegations of ¶110.
111 Based upon its breaches of the GPL and the misconduct described herein, SCO's rights under the GPL, including but not limited to the right to distribute the copyrighted works of others included in Linux under the GPL, terminated (pursuant to § 4 of the GPL). The GPL prohibits SCO from, among other things, asserting certain proprietary rights over, or attempting to restrict further distribution of any program distributed by SCO under the terms of the GPL, except as permitted by the GPL. Denies the allegations of ¶111. Denies the allegations of ¶111.
112 As a result of SCO's breaches of the GPL, countless developers and users of Linux, including IBM, have suffered and will continue to suffer damages and other irreparable injury. IBM is entitled to a declaration that SCO's rights under the GPL terminated, an injunction prohibiting SCO from its continuing and threatened breaches of the GPL and an award of damages in an amount to be determined at trial. Denies the allegations of ¶112. Denies the allegations of ¶112.
113 Seventh Counterclaim: Promissory Estoppel
IBM repeats and realleges the averments in paragraphs 1 through 112, with the same force and effect as though they were set forth fully herein.
Repeats and realleges ¶¶ 1-112, above. Repeats and realleges ¶¶ 1-112, above.
114 SCO made a clear and unambiguous promise to IBM and others that SCO would copy, modify or distribute programs distributed by IBM and others under the GPL only on the terms set out in the GPL; and would not assert rights to programs distributed by SCO under the GPL except on the terms set out in the GPL. Denies the allegations of ¶114. Denies the allegations of ¶114.
115 IBM and others reasonably, prudently and foreseeably relied upon these promises, such as by making contributions under the GPL and committing resources to open-source projects. Denies the allegations of ¶115.Denies the allegations of ¶115.
116 SCO knew or should have known that IBM and others would rely and in fact relied upon SCO's promises and knew or should have known that those promises would induce and in fact induced action or forbearance on the part of IBM and others. Denies the allegations of ¶116. Denies the allegations of ¶116.
117 SCO was and is aware of all material facts relating to IBM's reliance on SCO's promises including but not limited to IBM's contributions under the GPL, SCO's distributions under the GPL and the intent, meaning and import of the GPL. Denies the allegations of ¶117.Denies the allegations of ¶117.
118 As a result of its reliance upon SCO's promises, IBM has sustained injuries and is entitled to an award of damages in an amount to be determined at trial. In addition to an award of damages, IBM is entitled to declaratory and injunctive relief, including but not limited to a declaration that SCO is not entitled to assert proprietary rights with respect to products distributed by SCO under the GPL except upon the terms set out in the GPL. Denies the allegations of ¶118. Denies the allegations of ¶118.
119 Eighth Counterclaim: Copyright Infringement
IBM repeats and realleges the averments in paragraphs 1 through 118, with the same force and effect as though they were set forth fully herein.
Repeats and realleges ¶¶ 1-118, above.Repeats and realleges ¶¶ 1-118, above.
120 As stated, IBM has made contributions of source code to Linux under the GPL. IBM is, and at all relevant times has been, the owner of valid copyrights in these contributions, as well as of all the rights, title and interest in those copyrights. Admits that IBM has made contributions of source code to Linux under the GPL, but denies the applicability or enforceability of the GPL, alleges that part of said contributions by IBM violate SCO's contract and intellectual property rights, and denies the remaining allegations of ¶120 not specifically admitted herein. Admits that IBM made contributions of source code to Linux under the GPL, but denies the applicability or enforceability of the GPL, alleges that part of said contributions by IBM violate SCO's contract and intellectual property rights, and denies the remaining allegations of ¶120 not specifically admitted herein.
121 IBM holds the following certificates of copyright from the United States Copyright Office (copies of which are attached hereto as Exhibits O-U), among others:
Registration No.Date of RegTitle of Work
TX 5-757-696Aug 15, 2003IBM Enterprise Volume Management System
TX 5-757-697Aug 15, 2003IBM Enterprise Class Event Logging
TX 5-757-698Aug 15, 2003IBM Dynamic Probes
TX 5-757-699Aug 15, 2003IBM Linux Support Power PC64
TX 5-757-700Aug 15, 2003IBM Omni Print Driver
TX 5-757-701Aug 15, 2003IBM Journaled File System
TX 5-757-702Aug 15, 2003IBM Next Generation Posix Threading
Is without information sufficient to admit or deny the allegations of ¶121, and therefore denies the same. Is without information sufficient to admit or deny the allegations of ¶121, and therefore denies the same.
122 IBM has placed or caused to be placed a copyright notice on these contributions of source code to Linux under the GPL and has otherwise complied with the copyright laws of the United States in this respect. IBM does not permit the unauthorized copying of its Linux contributions. Admits that IBM has placed copyright notices on certain of its AIX and Dynix contributions to UNIX, but denies it has the legal authority to do so, denies the applicability or enforceability of the GPL, and denies the remaining allegations of ¶122 not specifically admitted herein. Admits that IBM placed copyright notices on certain of its AIX and Dynix contributions to UNIX, but denies it has the legal authority to do so, denies the applicability or enforceability of the GPL, and denies the remaining allegations of ¶122 not specifically admitted herein.
123 IBM granted SCO and others a non-exclusive license to the above-listed copyrighted contributions to Linux on the terms set out in the GPL and only on the terms set out in the GPL. IBM made these contributions on the condition that users and distributors of its copyrighted code, including SCO, abide by the terms of the GPL in copying, modifying and distributing Linux products. Denies the allegations of ¶123. Denies the allegations of ¶123.
124 SCO has infringed and is infringing IBM's copyrights by copying, modifying, sublicensing and/or distributing Linux products except as expressly provided under the GPL. SCO has taken copyrighted source code made available by IBM under the GPL, included that code in SCO's Linux products, and copied modified, sublicensed and/or distributed those products other than as permitted under the GPL. SCO has no right - and has never had any right - to copy, modify, sublicense and/or distribute the IBM copyrighted code except pursuant to the GPL. Denies the allegations of ¶124.Denies the allegations of ¶124.
125 As a result of SCO's infringement, IBM has been damaged and is entitled to an award of actual and/or statutory damages pursuant to 17 U.S.C. § 504 in an amount to be proven at trial. Because SCO's infringement has been willful, deliberate and in utter disregard and derogation of IBM's rights, IBM is entitled to enhanced statutory damages pursuant to 17 U.S.C § 504. IBM is entitled to costs and attorney's fees pursuant to 17 U.S.C. § 505. Denies the allegations of ¶125. Denies the allegations of ¶125.
126 In addition, IBM is entitled to injunctive relief pursuant to 17 U.S.C. § 502, as SCO will continue to infringe IBM's copyrights in violation of the copyright laws othe the United States unless restrained by this Court. IBM is also entitled to an appropriate order pursuant to 17 U.S.C. § 503. Denies the allegations of ¶126.Denies the allegations of ¶126.
127 Ninth Counterclaim: Patent Infringement
IBM repeats and realleges the averments in paragraphs 1 through 126, with the same force and effect as though they were set forth fully herein.
Repeats and realleges ¶¶ 1-126, above. Repeats and realleges ¶¶ 1-126, above.
128 IBM is the lawful owner, by assignment, of the entire right, title and interest in United States Patent No. 4,814,746 ("the `746 Patent"), duly and legally issued on March 21, 1989 to Miller et al., entitled "Data Compression Method". A copy of the `746 Patent is attached hereto as Exhibit V. Is without information sufficient to admit or deny the allegations of ¶128, and therefore denies the same. Is without information sufficient to admit or deny the allegations of ¶128, and therefore denies the same.
129 Upon information and belief, SCO has been and is infringing the `746 Patent within this judicial district and elsewhere by making, using, selling and/or offering to sell products, including UnixWare and Open Server, that practice one or more claims of the `746 Patent and therefore infringe that patent to the extent such infringing acts have occurred or occur during the effective period of that patent. Denies the allegations of ¶129. Denies the allegations of ¶129.
130 Upon information and belief, SCO will continue to infringe the `746 Patent unless enjoined by this Court. Denies the allegations of ¶130. Denies the allegations of ¶130.
131 IBM has been damaged by SCO's infringement of the `746 Patent, has been irreparably harmed by that infringement, and will suffer additional damages and irrevocable harm unless this Court enjoins SCO from further infringement. Denies the allegations of ¶131. Denies the allegations of ¶131.
132 Continued manufacture, use, sale or offer for sale of the infringing products, including UnixWare and Open Server, or evidence that SCO was aware of the `746 Patent, shall render SCO liable for willful infringement, as well as active inducement of infringement of the `746 Patent, making this an exceptional case and justifying the assessment of treble damages pursuant to 35 U.S.C. § 284, and the award of attorneys' fees pursuant to 35 U.S.C. § 285. Denies the allegations of ¶132. Denies the allegations of ¶132.
133 Tenth Counterclaim: Patent Infringement
IBM repeats and realleges the averments in paragraphs 1 through 132, with the same force and effect as though they were set forth fully herein.
Repeats and realleges ¶¶ 1-132, above. Repeats and realleges ¶¶ 1-132, above.
134 IBM is the lawful owner, by assignment, of the entire right, title and interest in United States Patent No. 4,821,211 ("the '211 Patent"), duly and legally issued on April 11, 1989 to Torres, entitled "Method of Navigating Among Program Menus Using a Graphical Menu Tree". A copy of the `211 Patent is attached hereto as Exhibit W. Is without information sufficient to admit or deny the allegations of ¶134, and therefore denies the same. Is without information sufficient to admit or deny the allegations of ¶134, and therefore denies the same.
135 Upon information and belief, SCO has been and is infringing the '211 Patent within this judicial district and elsewhere by making, using, selling, and/or offering to sell products, including SCO Manager, that practice one or more claims of the '211 Patent and therefore infringe that patent to the extent such infringing acts have occurred or occur during the effective period of that patent. Denies the allegations of ¶135. Denies the allegations of ¶135.
136 Upon Information and belief, SCO will continue to infringe the '211 Patent unless enjoined by this Court. Denies the allegations of ¶136.Denies the allegations of ¶136.
137 IBM has been damaged by SCO's infringement of the '211 Patent, has been irreparably harmed by that infringement, and will suffer additional damages and irrevocable harm unless this Court enjoins SCO from further infringement. Denies the allegations of ¶137.Denies the allegations of ¶137.
138 Continued manufacture, use, sale, or offer for sale of the infringing products, including SCO Manager, or evidence that SCO was aware of the '211 Patent, shall render SCO liable for willful infringement, as well as active inducement of infringement of the '211 Patent, making this an exceptional case and justifying the assessment of treble damages pursuant to 35 U.S.C. § 284, and the award of attorneys' fees pursuant to 35 U.S.C. § 285. Denies the allegations of ¶138.Denies the allegations of ¶138.
139 Eleventh Counterclaim: Patent Infringement
IBM repeats and realleges the averments in paragraphs 1 through 138, with the same force and effect as though they were set forth fully herein.
Repeats and realleges ¶¶ 1-138, above. Repeats and realleges ¶¶ 1-139, above.
140 IBM is the lawful owner, by assignment, of the entire right, title and interest in United States Patent No. 4,953,209 ("the '209 Patent"), duly and legally issued on August 28, 1990 to Ryder et al., entitled "Self-Verifying Receipt and Acceptance System for Electronically Delivered Data Objects". A copy of the '209 Patent is attached hereto as Exhibit X. Is without information sufficient to admit or deny the allegations of ¶140, and therefore denies the same. Is without information sufficient to admit or deny the allegations of ¶140, and therefore denies the same.
141 Upon information and belief, SCO has been and is infringing the '209 Patent within this judicial district and elsewhere by making, using, selling and/or offering to sell products, including UnixWare, that practice one or more claims of the '209 Patent and therefore infringe that patent to the extent such infringing acts have occurred or occur during the effective period of that patent. Denies the allegations of ¶141. Denies the allegations of ¶141.
142 Upon information and belief, SCO will continue to infringe the '209 Patent unless enjoined by this Court. Denies the allegations of ¶142. Denies the allegations of ¶142.
143 IBM has been damaged by SCO's infringement of the '209 Patent, has been irreparably harmed by that infringement, and will suffer additional damages and irrevocable harm unless this Court enjoins SCO from further infringement. Denies the allegations of ¶143. Denies the allegations of ¶143.
144 Continued manufacture, use, sale or offer for sale of the infringing products, including UnixWare, or evidence that SCO was aware of the '209 Patent, shall render SCO liable for willful infringement, as well as active inducement of infringement of the '209 Patent, making this an exceptional case and justifying the assessment of treble damages pursuant to 35 U.S.C. § 284, and the award of attorneys' fees pursuant to 35 U.S.C. § 285. Denies the allegations of ¶144. Denies the allegations of ¶144.
145 Twelfth Counterclaim: Patent Infringement
IBM repeats and realleges the averments in paragraphs 1 through 144, with the same force and effect as though they were set forth fully herein.
Repeats and realleges ¶¶ 1-144, above. Repeats and realleges ¶¶ 1-144, above.
146 IBM is the lawful owner, by assignment, of the entire right, title and interest in United States Patent No, 5,805,785 ("the '785 Patent"), duly and legally issued on September 8, 1998 to Dias et al., entitled "Method for Monitoring and Recovery of Subsystems in a Distributed/Clustered System". A copy of '785 Patent is attached hereto as Exhibit Y. Is without information sufficient to admit or deny the allegations of ¶146, and therefore denies the same. Is without information sufficient to admit or deny the allegations of ¶146, and therefore denies the same.
147 Upon information and belief, SCO has been and is infringing the '785 Patent within this judicial district and elsewhere by making, using, selling and/or offering to sell products, including Reliant HA, that practice one or more claims of the '785 Patent and therefore infringe that patent to the extent such infringing acts have occurred or occur during the effective period of that patent. Denies the allegations of ¶147. Denies the allegations of ¶147.
148 Upon information and belief, SCO will continue to infringe the '785 Patent unless enjoined by this Court. Denies the allegations of ¶148. Denies the allegations of ¶148.
149 IBM has been damaged by SCO's infringement of the '785 Patent, has been irreparably harmed by that infringement, and will suffer additional damages and irrevocable harm unless this Court enjoins SCO from further infringement. Denies the allegations of ¶149.Denies the allegations of ¶149.
150 Continued manufacture, use, sale or offer for sale of the infringing products, including Reliant HA, or evidence that SCO was aware of the '785 Patent, shall render SCO liable for willful infringement, as well as active inducement of infringement of the '785 Patent, making this an exceptional case and justifying the assessment of treble damages pursuant to 35 U.S.C. § 284, and the award of attorneys' fees pursuant to 35 U.S.C. § 285. Denies the allegations of ¶150. Denies the allegations of ¶150.
151 Thirteenth Counterclaim: Declaratory Judgment
IBM repeats and realleges the averments in paragraphs 1 through 150, with the same force and effect as though they were set forth fully herein.
Repeats and realleges ¶¶ 1-150, above.Repeats and realleges ¶¶ 1-150, above.
152 SCO has breached its contractual obligations to IBM, violated the Lanham Act, engaged in unfair competition, interfered with IBM's prospective economic relations, engaged in unfair and deceptive practices, breached the GPL, infringed IBM copyrights and infringed IBM patents, as stated above. Denies the allegations of ¶152. Denies the allegations of ¶152.
153 Pursuant to 28 U.S.C. § 2201, IBM is entitled to declaratory relief with respect to SCO's and IBM's rights, including among other things a declaration that SCO has violated IBM's rights as outlined above by breaching its contractual obligations to IBM, violating the Lanham Act, engaging in unfair and deceptive practices, breaching the GPL, infringing IBM copyrights and infringing IBM patents, and is estopped as outlined above. Denies the allegations of ¶153.Denies the allegations of ¶153.
154 Moreover, IBM is entitled to a declaration that (1) SCO has no right to assert, and is estopped from asserting, proprietary rights over programs that SCO distributed under the GPL except as permitted by the GPL; (2) SCO is not entitled to impose restrictions on the copying, modifying or distributing of programs distributed by it under the GPL except as set out in the GPL; and (3) any product into which SCO has incorporated code licensed pursuant to the GPL is subject to the GPL and SCO may not assert rights with respect to that code except as provided by the GPL. Denies the allegations of ¶154. Denies the allegations of ¶154.
155 There is a justiciable controversy between IBM and SCO with respect to all of the issues described above. Denies the allegations of ¶155.Denies the allegations of ¶155.
156 Absent declaratory relief, SCO's misconduct will continue to cause injury to IBM, the open-source community and the public at large. Denies the allegations of ¶156. Denies the allegations of ¶156.

FIRST AFFIRMATIVE DEFENSE
IBM fails to state a claim upon which relief may be granted.
FIRST AFFIRMATIVE DEFENSE
IBM fails to state a claim upon which relief may be granted.
SECOND AFFIRMATIVE DEFENSE
IBM claims are barred by the doctrines of waiver, estoppel, acquiescence, and/or laches.
SECOND AFFIRMATIVE DEFENSE
IBM's claims are barred by the doctrines of waiver, estoppel, acquiescence, and/or latches.
THIRD AFFIRMATIVE DEFENSE
IBM's contractual right to license, distribute or use AIX or Dynix has been properly and validly terminated, and any claim based thereon is barred.
THIRD AFFIRMATIVE DEFENSE
IBM's contractual right to license, distribute or use AIX or Dynix has been properly and validly terminated, and any claim based thereon is barred.
FOURTH AFFIRMATIVE DEFENSE
IBM's claims are barred by license.
FOURTH AFFIRMATIVE DEFENSE
IBM's claims are barred by license.
FIFTH AFFIRMATIVE DEFENSE
IBM's claims are barred by fraud, illegality, collusion, conspiracy and/or lack of clean hands.
FIFTH AFFIRMATIVE DEFENSE
IBM's claims are barred by illegality, collusion, conspiracy and/or lack of clean hands.
SIXTH AFFIRMATIVE DEFENSE
The General Public License ('GPL') is unenforceable, void and/or voidable, and IBM's claims based thereon, or related thereto, are barred.
SIXTH AFFIRMATIVE DEFENSE
The General Public License ("GPL") is unenforceable, void and/or voidable, and IBM's claims therein, or related thereto, are barred.
SEVENTH AFFIRMATIVE DEFENSE
The GPL is selectively enforced by the Free Software Foundation such that enforcement of the GPL by IBM or others is waived, estopped or otherwise barred as a matter of equity.
SEVENTH AFFIRMATIVE DEFENSE
The GPL is selectively enforced by the Free Software Foundation such that enforcement of the GPL by IBM or others is waived, estopped or otherwise barred as a matter of equity.
EIGHTH AFFIRMATIVE DEFENSE
The GPL violates the U.S. Constitution, together with copyright, antitrust and export control laws, and IBM claims based thereon, or related thereto, are barred.
EIGHT AFFIRMATIVE DEFENSE
The GPL violates the U.S. Constitution, together with copyright, antitrust and export control laws, and IBM's claims based thereon, or related thereto, are barred.
NINTH AFFIRMATIVE DEFENSE
IBM claims are barred, in whole or in part, by the First Amendment to the U.S. Constitution, by the doctrine of judicial immunity and by privilege.
NINTH AFFIRMATIVE DEFENSE
IBM's claims are barred, in whole or in part, by the First Amendment to the U.S. Constitution, by the doctrine of judicial immunity and by privilege.
TENTH AFFIRMATIVE DEFENSE
IBM lacks standing to assert these claims.
TENTH AFFIRMATIVE DEFENSE
IBM lacks standing to assert these claims.
ELEVENTH AFFIRMATIVE DEFENSE
IBM's claims are barred or preempted, in whole or in part, by the laws of the United States.
ELEVENTH AFFIRMATIVE DEFENSE
IBM's claims are barred or preempted, in whole or in part, by the laws of the United States.
TWELFTH AFFIRMATIVE DEFENSE
IBM's own conduct, including that of its agents, contractors and partners, and/or conduct of third parties constitute superseding or intervening causes with respect to IBM's claims of damage or injury.
TWELFTH AFFIRMATIVE DEFENSE
IBM's own conduct, including that of its agents, contractors and partners, and/or conduct of third parties constitute superseding or intervening causes with respect to IBM's claims of damage or injury.
THIRTEENTH AFFIRMATIVE DEFENSE
SCO has acted legally and properly at all relevant times and IBM is therefore barred from any relief whatsoever.
THIRTEENTH AFFIRMATIVE DEFENSE
SCO has acted legally and properly at all relevant times and IBM is therefore barred from any relief whatsoever.
FOURTEENTH AFFIRMATIVE DEFENSE
IBM's purported copyright registrations are invalid and/or IBM has violated copyright laws in respect to its claims alleged and the claims based on, or related to, copyrights are barred.
FOURTEENTH AFFIRMATIVE DEFENSE
IBM's purported copyright registrations are invalid and/or IBM has violated copyright laws in respect to its claims alleged and the claims based on, or related to, copyrights are barred.
FIFTEENTH AFFIRMATIVE DEFENSE
On information and belief, one or more of the copyrights at issue is, or may be, unenforceable by reason of IBM's inequitable conduct, acts or omissions before the United States Patent and Trademark Office.
[No equivalent to dropped affirmative defense.]
SIXTEENTH AFFIRMATIVE DEFENSE
IBM is not, or may not be, the owner of the #746, #211, #209 or #785 Patents at issue.
FIFTEENTH AFFIRMATIVE DEFENSE
IBM is not, or may not be, the owner of the '746, '211, '209, or '785 Patents at issue.
SEVENTEENTH AFFIRMATIVE DEFENSE
The patents at issue, and particularly the claims of those patents alleged to be infringed, are invalid and of no effect for failure to comply with one or more requirements set forth in Title 35 of the United States Code, including, but not limited to Sections 101, 102, 103 and/or 112.
SIXTEENTH AFFIRMATIVE DEFENSE
The patents at issue, and particularly the claims of those patents alleged to be infringed, are invalid and of no effect for failure to comply with one or more requirements set forth in Title 35 of the United States Code, including, but not limited to Sections 101, 102, 103, 112, 116, and/or 256.
EIGHTEENTH AFFIRMATIVE DEFENSE
On information and belief, IBM's claims under the patents at issue are precluded by the doctrine of prosecution history estoppel based on the admissions and representations made by IBM in proceedings before the United States Patent and Trademark Office during the prosecution of the applications of the patents at issue.
SEVENTEENTH AFFIRMATIVE DEFENSE
On information and belief, IBM's claims under the patents at issue are precluded by the doctrine of prosecution history estoppel based on the admissions and representations made by IBM in proceedings before the United States Patent and Trademark Office during the prosecution of the applications of the patents at issue.
NINETEENTH AFFIRMATIVE DEFENSE
On information and belief, the #746 Patent or one or more of the other patents at issue is, or may be, unenforceable by reason of IBM's inequitable conduct, acts or omissions before the United States Patent and Trademark Office.
EIGHTEENTH AFFIRMATIVE DEFENSE
On information and belief, U.S. Patent 4,814,746 ("the '746 patent") is unenforceable by reason of IBM's inequitable conduct, acts or omissions before the U.S. Patent and Trademark Office ("PTO"). The '746 patent, in the section entitled "Background of the Invention," cites one article directed to LZ78 data compression and indicates that it is representative of the prior art. U.S. Patent No. 4,814,746, column 1, lines 13-27. That statement is material, false and misleading and was known by IBM to be material, false and misleading. In fact, the single article cited in the '746 patent is not representative of the prior art. There are numerous other techniques such as LZ77, described in an article entitled "A Universal Algorithm For Sequential Data Compression," IEEE Transactions on Information Theory, Vol. IT-23, No. 3, May 1977, pp. 337-343. Other types of prior art data compression methods include run length encoding, arithmetic encoding and Huffman encoding. The falsity of IBM's statements is also reflected by the fact that in the period from December 9, 1975, to March 1, 1983, IBM itself obtained the issuance of at least 31 patents directed to data compression.

On September 22, 1988, during prosecution of the continuation patent application which led to issuance of the '746 patent, IBM filed an Information Disclosure Statement ("IDS") with the PTO. That IDS disclosed European Patent Office ("EPO") patent publication 129439. The inventor of that patent publication was Terry Welch. The patent publication was published on December 27, 1984. Inexplicably, while IBM mentioned the United States counterpart of the EPO publication, it did not cite that counterpart in the citation of prior art. Thus, the face of the '746 patent does not contain any reference to the U.S. counterpart. That counterpart was U.S. Patent No. 4,558,302. That patent contains claims which overlap with the '746 patent. The Welch U.S. Patent No. 4,558,302 was filed 19 days after the '746 patent was filed in the PTO. The closeness of these dates implicates 35 U.S.C. § 102(g) and raises serious question as to who was the first inventor of the claimed subject matter and who is entitled to the patent. The failure to cite the U.S. counterpart, the fact that IBM waited almost three years after the U.S. counterpart issued as a patent to even inform the PTO of the EPO publication, and the additional fact that IBM waited until after the claims of the '746 patent were allowed to file an IDS, were intended to deter the Patent Examiner from comparing the claims of the U.S. counterpart to the allowed claims of the '746 patent. These actions were material to the examination of the '746 patent.

IBM's IDS states that the U.S. counterpart patent "apparently is an improvement on the teaching of [another reference] and offers nothing more that would affect the patentability of the allowed claims in this case. ["] These statements were material, false and misleading and were known by IBM to be material, false and misleading. These statements and the fact that IBM cited the EPO publication and not the U.S. patent counterpart had the effects of not only mischaracterizing the disclosure of the Welch patent application, but also of concealing from the PTO the overlap between the claimed subject matter of the '746 patent and the counterpart U.S. patent.

IBM withheld additional prior art from the PTO. In February, 1981, IBM published an article entitled "Message Compression Method." The article was published as an IBM Technical Disclosure Bulletin, Volume 23, No. 9, pages 4197-98. That publication was material to the patentability of the '746 patent. IBM withheld this prior art with intent to deceive the PTO.

On information and belief, IBM was aware prior to the issuance of the '746 patent, of U.S. Patent No. 4,366,551, issued December 28, 1982, to Klaus E. Holz. This patent is material to the patentability of the claims of the '746 patent. On information and belief, IBM's intentional failure to disclose this prior art to the PTO was part of IBM's scheme to withhold material prior art.

On information and belief, U.S. Patent 5,805,785 ("the '785 patent") is unenforceable by reason of IBM's inequitable conduct, acts or omissions before the PTO. The '785 patent, entitled "Method for Monitoring and Recovery of Subsystems in a Distributed/Clustered System," was filed on February 27, 1996, listing as joint inventors Daniel Manuel Dias, Richard Pervin King, and Avraham Leff. Applicants also filed an IDS on this date. The IDS listed 12 references that are all U.S. patents. No other references, including technical papers authored by one or more of the joint inventors were listed. A review of papers authored by the three inventors reveals several that are material to patentability. In particular, Avraham Leff's Ph.D dissertation, entitled "A Dynamic and Decentralized Approach to Management of CPU and Memory," published at Columbia University in 1992, is material to the patentability of the '785 patent application. The dissertation describes a system of resource management that does not require a centralized coordinator. Sites cooperate in transmitting important state information to each other. Decisions made at one site are then factored by other sites into subsequent decisions. Because this dissertation was material to the patentability of the '785 patent application, the dissertation should have been disclosed to the PTO during prosecution of the '785 patent application. IBM withheld this reference with the intent to deceive the PTO.

Inventor Daniel M. Dias appears as joint author on three papers that relate directly to the subject matter claimed in the '785 patent. These three papers appear to have been published at about the same time as the '785 patent filing date of February, 1996. All three papers list joint authors, none of whom, other than Mr. Diaz, appears as an inventor on the '785 patent. "A Scalable and Highly Available Web Server," published in Proceedings of COMPCON '96, lists as authors, in addition to Mr. Dias, William Kish, Rajat Mukherjee, and Renu Tewari. "High Availability in Clustered Multimedia Servers," published in Proceedings -- International Conference on Data Engineering 1996, lists as authors, in addition to Mr. Dias, Renu Tewari, Rajat Mukherjee, and Harrick Vin. "Design and Performance Tradeoffs in Clustered Video Servers," published in Proceedings -- International Conference on Multimedia Computing and Systems 1996, lists as authors, in addition to Mr. Dias, Renu Tewari, Rajat Mukherjee, and Harrick Vin. All three of these papers describe concepts that can be found in the '785 patent claims, and thus Messrs. Kish, Mukherjee, Tewari, and Vin should have been listed as inventors on the '785 patent. IBM's decision not to list Messrs. Kish, Mukherjee, Tewari, and Vin as inventors on the '785 patent was with the intent to deceive the PTO.

U.S. Patent 5,129,080 ('[sic] the '080 patent"), entitled "Method and System Increasing the Operational Availability of a System of Computer Programs Operating in a Distributed System of Computers," filed October 17, 1990, issued July 7, 1992, and assigned to IBM, is material to patentability of the '785 patent, and should have been disclosed by IBM to the PTO. In particular, the '080 patent discloses high availability architectures, cooperative processing among nodes of a computer network, and fault recovery techniques. The '080 patent also discloses sharing of state information among the computer network nodes and global and local management. Because the '080 patent is material to patentability of the '785 patent application, the '080 patent should have been disclosed to the PTO during prosecution of the '785 patent application. IBM withheld this reference with the intent to deceive the PTO.

On information and belief, U.S. Patent 4,821,211 ("the '211 patent") is unenforceable by reason of IBM's inequitable conduct, acts or omissions before the PTO. The '211 patent was filed on November 19, 1987 and issued April 11, 1989. During prosecution of the '211 patent application, Applicants did not disclose any prior art references to the PTO through filing an IDS. On information and belief, Applicants were aware of prior art references that were material to patentability of the '211 patent, and which, therefore, were required to be disclosed to the U.S. Patent and Trademark Office.

More specifically, U.S. Patent 4,688,181 to Cottrell et al. ("the '181 patent"), filed April 30, 1986 and issued August 18, 1987, and assigned to IBM was material to the patentability of the '211 patent, but was not disclosed to the PTO. The '181 patent was cited by the patent examiner during prosecution of the '211 patent. Further, the '181 patent listed a number of prior art references that were themselves material to patentability of the '211 patent. These additional prior art references were not disclosed to the PTO during prosecution of the '211 patent. One of the prior art references cited during the Cottrell patent application prosecution is U.S. Patent 4,613,946 to Forman ("the '946 patent"). That patent was also material to the patentability of the '211 patent. Thus the '946 patent, and the other references cited during prosecution of the Cottrell patent application should have been disclosed to the PTO by IBM. IBM withheld these material references with the intention to deceive the PTO.

On information and belief, IBM was aware of other references that were material to the patentability of the '211 patent, and with deceptive intent, IBM did not disclose these references to the PTO. For example, U.S. Defensive Publication T980,008 ('[sic]the '008 publication"), entitled "Interactive Design of Character-Recognition Logics," filed July 19, 1976, published March 6, 1979, and assigned to IBM, is material to the patentability of the '211 patent, and should have been disclosed by IBM to the PTO. The '008 publication discloses generating graphic display of pattern locations and a menu of operations. The '008 publication also discloses using auxiliary operations in the menu to modify the sequence of input patterns. Because the '008 publication is material to the patentability of the '211 patent, the '008 publication should have been disclosed to the PTO during prosecution of the '211 patent. IBM withheld this reference with intent to deceive the PTO.

Other references of which IBM was aware and that were required to be disclosed to the PTO include U.S. Patent 4,731,606 to Bantz et al. ("the '606 patent["]), filed August 2, 1985 and issued March 15, 1988 and U.S. Patent 4,719,571 to Rissanen et al. ("the 571 patent"), filed March 5, 1986 and issued January 12, 1988, both assigned to IBM. Both the '606 patent and the '571 patent are material to patentability of the '211 patent, and both should have been disclosed to the PTO during prosecution of the '211 patent. IBM withheld these references with the intent to deceive the U.S. Patent and Trademark Office.

On information and belief, U.S. Patent 4,953,209 ("the '209 patent") is unenforceable by reason of IBM's inequitable conduct, acts or omissions before the PTO. The '209 patent, entitled "Self-verifying Receipt and Acceptance system for Electronically Delivered Data Objects," was filed on October 31, 1988. The '209 patent, in the section entitled "Background of the Invention," describes only two prior art references: U.S. Patent No. 4,757,533 to Allen et al. and U.S. Patent No. 4,757,534 ("the '534 patent") to Stephen M. Matyas et al.

The '534 patent is assigned to IBM. Stephen M. Matyas, co-inventor of the '534 patent, is listed as an author of more than 100 IBM publications related to cryptography or data encryption. Mr. Matyas is also listed as an inventor on more than 70 issued patents in this field. Mr. Matyas is well known in the field of cryptography and data encryption at IBM. When the '209 patent application was filed, IBM knew that some of Mr. Matyas' activities were material to the patentability of the '209 patent. However, as noted above, only the '534 patent was listed. IBM failed to cite other material prior art references associated with Mr. Matyas, including, for example, U.S. Patent 4,203,166 ("the '166 patent") in which Mr. Matyas is listed as an inventor. The '166 patent, entitled "Cryptographic File Security for Multiple Domain Networks," filed December 5, 1977, issued May 13, 1980, and assigned to IBM, is material to patentability of the '209 patent, and should have been disclosed by IBM to the PTO.

The '166 patent discloses a file security system for data files created at a first host system in one domain and recovered at a second host system in another domain of a multiple domain network. Specifically, the '166 patent discloses,[sic] a first host system that provides a file recovery key for subsequent recovery of a data file at a second host system. The first host system enciphers (modifies) the first host system plaintext to obtain first host system ciphertext as the data file. The file recovery key is used as header information for the data file. When the data file is to be recovered at the second host system, the file recovery key is provided at the second host system and the second host system transforms the file recovery key into a form, which is usable to decipher the data file. The second host system uses the transformed file recovery key to perform a cryptographic operation to obtain the first host system ciphertext in clear form (unmodified) at the second host system. Thus, the '166 patent is material to the patentability to the claims of the '209 patent. Because the '166 patent is material to the patentability of the '209 patent, the '166 patent should have been disclosed to the PTO during prosecution of the '209 patent. IBM withheld this reference with the intention to deceive the PTO.

IBM also failed to cite U.S. Patent 4,238,854 ("the '854 patent") in which Mr. Matyas is again listed as an inventor. The '854 patent, entitled "Cryptographic File Security for Single Domain Networks," filed December 5, 1977, issued December 9, 1980, and assigned to IBM, is material to patentability of the '209 patent, and should have been disclosed by IBM to the PTO. The '854 patent was filed concurrently with the '166 patent described above.

The '854 patent discloses that an operational key enciphered under the file key of the designated storage media, as header information, together with the host data enciphered under the operational key is written on the storage media as an enciphered data file. When the data file is recovered, the host data security device transforms the enciphered operational key header information under control of a host master key into a form which permits the operational key to be used for deciphering the enciphered data file to obtain the file data in clear form. Thus, the '854 patent is material to the patentability to the claims of the '209 patent. Because the '854 patent is material to the patentability of the '209 patent, the '854 patent should have been disclosed to the PTO during prosecution of the '209 patent. IBM withheld this reference with the intention to deceive the PTO.

Matyas is also one of the authors of an article entitled "Cryptographic Key Authentication in Communication System" published by IBM in March, 1978. The article was published as an IBM Technical Disclosure Bulletin, March 1978, pages 3990-92. This publication discloses that message communication protection is obtained by enciphering a clear data message X at a host under control of a working key KS to yield a ciphered data message Y. At the receiving terminal, the enciphered data message Y is deciphered under control of the working key KS to yield the clear data message X.

Another article in which Matyas is an author is entitled "Terminal Control of Encipher and Decipher Data Operations" published by IBM in August, 1981. The article was published as an IBM Technical Disclosure Bulletin, August, 1981, pages 1334-1339..[sic] This publication discloses that in communication security applications where data is to be transmitted in a cryptographic session, between a host unit and a remote terminal controller unit, a data encrypting session key (KS) is required to be established in a form suitable for use at each unit. Data may then be enciphered under KS at one unit and transmitted to the other unit where it is deciphered under KS.

Thus, the above publications, published as IBM Technical Disclosure Bulletins, are material to the patentability to the claims of the '209 patent. Because these publications are material to the patentability of the '209 patent, these articles should have been disclosed to the PTO during prosecution of the '209 patent. IBM withheld these references with the intention to deceive the PTO.

The foregoing actions constitute inequitable conduct and render the claims of the '746, '785, '211, and '209 patents unenforceable. Discovery in this proceeding is ongoing, and additional acts of inequitable conduct will be added to this defense at the appropriate time.

TWENTIETH AFFIRMATIVE DEFENSE
SCO has not infringed, literally or under the doctrine of equivalents, any valid claim of the #746, #211, #209 and #785 Patents.
NINTEENTH AFFIRMATIVE DEFENSE
SCO has not infringed, literally or under the doctrine of equivalents, any valid or enforceable claim of the '746, '211, '209 and '785 Patents.
TWENTY FIRST AFFIRMATIVE DEFENSE
On information and belief, IBM failed to mark patent articles covered by the #746, #211, #209 and/or #785 Patents at issue in the counterclaims. Any claim for damages is therefore limited by 35 U.S.C. Section 287.
TWENTIETH AFFIRMATIVE DEFENSE
On information and belief, IBM failed to mark patent articles covered by the '746, '211, '209 and/or '785 Patents at issue in the counterclaims. Any claim for damages is therefore limited by 35 U.S.C. §287.
TWENTY SECOND AFFIRMATIVE DEFENSE
On information and belief, IBM failed to provide SCO with actual notice of IBM's allegations of infringement of the patents at issue, and therefore IBM cannot recover any damages for SCO's actions before the filing of IBM's counterclaims.
TWENTY FIRST AFFIRMATIVE DEFENSE
On information and belief, IBM failed to provide SCO with actual notice of IBM's allegations of infringement of the patents at issue, and therefore IBM cannot recover any damages for SCO's actions before the filing of IBM's counterclaims.
TWENTY THIRD AFFIRMATIVE DEFENSE
IBM has not and cannot plead and meet the requirements for an award of enhanced damages or attorneys' fees.
TWENTY SECOND AFFIRMATIVE DEFENSE
IBM has not and cannot plead and meet the requirements for an award of enhanced damages or attorneys' fees.
TWENTY FOURTH AFFIRMATIVE DEFENSE
SCO has an express or implied license to practice some or all of the claims embodied in the patents at issue.
TWENTY THIRD AFFIRMATIVE DEFENSE
SCO has an express or implied license to practice some or all of the claims embodied in the patents at issue.
TWENTY FIFTH AFFIRMATIVE DEFENSE
Upon information and belief, IBM lacks standing to assert that SCO infringed some or all of the patents at issue.
TWENTY FOURTH AFFIRMATIVE DEFENSE
Upon information and belief, IBM lacks standing to assert that SCO infringed some or all of the patents at issue.
[No equivalent.] TWENTY FIFTH AFFIRMATIVE DEFENSE
SCO states that IBM's request for treble damages and attorneys fees is barred because SCO acted in good faith, and this is not an exceptional case within the meaning of the Patent Code.
TWENTY SIXTH AFFIRMATIVE DEFENSE
IBM has failed to join one or more parties needed for just adjudication of the counterclaims, including but not limited to the Free Software Foundation and contributors to the Linux 2.4 and 2.5 kernels.
TWENTY SIXTH AFFIRMATIVE DEFENSE
IBM has failed to join one or more parties needed for just adjudication of the counterclaims, including but not limited to the Free Software Foundation and contributors to the Linux 2.4 and 2.5 kernels.


  


Comparative Charts - IBM Counterclaims and SCO's Answers and Affirmative Defenses | 289 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Errors Here in this Thread Please
Authored by: PJ on Sunday, March 14 2004 @ 05:18 AM EST
Please record my mistakes for posterity here in this thread, so I can find them

easily. Thanks.

[ Reply to This | # ]

Comparative Charts - IBM Counterclaims and SCO's Answers and Affirmative Defenses
Authored by: jbeadle on Sunday, March 14 2004 @ 06:18 AM EST
Thanks to whoever did this (again)!!

-jb

[ Reply to This | # ]

Comparitive Charts for Patents
Authored by: Anonymous on Sunday, March 14 2004 @ 06:28 AM EST
This talk of patents makes me wonder how hard of a job would it be to assess
what patents Linux might be infinging, rate their danger index, and what can be
done to protect Linux from those patent lawsuits.

I also wonder what a side by side chart of MS's patents and IBM's patents, a
rating on how strong each patent is, how much each other infinges on the other's
patents without proper remedy, and who trumps who overall if a patent war were
to break out.

An idea for a Groklaw Jr. might be a dedicated forum to analyse the risker
patents and to either nullify them or find a way to protect Linux from them.

I also think we should start thinking about organizing ourselves into more
cohesive group so we can start focusing our strengths, talents, and energy into
one very very powerful voice.

Linux is millions strong, and a very large portion of them are passionate about
Linux (for good reasons we already know :). This is where SCO really screwed up
in their calculations of the Linux community. I think in their minds, the
community was a lot more loose knit than it was. We may not be focused, but we
share common ground we are willing to fight for. And when the attack came, the
defense wasn't a few scattered groups, but many many many over-lapping voices
that formed a wall SCO is smashing themselves against.

Do you think we could form an Open Source political and lobbying party? If this
is possible, I could see a political and social revolution. How many times has
it been the little man out there wants the playing field to be leveled? How
many times are we put down because we are not in power? How would politicians
operate as they do now if the government was open source? I think a lot of the
lying and BS we live with now would go away if there were no/little secrets in
the government.

[ Reply to This | # ]

Comparative Charts - IBM Counterclaims and SCO's Answers and Affirmative Defenses
Authored by: Anonymous on Sunday, March 14 2004 @ 06:39 AM EST
Sorry - is this the right context to contest a patent - is the judge in this
case able to make a judgement on the validity of the patents?

Shouldn't SCOG be fighting that in some other place that is geared towards
patents?

Until the patent is overturned or set aside, or whatever they do with invalid
patents, by the patents office surely it stands? Or are they trying to set up
delaying this case further until they get around to contesting the patent
successfully?

I admit to NOT reading all of the above, my hats off to lawyers and judges who
have to read and digest such dry, boring, naterial in the course of their jobs

[ Reply to This | # ]

Who should I cheer for?
Authored by: poncewattle on Sunday, March 14 2004 @ 06:47 AM EST
I fear software patents. Recent events point to software patents as being Microsoft's next attack dog. So, who do I cheer for? :-(

I suppose whether or not IBM wins this one will not impact the larger issue with software patents either way, so I therefore should cheer for IBM.

I'm going to feel awfully dirty.

[ Reply to This | # ]

Reseach techniques
Authored by: Anonymous on Sunday, March 14 2004 @ 06:51 AM EST
In this thread, I would like other's to share with everyone some of their
research techniques so we can better utilize those that want to participate but
can only offer opinion due to a lack of knowing how to pursue the information we
need to fight SCO and other dangers.

For instance, as for finding news, I find Google's news site to be and excellent
way to find many many sources on the same topic. The have a search feature and
a simple term like Linux will turn up hundreds of articles. Plus, Google is up
to date with many news sites. So you can read 10 different articles about the
same thing, and glean new insight and information that wouldn't be possible from
reading the headlines from one source.

This is just one way. Can anyone else suggest websites that are good to look
at. Any ideas on how to parse information for what is relevant. Maybe we can
include ideas here so we can make our investigation more efficient and
meaningful. Especially so those that are doing the legwork like PJ is and won't
have to work nearly as much or as hard to produce quality research.

One idea is to finally code permenant sticky threads, for errata, new urls and
news, relevant questions, genral opinions, trolling, OT posts, etc. so there is
more structure to the threads. As it is now, the general comments, the me too
comments, PJ rocks comments (as nice as they are), and any other comment that
doesn't contribute to what is going on at hand is making the site inefficient.
I, too, don't want to see any post get deleted at all (except those that pose a
danger such as posting someone else's personal info), but as it is now, the
posting structure adds a whole lot more work for everyone involved.

[ Reply to This | # ]

Relevance?
Authored by: cheros on Sunday, March 14 2004 @ 06:53 AM EST
I'm going to ask the luddite question here: isn't all this
debate about detail just a distraction from the main
claims?

It starts to feel like we'll end up with a third level
removed argument about spelling mistakes instead..

[ Reply to This | # ]

OT. Watch this space.
Authored by: tintak on Sunday, March 14 2004 @ 07:19 AM EST
Interesting news for M4 watchers.

http://www.theinquirer.net/?article=14713

---
'it is literally impossible' for SCO to itself provide
direct proof' Mark J. Heise 02/06/04

[ Reply to This | # ]

Comparative Charts - IBM Counterclaims and SCO's Answers and Affirmative Defenses
Authored by: the_flatlander on Sunday, March 14 2004 @ 07:22 AM EST
For a discussion of the patent defenses, have a look at the comments made by one Groklaw reader: Cesar Rincon

He made 3 comments regarding the patents and seemed quite well-versed on the prior art issue. To a "patent-challenged" reader like me, the SCOundrels' claims look a little worrisome, but the good Mr. Rincon's comments provide comfort. Links to the comments themselves don't appear to take one to the comments, only to the top of the comments section of the article.

The Flatlander

Groklaw: The Community's Mind and Memory, upgraded.

[ Reply to This | # ]

OT: What to Do if SCO Comes Knocking
Authored by: Avenger on Sunday, March 14 2004 @ 08:10 AM EST
Sorry, i haven't seen this link on groklaw yet:

http://www.internetnews.com/bus-news/article.php/3325411

[ Reply to This | # ]

What trade secrets?
Authored by: Anonymous on Sunday, March 14 2004 @ 09:17 AM EST
Response #53 still maintains that IBM has disclosed some of SCO's trade secrets.
If I recall correctly SCO has stated that there are no trade secrets in System
V. They did say that the trade secrets were from the Monterey project, but I
have yet to see a single reference to any specific trade secret. The only code
I have seen discussed other than code alleged to have been copied from SysV code
is Dynix/AIX code that SCO admits were written by Sequent and IBM. As I
understand the law concerning trade secrets, it serves to protect the CREATOR of
the trade secret. Is there any way that SCO could claim violation of trade
secret laws unless they specifically demonstrate some unique element derived
from SCO's contribution to project Monterey?

[ Reply to This | # ]

  • No - Authored by: Anonymous on Sunday, March 14 2004 @ 11:38 PM EST
Comparative Charts - IBM Counterclaims and SCO's Answers and Affirmative Defenses
Authored by: Bill The Cat on Sunday, March 14 2004 @ 09:42 AM EST
SEVENTH AFFIRMATIVE DEFENSE
The GPL is selectively enforced by the Free Software Foundation such that enforcement of the GPL by IBM or others is waived, estopped or otherwise barred as a matter of equity.
This may carry some weight. The FSF is going to have to attempt to control its rights or it can forever lose them. In many cases -- especially trademarks, if you don't attempt to protect your mark, you can end up without one.

So if the FSF is aware of infringement and does nothing to try and reign it in, then it is possible the courts could rule that since they knew and did nothing that it is all right.

---
Bill Catz

[ Reply to This | # ]

SCOG must be bleeding cash --- how much
Authored by: mandalay on Sunday, March 14 2004 @ 09:55 AM EST
SCOG must be bleeding cash to put up all this defense as well as the other
lawsuits it is pursuing. I wonder if you can correlate the length of the court
documents submitted and the cost per word --- then perhaps you can estimate the
amount they have spent on lawsuits, which so far, they have maintained as
confidential.


[ Reply to This | # ]

Groklaw's MasterWork!
Authored by: Anonymous on Sunday, March 14 2004 @ 10:45 AM EST
Congratulations to all groklawers. But the best appreciation can come only from
the opposition - more FUD against Groklaw and PJ. When is M$ going to do it?

This is one of the best collaborative efforts I've seen. I have developed
immense respect for all the groklawers and PJ. Thank you.

[ Reply to This | # ]

Comparative Charts - IBM Counterclaims and SCO's Answers and Affirmative Defenses
Authored by: Anonymous on Sunday, March 14 2004 @ 11:39 AM EST
I'm not trying to troll here, but hinging our hopes on IBM's software patents
being valid seems shortsighted. Considering how everyone says Software Patents
are the next Evil that Free Software has to face, shouldn't we be hoping that
they don't work out? Also it seems sort of optimistic to think that IBM, holder
of 10 billion+ patents, didn't rush some of them through the patent offices. I
agree SCO should be punished but I don't think patents are the answer.

[ Reply to This | # ]

OT: Some copyright and patent links
Authored by: RandomX on Sunday, March 14 2004 @ 02:02 PM EST
Resistance in the EU
The Draft IPR Enforcement Directive - A Threat to Competition and to Liberty
and EuroLinux

Lists some tactics under DCMA and UCITA
Copyrigh t Law for Academic Computing

A ruling on copyright and fair use - I don't know how much of this could apply,
but it's one of the most entertaining decisions I have read, and includes some interesting case law
OPERATION CLAMBAKE: SCIENTOLOGY COURT FILES

While not software patents, this paper discusses the current state of patent law
Foreseeability as a Bar to the Doctrine of Equivalents

An exerpt from ' DIGITAL COPYRIGHT ' by Jessica Litman

A link to a .pdf on copyright. Other good stuff linked from the home page
Envisioning Copyright Law's Digital Future

[ Reply to This | # ]

It does what now?
Authored by: PenguinLust on Sunday, March 14 2004 @ 02:04 PM EST
EIGHT AFFIRMATIVE DEFENSE The GPL violates the U.S. Constitution, together with copyright, antitrust and export control laws, and IBM's claims based thereon, or related thereto, are barred.

When was this decided and how come I never heard anything about it? Or is this perchance just some wishful thinking still and they're hoping if they keep slipping it in it will become reality?

That said some of their arguements against the counterclaim are pretty fantasy based as well. Their claims against #8 are a little odd. Given the Open Groups website seems to me to contain the standard for the Unix system, I'm going to chalk it up to some wierd legal defense I don't grasp. CAS

[ Reply to This | # ]

What exactly are they claiming now?
Authored by: penfold on Sunday, March 14 2004 @ 02:15 PM EST
On information and belief, U.S. Patent 4,814,746 ("the '746 patent") is unenforceable by reason of IBM's inequitable conduct, acts or omissions before the U.S. Patent and Trademark Office ("PTO"). The '746 patent, in the section entitled "Background of the Invention," cites one article directed to LZ78 data compression and indicates that it is representative of the prior art. U.S. Patent No. 4,814,746, column 1, lines 13-27. That statement is material, false and misleading and was known by IBM to be material, false and misleading. In fact, the single article cited in the '746 patent is not representative of the prior art. There are numerous other techniques such as LZ77, described in an article entitled "A Universal Algorithm For Sequential Data Compression," IEEE Transactions on Information Theory, Vol. IT-23, No. 3, May 1977, pp. 337-343. Other types of prior art data compression methods include run length encoding, arithmetic encoding and Huffman encoding. The falsity of IBM's statements is also reflected by the fact that in the period from December 9, 1975, to March 1, 1983, IBM itself obtained the issuance of at least 31 patents directed to data compression.
IANAL, and I know very little about patents and patent law. So I am not sure even what to lookup to find out what SCO is up to on this. So I am hoping someone can shed a little light for me on this.

From what I grasp from the filing, they are trying to say that IBMs patents are invalid because of prior art. I am wondering if they are, in typical SCO fashion, stretching the reality and the law, attempting to give their theories some traction.

As I read the above claim, I got the impression they are saying that IBM has patented compression, and since IBM didn't list all known methods of compression (at the time of filing for the patent) then IBM failed to give the PTO all the required information to issue a valid patent.

Now, I am pretty sure that IBM simply patented an algorithum or maybe a compression technique. (I haven't looked it up, and am not sure I would understand it if I knew where to look.) So, is SCO barking up the wrong tree again by claiming that IBM's compression patent is invalid becasue they didn't list other compression techniques (Huffman, run length, arithmatic encoding) that may not have anything to do with the technique IBM was patenting?

I would appreciate any guidence someone can offer.

---
Blood from a turnip? That's easy! Try getting SCOX to produce evidence!

[ Reply to This | # ]

OT: Deutsche Bank & Microsoft
Authored by: stdsoft on Sunday, March 14 2004 @ 02:28 PM EST
The timing and actions of Deutsche Bank appear to coincide with the needs of
Microsoft. A write-up is posted at Yahoo Finance regarding the possible
connection between Deutsche Bank and Microsoft as follows:

http://finance.messages.yahoo.com/bbs?.mm=FN&action=m&board=1600684464&a
mp;tid=cald&sid=1600684464&mid=109833

http://finance.messages.yahoo.com/bbs?.mm=FN&action=m&board=1600684464&a
mp;tid=cald&sid=1600684464&mid=109834

[ Reply to This | # ]

Fols - SCO might be claiming Linux ownership here
Authored by: trevmar on Sunday, March 14 2004 @ 02:32 PM EST
SEVENTH AFFIRMATIVE DEFENSE The GPL is selectively enforced by the Free Software Foundation such that enforcement of the GPL by IBM or others is waived, estopped or otherwise barred as a matter of equity.

Could SCO be saying that since SCO is apparently shipping parts of the Lunix system in contempt (or violation) of the GPL, and since none of the Copyright holders have objected, that those copyright holders have waived their rights to that software?

This is not something that should be overlooked. We have known that SCO is acting inethically or illegally with respect to Samba, they have proof we know they are shipping Samba, but the community is doing nothing. I think SCO might be touching a valid point here. The tip of the Iceberg. Has anybody checked that SCO is actually adhereing to the GPL on the GPL elements they have repackaged and are reshipping? Has anybody formally objected?

[ Reply to This | # ]

I've totally lost the big picture
Authored by: Anonymous on Sunday, March 14 2004 @ 02:49 PM EST
1 - Is a counterclaim a defense or an attack?
ie. Would a counterclaim
stand on its own as a suit?
2 - Do IBM's patents by themselves trump SCO's
straight
copyright or derivative copyright claims? Do they,
on
the other hand, just prove that "we were there first".
3 - Is it
possible that the patents can be used in a counter-
claim even if they
aren't valid?

[ Reply to This | # ]

Tit for tat
Authored by: Anonymous on Sunday, March 14 2004 @ 04:33 PM EST
Finally got around to reading IBM's actual patent claims against SCO. YIKES !!
PJ wasn't kidding about putting SCO's products at risk. If the press and
industry can stay awake long enough to read them, they'll have to note/report
thst the IBM suit has now put SCO's Open Server,HA, etc. in the same position of
doubt as SCO FUD has been trying to do to Linux. In other words, companies will
really want to think long and hard about buying SCO products with this hanging
over them. In addition SCO's whole line includes and relies on GPL stuff, which
they have declared is unconstitutional, illegal, and unenforceable

You would really have to have a death wish to buy anything from SCO now. If you
are a SCO customer you may want to start thinking about converting to a product
whose seller provides indemnification, or at least a clear, valid license, and
that ain't SCO anymore. Of course conversion will make you a target of a SCO
suit, right AutoZone?

[ Reply to This | # ]

  • Tit for tat - Authored by: Anonymous on Sunday, March 14 2004 @ 06:08 PM EST
  • Tit for tat - Authored by: Anonymous on Sunday, March 14 2004 @ 06:10 PM EST
    • Tit for tat - Authored by: PM on Sunday, March 14 2004 @ 06:23 PM EST
      • Tit for tat - Authored by: Anonymous on Sunday, March 14 2004 @ 07:27 PM EST
        • Tit for tat - Authored by: Anonymous on Sunday, March 14 2004 @ 10:50 PM EST
          • Life Insurance. - Authored by: Anonymous on Monday, March 15 2004 @ 02:55 PM EST
        • Tit for tat - Authored by: PM on Monday, March 15 2004 @ 12:08 AM EST
  • Tit for tat - Authored by: Anonymous on Sunday, March 14 2004 @ 07:42 PM EST
  • Tit for tat - Authored by: Anonymous on Sunday, March 14 2004 @ 08:27 PM EST
Patent 746
Authored by: schmuck on Sunday, March 14 2004 @ 08:00 PM EST
Well, I'm not sure what IBM has in patent 746,
but I think that SCO's claim:

In fact, the single article cited in the '746 patent is not representative of
the prior art. There are numerous other techniques such as LZ77, described in an
article entitled "A Universal Algorithm For Sequential Data
Compression," IEEE Transactions on Information Theory, Vol. IT-23, No. 3,
May 1977, pp. 337-343. Other types of prior art data compression methods include
run length encoding, arithmetic encoding and Huffman encoding. The falsity of
IBM's statements is also reflected by the fact that in the period from December
9, 1975, to March 1, 1983, IBM itself obtained the issuance of at least 31
patents directed to data compression.

is somewhat misleading. First LZ77 and LZ78
are universal compression schemes and the others
that they list are not. I have the impression that
patent 746 is about universal compression.

Second, I dug up the LZ78 paper
and sure enough, it cites the LZ77 one that SCO is
talking about. In fact, here is the reference list
of the LZ78 paper (Ziv, J. Lempel, A, "Compression of individual
sequences via variable-rate coding," IEEE Trans.
Inform. Theory, IT-24, pp. 530-536):

----------------------
[1] J. Ziv, "Coding theorems for individual sequences,"
IEEE Trans. inform Theory, IT-24, pp. 405-412, July 1978.

[2] S. Even, "Generalized automata and their information loslesness,"
Switching Circuit Theory and Logical Design,
AIEE Special Publ., S-141, pp.144-147, 1961.

[3] S. Even, "On information lossless automata of finite order," IEEE
Trans. Electronic Computers, vol. EC-1, pp. 561-569, Aug 1965.

[4] A. Lempel, J. Ziv, "On the complexity of finite sequences," IEEE
Trans. Inform. Theory, IT-22, pp. 75-81,
1976.

[5] J. Ziv, A. Lempel, "A universal algorithm for sequential data
compression," IEEE Trans. Inform. Theory,
IT-23, pp. 337-343, 1977.

[6] R. G. Gallager, Information Theory and Relizable Communication, New York:
Wiley 1968.
--------------------------

Note ref [5]... Also, if I look up the references of
the LZ77 paper, sure enough, it cites Hiffman
codes as reference [1] and a whole bunch of other
references. I find


--------------------
[1] D. A. Huffman, "A method for the construction of minimum-redundancy
codes," Proc. IRE, vol. 40, pp. 1098-1101, 1952.
[2] R. M. Karpm "Minimum-redundancy coding for the discrete noiseless
channel," IRE Trans. Inform. Theory, vol. IT-17, pp. 27-38, Jan. 1961.
[3] B. F. Varn, "Optimal Variable length codes," Inform. Contr., vol.
19, pp. 289-301.
[4] Y. Perl, R.M.Gray and S. Even, "Efficient generation of optimal prefix
code: Equiprobable words using unequal cost letters," J. ACM vol. 22, pp.
202-214, April 1975.
[5] A.Lempel, S. Even abd M. Cohn, "An algorithm for optimal prefix parsing
of a noiseless memoryless channel," IEEE Trans. Inform Theory, vol. IT-19,
pp.208-214, 1973.
[6] F. Jelinek and K. S. Schneider, "On variable length to block
coding," IEEE Trans. Inform Theory, vol. IT-18m pp.765-774, 1972
[7] R. G. Gallager, Information Theory and Relizable Communication, New York:
Wiley 1968.
[8] J. Ziv, "Coding for sources with unknown statistics -- Part I:
probability of encoding error," IEEE Trans. Inform.
Theory, vol IT-18, pp. 384-394, 1972.
[9] L. D. Davisson, "Universal noiseless coding", IEEE Trans. Inform.
Theory, vol IT-19, pp.783-795, 1973.
[10] A. Lempel, J. Ziv, "On the complexity of finite sequences," IEEE
Trans. Inform. Theory, IT-22, pp. 75-81,
1976.
[11] B. M. Fitingofm "Optimal coding in the case of unknown and changing
message statistics," Prob. Inform.
Transm., vol 2, pp.3-11, 1966.
--------------------



P.

[ Reply to This | # ]

OT: All software at risk. Consult your lawyer.
Authored by: swengr on Sunday, March 14 2004 @ 08:47 PM EST
Many articles in the press have cautioned against investing or depending on technologies without indemnification from the vendor.

The risk is not limited to the Linux kernel. All FOSS is vulnerable. And, all proprietary/closed source software as well.

It used to be "little" things, like the gif patent. Now there are attempts to claim things as fundamental as hyperlinking!

Had (for instance) Eolas prevailed, the cost to Microsoft users would have been incredible. Other suits against Microsoft also raise uncertainty.

Perhaps it's time for the press to ask:

Does Microsoft protect or indemnify you against claims?

They don't.

Maybe you should reconsider your investment. Could you afford to be in the position of Bank of America, when the police come and confiscate all your Windows computers?

---
Gratis is nice, Libre is an inalienable right.

[ Reply to This | # ]

compression patents
Authored by: Anonymous on Monday, March 15 2004 @ 12:10 AM EST
The research on the patent-encumbered state of compression algorithms has long ago been done, open source style. A fairly detailed account is one chapter of the FAQ for the comp.compression newsgroup: see the section entitled What about patents on data compression algorithms? It really is a fun read, pointing out how the patent office has repeatedly granted multiple patents for the same algorithm -- including the LZW algorithm covered by IBM patent '746 and Unisys patent '302, as mentioned here, as well as other duplicates.

I'm actually surprised patent '746 has any relevance still; the Unisys patent '302 on that algorithm expired in June 2003, twenty years after it was filed. (That was the patent that encumbered GIF images, which made Unisys so unpopular with free/open source folks when they tried to charge a fee for anything encoding GIF's...) Can anyone more knowledgable about law explain why the '746 patent, originally filed earlier, is still relevant?

[ Reply to This | # ]

defense 7 - mystery solved?
Authored by: Anonymous on Monday, March 15 2004 @ 12:22 AM EST
I've beed doing research to see exactly what the legal basis for a defense such
as 7 might be

"The GPL is selectively enforced by the Free Software Foundation such that
enforcement of the GPL by IBM or others is waived, estopped or otherwise barred
as a matter of equity."

At first I thought it was equitable estoppel. Some bizarre argument that not
enforcing in some cases caused SCO to rely on nonenforcement in its case. This
is such an obvious lost cause, that I took another look. I think the defense is
one of abuse of copyright. This is (almost?) always used in cases where a
company is trying to maintain or extend a monopoly by denying copyright license
to a competitor. Several of the cases are about copyrights on parts used in
field service. If you can't make a substitute part without infringeing, you
can't compete with the company's own service organization. This is what the
inkjet printer companies have been doing with cartridges, except they're
invoking the DMCA anticircumvention as well.

I'm not sure how SCO can say the FSF has a monopoly and also that SCO owns Unix,
but they were never very big on consistency. Since the basis of the defense is
violation of public policy, of which antitrust is an example, you could probably
argue for extending the concept if the FSFs conduct could be demonstrated to be
so inequitable as to override the copyright holder's right to not license. It
also looks like your hands don't have to be quite as clean as they would have to
be for equitable estoppel - the infringers knew or ought to have known what they
were doing. It's a guess, but it may be because copyright abuse is an offense
against the public, where as equitable estoppel is just a justification for your
behavior and has no public policy ramifications.

2 precedents are:

Lasercomb Am., Inc. v. Reynolds, 911 F. 2d 970 (4 th. Cir. 1990)
Saturday Evening Post Co. v. Rumbleseat Press, Inc., 816 F. 2d 1191 (7 th Cir.
1987),

The whole thing is a mess, since the Supreme Court apparently hasn't spoken yet.
The controlling precedent depends on the circuit.

IANAL

To save reply time let me say that I know that SCO mischaracterizes the nature
of the FSF and the GPL. That's already been covered above.

I think copyright abuse is a new one, though.

[ Reply to This | # ]

SCO's good faith
Authored by: Daddio on Monday, March 15 2004 @ 12:30 AM EST
TWENTY FIFTH AFFIRMATIVE DEFENSE
SCO states that IBM's request for treble damages and attorneys fees is barred
because SCO acted in good faith, and this is not an exceptional case within the
meaning of the Patent Code.

with regard to the patant claims this statement is true. If Openserver
/Unixware violate IBM's patents it was not intentional

However this will not help the lying sacks of SCO, because IBM allege Bad Faith
in SCO's treatment of IBM copyrighted material, and SCO's Lanham act violations,
and SCO's violation of the GPL, not IBM patents.

The patent claims don't require any monetary damages to be effective. If IBMs
pleading are answered affirmatively, SCO would have to (well first they'd have
to hire some developers) cease distibution of their entire product line until
they could rewite their code to circumnavigate the patented technologies.

---
Joshua A Clayton
~Salt Lake City UT

[ Reply to This | # ]

Comparative Charts - IBM Counterclaims and SCO's Answers and Affirmative Defenses
Authored by: crs17 on Monday, March 15 2004 @ 12:31 AM EST
Remember that relevance is in the eye of the beholder. To some extent this is
PJ's place and she can set boundaries, but for the rest of us, we have widely
varying interests. Some of us are interested in the law, some in software
development, some are linux users or have vested interests in products based on
linux, some are rights activists in a general sense, some are investors, etc.
Actually, many of us fit into more than one of the above-mentioned categories
and many of us probably don't fall in any of the categories that I managed to
think of.

Each of these categories find very different things to be relevant.

The point is that each of these categories find lots of juicy interesting
details in the SCO saga, but what's juicy to one category is often boring or
incomprehensible detail to another.

[ Reply to This | # ]

SCO's other patent defense
Authored by: Anonymous on Monday, March 15 2004 @ 12:34 AM EST
SCO has also raised an additionall defense to the'785 patent. The currentky
fashionable undisclosed inventor. Under patent law all the inventors have to be
on the patent and no noninventors (remember this when the boss wants his name on
the patent).

They claim that because the inventor wrote several articles about his invention
with coauthors, and because the journals had a rule that coauthors had to make
significant contributions to the article, they must have made significant
contributions to the patent. They'll need a bit more than this, and they
probably won't find it. I'm surprised they haven't asked for discovery
concerning this - labnotes and such.

[ Reply to This | # ]

Parsing the patent counterclaim 18th Affirmative Defense - the '746 patent...
Authored by: LionKuntz on Tuesday, March 16 2004 @ 05:06 AM EST



Here is what I did:

What I saw:

  • There is no similarity to the flowcharts or program codes in the '746 and '302 patents.

  • There is no similarity in the claims of the '746 patent to the '302 or '551 patents.

  • Inventors who did their own prior art searches almost never saw any similarity between the '746 and '551 patents. (only one patent cites both as prior art.

  • Inventors who did their own prior art searches almost never saw any similarity between the '302 and '551 patents. (only two patents cite both as prior art.)

  • 116 inventors who did their own prior art searches did not see similarity between the '302 and '746 patents. Out of 177 which cited '302 as prior art, only 61 also cited '746.

  • If the substance of '746 and '302 are so close as to be overlapping, than all 177 patents that cite '302 should also cite '746.

  • If the substance of '746 and '551 are so close as to be overlapping, than all 81 patents that cite '746 should also cite '551.

  • If the substance of '302 and '551 are so close as to be overlapping, than all 177 patents that cite '302 should also cite '551.



http://www.ecosyn.us /SCO_v_IBM_copyright_issues.html

SCO v IBM: SELECTED WEBPAGES CITATIONS OF COPYRIGHT LAW HISTORY RELEVENT TO UNIX SYSTEM V COPYRIGHT CLAIMS STATUS

[ Reply to This | # ]

Eben Moglen on the GPL
Authored by: Anonymous on Tuesday, March 16 2004 @ 12:55 PM EST
There's been a lot of back and forth about "accepting" or
"agreeing to" the GPL. This is what Eben Moglen has to say.

"The word 'license' has, and has had for hundreds of years, a specific
technical meaning in the law of property. A license is a unilateral permission
to use someone else's property. The traditional example given in the first-year
law school Property course is an invitation to come to dinner at my house. If,
when you cross my threshold, I sue you for trespass, you plead my 'license,'
that is, my unilateral permission to enter on and use my property.

A contract, on the other hand, is an exchange of obligations, either of promises
for promises or of promises of future performance for present performance or
payment. The idea that 'licenses' to use patents or copyrights must be contracts
is an artifact of twentieth-century practice, in which licensors offered an
exchange of promises with users: 'We will give you a copy of our copyrighted
work,' in essence, 'if you pay us and promise to enter into certain obligations
concerning the work.' With respect to software, those obligations by users
include promises not to decompile or reverse-engineer the software, and not to
transfer the software.
...
The GPL, however, is a true copyright license: a unilateral permission, in which
no obligations are reciprocally required by the licensor. Copyright holders of
computer programs are given, by the Copyright Act, exclusive right to copy,
modify and redistribute their programs. The GPL, reduced to its essence, says:
'You may copy, modify and redistribute this software, whether modified or
unmodified, freely. But if you redistribute it, in modified or unmodified form,
your permission extends only to distribution under the terms of this license. If
you violate the terms of this license, all permission is withdrawn."

Moreover the license says clearly that it pertains only to the software itself.

As far as I can see, anything else you do, omit to do, say or believe is
irrelevant. The very clever idea is to write a document that fulfills the goals
of the FSF without being a contract, and thus is not subject to the vagaries of
contract interpretation in 50 different states. Any attempt to read other sorts
of obligations into the GPL risks turning it into a contract.

http://lwn.net/Articles/61292/

[ Reply to This | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )