Hynix Semiconductor Inc. v. Rambus Inc.

609 F. Supp. 2d 988, 2009 U.S. Dist. LEXIS 17791, 2009 WL 541321

Opinion

PHASE III (CONDUCT TRIAL) FINDINGS OF FACT AND CONCLUSIONS OF LAW

RONALD M. WHYTE, District Judge.

This patent/antitrust litigation involves dynamic random access memory (“DRAM”) interface technology patented by Rambus and incorporated into industry-standard DRAMs. The litigation involves four actions. In the first action (Case No. 00-20905 or “Hynix /”), Hynix 1 (then Hyundai Electronics Industries Co., Ltd. and its subsidiaries) sued Rambus for a declaratory judgment regarding various Rambus patents. The court divided the issues into three trial phases. The issue in the first phase concerned whether Ram-bus’s patent infringement counterclaims were barred by the doctrine of unclean hands. On January 5, 2006 the court issued its Findings of Fact and Conclusions of Law on Unclean Hands in favor of Rambus. Hynix Semiconductor Inc. v. Rambus Inc., 591 F.Supp.2d 1038 (N.D.Cal.2006). The second phase concerned Rambus’s allegations that Hynix’s DRAMs infringed several of its patents. On April 26, 2006 a jury returned a verdict that Rambus’s patent claims were infringed and not invalid and that Rambus was entitled to $306,967,272 in damages. The court remitted the jury’s award to $133,584,129, which Rambus accepted.

The third phase concerned Hynix’s allegations that Rambus obtained its patents in violation of a disclosure obligation to members of the Joint Electron Device Engineering Council (“JEDEC”), a standards setting organization of which Rambus was a member. Hynix alleged that Rambus committed antitrust and related violations by attempting to assert its patent claims against manufacturers of DRAMs that complied with the JEDEC standard. Hynix also raised a number of defenses to its infringement based on this conduct. On March 26, 2008 a jury returned a verdict in favor of Rambus and against the Manufacturers on their legal claims. With these Findings of Fact and Conclusions of Law on the equitable claims and defenses, all issues in Hynix I have been resolved.

As mentioned, there are three other cases involving Rambus, DRAM manufacturers, and Rambus’s conduct at JEDEC. The court and the parties identified the issues regarding Rambus’s conduct common to these cases and Hynix I and the court consolidated those issues for trial. Thus, these findings and conclusions apply equally to these further cases as discussed below.

I. THE SCOPE OF THE CONSOLIDATED TRIAL PROCEEDINGS

These Findings of Fact and Conclusions of Law are made with respect to the non-jury claims and defenses asserted by the following entities: Hynix in cases C-00-20905 and C-05-00334; Nanya Technology Corp. and Nanya Technology Corp. U.S.A. (“Nanya”) in case C-05-00334; and Micron Technology, Inc., and Micron Semiconductor Products, Inc. (“Micron”) in case C-06-00244. The court refers to these entities collectively as “the Manufacturers.” The court consolidated for trial the claims and defenses delineated in Attachments 1-3 and 5 of the parties’ July 31, 2007 Joint Case Management Statement. 2 The trial, which the court and the parties refer to as “the Conduct Trial,” involved the following claims and defenses:

A. Consolidated Issues From Hynix I

The Hynix I action commenced on August 29, 2000, when Hyundai Electronics Industries Co., Ltd. and Hyundai Electronics America sought a declaratory judgment of noninfringement, invalidity, and unenforceability with respect to the following Rambus patents: U.S. Patents Nos. 5,915,105, 5,953,263, 5,954,804, 5,995,443, 6,032,214, 6,032,215, 6,034,918, 6,035,365, 6,038,195, 6,067,592, and 6,101,152. 3 Hyundai Electronics Industries Co., Ltd. and Hyundai Electronics America amended their complaint on October 17, 2000 to add Hyundai Electronics U.K., Ltd. and Hyundai Electronics Deutschland GmbH as plaintiffs and to add antitrust and other claims against Rambus. In response, Rambus counterclaimed on February 5, 2001 for infringement of the patents listed above. Hynix filed a Second Amended Complaint on June 11, 2001, which added claims against Rambus for fraud and constructive fraud and reflected the intervening change in the names of the Hynix entities. On November 25, 2002, Rambus amended its counterclaim to add infringement of four additional Rambus patents: U.S. Patents Nos. 6,324,120, 6,378,020, 6,426,916, and 6,452,863. On December 16, 2002, Hynix answered the counterclaims and asserted various affirmative defenses.

As discussed, the court held a bench trial in 2005 on Hynix’s unclean hands defense. Hynix contended that Rambus spoliated evidence resulting in prejudice to Hynix. The court rejected Hynix’s allegations of unclean hands. In the second phase of trial, held in' March and April 2006, Rambus elected to assert infringement of certain claims from the '105, '918, '120, '020, '916 and '863 patents. A jury found that the patents-in-suit were not invalid and infringed by Hynix’s DDR SDRAM, GDDR SDRAM, DDR SGRAM, DDR2 SDRAM, GDDR2 SDRAM, DDR3 SDRAM, and GDDR3 SDRAM devices, and that a subset of those claims were also infringed by Hynix’s SDRAM, SGRAM, and Handy SDRAM products.

As a result pf the prior two trial phases and the court’s rulings on Rambus’s mptions for summary adjudication, the following claims and defenses involving Hynix were left for trial in the consolidated Conduct Trial:

Claim/Defense . Nature Trier of Fact

First Claim For Relief ■ Monopolization (15 U.S.C. § 2) Jury

Second Claim for Relief_Attempted Monopolization (15 U.S.C. § 2)_Jury

Third Claim For Relief Unfair Competition (Cal. Bus. & Prof.Code Court ’_ § 17200)_

Eighth Claim For Relief_Actual Fraud_■ Jury

Fifth Affirmative Defense Equitable: Estoppel “relating to Court JEDEC [and] JEDEC’s Disclosure Rules”

Sixth Affirmative Defense Equitable Estoppel based on Rambus’s conduct Court during the course of its RDRAM relationship with Hynix

Seventh Affirmative Waiver Court

Defense__

Ninth Affirmative Defense Prosecution Laches Court

Eleventh Affirmative Unclean Hands (not including spoliation) Court Defense

B. Consolidated Issues From Case No. 05-00334

The '334 action commenced on January 25, 2005, when Rambus sued Hynix, Infineon, Nanya, and Inotera Memories, Inc. for infringement of the following Rambus patents: U.S. , Patent Nos. 6,182,184, 6,260,097, 6,266,285, 6,314,051, 6,324,120, 6,378,020, 6,426,916,' 6,452,863, 6,493,789, 6,496,897, 6,546,446, 6,564,281, 6,584,037, 6,697,295, 6,71)1,446,' 6,715,020, 6,781,696, and 6,807,598. Inotera Memories, Inc. and Infineon were later dismissed from the case.

Rambus filed its First Amended Complaint on June 6, 2005, asserting the same patents as the original January 25, 2005 complaint, but adding the Samsung entities as defendants. Hynix answered the First Amended Complaint and counterclaimed on June 27, 2005. It filed a First Amended Answer and First Amended Counterclaims on February 22, 2007. Nanya answered the First Amended Complaint and counterclaimed on July 18, 2005. Nanya filed a First Amended Answer and First Amended Counterclaims on July 9, 2007. The Hynix and Nanya answers and counterclaims assert equitable defenses including prosecution laches, equitable estoppel, waiver, laches, and claims for declaratory judgment, monopolization, attempted monopolization, fraud, and unfair competition (Cal. Bus. & Prof. Code § 17200).

In response to Hynix and Nanya’s answers and counterclaims, Rambus filed its answer and Counterclaims in Reply on July 9, 2007 and July 24, 2007 respectively. In these Counterclaims in Reply, Rambus added infringement claims against, inter alia, DDR3 SDRAM and GDDR4 SDRAM products. On July 30, 2007, Hynix replied to Rambus’s Counterclaims in Reply and filed its own Counterclaims in Reply to the Counterclaims in Reply, alleging the same claims and defenses as its First Amended Answer and First Amended Counterclaims had alleged. Rambus replied to Hynix’s Counterclaims in Reply on August 20, 2007. On December 21, 2007, Nanya replied to Rambus’s Counterclaims in Reply and filed its own Counterclaims in Reply to the Counterclaims in Reply, alleging the same claims and defenses as its First Amended Answer and First Amended Counterclaims had alleged earlier. From these pleadings, the court consolidated for trial the following claims and defenses:

1. Hynix’s Claims and Defenses in C-05-00334

Hynix’s claims and defenses from the '334 action that were tried in the Conduct Trial are:

Claim/Defense Nature Trier of Fact

First Counterclaim Monopolization (15 U.S.C. § 2) Jury

Second Counterclaim Attempted Monopolization (15 U.S.C. § 2) Jury

Third Counterclaim Unfair Competition (Cal. Bus. & Prof.Code Court _§ 17200)_

Fourth Counterclaim Fraud Jury

Eighth Affirmative Defense Prosecution Laches Court

Ninth Affirmative Defense Estoppel regarding JEDEC Court

Tenth Affirmative Defense Estoppel regarding “Other DRAM” Court

Eleventh Affirmative Waiver Court Defense

Twelfth Affirmative Defense Unclean Hands (not including spoliation) Court

Thirteenth Affirmative Laches Court Defense

2. Nanya’s Claims and Defenses

Nanya’s claims and defenses from the '334 action that were tried in the Conduct Trial are:

Claim/Defense Nature Trier of Fact

First Counterclaim Monopolization (15 U.S.C. § 2) Jury

Second Counterclaim Attempted Monopolization (15 U.S.C. § 2) Jury

Third Counterclaim Unfair Competition (Cal. Bus. & Prof.Code Court _§ 17200)_

Fourth Counterclaim Fraud Court 4

Seventh Counterclaim Declaratory Judgment of Unenforceability Court

Eighth Affirmative Defense Prosecution Laches Court

Ninth Affirmative Defense Estoppel regarding JEDEC Court

Eleventh Affirmative Laches Court Defense

Twelfth Affirmative Defense Equitable Estoppel Court

Thirteenth Affirmative Waiver Court Defense

Sixteenth Affirmative Patent Misuse Court Defense

C. Consolidated Issues From Case No. 06-00244

The '244 action commenced on January 13, 2006, when Rambus sued Micron for patent infringement. Rambus then filed a Corrected First Amended Complaint on April 18, 2006 alleging infringement of the following Rambus patents: U.S. Patent Nos. 6,182,184, 6,260,097, 6,266,285, 6,314,051, 6,493,789, 6,496,897, 6,546,446, 6,564,281, 6,584,037, 6,697,295, 6,701,446, 6,715,020, 6,781,696, and 6,807,598. Micron answered the Corrected First Amended Complaint and alleged its own Counterclaims on June 2, 2006. It then filed a First Amended Answer and First Amended Counterclaims on May 30, 2007. Micron’s answer and counterclaims include equitable defenses of prosecution laches, equitable estoppel, waiver, implied license, promissory estoppel, laches, and claims for declaratory judgment, monopolization, attempted monopolization, fraud, and unfair competition (Cal. Bus. & Prof. Code § 17200) and fraud. In response to Micron’s answers and counterclaims, Rambus filed its answer and Counterclaims in Reply on July 9, 2007. In these Counterclaims in Reply, Rambus added infringement claims against DDR3 SDRAM products. On December 3, 2007, Micron replied to Rambus’s Counterclaims in Reply and filed its own Counterclaims in Reply to the Counterclaims in Reply, alleging the same claims and defenses as its First Amended Answer and First Amended Counterclaims had alleged. Rambus answered Micron’s Counterclaims in Reply on December 26, 2007.

Micron’s claims and defenses from the '244 action that were tried in this phase of the trial of this action are:

Claim/Defense Nature Trier of Fact

Fifteenth Counterclaim Monopolization and Attempted Monopolization (15 Jury U.S.C. § 2)

Eighteenth Counterclaim Fraud Jury

Twenty-first Counterclaim Unfair Competition (Cal. Bus. & Prof.Code Court § 17200)

First through Fourteenth Declaratory Judgments of Unenforceability Court Counterclaims

Ninth Affirmative Defense Implied License Court

Thirteenth Affirmative Equitable Estoppel Court Defense

Fourteenth Affirmative Waiver Court Defense

Sixteenth Affirmative Laches Court Defense

II. FINDINGS OF FACT

The focus of the Conduct Trial was on the disclosure obligation, if any, that Ram-bus had to JEDEC or its members with respect to possible patent coverage of any DRAM built in accordance with industry standards adopted by JEDEC. The court first makes findings of fact with respect to whether JEDEC members had an expectation that Rambus would disclose any intent it had to seek patent coverage of any standard being proposed at JEDEC. The court then sets forth its factual findings relevant to whether Rambus misled any of the Manufacturers by its conduct at JE-DEC. Finally, the court makes findings relevant to whether Rambus misled any Manufacturer by its dealings with that Manufacturer.

A. 1991-1996: Rambus and its Involvement with JEDEC

1. Rambus was founded in 1990 by two professors, Dr. Michael Farmwald and Dr. Mark Horowitz, who had been working together to address the increasing gap between microprocessor performance and DRAM performance. Conduct Trial Transcript at 4079:8-4081:24, 4091:9-4095:10, 5489:23-5490:3 (“Tr__”).

