Implicit Networks, Inc. v. Juniper Networks, Inc.

Filing 144

ORDER ON JUNIPER'S MOTION TO COMPEL RE PRIVILEGE AND INTERROGATORY RESPONSES 140 142 (Illston, Susan) (Filed on 8/16/2012)

Download PDF
1 2 3 IN THE UNITED STATES DISTRICT COURT 4 FOR THE NORTHERN DISTRICT OF CALIFORNIA 5 6 7 8 9 ORDER ON JUNIPER’S MOTION TO COMPEL RE PRIVILEGE AND INTERROGATORY RESPONSES Plaintiff, v. JUNIPER NETWORKS, INC., 10 United States District Court For the Northern District of California No. C 10-04234 SI IMPLICIT NETWORKS, INC., Defendant. / 11 12 Currently before the Court is Juniper’s motion to compel regarding documents Implicit has and 13 has not identified on its privilege log, as well as Juniper’s motion to compel further interrogatory 14 responses. [Docket No. 138]. The Court rules as follows. 15 With respect to privilege issues, Juniper first argues that Implicit improperly withheld documents 16 as attorney-client privileged when no attorney sent or received the correspondence. Implicit responds 17 that in a July 30, 2012 letter Implicit informed Juniper that each of the challenged documents 18 “recounted” or otherwise disclosed advice of counsel and, therefore, was withheld. See Docket No. 140, 19 Ex. A. Juniper contends that Implicit’s letter fails to identify the name of the counsel whose advice is 20 at issue in each document, and therefore, Implicit has waived the privilege. See Docket 142. The Court 21 disagrees and finds that Implicit’s July 30, 2012, letter generally provides sufficient information 22 regarding the counsel or the firm whose advice is at issue.1 23 Juniper also argues that Implicit’s privilege log is deficient because it does not identify 24 “mediation documents” that have been withheld and that those documents – whether they were created 25 pre or post-filing the instant action – should be identified on the log. Implicit responds that pursuant 26 27 28 1 Juniper does not argue that information provided in the privilege log, in combination with the information provided in the July 30, 2012 letter, leaves a significant question as to whether the privilege is appropriately asserted for any document in particular. 1 to the parties’ agreement, no post-filing mediation documents have been identified because the parties 2 agreed not to include post-filing privileged documents in their logs. Implicit, however, fails to explain 3 why the pre-filing mediation documents have not been included in the log.2 Therefore, the Court orders 4 Implicit to supplement is privilege log within seven (7) days of the date of this Order to include pre- 5 filing “mediation” documents. Juniper also complains that the log does not contain any internal pre-filing investigation 7 documents. Implicit responds that any such documents are not relevant and, in any event, would be 8 privileged. The Court finds that pre-filing investigation documents may be relevant to Juniper’s unclean 9 hands defense and, therefore, should be listed on Implicit’s privilege log. Implicit shall supplement is 10 United States District Court For the Northern District of California 6 privilege log within seven (7) days of the date of this Order to include pre-filing investigation 11 documents. 12 Finally, Juniper requests that the Court order Implicit to provide a deposition witness regarding 13 the facts disclosed in Implicit’s privilege log and any documents produced in response to this motion. 14 The Court finds there is no justification for Juniper’s request. 15 Juniper also argues that Implicit’s response to its Interrogatory No. 20 is deficient. Interrogatory 16 No. 20 asks Implicit to identify with specificity what Implicit contends to be the “‘first packet’ in the 17 context of an alleged infringement by the Juniper accused products.” Implicit’s response is that “first 18 packet” means “the first packet of a new message that creates a stateful data processing path.” In its 19 interrogatory response, Implicit cites to Juniper documentation showing when the creation of a “stateful 20 data processing path” occurs. See Ex. D to Docket No. 138 at pg. 7. In its response to the motion to 21 compel, Implicit explains further that what is the “first packet” depends on the device configuration and 22 gives two additional examples (first control packet in “establishing the TCP/IP handshake” and first 23 packet “containing content. . . .”). Docket No. 140 at 2. Implicit argues this “functional” definition is 24 a sufficient response. The Court agrees. Implicit has, through its interrogatory response and response 25 2 26 27 28 In its July 23, 2012 Order, the Court held that “[b]ased on the current record, the Court does not find sufficient cause to order Implicit to produce its confidential communications submitted to third-party mediators. However, that conclusion may change as depositions in this case continue and expert discovery commences.” Docket No. 119 at 2. That issue, however, is not yet before the Court. The only issue before the Court is whether these mediation documents should be included on Implicit’s privilege log. 2 1 to the motion to compel, explained the first packet in the “context” of the alleged infringing Juniper 2 products. Implicit’s definition may be broad, but it is sufficiently clear to allow Juniper to defend this 3 case. 4 Juniper also moves to compel the identification of internal documents regarding pre-1999 5 “sales,” which Implicit represented had been produced but now claims do not exist. See Docket No. 113 6 (July 16, 2012 Order requiring Implicit to identify internal documents already produced). Implicit 7 responds that when it went back to attempt to identify any pre-1999 internal sales documents, it did not 8 find any. The Court cannot compel Implicit to identify documents that do not exist, even if Implicit 9 mistakenly informed the Court that such documents had already been produced. United States District Court For the Northern District of California 10 11 IT IS SO ORDERED. 12 13 Dated: August 16, 2012 SUSAN ILLSTON United States District Judge 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 3

Disclaimer: Justia Dockets & Filings provides public litigation records from the federal appellate and district courts. These filings and docket sheets should not be considered findings of fact or liability, nor do they necessarily reflect the view of Justia.


Why Is My Information Online?