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
SCO's Objections to Notice of Deposition (the Configurable High Availability Notice) - as text
Friday, January 28 2005 @ 01:24 AM EST

And now, the final of the three objections, SCO's Objections to International Business Machine Corporation's Rule 30(b)(6) Notice of Deposition ("the Configurable High Availability Notice") -- as text, once again thanks to AntiFUD.

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

Brent O. Hatch (5715)
Mark F. James (5295)
HATCH, JAMES & DODGE
[address, phone, fax]

Stephen N. Zack (admitted pro hac vice)
BOIES, SCHILLER & FLEXNER LLP
[address, phone, fax]

Robert Silver (admitted pro hac vice)
Edward Normand (admitted pro hac vice)
Sean Eskovitz (admitted pro hac vice)
BOIES, SCHILLER & FLEXNER LLP
[address, phone, fax]

Frederick S. Frei (admitted pro hac vice)
John K. Harrop (admitted pro hac vice)
ANDREWS KURTH LLP
[address, phone, fax]

Attorneys for The SCO Group, Inc.

__________________________

IN THE UNITED STATES DISTRICT COURT
FOR THE DISTRICT OF UTAH

__________________________

THE SCO GROUP, INC.

Plaintiff/Counterclaim-Defendant,

v.

INTERNATIONAL BUSINESS
MACHINES CORPORATION,

Defendant/Counterclaim-Plaintiff.

___________________________