2. On April 18, 1990, Drs. Farmwald and Horowitz filed a patent application, serial number 07/510,898 (“the '898 application”) containing numerous claims relating to their efforts to solve this performance gap problem. Exh. 5131.

3. On April 16, 1991, Rambus filed an international patent application pursuant to the Patent Cooperation Treaty (the “PCT application”). Exh. 3583. The PCT application was published on October 31, 1991. The specification contained in the PCT application was identical to that contained in the '898 application and described, according to Rambus, the inventions that are at issue in Rambus’s infringement claims. Id.

4. Rambus attended its first JEDEC meeting as a guest on December 4-5, 1991. Ex. 3001 at 2. Rambus attended its final JEDEC meeting in December 1995. Tr. 1288:5-9. Rambus formally resigned from JEDEC by letter in June of 1996. Tr. 960:24-961:4.

5. Hynix was found to infringe all the patents Rambus selected to assert in the Hynix I trial. None of those patents were applied for until well after Rambus had resigned from JEDEC. Those patents are:

Patent Date of Date of Number_Title_Application_Issue

5,915,105 Integrated Circuit I/O Using a High 11/26/1997 06/22/1999 _Performance Bus Interface_

6,034,918 Method of operating a Memory 02/19/1999 03/07/2000 Having a Variable Data Output Length and a Programmable _Register_

6,324,120 B2 Memory Device Having a Variable 02/08/2001 11/27/2001 _Data Output Length_

6,378,020 B2 System Having Double Data 04/10/2000 04/23/2002 Transfer Rate and Integrated _Circuit Therefor_

6,426,916 B2 Memory Device Having a Variable 02/27/2001 07/30/2002 Data Output Length and a _Programmable Register_

6,452,863 B2 Method of Operating a Memory 02/27/2000 09/17/2002 Device Having a Variable Data _Input Length_

6.Rambus’s patent infringement claims against Hynix, Nanya and Micron in the '334 and '244 eases have been consolidated for trial but trial has not yet occurred. Not one of the patents Rambus has selected for assertion in the consolidated proceeding was applied for until approximately three-and-one-half years after Rambus resigned from JEDEC. Those patents include the '120, '020, '916, and '863 listed above plus the following:

Patent Date of Date of Number_Title_Application_Issue

6,182,184 Method of Operating a Memory 02/22/2000 01/30/2001 Device Having a Variable Data _Input Length_

6,266,285 Method of Operating a Memory 05/08/2000 07/24/2001 _Device Having Write Latency_

6,314,051 Method of Operating a Memory 07/31/2000 11/06/2001 _Device Having Write Latency_

6,546,446 Synchronous Memory Device Having 12/21/2001 04/08/2003 _Automatic Precharge_

6,584,037 Memory Device Which Samples Data 02/04/2002 06/25/2003 _after an Amount of Time Transpires_

6,751,696 Memory Device Having a 04/13/2001 06/15/2004 _Programmable Register_

B. Background Regarding JEDEC

7. JEDEC is a standards development organization. It develops standards for semiconductor products, including DRAMs. Tr. 444:9-24.

8. JEDEC is a non-profit organization. It formerly existed as part of the Electronic Industry Association (EIA), but it is now an independent organization. Tr. 457:13-^458:3; 619:5-621:18. While Rambus was a member of JEDEC, JEDEC operated as part of the EIA.

9. JEDEC has a board of directors. Below the board of directors, JE-DEC has approximately 50 committees. See Tr. 457:21-460:13.

10. The DRAM standards relevant to this case were developed by one such committee, JC^42.3. See Tr. 539:1-11.

11. JEDEC’s membership comprises numerous companies involved in industries related to semiconductors. It includes manufacturers like Hynix, Micron, Nanya and Samsung. It also includes users like HP, IBM, Intel and Sun. Tr. 446:5-446:25.

12. The JC-42.3 committee met about four to seven times a year. Meetings typically revolved around presentations made by committee members, which triggered discussions about the technology or feature that was the subject of the presentation. See Tr. 460:14-462:13. Meetings also included balloting during which members voted (2/3 majority required) on the contents of the standard being developed. Tr. 463:21-464:9.

13. JEDEC typically prepared minutes for all of its committee meetings. The minutes covered the “highlights” of activity at the meetings and are distributed to every member. Tr. 464:10-24. The minutes strived to reflect the “key decisions” and to “note presentations.” Id. After a meeting, the minutes were distributed to every member. Tr. 464:21-24. A meeting’s minutes were normally approved at the next committee meeting. See, e.g., Ex. 3005 at 4 (agenda item immediately following introductions was corrections and approval of prior meeting minutes). The fidelity of the minutes is significant because on various topics the minutes disagree with the trial testimony of various witnesses. Given that approximately fifteen years have elapsed and the natural biases of many of the witnesses, the court finds that the minutes are a more trustworthy source of evidence regarding what happened at JC-42.3’s meetings than most of the witness testimony.

C. JEDEC’s Patent Policy — JEDEC’s Manuals

14. When asked whether JEDEC had a “big rule book,” Desi Rhoden — a JEDEC board member and paid expert witness of the Manufacturers — responded, “Not really. Engineers wouldn’t read it anyway, I suppose.” Tr. 479:25-480:2. 5

15. Nonetheless, a few manuals existed. When Rambus joined JEDEC in 1991, JEDEC Manual of Organization and Procedure 21-H was in effect. Tr. 595:22-596:5; Ex. 6769. Manual 21-H lacks any rules or guidelines regarding disclosure of patent rights. See Ex. 6769.

16. Thus, while Manual 21-H was in effect, any written patent policy applicable to JEDEC trickled down from EIA’s rules. See Tr., 620:8-622:9. For example, at Richard Crisp’s first JEDEC meeting, the minutes reflect that JC-42.3 chairman Jim Townsend presented “the EIA patent policies.” Ex. 3002 at 5; Tr. 1039:8-1040:6. The “patent policy,” section 3.4 of the EIA Style Manual from August 1990, shown to the attendees was:

Avoid requirements in EIA standards that call for the exclusive use of a patented item or process. No program standardization shall refer to a patented item or process unless all of the technical information covered by the patent is known to the formulating committee or working group, and the committee chairman has received a written expression from the patent holder that one of the following conditions prevails:

(1) a license shall be made available without charge to applicants desiring to utilize the patent for the purpose of implementing this standard, or

(2) a license shall be made available to applicants under reasonable terms and conditions that are demonstrably free of any unfair discrimination.

Ex. 3002 at 28; see Tr. 1040:7-1041:15.

17.The EIA patent policy shown at the February 1992 JC-42.3 meeting says nothing about patent applications. It says nothing about a member’s intentions to file for patent coverage. It is unclear whether or how it imposes a duty on members of JEDEC to disclose issued patents, but it does require JEDEC not to include patented items or processes in a standard unless certain licensing conditions pertain.

18. At the September 1993 JC-42.3 meeting, the attendees saw a different patent policy presented. Tr. 506:10-507:16; 509:10-510:6; Ex. 3214 at 10. This “EIA/JEDEC PATENT POLICY SUMMARY” read as follows:

Standards that call for the use of a patented item or process may not be considered by a JEDEC committee unless all of the relevant technical information covered by the patent or pending patent is known to the committee, subcommittee, or working group. In addition, the committee Chairperson must have received written notice from the patent holder or applicant that one of the following conditions prevails:

(1) a license shall be made available without charge to applicants desiring to utilize the patent for the purpose of implementing this standard(s), or

(2) a license shall be made available to applicants under reasonable terms and conditions that are demonstrably free of any unfair discrimination.

Ex. 3214 at 12 (emphasis added to note substantive changes); see Tr. 509:10-15. At page 3 of the minutes, this attachment is described as “the policies.” Ex. 3214 at 3. On the actual attachment, the policy is clearly marked “JEDEC Manual No. 21-1 (Draft 3.1).” Ex. 3214 at 12. It also states “This material is a proposed revision of Std. 21-H and has not been approved by JEDEC.” Id.

19. Unlike the EIA policies previously shown at JC-42.3 meetings, this policy mentions patent applications but still does not mention “intentions” to file patent applications. The policy remains focused on the work of the committee and whether it may approve standards including patented technology. The policy does not clearly explain any disclosure mechanism.

20. The “final” version of Manual 21-1 contains language that is much more detailed than the draft summary shown in September 1993. The version of Manual 21-1 in evidence contains three provisions touching on patent disclosure, section 9.3, 9.3.1, and 9.3.2. See Ex. 3215, 19-20; Tr. 517:14-22 (admitting exhibit 3215).

21. The pertinent portion of section 9.3, titled “Reference to Patented Products in EIA Standards,” reads as follows:

EIA and JEDEC standard and nonproduct registration (e.g., package outline drawings) that require the use of patented items should be considered with great care. While there is no restriction against drafting a proposed standard in terms that include the use of a patented item* * if technical reasons justify the inclusion, committees should ensure that no program of standardization shall refer to a product on which there is a known patent unless all the relevant technical information covered by the patent is known to the formulating committee [sic] subcommittee, or working group. If the committee determines that the standard requires the use of patented items, then the committee chairperson must receive a written assurance from the organization holding the rights to such patents that a license will be made available without compensation to applicants desiring to implement the standard, or written assurance that a license will be made available to all applicants under reasonable terms and conditions that are demonstrably free if any unfair discrimination.

* * For the purpose of this policy, the word “patented” also includes items and processes for which a patent has been applied and may be pending.

22. The pertinent portion of section 9.3.1, titled “Committee Responsibility Concerning Intellectual Property,” reads as follows:

The Chairperson of any JEDEC committee, subcommittee, or working group must call to the attention of all those present the requirements contained in the EIA Legal Guides, and call attention to the obligation of all participants to inform the meeting of any knowledge they may have of any patents, or pending patents, that might be involved in the work they are undertaking. Appendix E (Legal Guidelines Summary) provides copies of viewgraphs that should be used at the beginning of the meeting to satisfy this requirement. Additionally, all participants must be asked to read the statement on the back of each EIA Sign-in/Attendance Roster....

23. Section 9.3.2, “Policy Statements on EIA/JEDEC Sign-in/Attendance Rosters,” states that “[t]he policy statements reproduced on the reverse side of EIA/JEDEC Sign-in/Attendance Rosters shall become an integral part of all Committee and working group meetings’ minutes, and a statement shall be included in the minutes indicating compliance with the foregoing policy.”

24. Finally, Appendix E includes the sample viewgraph that was intended to convey the patent policies to committee meeting attendees. Ex. 3215 at 27. The sample viewgraph is substantially similar to the one shown at the September 1993 meeting and reproduced above in paragraph 18. The sample viewgraph does not mention section 9.3.1’s “obligation of all participants to inform the meeting of any knowledge they may have of any patents, or pending patents, that might be involved in the work they are undertaking.”

25. It is not clear when or whether JEDEC Manual 21-1 was approved. The admitted version of manual 21-1 bears the date “October 1993.” See Ex. 3215 at 1. Mr. Rhoden believed that the seals and appearance of the manual confirm that it was approved by JEDEC by October 1993. Tr. 767:4-768:1. On the other hand, testimony from John Kelly, the president of JE-DEC and general counsel to EIA in 2001, suggested that manual 21-1 was never properly approved by the appropriate governing body. See Tr. 5168:24-5169:221; Docket No. 3573 (Mar. 19, 2008) (lodged video testimony of John Kelly played at trial).

26. It is also not clear when or how JEDEC Manual 21-1 was distributed to JEDEC members. Rambus’s JEDEC representative Richard Crisp did not receive a copy of Manual 21-1 until the middle of 1995, and he received it only after making a special request for “some rules” because “[he] was considering making a proposal for standardization.” Tr. 1083:14-1084:8.

27. Putting aside whether Manual 21-1 was ever officially approved, it appears to have guided JEDEC’s activities throughout the remaining period of Rambus’s attendance, at least in name. Tr. 771:13-772:5. For example, the minutes from the JC-42.3 committee meeting of September 1994 conclude with the prominent statement “THIS MEETING WAS CONDUCTED IN ACCORDANCE WITH EIA

• LEGAL GUIDES AND THE JE-DEC MANUAL OF ORGANIZATION AND PROCEDURE 21-1.” Ex. 3005 at 13; Tr. 611:3-14; 1208:10-20 (admitting exhibit into evidence). On the other hand, the “patent policies” presented by the chairman, Jim Townsend, and included as attachment A to the minutes of the September 1994 meeting, continue to recite the EIA policy from 1990 discussed above and attached to the 1992 minutes. See Ex. 3005 at 14; Tr. 611:21-612:10. Attachment A does not include the viewgraph purportedly required by Manual 21-1. It does not mention an obligation by members to disclose anything.

28. Whichever official manual governed JEDEC’s conduct, it is clear from the testimony of the secretary of JC-42 Kenneth McGhee and the manuals in evidence that no written policy ever required a JEDEC member to “reveal its intention ... to file patent applications in the future.” Docket No. 3551 (Mar. 17, 2008) (lodged video testimony of Kenneth McGhee played at trial).

D. JEDEC’s Patent Policy — JEDEC’s Sign-in Sheets

29. Mr. Rhoden also testified at length about the sign-in sheets used at JC-42.3 meetings. See Tr. 520:17-522:6; Ex. 3233. According to Mr. Rhoden, JEDEC’s patent policies were “very important” and the sign-in sheets “ma[de] sure that nobody can forget it.” Tr: 521:17-21. To that end, the sign-in sheet included on its backside language about JEDEC’s patent policies. Tr. 521:23-522:6.

30. The sample sign-in sheet reproduces what, at first glance, appears to be section 9.3 of Manual 21-1. Compare Ex. 3233 at 2 with Ex. 3215 at 19. Upon inspection, an important difference emerges. The sample sign-in sheet refers only to a “patented item.” It does not mention anything about features covered by pending applications. The sample sign-in sheet also lacks any language resembling section 9.3.1 of Manual 21-1. The sign-in sheet says nothing about any obligation to disclose any known patents or applications. It speaks only of using “great care” in considering whether to use a patented feature in a standard and of the obligation of the committee chairperson to ensure that no standard include a patented feature unless assurances have been made.

31.Notably, the sign-in sheet includes other reminders aimed at ensuring JEDEC’s and its members’ compliance with the antitrust laws. Among those provisions is the reminder that “the exchange of company information relating to future plans affecting the design, research and development, production, and distribution or marketing of products” is improper. Ex. 3233 at 2; see Tr. 623:8-627:24. From the evidence presented at trial, a JEDEC member did not have guidance and would probably not understand, at least from any information acquired from JE-DEC, how a JEDEC member could safely comply with both (a) the purported duty requiring a member to disclose its “intentions” to file a patent application as advocated by the Manufacturers and (b) the duty not to disclose a company’s future plans relating to the research and development of products given the intertwined nature of conducting research and preparing a patent application.

32. By contrast to Mr. Rhoden’s testimony that JEDEC’s patent policies were “very important” and that the sign-in sheets were used to “make sure that nobody can forget it,” Micron’s Terry Lee (a JEDEC representative) explained the flaws in the sign-in process: “[T]he way the sign-in process worked is they would just pass around a stapled form and you’d check your name off, or you’d sign your name on. And if I was out of my seat at the time, I would sign in. But sometimes you were out of the room talking or checking in or out of the hotel.” Tr. 3169:10-22. This process explains why Mr. Lee “usually” but “not always” signed in at meetings. Tr. 3169:10-15. Based on Mr. Lee’s testimony, it is doubtful that many JEDEC representatives read the EIA patent policy on the reverse side of the sign-in sheet or that it meaningfully informed their expectations.

E. JEDEC’s Patent Policy — JEDEC’s Ballots

33. In addition to sign-in sheets, Mr. Rhoden testified that JEDEC’s ballots were “another expression of the importance that JEDEC placed upon disclosure of [intellectual property].” Tr. 524:1-4. The Manufacturers submitted a ballot from June 1992 as a sample of the “ballot form used at JEDEC at or about [1992].” Id. 522:12-523:3; Ex. 3613.

34. The Manufacturers did not submit ballot forms from the 1993-1996 period, leading the court to infer that JEDEC did not change the ballot forms with respect to patent disclosure during that time period.

35. The 1992 ballot form states: “If anyone receiving this ballot is aware of patents involving this ballot, please alert the committee accordingly during your voting response.” Ex. 3613 at 2; Tr. 522:17-25. The ballot form does not state that anyone receiving the ballot must disclose patent applications or intentions to file applications of which the recipient is aware.

36. Rambus’s JEDEC representatives received ballots instructing them to disclose such patents. Tr. 524:5-9.

37. When asked whether Rambus “actually voted in any of the elections that they ... were presented ballots for,” Mr. Rhoden testified: “Yes. They, they voted quite often, actually. I counted the ballots. That’s how I know.” Tr. 524:10-25. He further testified: “The chairman — the person that’s actually doing the, the distribution of the ballots is the person that winds up counting them. So in this case, it was associated with SDRAM, and I was the one who actually counted the ballots. So, yes, I counted their ballots many times.” Id.

38. To the extent Mr. Rhoden’s testimony suggests that Rambus voted at more than one meeting, it is misleading. On the contrary, the unrebutted evidence of Rambus’s voting record presented at trial is as follows. Rambus voted at only one meeting. Tr. 1003:23-1004:6. The ballots concerned four technologies that the committee was considering to be included in SDRAM. Id. Rambus’s representative at the time, Richard Crisp, voted “no” as to each technology. Id.; Tr. 1154:23-25; Tr. 1383:12-18. The technologies on the ballot included programmable CAS latency and programmable burst length. See Ex. 3613 at 3.

39. After Rambus voted “no,” Hitachi’s representative Farhad Tabrizi criticized Rambus for its vote. Tr. 1385:7-23 (Crisp); Tr. 3780:9-13 ■ (Tabrizi). Mr. Tabrizi explained . that his criticism was based on his opinion that Rambus’s “no” vote was intended to delay the standardization of SDRAM. Tr. 3780:9-3782:16. While Mr. Tabrizi initially testified that he made this criticism privately, Tr. 3780:20-3781:1, his refreshed recollection was that he criticized Rambus in front of many other JEDEC members and that the rest of the committee agreed with his criticism of Rambus, Tr. 3782:8-16.

40. Following this incident, Mr. Crisp’s superior Dave Mooring instructed him not to vote at JEDEC meetings. Rambus (through Mr. Crisp) never voted again. Tr. 1385:24-1386:9.

F. JEDEC’s Patent Policy — Other Minutes’ Records of the Patent Policy Presentations

41. As • discussed above, the JC 42.3 committee meeting minutes from February 1992 attached EIA’s policy referring to the use of features covered by issued patents. The September 1993 minutes attached a draft of the “policy summary” of Manual 21-1 that suggested that standards should not include features covered by pending patents. The September 1994 minutes state that Manual 21-1 governed the conduct of the meeting, but attached the old EIA guidelines that do not mention pending patents.

42. The minutes from the September 11, 1995 meeting include the familiar 1990 EIA policy (seen in the February 1992 and September 1994 minutes) regarding the use of features covered by issued patents. Ex. 3224 at 20; Tr. 1107-20-1109:5 (admitting the exhibit into evidence). The attachment of the “patent policy” does not include the 21-1 viewgraph mentioning applications. The minutes include no other “patent policy.”

43. The attachment from the September 1995 meeting lays out the following procedure:

— Show JEDEC Patent Policy at each Task Group and Committee meeting.

— Include JEDEC Policy in each committee’s official minutes.

— Request Presentation Sponsors to state their Company’s patent position.

— Continue to ask for ballot response forms to indicate patent position.

— Submit proposed ballot items known to have patents to EIA Legal Counsel.

—. Review items identified as of potential patent interest at each meeting, and resolve patent status prior to (choose one):

A. Presentation

B. Approval to go to Ballot

C. Ballot Approval

D. Ballot Submission to Council

E. Ballot Approval by Council

Ex. 3224 at 20. An identical “procedure” appears in the attachment to the September 1994 minutes. See Ex. 3005 at 14.

44. This procedure — in use long after the purported adoption of Manual 21-1 — “requested] presentation sponsors to state their Company’s patent position.” Such a require ment accords well with principles of equitable estoppel — that a JEDEC member could rely on the assumption that if a sponsor advocated a particular standard the sponsor’s company did not have and had not applied for patent coverage on the standard. A reasonable inference, however, is that members other than presentation sponsors were not expected to disclose any knowledge they possessed of patents, patent applications, or intentions to file patent applications anytime such materials related to the work of the committee. Also curious is the procedure’s repeated reference to a need to ‘‘continue to ask for ballot response forms to indicate patent position.” The sensible inference from this bullet point in the patent policy procedure is that members of JC-42.3 repeatedly failed to disclose patent positions on ballots, despite the wording on the ballots. Such repeated failure does not reconcile with Mr. Rho-den’s belief that JEDEC members shared a broad disclosure expectation.

45.Before every JC-42.3 meeting, JE-DEC held a plenary session for all of the JC-42 committees. Tr. 3839:16-25. At the December 9, 1996 JC-42 plenary session (i.e., shortly after Rambus’s resignation), the combined committees went over the “EIA/JEDEC patent policies” and attached them. Ex. 8307 at 4; Tr. 3838:23-3839:4 (admitting pages 1, 4 and 10 of Ex. 8307). Page 10 of the minutes show the “patent policy.” Tr. 3840:21-3841:3. The attached “patent policy” is an updated (1995) version of the EIA rule urging the committee to “avoid requirements in EIA Standards that call for use of a patented item or process.” Ex. 8307 at 10. No mention of patent applications appears in the attachment. See id. No mention of disclosure obligations appears in the attachment. See id. The same 5-step procedure discussed above also appears in the December 1996 plenary session minutes. Id.

46. In 1997 in correspondence between Hynix’s Farhad Tabrizi and JE-DEC, Mr. Tabrizi asked for “a copy of the JEDEC patent laws or part of the JEDEC bylaws that deals with patent and patent disclosure and licensing.” Jim Townsend wrote back: “[T]hat is in every set of minutes we shgow [sic] it at the plenary session each time. The exact paragraphs [sic] are cited and reproduced as part of the cover material.” Ex. 6293; Tr. 3835:10-3838:5. Mr. Tabrizi understood Mr. Townsend to be telling him that if Mr. Tabrizi consulted the minutes, he would find the patent policy. Tr. 3838:2-5.

47. Minutes from other JC^42.3 meetings following the 21-1 policy were authenticated, e.g., December 1994 (Ex. 3491), March 1995 (Ex. 3492), May 1995 (Ex. 3033), January 1996 (Ex. 3070), and March 1996 (Ex. 3080). Tr. 1301:17-1304:5. Most of these exhibits were never received into evidence, and the pages of the exhibits that were eventually received did not relate to patent policies.

G. JEDEC’s Patent Policy — Patent Tracking List

48. A prominent feature of the committee’s minutes was Jim Townsend’s “patent tracking list.” According to Desi Rhoden, the list kept track of everything “that has been dis closed inside the committee so we can make appropriate decisions as we’re moving forward on the standards.” Tr. 471:21-473:13.

49. Jim Townsend introduced the patent tracking list at JC-42.3’s meeting in December of 1991 (Rambus’s first meeting). See Ex. 3003 at 11. The minutes reflect that Texas Instruments (TI) “asked what the purpose of the list was.” Id. The minutes note the response: “The purpose was only to track and identify patented items of Committee proposals. Companies who hold patents identified can respond to Committee, if they wish.” Id. (emphasis added).

50. When confronted with the minutes’ statement that members could respond to the patent tracking list “if they wish,” Mr. Rhoden testified “well, they — they—perhaps the wording is not right. But they are required to disclose. They were required to disclose at this time. So the — they can respond if they wish, but it was — it’s not optional.” Tr. 637:17-22. Mr. Rhoden previously testified that the minutes reflect the “highlights” and “key decisions” of meetings. He conceded that no one corrected the minutes to reflect the “not optional” nature of patent disclosure in 1991. Id. 637:23-638:8.

51.The patent tracking list from the September 1993 meeting was admitted into evidence and discussed. See Tr. 471:13-474:22; Ex. 3005 at 16-18. The entries listed the “patent number,” holder, subject matter or feature, the source of the information, and the committee whose work the patent involved. Ex. 3005 at 16-18. A portion of the September 1993 tracking list is reproduced below:

Patent Issues to Track

Patent Number Holder Subject Source Status

3,771,145 P. Weiner ROM Addressing Toshiba JC42.3

9 AMD Slew Rate-CTT Ram-tron JC42.3

Negative GTL AT&T JC16

Japan? AMP Small Outline SIMM AMP JC42.5

(3) AMP SIMM SOCKETS AMP JC42.5

4,851,834 DEC 3-Port VRAM DEC JC42.3

Foxconn card polarization Foxconn JC42.5

pending Fujitsu VSMP Fujitsu JC42.3

Gould ZIP-SIP HP JC42.5

4,811,299 Hitachi WCBR Hyundai JC42.3

pending Hitachi ST-ZIP Package Hitachi JC42.5

Further Study Hitachi? Addressing with Redundant Address IBM JC42.3

4,928,265 Hitachi SDRAM Toshiba JC42.3

5,083,296 Hitachi SDRAM Toshiba JC42.3

4,984,214 IBM Half SAM IBM JC42.3

pending IBM 8 byte SIMM IBM JC42.5

IBM? BGA Toshiba JC42.3

5,126,975 IDTI Burst Mode Unisys JC42.3

52. A few aspects of the list deserve attention. First, the entire list runs three pages and contains sixty entries. Three of the entries (all included in the excerpt shown above) are “pending,” i.e., patent applications. In other words, the patent tracking list reflects that as of September 1998 there had been only three instances of a JEDEC representative disclosing a pending patent application that related to the work of the committee.

53. Approximately one-third of the entries on the list reflect a “source”

that is different than the “holder.” In other words, a substantial portion of the “patent issues to track” were not voluntarily disclosed but first raised by others. This explains why the patent tracking list was referred to as “the squealer’s list” among the members of JC-42.3. Tr. 4707:17-4708:9 (testimony of Alan Grossmeier, Cray’s JEDEC representative).

54.The last patent tracking list in evidence comes from JC 42’s plenary session from December 1996. See Ex. 8307 at 11-12; Tr. 8341:4-17 (admitting pages 11 and 12). For comparison, the same portion of the list is reproduced below:

[[Image here]]

55. The list is notable for its similarities. The three previously disclosed “pending” patent applications remain pending, over three years later. The Hitachi matter that required “further study” in September of 1993 continued to require “further study” at the end of 1996.

56. In total, the tracking list as of December 1996 comprised 84 entries. In addition to three prior “pending” disclosures (all of which remained “pending”), the list identified two further disclosures of “pending” applications related to a feature.

57.In other words, over the span of two years (implying at least eight meetings of JC-42), the committee had identified 24 new patent issues to track, or approximately 3 per meeting. At each meeting of JC 42’s various committees, Desi Rho-den believed that “fifty or one hundred [presentations] would not be

uncommon.” Tr. 463:6-11. Based on Mr. Rhoden’s approximation and the two patent tracking lists, the court estimates that roughly (and generously) 1 in 15 presentations about a feature or technology at JEDEC also included a disclosure of a “patent issue.” Compare with Tr. 552:2-22 (Rhoden testimony about how disclosures happened at presentations).

58. The December 1996 list reflects no disclosures of Hyundai (now Hynix) intellectual property. The list reflects two disclosures of Micron intellectual property, both of which were on the September 1993 list. The list reflects no disclosures of VLSI (Desi Rhoden’s employer) intellectual property. In other words, trial witnesses Farhad Tabrizi, Terry Lee, and Desi Rhoden made no disclosures of their companies’ intellectual property between 1993 and 1996.

59. In its June 1996 resignation letter, Rambus identified a number of patents. JEDEC did not add any of those patents to the December 1996 patent tracking list. Compare Ex. 3120 at 2 with Ex. 8307 at 11-12.

60. As seen on both of the patent tracking list excerpts reproduced above, Toshiba suggested by September of 1993 that IBM might have intellectual property rights to “BGA” or “ball grid array.” This confrontation produced substantial testimony at trial about how the patent tracking list and any JE-DEC disclosure duty functioned in practice, e.g., Tr. 644:14-654:5.

61. Following Toshiba’s disclosure, IBM’s representative, Gordon Kelley, responded regarding the BGA feature with an August 31, 1993 fax to JC-42.3 chairman Jim Townsend and JC-42.3 secretary Ken McGhee. See Ex. 6092. The subject of the fax was “BGA Patent/License Rights” and read:

Jim: IBM Intellectual Property Law attorney’s [sic] have informed me that we will not use JEDEC as a forum for discussing this subject. It is the responsibility of the producer to evaluate the subject and to workout [sic] the proper use of rights. So, I can not confirm or deny any [intellectual property law] rights,

Gordon Kelley

IBM Member JC-42.3

62. Mr. Kelley testified that he believed that his response complied with his understanding of any disclosure duty. He explained that he further investigated the subject of whether IBM had patents to ball grid arrays, and his investigation uncovered 5,000 (five thousand) such patents held by IBM and relating to ball grid arrays. He “looked at the first 200 to 300 of those patents” and determined that those patents did not apply to the standard under consideration and that he told this to the JC-42.3 committee following the fax. Tr. 3605:12-3608:9; see also Docket No. 3508 (lodged Kelley video testimony).