OBJECTIONS TO INTERNATIONAL
BUSINESS MACHINE
CORPORATION'S RULE 30(b)(6)
NOTICE OF DEPOSITION ("THE
CONFIGURABLE HIGH
AVAILABILITY NOTICE")

Case No. 2:03CV0294DAK
Honorable Dale A. Kimball
Magistrate Judge Brooke C. Wells

_____________________________

In response to Defendant/Counterclaim-Plaintiff International Business Machine Corporation's ("IBM") Notice of 30(b)(6) deposition, served by U.S. Mail on January 10, 2005, and by facsimile on January 11, 2005 ("the Configurable High Availability Notice"),

1

Plaintiff/Counterclaim-Defendant The SCO Group, Inc. ("SCO") submits the following objections.

Notwithstanding its General and Specific Objections set forth herein, SCO will attempt to identify witnesses knowledgeable concerning the topics set forth in IBM's Notice. SCO will confer with patent counsel for IBM with respect to the designated topics and to agree on dates and locations for these depositions.

GENERAL OBJECTIONS

1. SCO objects generally to the Configurable High Availability Notice as overly broad and unduly burdensome. The Configurable High Availability Notice was served simultaneously with two other Rule 30(b)(6) deposition notices. Together, these three notices listed fifty-one (51) topics. These notices are overbroad and unduly burdensome for the further reason that IBM provided SCO with only two weeks' notice to prepare for these depositions.

2. SCO objects generally to the Configurable High Availability Notice as unduly burdensome because IBM has scheduled this deposition to take place in the offices of its local counsel in Salt Lake City, Utah. Many of the individuals likely to have knowledge of the topics listed in IBM's Configurable High Availability Notice reside in the Eastern United States, as do SCO's counsel and IBM's counsel. It would be far less burdensome for these depositions to take place at or near SCO's offices in New Jersey.

3. SCO objects generally to the Configurable High Availability Notice as unduly burdensome because IBM gave SCO only two weeks to prepare for each of the topics listed and further reduced the time available to prepare by not serving SCO's patent counsel, who have

2

already entered an appearance in this case, thereby further prejudicing SCO and increasing the burden imposed by IBM's Configurable High Availability Notice.

4. SCO objects generally to each Topic within the Configurable High Availability Notice insofar as it seeks disclosure of information that will become known to SCO only after the completion of discovery or is otherwise premature, particularly because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in-suit.

5. SCO objects to each Topic within the Configurable High Availability Notice insofar as it causes annoyance, oppression, undue burden, or expense to SCO, particularly because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in-suit.

6. SCO objects to each Topic within the Configurable High Availability Notice insofar as it seeks information not reasonably calculated to lead to the discovery of admissible evidence, and/or which exceeds the scope of discovery permitted by the Federal Rules of Civil Procedure.

7. SCO objects to each Topic within the Configurable High Availability Notice insofar as it purports to seek information or documents protected from discovery by the attorney- client privilege or any other applicable privilege or immunity.

8. SCO objects to each Topic within the Configurable High Availability Notice insofar as it seeks work product, mental impressions, conclusions, opinions, or legal theories of

3

SCO's counsel, experts, and/or consultants developed in connection with or in anticipation of this or other litigation or other business transactions not related to this litigation.

9. SCO objects to IBM's definition of "SCO Product" or "SCO Products" within the Configurable High Availability Notice as "any and all products that are or were created by, for, or on behalf of, or acquired by SCO, or any predecessor in interest thereof (whether or not for a fee), from six years prior to August 6, 2003 to the present date" because it renders the topics overly broad and unduly burdensome. Moreover, SCO objects to any Topic within the Configurable High Availability Notice that seeks SCO's response on behalf of any entity not wholly owned by SCO or with regard to a product not sold, manufactured, or used by SCO.

10. SCO objects to IBM's definition of "SCO Product" or "SCO Products" within the Configurable High Availability Notice wherein it "refers to any and all products that are or were created by, for, or on behalf of, or acquired by SCO, or any predecessor in interest thereof (whether or not for a fee), from six years prior to August 6, 2003 to the present date" on the grounds that it seeks "any and all products" not only created by SCO but also relating in any way to SCO (including simply acquired by SCO) or any predecessor, and is therefore overly broad and unduly burdensome.

11. SCO objects generally to the definition of "Configurable High Availability Product" within the Configurable High Availability Notice as vague, overbroad, and unduly burdensome to the extent that it includes SCO Products that IBM has not accused of infringement of the relevant patents-in-suit.

12. SCO objects further that this Notice is premature because it has outstanding discovery asking IBM to construe its asserted claims which has not been fully answered.

4

13. SCO objects generally to the term "Configurable High Availability Products" within the Configurable High Availability Notice as overly broad and unduly burdensome to the extent that it incorporates the term "Configurable High Availability Feature" as objected to above.

14. SCO further objects to the term "Configurable High Availability Products" within the Configurable High Availability Notice as overly broad and unduly burdensome to the extent that it includes products, other than those which IBM has accused of infringement.

15. SCO incorporates its General Objections with regard to each topic as though fully set forth therein.

SPECIFIC OBJECTIONS

TOPIC NO. 1

1. SCO objects specifically to Topic No. 1 of the Configurable High Availability Notice on the grounds that the discovery tool IBM has chosen is the most expensive and unduly burdensome tool available considering the type of information that is being sought and that interrogatories are the appropriate tool for this type of "identification" information.

2. SCO further objects specifically to Topic No. 1 because, by seeking "each version or release of each Configurable High Availability Product," the topic is overly broad and unduly burdensome.

TOPIC NO. 2

3. SCO objects specifically to Topic No. 2 because it is overbroad and unduly burdensome to the extent that it seeks information related to Configurable High Availability

5

Products to the extent that term can be construed to include products other than those that IBM has accused of infringing the patents-in-suit.

4. SCO further objects specifically to Topic No. 2 to the extent that it seeks information that is just as burdensome for SCO to produce as it is for IBM to obtain. SCO has previously produced the source code corresponding to each accused product. It is no more burdensome for IBM to undertake the inquiry requested in Topic No. 2 than it would be for SCO to do so.

5. SCO further objects specifically to Topic No. 2 on the grounds that the discovery tool IBM has chosen is the most expensive and unduly burdensome tool available considering the type of information that is being sought and that interrogatories are the appropriate tool for this type of "identification" information.

TOPIC No. 3

6. SCO objects specifically to Topic No. 3 because it is overbroad and unduly burdensome to the extent that it seeks information related to Configurable High Availability Products to the extent that term can be construed to include products other than those that IBM has accused of infringing the patents-in-suit.

7. SCO further objects specifically to Topic No. 3 because, by seeking "the function and operation of each Configurable High Availability Feature within each Configurable High Availability Product," the topic is overly broad and unduly burdensome to the extent it seeks information pertaining to products other than those IBM has accused of infringement.

6

TOPIC NO. 4

8. SCO objects specifically to Topic No. 4 because, by seeking "testing, evaluation, analysis and debugging of each Configurable High Availability Product" the topic is overly broad and unduly burdensome to the extent it seeks information pertaining to products other than those IBM has accused of infringement.

9. SCO further objects specifically to Topic No. 4 as premature because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in- suit.

10. SCO further objects specifically to Topic No, 4 as vague and ambiguous because it does not describe what information concerning the "testing, evaluation, analysis, and debugging of each Configurable High Availability Product" it seeks.

TOPIC NO. 5

11. SCO objects specifically to Topic No. 5 because, by seeking "[u]se made by SCO or SCO's knowledge of its customers' uses of any Configurable High Availability Product," the topic is overly broad and unduly burdensome to the extent it seeks information pertaining to products other than those IBM has accused of infringement.

12. SCO further objects specifically to Topic No. 5 as premature because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in- suit.

7

13. SCO further objects specifically to Topic No. 5 as vague and ambiguous because it does not describe what information concerning "[u]se made by SCO or SCO's knowledge of its customers' uses of any Configurable High Availability Product" it seeks.

TOPIC NO. 6

14. SCO further objects specifically to Topic No. 6 as premature because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in- suit.

15. SCO further objects specifically to Topic No. 6 as vague and ambiguous because it does not describe what information concerning "[t]he use of customizable detectors in the ReliantHA product, including but not limited to the identification of component failures to the Configuration Monitor" it seeks.

TOPIC NO. 7

16. SCO objects specifically to Topic No. 7 as premature because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in- suit.

17. SCO further objects specifically to Topic No. 7 as vague and ambiguous because it does not describe what information concerning "[t]he use of recovery schemes in the ReliantHA product, including but not limited to the use by the Configuration Monitor of user supplied configuration files to initiate recovery actions" it seeks.

8

TOPIC NO. 8

18. SCO objects specifically to Topic No. 8 as premature because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in- suit.

19. SCO further objects specifically to Topic No. 8 as vague and ambiguous because it does not describe what information concerning "[t]he capability to define a new resource type and provide a detector process for the new resource type in the ReliantHA product" it seeks.

TOPIC NO. 9

20. SCO objects specifically to Topic No. 9 as premature because IBM has not yet provided specific constructions for its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in-suit.

21. SCO further objects specifically to Topic No. 9 as vague and ambiguous because it does not describe what information concerning "[t]raining, recmmendations, suggestions and instructions provided by SCO or any third party to SCO's customers or potential customers concerning the use, configuration, intended use or intended configuration of each Configurable High Availability Product" it seeks.

TOPIC NO. 10

22. SCO objects specifically to Topic No. 10 because, by seeking information related to the "[t]he manufacture of each Configurable High Availability Product," the topic is overly

9

broad and unduly burdensome to the extent it seeks information pertaining to products other than those IBM has accused of infringement.

23. SCO further objects specifically to Topic No. 10 as premature because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in- suit.

24. SCO further objects specifically to Topic No. 10 as vague and ambiguous because it does not describe what information concerning the "[t]he manufacture of each Configurable High Availability Product" it seeks.

TOPIC NO. 11

25. SCO objects specifically to Topic No. 11 because, by seeking "[p]roposed or actual design alternatives to the use of configurable monitors and recovery schemes in each Configurable High Availability Product, including but not limited to my alleged designs SCO would use as noninfringing alternatives to the current version," the topic is overly broad and unduly burdensome to the extent it seeks information pertaining to products other than those IBM has accused of infringement.

26. SCO further objects specifically to Topic No. 11 as premature because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in- suit.

10

TOPIC NO. 12

27. SCO objects specifically to Topic No. 12 because, by seeking "[t]he release history of each Configurable High Availability Product," the topic is overly broad and unduly burdensome to the extent it seeks information pertaining to products other than those IBM has accused of infringement.

28. SCO further objects specifically to Topic No. 12 as premature because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in- suit.

TOPIC NO. 13

29. SCO objects specifically to Topic No. 13 because, by asking that "[t]o the extent any Configurable High Availability Product was acquired or otherwise not originally developed by SCO, the identity of the original developer and all persons who worked on, and the location of any documents regarding, the development of configurable monitors and recovery schemes in such product," the topic is overly broad and burdensome to the extent it seeks information pertaining to products other than those IBM has accused of infringement.

30. SCO further objects specifically to Topic No. 13 as premature because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in- suit.

31. SCO further objects specifically to Topic No. 13 on the grounds that the discovery tool IBM has chosen is the most expensive and unduly burdensome tool available considering

11

the type of information that is being sought and that requests for production of documents or interrogatories are the appropriate tool for this type of "identification" information.

TOPIC NO. 14

32. SCO objects specifically to Topic No. 14 as premature because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in- suit.

33. SCO further objects specifically to Topic No. 14 on the grouds that the discovery IBM seeks is available from third parties and should be obtained from them.

TOPIC NO. 15

34. SCO objects specifically to Topic No. 15 because, by seeking "[t]he facts, circumstances and documents relating to the decision by SCO to continue to use configurable monitors and recovery schemes in each Configurable High Availability Product after August 6, 2003," the topic is overly broad and unduly burdensome to the extent it seeks information pertaining to products other than those IBM has accused of infringement.

35. SCO further objects specifically to Topic No. 15 on the grounds that the discovery tool IBM has chosen is the most expensive and unduly burdensome tool available considering the type of information that is being sought and that requests for documents are the appropriate tool for this type of information.

36. SCO objects specifically to Topic No. 16 because, by seeking "[t]he facts, circumstances and documents relating to SCO's licensing of the ReliantHA product from any entity including: Veritas, Pyramid Technology Corporation, Siemens Nixdorf Information

12

Systems AG, Siemens Pyramid and Fujitsu Computers, Inc.," the topic is overly broad and unduly burdensome for the reasons SCO enumerated in its specific objections to items 1-16 above.

37. SCO further objects specifically to Topic No. 16 as premature because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in- suit.

TOPIC NO. 17

38. SCO objects specifically to Topic No. 17 because, by seeking "[t]he identity of SCO's personnel most knowledgeable concerning the subject matter described in items 1-16 above," the topic is overly broad and unduly burdensome for the reasons SCO enumerated in its specific objections to items 1-16 above.

39. SCO further objects specifically to Topic No. 17 as premature because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in- suit.

TOPIC NO. 18

40. SCO objects specifically to Topic No. 18 because, by seeking "[d]ocuments concerning the subject matter set forth in paragraphs 1-16 above," the topic is overly broad and unduly burdensome for the reasons SCO enumerated in its specific objections to items 1-16 above.

13

41. SCO further objects specifically to Topic No. 18 as premature because IBM has not yet provided specific constructions of its asserted claims, nor the support for such claim constructions, nor has IBM stated how SCO's accused products allegedly infringe the patents-in- suit.

DATED this 24th day of January, 2005

Respectfully submitted,

HATCH, JAMES & DODGE, P.C.
Brent O. Hatch
Mark James

BOIES, SCHILLER & FLEXNER LLP
Robert Silver (admitted pro hac vice)
Stephen N. Zack (admitted pro hac vice)
Edward Normand (admitted pro hac vice)
Sean Eskovitz (admitted pro hac vice)

ANDREWS KURTH LLP
Frederick S. Frei
John K. Harrop

By: ___[signature]____

Attorneys for The SCO Group, Inc.

14

I hereby certify that the foregoing OBJECTIONS TO INTERNATIONAL BUSINESS MACHINE CORPORATION'S RULE 30(b)(6) NOTICE OF DEPOSITION ("THE CONFIGURABLE HIGH AVAILABILITY NOTICE") was served this 24th day of January, 2005:

By facsimile and Federal Express to:

David Marriott, Esq.
Cravath, Swaine & Moore LLP
[address, fax]

A copy was also sent by depositing a copy of same in the United States mail, first class, postage prepaid, this 24th day of January, 2005 to the following:

Todd M. Shaughnessy, Esq.
Snell & Wilmer L.L.P.
[address]

Donald J. Rosenberg, Esq.
[address]

___[signature]____

15


  


SCO's Objections to Notice of Deposition (the Configurable High Availability Notice) - as text | 14 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Looks like a (partial) copy/paste and find/replace job
Authored by: fudisbad on Friday, January 28 2005 @ 03:42 AM EST
Must be those capped legal fees.

---
See my bio for copyright details re: this post.
This subliminal message has been brought to you by Microsoft.

[ Reply to This | # ]

OT Here Please
Authored by: fudisbad on Friday, January 28 2005 @ 03:48 AM EST
For current events, legal filings and CC10 rulings.

Speaking of legal filings, G2's Reply re: motion to unseal and an opposition
memo re: Sam Palmisano were due yesterday (unless delayed).

SCO's 10-K (2004) is due Monday.

---
See my bio for copyright details re: this post.
This subliminal message has been brought to you by Microsoft.

[ Reply to This | # ]

Corrections Here Please
Authored by: fudisbad on Friday, January 28 2005 @ 03:51 AM EST
You know why...

---
See my bio for copyright details re: this post.
This subliminal message has been brought to you by Microsoft.

[ Reply to This | # ]

Corrections - errors and omissions excepted
Authored by: Wol on Friday, January 28 2005 @ 04:56 AM EST
There is no "Topic no 16" header. Missing from the original too?

Cheers,
Wol

[ Reply to This | # ]

No Business Like SCO Business
Authored by: Anonymous on Friday, January 28 2005 @ 09:10 AM EST
Hopfully :-)

[ Reply to This | # ]

I'm disappointed
Authored by: Anonymous on Friday, January 28 2005 @ 03:12 PM EST
I wanted to see IBM ask for all the code "SCO" has produced in their
"25 year history"...

Would've been hilarious reading their explanations of why their 25th anniversary
celebration and their actual coding history had no relation to one another!

[ 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 )