63. The December 1993 JC-42.3 meeting also involved “lots of patent issues” (related to TI) and more involvement by Gordon Kelley. Tr. 654:6-656:5. The minutes state that “[a]s a side issue, IBM noted that in the future they will not come to the Committee with a list of applicable patents on standards proposals. It is up to the user of the standard to discover which patents apply.” Ex. 6098 at 8.

64. Mr. Rhoden testified that with both BGA and this December 1993 disclosure, Mr. Kelley actually said to the committee that IBM would not search their patent database. This did not bother Mr. Rhoden because he understood JEDEC’s policy to be that if a member does not disclose a patent, that member could not enforce the patent against the standard. Thus, Mr. Rhoden felt that IBM’s declination was “no harm, no foul.” Tr. 656:6-658:4. Mr. Rhoden’s testimony on this point is not credible because the actual documents — the minutes and the August fax — are inconsistent with the theory that IBM did not intend to assert its BGA, or other, patents. They are also inconsistent with Mr. Kelley’s “promise” to the committee that he would “give you all of the information that I am aware of as the member for IBM, but I cannot promise to give you all of the tens of thousands of patents that are created annually by IBM Corporation.” Docket No. 3508 (lodged Kelley video testimony).

65. Gordon Kelley also testified that he disclosed more patents and patent applications than ended up on the patent tracking list. See Tr. 3627:9-21. Mr. Kelley admitted that he made no effort to correct the minutes to reflect such additional disclosures. Id. 3627:22-3628:9. To the extent Mr. Kelley did make disclosures on IBM’s behalf that do not appear on the patent tracking list, it appears that Mr. Kelley would have made those disclosures in conflict with directions he received from IBM’s lawyers. See id. 3628:10-3629:3. This might explain Mr. Kelley’s failure to correct the minutes, but raises the possibility that JEDEC representatives like Mr. Kelley deliberately disobeyed their principals’ instructions in favor of JE-DEC. Furthermore, his testimony calls into question the accuracy of the minutes and their trustworthiness. In short, if the testimony is true, it implies that JEDEC’s records are deliberately incomplete and that some JEDEC representatives acted in JEDEC’s interests at the expense of their principals’. This is a plausible interpretation of the evidence, but the court is more inclined to believe that Mr. Kelley’s memory about additional disclosures was incorrect, that the patent tracking list is accurate, and that JEDEC representatives like Mr. Kelley did not act at cross-purposes to their lawyers. The court therefore declines to credit the testimony that additional disclosures were made that were not reflected on the list.

66.Mr. Rhoden testified that the patent tracking list helped the committee “make appropriate decisions as we’re moving forward on the standards.” After a critical analysis of the patent tracking lists in evidence, how the lists were updated, and how many entries there are, the court draws three conclusions. First, if any disclosure duty within JEDEC was as broad as suggested, the patent tracking list should have been substantially longer. Second, the gaps and failures to follow up on “?” entries on the list suggest that JEDEC’s members did not consider tracking patent issues to be terribly important. Third, the JEDEC disclosure duty advocated by the Manufacturers could not have possibly accomplished the purported goal of creating an “open standard” because the alleged duty was limited to the knowledge (and potential willful ignorance) of JE-DEC’s member representatives. Because it would have been ineffectual, it is less likely the disclosure duty advocated by the Manufacturers existed.

H. JC-42.3 Committee Members’ Expectations and Recollections

67. Desi Rhoden testified that his understanding of JEDEC’s patent disclosure policy was: “JEDEC members are required to disclose anything in the patent process for which they have knowledge that’s relevant to or involving • work for JEDEC.” Tr. 481:15-19; see id. 473:4-13;- 510:7-22. He believed such disclosures had to be made “as early as possible whenever presentations are made.” Id. 552:23-553:8. He summarized it as “early and often” and testified that disclosures had to be repeated. Id. 553:9-13.

68. Richard Crisp, Rambus’s representative, believed that he should disclose any patents or pending patents that he thought related to a feature if he proposed that feature, but that he also had the impression that any disclosure was voluntary. Tr. 1368:7-13; 1400:12-1401:16.

69. Richard Crisp’s contemporaneous documents from his time as a JE-DEC representative support the prevailing confusion about the scope of any duty. See Tr. 1057:22-1059:22; Ex. 3030. Exhibit 3030, an email of Mr. Crisp’s reporting on a December 1992 JE-DEC meeting, indicated that a patent lawyer from Bronson, Bronson, & McKinnon had come to speak to the committee and that the lawyer was unclear on what JEDEC required its members to disclose and that it would be “inadvisable” to require the disclosure of patent applications. Ex. 3030.

70. Alan Grossmeier was Cray’s representative-at JC-42.3 meetings from 1989 through 2000. Tr. 4704:14-4705:3. There was no indication that Mr. Grossmeier was biased in favor of either Rambus or the Manufacturers. On the other hand, Mr. Grossmeier conceded that “patent issues were not necessarily the priority for [him]” and that others at JEDEC were more interested in the requirements of-tbe patent policy. ' Id. 4710:8-15. Taken as a whole, the court found Mr. Grossmeier’s testimony credible.

71. Mr. Grossmeier recalled Jim Townsend’s presentations ■ differently than Desi Rhoden: “Typically he would flash these, slides, usually not long enough to read them. He would, just kind of, these are the JEDEC patent policy and don’t worry about reading them. They will be in the minutes. ,He would flash the, the first couple slides and then he -had a tracking list of, it was humorously- referred to as the squealer’s list, basically.” Id. 4707:9-20.

72. Mr. Grossmeier recalled that Mr. Townsend presented EIA’s patent policy and that JEDEC was governed by EIA’s patent policy. Tr. 4708:18-4709:1. He did not recall “any formal documentation” of the patent policiés and “[his] interpretation was based more on how the committee members themselves handled it.” Id. 4709:2-11.

73. Mr. Grossmeier believed that JE-DEC required sponsors presenting features to disclose patents and that the rules were otherwise vague about disclosing issued patents. Tr. 4709:12^1709:25. He was adamant that patent applications did not have to be disclosed. Id. 4710:1-7 (“They were not. They were not. No, I did not expect that someone would [disclose applications].”).

74. Gordon Kelley of IBM testified that he understood the JEDEC disclosure duty to require members to disclose patents and patent applications of which the member was aware that would be required for use of the patented feature. Tr. 3602:13-3603:3. He felt the need to be clear though that any duty was limited to the JEDEC representative’s personal knowledge; he was not willing “to crawl through 5,000 patents” held by IBM. Docket No. 3508 (Mar. 11, 2008) (lodged video testimony of Gordon Kelley); Tr. 3620:12-16.-

75. The Manufacturers also presented expert testimony from Graham Allan, an engineer who attended JC-42.3 meetings and was “very active” in setting the SDRAM, DDR, and DDR2 standards. Tr. 2578:10-2580:22. ■ Mr. Allan represented Mosaid, a “third party designer” that does not build DRAMs; rather, Mosaid designs memory schematics for other people. See id. 2578:4-9; 2578:15-2579:1. Despite Mr. Allan’s intimate involvement with JEDEC, the Manufacturers explicitly declined to ask him about his expectations and understanding of any disclosure duties. See id. 2581:12-21. Although the Manufacturers had their reasons for not asking Mr. Allan such questions, the court infers that had Mr. Allan testified on this topic, his testimony would not have supported the broad disclosure duty urged by the Manufacturers. 6

76.Hynix’s JEDEC representative, Farhad Tabrizi, testified that his understanding of the JEDEC disclosure duty was: “The policy was you have to disclose anything that you know about your intention of patent, patent application, your intention of filing. If you don’t disclose, you cannot collect later.” Tr. 3722:25-3724:1. Squaring Mr. Tabrizi’s testimony about his memory of the disclosure duty with his 1997 email requesting copies of “the JE-DEC patent laws or part of the JEDEC bylaws that deals with patent and patent disclosure and li censing” is somewhat difficult. Mr. Tabrizi’s testimony supports a broad disclosure duty based on expectations, but his writing in 1997 suggested that he (a) did not know where to find JEDEC’s rules regarding patent disclosure, and (b) believed that such rules would be written down. Further, his intense bias against Rambus may have colored his testimony.

77.Micron’s JEDEC representative, Terry Lee, also testified about the JEDEC disclosure duty from 1994 to 1996. See Tr. 3242:17-3243:25. His testimony corroborated Mr. Grossmerier’s that the committee chairman Jim Townsend would take a transparency and “stick one down on the overhead and say this is the patent policy.” Id. 3243:12-18. He described Mr. Townsend as a “colorful character” and that sometimes people would ask him questions about the policy and “Jim would usually answer them.” Id. 3243:15-21. Mr. Lee remembered the disclosure duty as: “a requirement to disclose any patents or patent pending that may relate to the work of the committee. And the committee had the responsibility to avoid the use of the patents in the standard. And in the case that a patent was identified, then there was a requirement to provide what we called a rand licensing term, or whoever held the patent had to agree on a reasonable and non-discriminatory licensing term.” Id. 3244:17-3245:1. In other words, Mr. Lee — a Micron witness — did not recall a duty to disclose intentions to file patent applications. He did, however, testify that he believed he had to disclose patent applications.

I. Rambus Did Not Breach Any Clearly Defined Disclosure Expectation

78. The evidence suggests that the scope of a JEDEC member’s expectation of disclosure ranged from non-existent to astonishingly broad. The jury found that the JEDEC members did not share a clearly defined expectation that members would disclose relevant knowledge they had about patent applications or the intent to file patent applications:

Disclosure expectations. “Did JEDEC members share a clearly defined expectation that members would disclose relevant knowledge they had about patent applications or the intent to file patent applications on technology being considered for adoption as a JEDEC standard? No.”

Special Verdict Form ¶ 45.

79. It does appear, however, that members at least expected those making sponsoring presentations to disclose any patents the sponsoring company had covering the advocated standard. The members may well have had a broader disclosure expectation. However, Mr. Rho-den’s testimony suggesting that the applications Rambus had in prosecution during its membership should have been disclosed was equivocal and lacking in analysis. He testified that he believed certain applications should have been disclosed based on his reading of the claim language. Tr. 553:14-559:2. This analysis was cursory and turned on Mr. Rhoden’s belief that the applications should have been disclosed because they “involved the work of JEDEC,” a standard that has no clear definition or meaningful support. In any

event, Rambus’s alleged conduct— failing to disclose intentions to seek patents and failing to disclose certain applications it had in prosecution (which were based on the same specification that was disclosed twice to JEDEC) — did not violate any clearly defined disclosure expectation. By the time it withdrew from JEDEC, Rambus had not filed a patent application claiming a standardized feature under consideration during its JEDEC membership.

J. Rambus’s Representations at JE-DEC — The 1992 SDRAM Ballot

The Manufacturers’ also base their estoppel defense arising from JEDEC on the nature of the few statements Rambus actually made at JEDEC.

80. As discussed above, Rambus voted on one set of ballots involving SDRAM. The members of JC-42.3 were aware of Rambus’s voting and publicly disapproved of Rambus’s behavior because of their belief that Rambus was trying to stall the standardization of SDRAM.

81. In light of the narrow scope of the duty to disclose defined on the ballot, no reasonable person within JEDEC could interpret Rambus’s ballots as a statement that Rambus would not seek intellectual property on matters related to the ballot.

K. Rambus’s Representations at JE-DEC — Richard Crisp’s Head Shake

82. According to Mr. Rhoden, the JC-42.3 chairman Gordon Kelley asked Richard Crisp “if Rambus had any, any I.P. that related to any of the things that were present.” Tr. 539:1-17. Mr. Rhoden testified that Mr. Crisp “just shook his head. He didn’t say a word.” Tr. 539:21. Mr. Rhoden testified that he personally witnessed this because he was in the room at the time. Tr. 540:4-5. Mr. Rhoden could not recall clearly when this occurred however. Tr. 538:14-19.

83. Mr. Crisp remembered the interaction differently. See Tr. 1138:21— 1139:1. Mr. Crisp testified that “he asked me if I cared to comment.” Mr. Crisp says that he declined to comment. Tr. 1138:21-1139:10. Mr. Crisp did this by shaking his head “no.” Tr. 1140:7-14. Mr. Crisp also testified that no one followed up on his refusal to comment or complained that “not commenting” was forbidden. Id. 1347:5-1348:9.

84. Mr. Crisp sent contemporaneous emails from JEDEC meetings to other Rambus personnel. In an email he sent from this JEDEC meeting, Mr. Crisp wrote: “Siemens expressed concern over potential Rambus Patents covering 2 bank designs. Gordon Kelly [sic] of IBM asked me if we would comment which I declined.” Ex. 3412; Tr. 1144:12-23 (admitting exhibit).

85. The portions of the JEDEC minutes from the meeting in evidence contain no mention of this discussion. See Tr. 1128:8-13; Ex. 3003, 1-2, 30-37. The court infers from the absence of evidence in the record that the minutes lack any record of this event.

86. The deposition testimony of Gordon Kelley accords with Mr. Crisp’s version of events. See Docket No. 3568, 379:14-380:2 (“I remember that both Motorola and Rambus were represented at that meeting and did not comment on those patents.”).

87. Of the two versions of the events, the court believes Mr. Crisp’s. First, his story is confirmed by contemporaneous documentation that long pre-dated any litigation. Second, Mr. Crisp’s testimony is corroborated by Mr. Kelley’s. Third, Mr. Crisp’s testimony was consistent with Rambus’s policy of not commenting. Finally, Mr. Rho-den’s testimony was contradicted by the contemporaneous documentation of events, suggesting that Mr. Rhoden’s memory of these events (which took place about 15 years ago) has slipped.

88. The court therefore finds that when Rambus was asked to comment about patents related to 2-bank memory architecture (a feature not at issue in this case), Rambus declined to comment. The committee did not follow up on the issue, nor consider the issue worth following with its patent tracking lists.

89. Mr. Crisp’s head shake could not have been reasonably construed as a statement that Rambus lacked any form of intellectual property on the 2-bank design, let alone a statement that Rambus lacked any form of intellectual property covering any other feature under consideration.

L. Rambus’s Representations at JE-DEC — The '703 Patent

90. Richard Crisp disclosed one Ram-bus patent to the JC-42.3 committee, U.S. Patent No. 5,423,703 (Exhibit 3219). The '703 patent has the same specification as all of the patents-in-suit. The claims-in-suit, however, were not even drafted while Rambus was a member of JEDEC.

91. The '703 patent was Rambus’s first issued patent. Tr. 928:5-16. Mr. Crisp was proud of Rambus’s first issued patent. Id. 1143:6-11. He was, however, later reprimanded by Rambus for disclosing a patent to JEDEC without authorization. Id. 1212:6-21.

92. Richard Crisp did not believe the patent related to JEDEC’s work, but he disclosed it at the September 1993 JEDEC meeting. Tr. 928:22-931:24. Despite the patent’s “unrelatedness” to the work of JEDEC, the '703 patent was placed on the patent tracking list and remained there until at least December of 1996. See Ex. 8307 at 11.

93. Nobody at the September 1993 JE-DEC meeting followed up the '703 disclosure with questions about the patent, or the list of related applications listed on the patent. Tr. 1346:16-25.

94. Farhad Tabrizi, a Hitachi JEDEC representative and eventually Hynix’s JEDEC representative, “looked at” the '703 patent but “did not analyze it:” By “looked at,” Mr. Tabrizi meant that he reviewed the first page, i.e., the abstract. See Tr. 3940:5-3941:12. The '703 patent was the only Rambus patent Farhad Tabrizi reviewed before the litigation began. Id. 3938:22-3939:8.

95. Mr. Crisp’s disclosure of the '703 patent could have given JEDEC members the impression in 1993 that Rambus would disclose its issued patents. Rambus’s later statements clarified this point. Whether or not Rambus disclosed issued patents, however, is not relevant, because the Manufacturers do not accuse Rambus of failing to disclose an issued patent.

M. Rambus’s Representations at JE-DEC — Rambus’s SyncLink Statement

96. In May 1995, a proposal for a different DRAM architecture — Syn-cLink or SLDRAM — was introduced at JEDEC. Tr. 1254:2-20. Because the SyncLink proposal resembled Rambus’s RDRAM, 7 Ram-bus was asked whether it possessed patents related to SyncLink. Id. 1254:21-1255:16. Richard Crisp did not answer at that meeting, but instead consulted with his superiors at Rambus about how to answer. Id. The Manufacturers authenticated the minutes from this meeting through Mr. Crisp, but did not move the document into evidence during Mr. Crisp’s examination. Id. 1302:20-23. The court infers from this that nothing in the minutes would bolster the Manufacturers’ case.

97. Mr. Crisp prepared a response to the committee’s concern with the help of Rambus’s in-house counsel, Anthony Diepenbrock. Messrs. Crisp and Diepenbrock were concerned about equitable estoppel, and they prepared Rambus’s response accordingly. Tr. 1256:9-1258:2. It bears noting that Mr. Diepenbrock was concerned about Rambus’s attendance at JEDEC, and Rambus stopped attending JE-DEC by the end of 1995 and formally resigned in 1996.

98. Accordingly, Mr. Crisp read a prepared statement at the September 1995 statement to address the committee’s concerns about Rambus’s intellectual property and SLDRAM. Tr. 1258:3-25; 1259:10-21. Rambus’s statement to the committee, Exhibit 3090, was as follows:

At the last JEDEC meeting it was noted that the subject of the SyncLink DRAM proposal bears a strong resemblance to Rambus DRAMs and so I was asked to make a comment about the Rambus intellectual property position as it may relate to the Synclink proposal.

The first Rambus patents were filed more than five years ago, with development starting years before. We have confirmed that the first Ramlink and Synclink committee meetings and draft proposals occurred years after Rambus began development.

Today there is no finalized Synclink specification or DRAMs to analyze for potential infringement. Best case, it will be several years before they will exist. So to fully determine Synclink patent risk, this committee should look not just to Rambus but also internally. For example, we are aware of 13 U.S. patents relating to SDRAMs which were issued to member companies of this committee. All were active participants in the SDRAM standardization process. Included in this list are Hitachi, Mitsubishi, Mosaid, Motorola, Oki, Samsung, TI, and Toshiba.

Additionally, Synclink is being sponsored by an organization with a less stringent patent policy than JEDEC. Under the bylaws of the IEEE working groups, attendees represent themselves only, not their employers. Furthermore they are free to patent whatever they desire, and are not bound to relinquish any of their rights to their patents by presenting their ideas for standardization.

Therefore, we conclude that products defined by committees are not guaranteed to be free of patent encumberances [sic].

At this time, Rambus elects to not make a specific comment on our intellectual property position relative to the Syn-clink proposal. Our presence or silence at committee meetings does not constitute an endorsement of any proposal under the committee’s consideration nor does it make any statement regarding potential infringement of Rambus intellectual property.

Ex. 3090. In addition to reading the statement, Mr. Crisp showed it on the overhead and provided a copy to be included in the minutes. Tr. 1265:2-10; accord Tr. 1392:6-1393:4; Ex. 3224 at 26 (including Mr. Crisp’s statement as Attachment C to the September 1995 minutes).

99. The committee’s response to Ram-bus’s statement was less than enthusiastic. The chairman, Gordon Kelley, responded “I heard a lot of words, but I don’t know if anything was said.” Tr. 1265:11-15.

100. Construed in isolation, portions of Rambus’s statement could be misleading, specifically the insinuation that JEDEC had stronger rules than IEEE. Taken as a whole, however, no reasonable JE-DEC member could have been misled by this statement. The statement is replete with warnings, and ends with the most clear warning of all: “Our presence or silence at committee meetings does not constitute an endorsement of any proposal under the committee’s consideration nor does it make any statement regarding potential infringement of Rambus intellectual property.”

101. Even were it reasonable to be misled by Mr. Crisp’s statement, the JC-42.3 committee was not, as evidenced by chairman Gordon Kelley’s skeptical and pointed response.

N. Rambus’s Representations at JE-DEC — Rambus’s Resignation Letter and the Omitted Patent

102. Rambus sent its resignation letter to JEDEC on June 17, 1996. Tr. 1293:13-1294:1; Ex. 3120. The letter contained two substantive paragraphs:

Recently at JEDEC meetings the subject of Rambus patents has been raised. Rambus plans to continue to license its proprietary technology on terms that are consistent with the business plan of Rambus, and those terms may not be consistent with the terms set by standards bodies, including JEDEC. A number of major companies are already licensees of Rambus technology. We trust you will understand that Rambus reserves all rights regarding its intellectual property. Rambus does, however, encourage companies to contact Dave Mooring of Rambus to discuss licensing terms and sign up as licensees.

To the extent that anyone is interested in the patents of Rambus, I have enclosed a list of Rambus U.S. and foreign patents. Rambus has also applied for a number of additional patents in order to protect Rambus technology.

Ex. 3120 at 1. •

103. The resignation letter contains a number of explicit warnings to JEDEC and JEDEC’s members. First, it emphasizes that Ram-bus’s business model and licensing plan are not necessarily the same as JEDEC’s. Second, Rambus clarified that it “reserve[d] all rights regarding its intellectual property.” While such a phrase is somewhat vague, it does communicate the position that Rambus did not believe it had waived any rights or intend to waive any rights. Third, it concluded with a clear statement that Rambus had a number of patent applications pending.

104. The letter also included a list of over twenty Rambus patents. Ex. 3120 at 2. The letter omitted one Rambus patent, the '327 patent, which issued on April 30, 1996. Tr. 1298:8-1299:5.

105. The omission was innocent. Ram-bus’s outside patent attorney, Lester Vincent, generated the list of Rambus patents by doing a Lex Pat database search in March of 1996 when helping Richard Crisp prepare a draft of the resignation letter. See Tr. 1814:16-1817:9. Because the '327 patent issued after the database search but before Rambus sent the resignation letter, it was accidentally left off the list.

106. There is no evidence that any JE-DEC member relied on the letter’s list of Rambus’s patents. The December 1996 tracking list does not include any of the patents disclosed in the letter. See Ex. 8307 at 11-12. No witness for any Manufacturer testified that they read or relied on Rambus’s resignation letter.

O.Rambus’s Representations at JE-DEC — Reasons Not to Disclose Patent Applications

107. Rambus had a number of reasons for choosing not to disclose patent applications or its intentions to seek patents. Rambus’s outside patent prosecutor, Lester Vincent, repeatedly advised Rambus to keep its patent applications confidential. Tr. 1634:5-8; 1707:21-1708:5. Mr. Vincent advised Rambus that disclosing its patent applications could lead others to file interferences and to give others a head start at designing around (or copying) Rambus’s technology. Id. 1708:6-1711:6.

108. Mr. Vincent’s advice to Rambus was the generic advice he gave to all of his clients. Id. 1711:7-13.

P. Rambus’s Representations at JE-DEC — Conclusions

109. Rambus made no affirmative representations that it had no intellectual property pertaining to the work of JEDEC. See Jury’s Special Verdict ¶¶ 12, 19 and 26. Further, Rambus uttered no half-truths about its intellectual property coverage or potential coverage of products compliant with synchronous DRAM standards being considered by JEDEC. Id. at ¶ 31. Consistent with the jury’s finding, the court agrees that Rambus made no misrepresentations and uttered no deceptive half-truths to JEDEC and its members.

Q. 1993-2000: Rambus’s Dealings with Hynix: The “Other DRAM” Clause

110. Rambus contacted Hynix about licensing Rambus’s technology in 1993 and began negotiations. Tr. 1847:12-21. In December 1995, Dr. Kye Hwan Oh signed a license ■ agreement with Rambus on behalf of Hynix (then Hyundai Electron ics). Tr. 1845:2-1846:24; Ex. 4028 (the license agreement).

111. While Rambus and Hynix were negotiating the license agreement, Hynix was a member of the Syn-cLink consortium, an organization of DRAM manufacturers seeking to develop a next-generation DRAM. Tr. 1857:22-1858:12. Rambus cautioned Hynix that a SyncLink DRAM might infringe Rambus’s patents. Id. 1861:3-18.

112. The December 1995 agreement licensed Hynix to make Rambus’s RDRAM. Tr. 1862:3-14. The agreement also licensed Hynix to make “Other DRAM,” which the contract defined as: “each DRAM which incorporates part of the Rambus Interface Technology but is not Compatible with the Ram-bus Interface Specification.” Ex. 4028 ¶ 1.5. The license set a royalty rate of 2.5% for “Other DRAMs.” Id. ¶ 5.3(a)(ii).

113. Dr. Oh believed that “Other DRAM means SyncLink.” Tr. 1862:24-1863:1; 1864:212-1865:19. He did not believe “Other DRAM” encompassed Hynix’s JEDECstandard SDRAM and did not intend to pay royalties to Rambus under the Other DRAM provision on Hynix’s SDRAM sales. See id. 1863:11 — 18. 8 On the other hand, the clause was written without making a specific reference to SyncLink and former Rambus CEO Geoff Tate did not believe that Hynix ever told Rambus that the clause was “intended to apply only to a SyncLink device.” Id. 3094:19-23. Mr. Tate understood the clause to be broader “[ojtherwise we would have called it the SyncLink clause.” Id. 3095:4-9.

114. The license lacked provisions dictating how the parties would decide whether an “Other DRAM” incorporates part of the Rambus Interface Technology such that Hynix would owe Rambus royalties on such a DRAM. See generally Ex. 4028. Rambus asked Dr. Oh whether Hynix would have paid 2.5% royalties on SyncLink DRAM sales without proof that “SyncLink infringed Rambus patents.” Tr.l908:16-1909:5. Dr. Oh’s response was clear: “of course not.” Id. 1909:5. Dr. Oh clearly affirmed again that Hynix would only have paid royalties under the Other DRAM clause if Rambus proved that the “Other DRAM” infringed a Rambus patent. Id. 1909:6-10; see also Docket No. 3578, 268:5-11, 15-17 (testimony of Hynix employee D.S. Chung that “I think that we would have refused to pay any royalty even if you had asked for that.”); Tr. 5069:16-5070:6 (Hynix’s refusals to admit that it would have paid royalties with respect to SDRAM and DDR SDRAM pursuant to the “Other DRAM” clause).

115. Mr. Tate’s testimony suggested that Hynix perhaps should have paid even if Rambus did not have an issued patent, but he believed that “practically speaking” Ram- bus would have to prove the “Other DRAM” infringed a patent. Id. 3095:22-3096:4.

116. Rambus did not possess issued patents that read on Hynix’s SDRAM in 1995. The first patent Hynix was found by the jury to infringe issued on June 22, 1999.

117. Rambus never demanded royalties from Hynix for its SDRAM and DDR SDRAM sales under the “Other DRAM” clause. Tr. 3096:6-8. According to Mr. Tate, there was a “very small number of months, two or three months, where we had issued patents and the, this contract was in effect[.]” Id. 3096:21-23.

R. 1993-2000: Rambus’s Dealings with Hynix: Negotiations About Amending the “Other DRAM” Provision

118. In April 1998, a dispute arose between Hynix and Rambus regarding whether Hynix was complying with the license and making its “best efforts” to manufacture and market Rambus’s RDRAM memories. See Exs. 3226; 3228 (correspondence between Mr. Yoo and Deepak Mithani, Rambus’s then-Director of Business Development). 9

119. In June 1998, Hynix and Rambus met to discuss issues related to Hynix’s efforts to develop and promote RDRAM. See Ex. 3229. In exchange for excusing Hynix’s obligations with respect to RDRAM, Rambus proposed “removing the clause on ‘Other DRAMs.’” Id.

120. July of 1998 saw further negotiations regarding the “Other DRAM” clause. Docket No. 3322, 44:8-11; 53:16-54:1. At a meeting on July 6, Hynix shared its product roadmap with Rambus and revealed its intentions and timeline for developing and selling SDRAM, DDR SDRAM, Ram-bus’s concurrent RDRAM and SyncLink (or “SLDRAM”). Id. 60:9-61:15; Ex. 3238. Following the meeting, Rambus responded with another proposal for modifying the “Other DRAM” clause. Id. 74:22-75:5; Ex. 3156.

121. Rambus’s letter proposed amending the agreement’s royalty rate provision for “Other DRAMs” to read “an ‘Other DRAM Product’ means a particular type of Other DRAM (e.g., if otherwise within the definition of Other DRAM, each of a SDRAM, DDR SDRAM, and SLDRAM would be a separate Other Dram [sic] Product, regardless of density). The royalty rate for each Other DRAM Product shall be negotiated separately by the parties upon Hyundai’s first Sale of that Other DRAM Product[.]” Ex. 3156 at 2. Notwithstanding the timing of the proposal, Mr. Yoo testified that there was “none whatsoever” discussion of SDRAM, DDR, or SLDRAM being “Other DRAM” at the July 6 meeting. Docket No. 3322, 76:6-76:10.

122. Hynix responded to the proposed changes to the “Other DRAM clause” and found them “difficult to accept.” Ex. 3239. Hynix explained that under Rambus’s proposal, if a dispute arose as to whether a Hynix DRAM incorporated “Rambus Interface Technol ogy” (and thus would be an “Other DRAM” under the license), Hynix would “always bear the burden to prove that it has not made use of the Rambus Interface Technology in every future DRAM product developed by itself if Rambus should simply assert [Hynix’s] use of Rambus Interface Technology.” Id. at 1-2. Hynix believed that “[n]o one will treat this language as fair or consistent with the License Agreement.” Id. at 2.

128. Hynix further explained that it believed Rambus had been hesitant to grant the Other DRAM clause, and that “SLDRAM, DDR SDRAM, and Synchronous DRAMs might be counted as Other DRAMs from the perspective of Rambus.” Id. at 2; accord Tr. 3094:6-13 (former Ram-bus CEO Geoff Tate testified that the “Other DRAM” clause “was a concession that we made very reluctantly”). The following lines are significant, but their meaning is unclear: “Undoubtedly, [Hynix] has been, and will be, willing and ready to protect Rambus’ valuable intellectual properties developed with huge amount of money and time invested. Nonetheless, please be reminded that Rambus already withdrew from its initial position that it eventually granted [Hynix] the license that Rambus Interface Technology could be incorporated by [Hynix] into the competitive DRAM products, including, but not limited to, SLDRAM, DDR and Synchronous DRAMs, as well, subject to [Hynix] paying running royalties calculated at the rate of 2.5%. We believe that [Hynix] shall not be required to concede any more in terms of the running royalty rates applicable to Other DRAMs.” Id It is not clear what the middle line means. One interpretation is that Hynix is conceding that SDRAM and DDR SDRAM are covered and should be subject to a 2.5% royalty, and no more. Another interpretation is that Hynix is reminding Ram-bus that Rambus withdrew its contention that SDRAM and DDR SDRAM were “Other DRAMs.”

124. That aside, Mr. Yoo stated that by the time Hynix saw Rambus’s July 10 proposal and responded with its letter, Hynix knew that Rambus believed that SDRAM and DDR SDRAM used “Rambus Interface Technology” and that Rambus believed Hynix owed Rambus royalties under the “Other DRAM” clause. Docket No. 3322, 124:10-14; 124:17-126:25. Mr. Yoo responded that Hynix took no action, however, because Hynix did not believe that SDRAM and DDR SDRAM used “Rambus Interface Technology” and were not “Other DRAMs.” Id. 127:1-5, 9-12. Mr. Yoo also expressed disappointment that Rambus had not shared this interpretation of the “Other DRAM” clause in 1997 when Hynix began work on those products because Hynix might then have “taken certain measures to do things differently.” Id. 129:6-9; 129:12-130:5.

125. There is no evidence of how Ram-bus responded to Hynix’s rejection of the proposed amendment to the “Other DRAM” clause. In August of 1999, Rambus internally considered looking into how much it stood to gain if Hynix were to pay royalties under the “Other DRAM” clause for DDR SDRAM. Tr. 3636:19-3638:10; Ex. 3163. The tone of the Rambus email— Exhibit 3163 — suggests that Ram-bus did not believe Hynix would pay royalties on DDR SDRAM pursuant to the “Other DRAM” clause.

126. In 1999, Hynix (then Hyundai) merged with LG Electronics, which also had a license with Rambus. The resulting entity operated under LG’s version of the license, and this version of the license lacked an “Other DRAM” clause. Tr. 3096:9-15.

S. 1993-2000: Rambus’s Dealings with Hynix: Understanding of the Parties Regarding the Meaning of the “Other DRAM” Clause

127. The parties’ decision to word the “Other DRAM” clause such that it was not explicitly limited to Syn-cLink, and Rambus’s reluctance in granting the provision at all, suggest that Hynix in 1995 understood, or should have realized, that Rambus’s intellectual property coverage might one day extend to SDRAM and other designs Hynix might pursue.

128. By 1998, Rambus and Hynix were both aware that the other side possessed a different understanding of the scope of “Rambus Interface Technology” and of the universe of products covered by the “Other DRAM” clause.

129. Hynix’s unwillingness to pay royalties under the clause without proof of infringement was known to Rambus and explains Ram-bus’s failure to press Hynix for royalties. Furthermore, Ram-bus’s desire to encourage Hynix to produce RDRAM explains its unwillingness at the time to push Hynix on the “Other DRAM” clause.

130. Hynix was not misled about the possible scope of Rambus’s patent portfolio by Rambus’s failure to seek royalty payments. On the contrary, Hynix suspected that Rambus might have patent coverage of products like SDRAM in 1995 when it sought the expansive language in the “Other DRAM” clause and knew that Rambus believed it would have patents covering SDRAM and DDR SDRAM by the middle of 1998.

T. 1995-2000: Rambus’s Dealings with Micron — The December 1995 Meeting

131. Terry Lee, Micron’s JC-42.3 representative, first met with Ram-bus in December 1995 at Micron’s facility in Boise. Tr. 3149:18-22; 3152:16-21. Mr. Lee, Gene Cloud (VP of marketing), Kevin Ryan, and Jeff Mailloux represented Micron at the meeting. Id. 3152:22-3153:2. The meeting was called to discuss an RDRAM license. See id. 3153:6-14. Rambus had contacted Micron to license it as an RDRAM manufacturer. Id. 3153: 6-10.

132. To prepare for the meeting, Mr. Lee downloaded information from Rambus’s website because he “didn’t know too much about Rambus.” Tr. 3153:15-23. Mr. Lee also reviewed a collection of Rambus’s patents’ abstracts. Tr. 3153:24-3154:2.

133. Rambus presented its RDRAM technology to Micron at the meet ing. Tr. 3158:16-22. At no point did Rambus indicate anything about SDRAM. Id. 3158:23-3159:9. Rambus did not disclose whether or not it was seeking patents on SDRAM. Id. 3159:7-9.

134. The meeting ended with Micron declining to take an RDRAM license. Id. 3159:10-15.

U. 1995-2000: Rambus’s Dealings with Micron — The December 1996 Meeting

135. Micron (represented by Mr. Lee, Kevin Ryan, Jeff Mailloux, and Gene Cloud) next met with Ram-bus and Intel in December 1996. Tr. 3159:16-3160:6. At this point, Rambus had resigned from JE-DEC. Intel had announced that it had selected Rambus’s RDRAM design as the next memory that would work with the chips Intel designed. Id. 3160:14-23. The purpose of the meeting was to license Micron to manufacture RDRAM. Id. 3161:4-21.

136. SDRAM was not discussed at the meeting. Tr. 3162:8-15.

137. Micron entered into an RDRAM license with Rambus around March of 1997. Tr. 3163:12-18.

V. 1995-2000: Rambus’s Dealings with Micron — Rambus Did Not Mislead Micron

138. Rambus did not make any misrepresentations or utter any half-truths about the scope of its intellectual property during its RDRAM license negotiations with Micron. See Special Verdict Form ¶¶ 19, 31.

W.Nanya’s Failed RDRAM Negotiations

139. Nanya Technology Corp. was formed around 1995. It founded its subsidiary, Nanya Technology Corp. USA, in 1997. Id. 2730:9-12. Nanya formed its American subsidiary to sell JEDEC-standard DRAMs. Id. 2741:3-23.

140. Rambus met with Ken Hurley (the founder of Nanya USA) in late 1998 to discuss an RDRAM license. Tr. 2749:13-2750:4. The negotiations lasted about a year. Id. 2750:10-2752:3.

141. At no point did Rambus advise Nanya that Rambus believed that its JEDEC-standard DRAMs were infringing Rambus patents. Tr. 2750:10-2752:3. However, Nanya only began selling some infringing SDRAM at the end of 1998. Id. 2752:3-23. It began selling DDR SDRAM “in the 2000 time frame.” In other words, when Rambus first negotiated with Nanya, Nanya did not sell any infringing devices. As negotiations progressed, Nanya began to sell some infringing SDRAM. At no point in Nanya’s negotiations with Rambus did Nanya sell infringing DDR SDRAM.

142. Mr. Hurley confirmed that during these negotiations, he was not told that Rambus’s intellectual property was limited to RDRAM and he was not told what Rambus’s intellectual property did cover. Tr. 2763:18-2764:3.

143. Mr. Hurley first learned that Rambus believed its patents covered SDRAM and DDR SDRAM when he read about Rambus’s litigation against Hitachi in early 2000. Tr. 2765:9-2766:7. Despite learning about this litigation in 2000, Mr. Hurley was not aware of any steps taken by Nanya (a) to determine if it needed a license from Rambus, and (b) to develop a non-infringing DRAM. Id. 2777:6-20.

144. Rambus sued Nanya alleging that Nanya’s DDR2 SDRAM infringed Rambus’s patents in January 2005. Rambus accused Nanya’s SDRAM and DDR SDRAM of infringement in its counterclaims in reply in July 2007. Tr. 2754:23-2756:2.

145. Nanya did not rely to its detriment on any misrepresentation or concealment by Rambus of its patent coverage of SDRAM and DDR SDRAM or on the fact that Ram-bus delayed in instituting suit against Nanya. See Special Verdict Form ¶¶ 26, 31.

X. Jury’s Findings from Conduct Trial Adopted by Court

146. The Conduct Trial commenced before a jury selected on January 31, 2008 and concluded on March 26, 2008 when the jury rendered its Special Verdict. The jury found in favor of Rambus on each of the Manufacturers’ claims submitted to it. Special Verdict Form (Docket No. 3613, Hynix Semiconductor, Inc. v. Rambus Inc., C-00-20905-RMW).

147. The jury found that the six technology markets alleged by the Manufacturers existed (latency technology market, burst length technology market, data acceleration technology market, clock synchronization technology market, precharge technology market, and write latency technology market) (id. at ¶ 1) but that Rambus did not commit anticompetitive conduct in any of the six technology markets. Id. at ¶ 8; see also ¶ 4.

148. The jury also found that Rambus did not make important representations that it did not have any intellectual property pertaining to the work of JEDEC and intend or reasonably expect that the representations would be heard by or repeated to others including Hynix, Micron and Nanya. Id. at ¶¶ 12,19, and 26.

149. In addition, the jury found that Rambus did not utter half-truths about its intellectual property coverage or potential coverage of products compliant with synchronous DRAM standards then being considered by JEDEC by disclosing some facts but failing to disclose other important facts, making the disclosure deceptive. Id. at ¶ 31.

150. Finally, the jury found that JE-DEC members did not share a clearly defined expectation that members would disclose relevant knowledge they had about patent applications or the intent to file patent applications on technology being considered for adoption as a JEDEC standard. Id. at ¶ 45.

III. CONCLUSIONS OF LAW

A. The Seventh Amendment Requirement to Adopt Jury’s Factual Findings

The Seventh Amendment requires the court to apply the jury’s “implicit [and] explicit factual determinations” when ruling on equitable claims that are “based on the same facts” as the legal claims tried to the jury. Los Angeles Police Protective League v. Gates, 995 F.2d 1469, 1473 (9th Cir.1993). Because of the substantial factual overlap between the claims tried to the jury and the Manufacturers’ equitable claims and defenses, the court therefore adopts the findings of the jury.

B. Unfair Competition (Cal. Bus. & Prof.Code § 17200 et seq.)

All three Manufacturers claim that Rambus engaged in unfair competition in violation of California Business & Profession Code § 17200. That statute defines “unfair competition” as “any unlawful, unfair, or fraudulent business act or practice.” Cal. Bus. Prof.Code. § 17200. “[I]t establishes three varieties of unfair competition — acts or practices which are unlawful, or unfair, or fraudulent.” Cel-Tech Commc’ns, Inc. v. Los Angeles Cellular Tel. Co., 20 Cal.4th 163, 180, 83 Cal. Rptr.2d 548, 973 P.2d 527 (1999). “Although the unfair competition law is broadly written to permit courts to restrain dishonest or unfair business dealings, the scope of the law is not unlimited. ‘Courts may not simply impose their own notions of the day as to what is fair or unfair.’ ” Scripps Clinic v. Superior Court, 108 Cal.App.4th 917, 938, 134 Cal. Rptr.2d 101 (2003) (quoting Cel-Tech, 20 Cal.4th at 180, 83 Cal.Rptr.2d 548, 973 P.2d 527).

The Manufacturers described their § 17200 claims in the Joint Case Management Conference Statement dated July 31, 2007. Hynix said: “Claim arises out of Rambus’s anticompetitive conduct at JE-DEC; the continuing exercise of its unlawful monopoly and deception outside of JE-DEC; and Rambus’s conduct arising out of the Rambus/Hynix RDRAM relationship.” Attachment 1 to 7/31/07 PTC Stmt. Nanya similarly described the claim: “This claim arises, without limitation, out of Rambus’s anticompetitive conduct at JE-DEC; the continuing exercise of its unlawful monopoly and deception outside of JE-DEC including its enforcement of patents known to be invalid; and Rambus’s conduct during the course of its relationships with the DRAM manufacturers, and others.” Attachment 3 to 7/31/07 PTC Stmt. 10 Micron gave an essentially identical description: “This arises, without limitation, out of Rambus’s anticompetitive conduct at JEDEC; and the continuing exercise of its unlawful monopoly and deception outside of JEDEC.” Attachment 2 to 7/31/07 PTC Stmt.

To support their § 17200 claims, the Manufacturers focused on attempting to show that Rambus failed to disclose its intent to seek patent coverage of the DRAM standards being considered by JE-DEC. The jury’s findings defeat any claim by the Manufacturers that Rambus’s conduct was “unlawful” or “fraudulent,” specifically the findings: (1) that Rambus did not commit anticompetitive conduct in any of the six technology markets (Finding of Fact 147 (“FOF_”)); (2) that Rambus did not make any misrepresentations about having intellectual property pertaining to the work of JEDEC (FOF 148); (3) that Rambus did not utter half-truths about its intellectual property coverage or potential coverage of products compliant with synchronous DRAM standards then being considered by JEDEC (FOF 149); and (4) that JEDEC members did not share a clearly defined expectation that members would disclose patent applications or the intent to file patent applications on technology being considered for adoption as a JEDEC standard. (FOF 150).

The Manufacturers, nonetheless, assert that the evidence showed that Rambus’s conduct was “unfair” and violated § 17200. The California Supreme Court has set the standard for establishing a violation of § 17200 by an “unfair” act or practice.

When a plaintiff who claims to have suffered injury from a direct competitor’s “unfair” act or practice invokes section 17200, the word “unfair” in that section means conduct that threatens an incipient violation of an antitrust law, or violates the policy or spirit of one of those laws because its effects are comparable to or the same as a violation of the law, or otherwise significantly threatens or harms competition.

Cel-Teck, 20 Cal.4th at 187, 83 Cal. Rptr.2d 548, 973 P.2d 527. Since the jury found that Rambus’s conduct was not anti-competitive and that JEDEC members did not have a clearly defined expectation of disclosure, Rambus’s failure to disclose cannot be considered “unfair.” Not only did Rambus not have an obligation to disclose pending or anticipated patent applications, it had sound reasons for not doing so. As advised by counsel, Rambus understood that patent applications were confidential and that disclosure of the contents of an application before a patent actually issued exposed the applicant to various risks or claims. (FOF 107-08). In light of the jury’s findings and the evidence presented, the court concludes that the Manufacturers failed to establish that Rambus violated § 17200 by its conduct before JE-DEC.

The totality of the evidence concerning a disclosure duty showed that, as the jury found, there was no clearly understood agreement of JEDEC members to disclose patent applications or the intent to seek patents relevant to standards being discussed at JEDEC. The strongest evidence of such an obligation appears in section 9.3.1 of Manual 21-1 dated “October 1993” which may or may not have been adopted and distributed. (FOF 18-28). Even if adopted and distributed, the purported obligation in Manual 21-1 goes further than any contemporaneous disclosure request or requirement recited in sign-in sheets (refer only to “patented item” (FOF 30; see 29-32)), printed on ballots (“if anyone receiving this ballot is aware of patents involving this ballot, please alert the committee accordingly during you voting response” (FOF 35; see 33^10)), or contained in the meeting minutes (FOF 41-47; see, e.g. FOF 43-44 which refers to disclosure by “presentation sponsors”). In any event, nothing ever required a JEDEC member to reveal an intent to file for a patent in the future. See Rambus, Inc. v. Infineon Techs. AG, 318 F.3d 1081, 1102 (Fed.Cir.2003) (holding on a similar record “that the record supports only the conclusion that a member’s intentions to file or amend applications do not fall within the scope of JEDEC’s disclosure duty.”).

The testimony of JEDEC members concerning any disclosure obligations was varied and, in some cases, inconsistent, thus bolstering the conclusion that there was no clearly defined disclosure obligation at least with respect to a member’s patent applications or intentions to file for patents in the future. See, e.g., FOF 73 (Grossmeier); 75 (Tabrizi). The relatively modest length and static nature of the patent tracking list also suggests that JEDEC members were not generally disclosing patent applications or even making much effort to disclose their companies’ relevant patents. The minutes of the December 1991 committee meeting, the first that Rambus attended and the meeting at which the tracking list was introduced, described the list’s purpose: “The purpose was only to track and identify items of Committee proposals. Companies who hold patents identified can respond to Committee, if they wish.” FOF 49 (emphasis added). The subsequent development of the list seems consistent with this purpose and not with a broader disclosure obligation.

At the time of its withdrawal from JE-DEC, Rambus had not even applied for any of the patents-in-suit. See FOF 5-6. Accordingly, the court concludes that the Manufacturers are not entitled to recover on their unfair competition claims. See also infra § III-E (Equitable Estoppel).

C. Fraud

Nanya was the only Manufacturer whose fraud claim was tried to the court. Although the jury’s verdict as to the fraud issues was only advisory as to Nanya, the court accepts the advisory verdict. The evidence did not support a finding of any material misrepresentation, half truths or fraudulent concealment by Rambus related to JEDEC upon which Nanya relied.

D. Prosecution Laches

The Manufacturers did not put on evidence relevant to their prosecution laches defenses. For example, the Manufacturers did not call either of their two disclosed expert witnesses (Gerald Mossinghoff and R. Polk Wagner) on prosecution laches. This absence led Rambus to move for judgment as a matter of law. Tr. 4066:3-8; Docket No. 3444 (Mar. 10, 2008). Following Rambus’s motion, the Manufacturers indicated that they did not “intend to proceed with the prosecution laches part of the case.” Id. 4511:4-12.

The only evidence related to Rambus’s patent prosecution came from its patent attorney in the mid-nineties, Lester Vincent. Nothing in his testimony established that Rambus unduly delayed in prosecuting the claims in suit.

E. Equitable Estoppel

1.Elements of Equitable Estoppel

All the Manufacturers assert the doctrine of equitable estoppel as a bar to Rambus’s claims for patent infringement.

Equitable estoppel, which bars a patentee from receiving relief, consists of three elements: (i) the patentee must communicate to the accused infringer (by words, conduct or silence) that the patentee will not pursue an infringement claim; (ii) the accused infringer must rely on that communication; and (iii) the accused infringer must establish that it would be materially prejudiced if the patentee is now permitted to proceed with the infringement claim.

B. Braun Med., Inc. v. Abbott Labs., 124 F.3d 1419, 1425 (Fed.Cir.1997); see A.C. Aukerman Co. v. R.L. Chaides Const. Co., 960 F.2d 1020 (Fed.Cir.1992). Silence alone will not create an estoppel unless there is a clear duty to speak or somehow the patentee’s continued silence reinforces the defendant’s belief that the defendant will be unmolested. Id. at 1043-44; see also Hemstreet v. Computer Entry Sys. Corp., 972 F.2d 1290, 1295 (Fed.Cir.1992) (“mere silence must be accompanied by some other factor which indicates that the silence was sufficiently misleading as to amount to bad faith”). Even if the three elements are met, the court must take into consideration all other evidence respecting the equities of the parties in exercising its discretion in deciding whether to allow the defense to bar the suit. Id. at 1043.

2. Burden of Proof

Except where equitable estoppel is based solely upon intentional fraud, the burden of proof is the preponderance of evidence. “[Wjhile the facts relied upon to establish equitable estoppel must be clear, positive, and unequivocal in their implication, these facts need not be established by any more than a fair preponderance of the evidence.” Aukerman Co., 960 F.2d at 1046.

3. Equitable Estoppel Based Upon Rambus’s Participation in JEDEC

All the Manufacturers assert that Rambus’s words, conduct and silence in connection with its participation in JEDEC communicated an intent by Rambus not to enforce the patents-in-suit. Although the Manufacturers did offer some evidence supporting an obligation by JEDEC members to make disclosures concerning their patents relevant to any standard being considered, the evidence was not persuasive that there was any understanding among members that they had to disclose pending patent applications or the intent to file such applications. The jury specifically found that JEDEC members did not share a clearly defined expectation that such disclosures would be made (FOF 150).

The recent case of Qualcomm Inc. v. Broadcom Corp., 548 F.3d 1004 (Fed.Cir. 2008) involved similar issues but is factually distinguishable in several critical ways. It held that Qualcomm had a duty to disclose the existence of patents it owned that “reasonably might be necessary” to practice the standard being considered by the standards setting organization of which it was a member. The court found that Qualcomm participated in the standard setting during the time the relevant standard was being considered despite Qualcomm’s denials and affirmative attempts to conceal that participation. The court found that not only the written policies of the SSO required, disclosure (id. at 1012— 15) but that the understanding among the members required disclosure of patents that reasonably might be necessary to practice the standard. Id. at 1015-17. The court further found that Qualcomm’s intentional nondisclosure in face of the duty to speak constituted an implied waiver of the right to assert infringement. Id. at 1019-22. It also suggested that such conduct would result in a defense of equitable estoppel, but did not remand the action for consideration of that defense since there had been an implied waiver.

The instant case is distinguishable from Qualcomm in the following material ways. First, the written JEDEC disclosure policies did not clearly require members to disclose information about patent applications and the intent to file applications in the future and there is no indication that members ever legally agreed to do so. FOF 14-77; see Infineon, 318 F.3d at 1098. In Infineon, a case involving similar claims against Rambus based upon its involvement with JEDEC, the court observed “there is a staggering lack of defining details in the EIA/JEDEC patent policy.” 318 F.3d 1081, 1102 (Fed.Cir.2003). Similarly, in Rambus Inc. v. F.T.C., 522 F.3d 456, 462 (D.C.Cir.2008), the D.C. Circuit commented in reversing the Federal Trade Commission’s finding that Rambus, as a member of JEDEC, had engaged in an unfair method of competition and unfair or deceptive acts or practices prohibited by § 5(a) of the FTC Act:

We ... conclude that the Commission failed to demonstrate that Rambus’s conduct was exclusionary under settled principles of antitrust law. Given that conclusion, we need not dwell very long on the substantiality of the evidence, which we address only to express our serious concerns about the breadth the Commission ascribed to JEDEC’s disclosure policies and their relation to what Rambus did or did not disclose.

Id. at 462.

Second, the jury in this case expressly found that JEDEC members did not share a clearly defined expectation that members would disclose relevant knowledge they had about patent applications or the intent to file patent applications on technology being considered for adoption as a JEDEC standard. The evidence supported that finding (FOF 67-79).

Third, Qualcomm failed to disclose existing patents which it intentionally con cealed. The patent-at-issue in this case had not even been applied for during Ram-bus’s membership in JEDEC. The only-suggestion that other patents that Rambus had obtained or applied for might reasonably have been of interest to JEDEC came from Mr. Rhoden who was both vague and not convincing in his testimony on the subject (FOF 67, 82).

However, an estoppel may be found even though the party estopped did not actually intend to mislead or to defraud the other person. See A.C. Aukerman Co., 960 F.2d at 1044, fn. 18. The Manufacturers assert that in addition to Rambus’s knowledge that at least some members of JEDEC believed there was an obligation to disclose, Rambus was aware that JE-DEC had taken adverse action against Wang and Texas Instruments for their failures to disclose. However, both those situations involved affirmative conduct at JEDEC and the failure to disclose relevant, issued patents and not mere silence about an intent to obtain future patents with particular coverage.

Rambus’s involvement at JEDEC was primarily through Richard Crisp, Ram-bus’s representative at JEDEC. Essentially, his only outward expressions of significance were his negative shake of his head at a May 1992 JEDEC meeting when Rambus was asked if it cared to comment on specific patent issues (FOF 82-89), his disclosure of the '703 patent in 1993 (FOF 90-95) and his reading of a letter dated September 12, 1995 at a JEDEC meeting concerning Rambus’s refusal to comment on potential patent coverage of the Syn-cLink design (FOF 96-101). Mr. Crisp did not discuss non-public Rambus intellectual property at JEDEC, nor did he actively advocate adopting the standards JE-DEC eventually adopted. Further, at the time Mr. Crisp attended his last meeting of JEDEC in late 1995 (Rambus officially withdrew in June 1996), Rambus did not have any patent application pending that covered a JEDEC standard and it was months before it did. (FOF 5-6).

The Manufacturers’ suggestion that Rambus misled JEDEC’s members when Mr. Crisp read the letter wherein Rambus responded to a question about Synclink, a type of DRAM being developed that bore a strong resemblance to Rambus DRAMs, is not persuasive. See Ex. 3090. In the letter Rambus noted that Synclink was being sponsored by an organization with a less stringent patent policy than JEDEC. Id. At the close of the letter Rambus stated that it “elects to- not make a specific comment on our intellectual property position relative to the Synclink proposal. Our presence or silence at committee meetings does not constitute an endorsement of any proposal under the committee’s consideration nor does it make any statement regarding potential infringement of Rambus intellectual property.” Id. The Manufacturers suggest that this comment about Synclink implied that Rambus did not have intellectual property that covered standards that were being developed at JE-DEC. Since Rambus was responding to a question raised specifically about Synclink, it is not reasonable to infer that Rambus was commenting beyond Synclink or that patents it might obtain in the future would cover DRAMs built in accordance with standards then being developed by JE-DEC. Further, the last sentence of the letter is consistent with Rambus’s policy of not commenting on potential infringement of Rambus’s intellectual property.

4. Estoppel Based On the “Other DRAM” Clause in Hynix License

Hynix contends that Rambus’s silence during its licensing negotiations with Rambus resulting in the December 1995 licensing agreement between Hynix and Rambus supports its asserted defense of equitable estoppel. In particular, Hynix contends that Rambus’s silence about the scope of its intellectual property in light of the inclusion of the “Other DRAM” clause in the agreement misled the company into believing that the “Other DRAM” clause would not require Hynix to pay royalties on SDRAMs or DDR SDRAMs incorporating Rambus’s inventions and that Ram-bus should therefore be estopped from enforcing its patent rights against Hynix for these products. However, Hynix offered little more than a statement by its former Executive Vice President for Semiconductors, Dr. Kye-hwan Oh, that “Other DRAM means Synclink.” (FOF 110-130). Although he insisted that Hynix understood that “Other DRAM” carried this specific meaning, Dr. Oh could not explain why the 1995 licensing agreement never refers to Synclink. His credibility on this issue was questionable. Moreover, Dr. Oh acknowledged that, at the time of the negotiations with Rambus, he was aware of Rambus’s royalty-based business model and knew Rambus had 40 patent applications related to its technologies, that he had read about Rambus’s inventions in the international and trade press, and that it was a common practice for companies seeking to protect their intellectual property to file broad applications. Although it may well be that Hynix did not appreciate the extent of Rambus’s intellectual property at the time, its failure to appreciate the scope does not mean that Rambus communicated to Hynix that it would not pursue an infringement claim. Accordingly, Hynix has failed to establish the first element of its equitable estoppel claim by a preponderance of the evidence.

5. Estoppel Based on Conduct with Micron Outside of JEDEC

In their Proposed Findings of Fact and Conclusions of Law, the Manufacturers propose as Finding of Fact 194 that “Ram-bus’s conduct and communications with Micron outside of JEDEC were also deceptive and misleading.” However, they do not explain what particular conduct or communications were deceptive or misleading.

In December 1995 Rambus met with Micron and presented its RDRAM technology in the hope of being able to license that technology to Micron. No agreement was reached. There was no discussion concerning SDRAM and no reason for Rambus to discuss its patenting intentions with Micron. (FOF 131-134).

Micron next met with Rambus and Intel in December 1996. (FOF 135-137). At this point, Rambus had resigned from JE-DEC and Intel had announced that it had selected Rambus’s RDRAM design as the next memory that would work with the chips Intel designed. The purpose of the meeting was to license Micron to manufacture direct RDRAM. Micron entered into a license with Rambus around March of 1997. SDRAM was not discussed at the December 1996 meeting, and Rambus did not suggest that it had patent rights that extended to SDRAM.

Neither Rambus’s conduct nor communications with Micron with respect to RDRAM was misleading nor did the relationship between them create any obligation on Rambus’s part to disclose its intent to obtain patent coverage (FOF 138). Rambus is not estopped from asserting its infringement claims based upon any conduct toward or communications with Micron.

6. Estoppel Based on Conduct with Nanya Outside JEDEC

Nanya dropped any claim for equitable estoppel other than with respect to Ram-bus’s conduct at JEDEC. Tr. 803:24-804:5.

F. Waiver Defenses

1. Waiver Based Upon Participation in JEDEC

The Manufacturers contend that Rambus’s “misleading omissions and unfair conduct as a whole” manifested a waiver of its right to sue for infringement. See Manu. Brf. Re: Clms. and Def. at 15. The Manufacturers focus on the same evidence as they do for their claim of equitable estoppel — Rambus’s participation in JE-DEC and its failure to disclose its intent to obtain patents covering the JEDEC standard. Nanya asserts that Rambus’s failure to file suit against it until 2005 further supports a finding of waiver, particularly in light of Rambus’s failure to reveal its intent from 1998 to 2000 when Rambus unsuccessfully negotiated an RDRAM licensing agreement with Nanya. Although often discussed together, waiver and equitable estoppel are separate concepts with different requirements.

Waiver always rests upon intent. Waiver is the intentional relinquishment of a known right after knowledge of the facts. The burden, moreover, is on the party claiming a waiver of a right to prove it by clear and convincing evidence that does not leave the matter to speculation, and doubtful cases will be decided against a waiver.

DRG/Beverly Hills, Ltd. v. Chopstix Dim Sum Cafe & Takeout III, Ltd., 30 Cal. App.4th 54, 60, 35 Cal.Rptr.2d 515 (1994).

Rambus’s conduct at JEDEC, and specifically its alleged failure to comply with the alleged JEDEC disclosure policy, did not constitute a waiver of its rights to enforce its patents. The Manufacturers’ evidence did not show clearly and convincingly, or even by a preponderance of the evidence, that Rambus’s conduct at JE-DEC manifested an intent to relinquish any right to sue for infringement of any patents it should later obtain. As the jury found, there was no clearly defined expectation that patent applications or anticipated applications would be disclosed. Ram-bus’s refusal to comment on its intellectual property tends to negate any inference that its silence manifested an intent to relinquish. Moreover, the Manufacturers failed to establish that Rambus’s conduct at JEDEC violated any “clear duty to speak” that might have implied a waiver. See Kacha v. Allstate Ins. Co., 140 Cal.App.4th 1023, 1034, 45 Cal.Rptr.3d 92 (2006).

2. Nanya’s Waiver Defense

Nanya’s waiver defense focuses on the delay between the alleged abandonment of licensing negotiations between Rambus and Nanya for SDRAM in April 2001 (evidence of such negotiations is lacking) and April 2004 when Rambus contacted Nanya about infringement. An infringement suit was filed by Rambus against Nanya on January 25, 2005. Between April 2001 and April 2004 Nanya claims to have spent millions of dollars producing JEDEC compliant DRAM products. These facts do not establish that Rambus in any way intended to relinquish any patent rights. In fact, during that time Rambus was in, or had been in, litigation with other DRAM manufacturers which was public knowledge and illustrated that Rambus intended to pursue infringement claims. Also, many of the patents asserted against Nan-ya did not issue until after April 2001 thus showing Rambus filed suit within a short time after many of the patents issued. 11 Further, there is no evidence suggesting that Nanya would have done anything differently had it been sued in 2001 rather than 2005. Nanya’s waiver defense lacks both evidentiary and legal support.

G.Patent Misuse Defenses Asserted By Nanya and Micron

Nanya and Micron assert that Rambus’s patent claims are not enforceable because Rambus engaged in patent misuse. The patent misuse defense in this consolidated proceeding appears to be based upon Rambus’s alleged anticompetitive conduct in failing to disclose patent applications and intended applications to JEDEC and then asserting the patents after they issued. 12 Patent misuse “arises from the equitable doctrine of unclean hands, and relates generally to the use of patent rights to obtain or to coerce an unfair commercial advantage.” C.R. Bard, Inc. v. M3 Sys., Inc., 157 F.3d 1340, 1372 (Fed.Cir.1998). “The key inquiry is whether, by imposing conditions that derive their force from the patent, the patentee has impermissibly broadened the scope of the patent grant with anticompetitive effect.” Id. The Federal Circuit has cautioned that the defense not be read broadly to capture any generally-alleged “wrongful” use of patents. Id. at 1373 (“Although the defense of patent misuse ... evolved to protect against ‘wrongful’ use of patents, the catalog of practices labeled ‘patent misuse’ does not include a general notion of ‘wrongful’ use.”). Rather, the defense is generally directed towards conduct that “affect[s] competition in unpatented goods or that otherwise extend[s] the economic effect beyond the scope of the patent grant.” Id. Since Micron and Nanya base that their patent misuse defense on the same allegations as their antitrust and unfair competition claims and since those claims were not proved, the defense necessarily fails.

H. Micron’s Claim of an Implied License

Micron alleges as a defense that it had an implied license to use Rambus’s patents. This defense is asserted on the theory that Rambus either waived its right to assert the patents-in-suit or that it is equitably estopped from doing so. “In patent law, an implied license merely signifies a patentee’s waiver of the statutory right to exclude others from making, using, or selling the patented invention.” Wang Labs., Inc. v. Mitsubishi Electronics America, Inc., 103 F.3d 1571, 1580 (Fed. Cir.1997). An implied license can also arise from conduct that supports a finding of equitable estoppel. Id. at 1580-82. Since Micron failed to prove that Rambus either waived its right to enforce its patents or is estopped from attempting to enforce them, Micron cannot claim it has an implied license.

I. Laches

All of the Manufacturers assert the defense of laches. Nanya contends that Rambus unreasonably delayed in bringing suit against it following the termination of licensing negotiations between them. The only evidence of negotiations between Rambus and Nanya involved RDRAM and occurred in the late 1990’s. However, what Nanya’s papers appear to allege is unreasonable delay between April of 2001 (when there were purportedly negotiations for SDRAM and DDR SDRAM) and April of 2004.

A defendant, in order to invoke the defense of laches, must prove: “(1) [that] the plaintiff delayed filing suit for an unreasonable and inexcusable length of time from the time the plaintiff knew or reasonably should have known of its claim against the defendant, and (2) [that] the delay operated to the prejudice or injury of the defendant.” A.C. Aukerman Co. v. R.L. Chaides Constr. Co., 960 F.2d 1020, 1032 (Fed.Cir.1992) (en banc). A presumption of laches arises “upon proof that the patentee delayed filing suit for more than six years after actual or constructive knowledge of the defendant’s alleged infringing activity.” Id. at 1035-36.

Symantec Corp. v. Computer Associates Int’l, Inc., 522 F.3d 1279, 1294 (Fed.Cir. 2008).

Nanya’s evidence fails to show that Rambus unreasonably delayed in bringing suit against Nanya. The earliest issue date of a patent selected by Rambus for assertion against Nanya is January

30, 2001 (the issue date of the '184 patent) and the latest is June 24, 2004 (the issue date of the '696 patent). Although calculation should probably be made from the date Rambus knew of its claim under the '696 patent, even if Rambus knew of its claim under the '184 patent the day it issued and if that is the beginning date for calculating laches, the delay in bringing suit was not unreasonable or inexcusable. See Meyers v. Asics Corp., 974 F.2d 1304, 1307 (Fed.Cir.1992) (suggesting time runs from the latest issue date of the patents on which suit is brought). Further, Nanya made no showing of reliance to its prejudice on any statement or conduct of Ram-bus.

Hynix and Micron do not appear to be seriously pursuing laches as a separate defense. They offered no proposed Findings of Fact and Conclusions of Law directed to the defense. In the July 30, 2007 Joint Case Management Conference Statement Hynix said its defense is based upon “Rambus’s deception of the industry as to the scope of its proprietary technology, including the conduct arising out of the Rambus/Hynix RDRAM relationship.” July 31, 2007 Joint Case Management Conference Statement Attachment 1 at 2:24-27. Micron set forth its defense as “Rambus’s failure to timely assert claims for patent infringement and its deception regarding its alleged proprietary technology.” Id., Attachment 2 at 5:20-25. The court believes that Hynix and Micron are just putting another label on their equitable estoppel defense that Rambus should be barred from suing for infringement for its allegedly misleading conduct concerning its patenting intentions during the time it was a member of JEDEC and during licensing negotiations. Neither Hynix nor Micron, to the extent either is relying on a laches defense, has explained or marshaled the evidence supporting the defense.

The Manufacturers’ laches defenses fail.

J. Unenforceability and Unclean Hands

Finally, Hynix asserts a defense of unclean hands, distinct from Rambus’s alleged spoliation, arising from Rambus’s conduct discussed above. Micron and Nanya seek a declaratory judgment that Rambus’s patents are unenforceable based on Rambus’s conduct. In light of the jury’s verdict and the court’s findings, there is no basis for the unclean hands defense or unenforceability claim.

1 . By “Hynix,” the court refers to the four entities sued by Rambus: Hynix Semiconductor Inc., Hynix Semiconductor America Inc., Hynix Semiconductor U.K. Ltd., and Hynix Semiconductor Deutschland GmbH. The latter three entities are all wholly-owned subsidiaries of Hynix Semiconductor, Inc. See Docket No. 1649, C-00-20905-RMW, at 5, ¶4 (N.D.Cal. Feb. 2, 2006). "Hynix” also includes Hynix Semiconductor Manufacturing America, a subsidiary named in the 05-00334 case but not the 00-20905 case.

2 . The Samsung entities — Samsung Electronics Co., Ltd., Samsung Electronics America, Inc., Samsung Semiconductor, Inc., and Samsung Austin Semiconductor, L.P. ("Samsung”) — that are parties to Case No. C-05-00334 and C-05-02298 did not assert antitrust claims, did assert some claims that uniquely applied to them and did not make a jury demand. Therefore, the court tried the Samsung claims and defenses in a separate proceeding.

3 . Throughout this order, the court refers to specific patents by the patent’s last three digits, i.e., U.S. Patent No. 5,915,105 is referred to as “the'105 patent.”

4 . Rambus moved in limine to prelude presentation of the Manufacturers' fraud claims to a jury because, according to Rambus, the Manufacturers had no evidence that they had suffered damages as the result of the alleged fraud. The court found that Nanya had not offered any evidence of fraud damages but nevertheless let the fraud issue as to Nanya go to the jury for an advisory verdict. Sufficient evidence was offered to support a claim for fraud damages by Hynix and Micron. Hynix Semiconductor Inc. v. Rambus, Inc., 527 F.Supp.2d 1084 (N.D.Cal.2007).

5 . On cross-examination, Mr. Rhoden wavered, testifying that JEDEC’s patent policy was "written down.” Tr. 627:25-628:20. Mr. Rhoden then backed off, suggesting he believed that he understood JEDEC’s patent policy more as something that was explained at meetings to the engineers present. Id. 628:22-25. Incidents like this one, and other conflicts in his testimony described below, as well as an obvious pro-JEDEC, anti-Rambus bias, undermined Mr. Rhoden’s credibility.

6 . The Manufacturers took this approach to avoid opening the door to evidence about Micron’s litigation with Mosaid in which Micron makes similar allegations that Mosaid breached JEDEC’s disclosure duty by failing to disclose information about its patent portfolio. Tr. 2376:25-2378:20; 2381:16-22.

The Manufacturers argued in their new trial motion that such an inference cannot ethically be drawn because Mr. Allan’s expert report suggests that he understood the disclosure obligation at JEDEC to extend to applications and the intent to file patent applications. The court disagrees, as stated in its denial of the new trial motion. Hynix Semiconductor Inc. v. Rambus Inc., 2008 WL 2951341, *9-*10 (N.D.Cal. Jul.24, 2008).

Neither Mr. Allan’s report, nor the reason the Manufacturers did not question Mr. Allan, is in evidence. The court is left with evidence that someone with first hand knowledge about the disclosure policy was not asked about it. This permits the inference drawn by the court and the court sees no ethical problem in drawing that inference. However, it is not an inference on which the court places much weight in light of the testimony of Messrs. Crisp and Grossmeier.

7 . "RDRAM” or "Rambus DRAM” refers to Rambus's proprietary memory architecture that it developed in the early 1990s and that competed with JEDEC’s standards and SLDRAM throughout the 1990s.

8 . Min Kwon Yoo, the Hynix employee responsible for memory technical marketing and for negotiating with Rambus three years later in 1998, admitted that at that time “I myself didn't quite understand as to what ‘Other DRAMs’ was in reference to, so I asked the folks at Rambus about that, but didn’t really get a straight answer.” Docket No. 3322, 12:1-13:3; 43:2-43:8 (video testimony).

9 . Various trial exhibits corresponding to documents used in Mr. Yoo's depositions were admitted into evidence. See Tr. 2177:5-2179:8.

10 . Any claim by Nanya that the PTO issued patents to Rambus which Rambus knew were invalid but yet attempted to enforce was not included in the trial and reserved by Nanya for later resolution.

11 . The latest patent-in-suit was U.S. Patent No. 6,751,696 issued June 15, 2004.

12 . Nanya’s patent misuse defense base upon Rambus’s alleged procurement of the patents-in-suit by fraud on the patent office was not tried in this phase of the lawsuit Rambus brought against Nanya and is reserved for later resolution.