Case 3:17-cv-05659-WHA Document 67-18 Filed 04/19/18 Page 1 of 11
`
`Case 3:17-cv-05659-WHA Document 67-18 Filed 04/19/18 Page 1 of 11
`
`EXHIBIT 16
`
`

`

`Case 3:17-cv-05659-WHA Document 67-18 Filed 04/19/18 Page 2 of 11
`
`From: Kastens, Kris
`Sent: Tuesday, March 27, 2018 4:47 PM
`To: Glucoft, Josh
`Cc: Andre, Paul; Kobialka, Lisa; Hannah, James; Kagan, Jonathan; Carson, Rebecca; Wang, Kevin; Holland, Eileen;
`Manes, Austin; Curran, Casey; Manes, Austin; Lee, Michael H.
`Subject: RE: Finjan v. Juniper - Discovery
` 
`Josh, 
` 
`We write regarding Juniper’s refusal to provide discovery into the ATP Appliance and Spotlight Secure.  We understand 
`that Juniper refuses to provide any discovery into these products because it contends they were not properly identified 
`by Finjan in its complaint.  Juniper is incorrect that these products were not properly identified.  First, Finjan identified 
`and described the dynamic analysis functionality in Sky ATP in its complaint, which includes the same type of 
`functionality provided in the ATP Appliance.  See Dkt. 1 at Pars. 45‐50.  Additionally, the Spotlight Secure is part of Sky 
`ATP, and was therefore properly identified as well.   
` 
`Furthermore, as required under the Patent Local Rules, Finjan properly identified both products in great detail in its 
`March 8, 2018, infringement contentions, which set forth the basis for Finjan’s infringement allegations.  See PLR 3‐1.  As 
`such, these products were properly and timely disclosed to Juniper and are part of this case.  
` 
`As such, confirm by end of the day tomorrow that Juniper will agree that these products are in the case and that it will 
`provide discovery into them, or provide a date this week to meet and confer.  I am available Thursday, March 29th 
`between 3PM‐5PM and Friday, March 30th between 10AM‐Noon and 2PM‐4PM.   
` 
`Sincerely, 
`Kris 
` 
`From: Kastens, Kris
`Sent: Monday, March 26, 2018 9:53 AM
`To: Glucoft, Josh
`Cc: Andre, Paul; Kobialka, Lisa; Hannah, James; Kagan, Jonathan; Carson, Rebecca; Wang, Kevin; Holland, Eileen;
`Manes, Austin; Curran, Casey; Manes, Austin; Lee, Michael H.
`Subject: RE: Finjan v. Juniper - Discovery
` 
`Josh, 
`We write regarding a number of outstanding discovery issues. 
` 
`Deficiencies in Juniper’s Document and Source Code Production 
`Juniper’s document production remains deficient.  For example, we still have not received any confidential design or 
`development documents from Juniper related to the accused products.  Confirm that Juniper will produce these 
`documents by March 30. 
` 
`
`1
`
`

`

`Case 3:17-cv-05659-WHA Document 67-18 Filed 04/19/18 Page 3 of 11
`
`Juniper’s source code production is deficient as well.  First, it does not appear that key source code was produced, 
`including: 
` source code for dynamic analysis/sandbox in Sky APT 
` source code for Juniper’s ExpressAV  
` rules/patterns used for static and dynamic analysis in Sky ATP, ExpressAV 
` metadata for the source code.  Metadata was removed, as the last modified date for nearly every file is the 
`same 
`
` 
`Juniper also needs to untar or decompress the .tgz files in the following directory and subdirectories so that they can be 
`reviewed:  
` Review\JUNOS\17.4R1.16\17.4R1.16\src\dstfiles\ 
`
` 
`Confirm that Juniper will address these issues and also make the ATP Appliance source code available for inspection by 
`April 10.   
` 
`We have also identified technical documents in Juniper’s source code that appear to be improperly withheld as source 
`code and must be produced under a lower designation.  As such, confirm that the following documents will be produced 
`by March 30: 
` Help documents (e.g. help‐summary.html) from the following directory:  
`o Review\JUNOS\17.4R1.16\17.4R1.16\src\doc\online\html\ 
`
` 
`Furthermore, the search capability that was provided by Juniper is insufficient.   Juniper did not provide an indexed 
`search tool (https://en.wikipedia.org/wiki/Search_engine_indexing), despite Finjan’s request for one.  As a result, 
`searching takes an inordinate amount of time and the contents of files cannot  be searched.   Furthermore, it appears 
`that Juniper has not activated the search functionality in the UltraEdit program (the UltraFinder functionality).  Confirm 
`that Juniper will address this before the next source code review. 
` 
`Finally, Finjan identifies Andy Jian and Michael Lee for reviewing Juniper’s source code starting on Tuesday, April 10th 
`and continuing each day until Friday, April 13th. 
` 
`Finjan’s Production of Documents and Third Party Confidential Information 
`Finjan has produced tens of thousands of pages to Juniper, including prosecution histories, thousands of pages of 
`confidential technical documents, other internal documentation, and invalidity contentions.  Finjan has also already 
`made its source code available for inspection.  As such, we expect that the majority of Finjan’s non‐ESI and non‐third 
`party confidential production was completed weeks ago. 
` 
`Second, we have not seen a response from Juniper to Intel’s outside counsel (Jason Choy) accepting Intel’s conditions on 
`the production of its license.  If Juniper agrees with these conditions send a confirmation to Mr. Choy and include us on 
`the email.  Further, we have not received any confirmation that Juniper has spoken to counsel for Symantec/Blue Coat 
`(Robin Brewer) about its license, as we indicated was necessary last week.  If you reached agreement with 
`Symantec/Blue Coat, please send an email confirming this that includes me and counsel for Symantec/Blue Coat.  Finjan 
`is ready to produce these documents and is waiting on action from Juniper.  Finjan will also prepare a provision specific 
`to the Proofpoint license in the Protective Order and will produce its agreement with Aladdin (which is not a license).  
` 
`Third, we strongly disagree that Finjan is late on providing notice to third parties.  As shown in my March 16th email, we 
`reached out to Juniper soon after we received Juniper’s RFPs requesting third‐party confidential information to see if the 
`scope of the requests could be narrowed.  We met and conferred last Monday about this and were expecting 
`confirmation from Juniper on how it would narrow its requests.  However, we understand from your last email that you 
`are not agreeing to narrow any of your requests in any way, and we will start providing expedited notice to those 
`affected third parties starting today, more than a week before Finjan’s objections to these RFPs are even due.  As we 
`noted on our call, we expect that these third parties will object to Juniper’s current requests if they are not 
`narrowed.  As such, we will provide your contact information to the notified third parties to discuss Juniper’s requests. 
`
`2
`
`

`

`Case 3:17-cv-05659-WHA Document 67-18 Filed 04/19/18 Page 4 of 11
`
` 
`Fourth, Finjan agreed to produce expert reports and Finjan employee deposition transcripts that did not include third 
`party confidential information on an expedited basis, which it did last Monday.  The remaining expert reports and 
`deposition transcripts include confidential information of third parties and will be produced subject to our objections 
`and after we provide notice to those third parties, which we are providing on an expedited basis.  
` 
`Sincerely, 
`Kris   
` 
` 
`
`
`Kris Kastens
`Associate
`
`
`Kramer Levin Naftalis & Frankel LLP
`990 Marsh Road, Menlo Park, California 94025
`T 650.752.1715 F 650.752.1815
`
`This communication (including any attachments) is intended solely for the recipient(s) named above and may contain information that is
`confidential, privileged or legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received
`this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication.
`Thank you for your cooperation.
`
`
`
`From: Glucoft, Josh [mailto:JGlucoft@irell.com]
`Sent: Wednesday, March 21, 2018 2:08 PM
`To: Kastens, Kris
`Cc: Andre, Paul; Kobialka, Lisa; Hannah, James; Kagan, Jonathan; Carson, Rebecca; Wang, Kevin; Holland, Eileen;
`Manes, Austin; Curran, Casey; Manes, Austin; Lee, Michael H.; #Juniper/Finjan [Int]
`Subject: [EXTERNAL] RE: Finjan v. Juniper - Discovery
` 
`Kris,
`
`Juniper confirms that it will not share confidential third party licenses with Designated House Counsel for those third
`parties that object to such disclosure. This confirmation should suffice for you to produce the licenses for Webroot,
`Secure Computing, and McAfee. As I discussed on my call today with Austin, please send us the language for the PO
`addendum to satisfy Proofpoint’s request, and please put us in contact with Symantec so that we can confirm with
`them. Please confirm that Finjan has no agreement with Aladdin transferring an interest in any patent-in-suit as you
`suggested on our call, and please confirm that Finjan has not withheld any other agreements transferring an interest in any
`patent-in-suit.
`
`As for our discovery requests, Juniper is not narrowing the scope of any of its requests for production, so Finjan should
`promptly provide notice to potentially affected third parties, which Finjan should have done weeks ago.
`
`In light of the expedited nature of this proceeding, we have produced the key documentation identified by Finjan—
`Juniper’s highly confidential source code—more than a month in advance of when such production is otherwise
`contemplated under the Patent Local Rules. Finjan must reciprocate its diligence and produce the key documentation we
`identified that is readily available to Finjan. Finjan has already delayed by failing to promptly provide notice to third
`parties, and it appears that Finjan is seeking to delay producing even non-confidential documentation we
`identified. Specifically, we sought expedited production of documents related to patent marking, which includes licensee
`correspondence such as infringement charts, but Finjan has offered to produce only “Documents showing marking” even
`though any such infringement charts or licensee correspondence are not confidential information. Likewise, we identified
`as key documentation deposition transcripts of Finjan experts related to any of the patents-in-suit, but Finjan has not
`offered to produce any expert deposition transcripts, even those related to invalidity that are not confidential. Please
`
`3
`
`

`

`Case 3:17-cv-05659-WHA Document 67-18 Filed 04/19/18 Page 5 of 11
`
`confirm that Finjan will promptly produce this critical documentation in full, and please confirm that Finjan will promptly
`provide notice to potentially affected third parties as Finjan is required under the Interim Model Protective Order.
`
`Thanks,
`Josh
`
`
`From: Kastens, Kris [mailto:KKastens@KRAMERLEVIN.com]  
`Sent: Friday, March 16, 2018 4:02 PM 
`To: Glucoft, Josh <JGlucoft@irell.com> 
`Cc: ~Andre, Paul <pandre@kramerlevin.com>; ~Kobialka, Lisa <lkobialka@kramerlevin.com>; ~Hannah, James 
`<jhannah@kramerlevin.com>; Kagan, Jonathan <JKagan@irell.com>; Carson, Rebecca <RCarson@irell.com>; Wang, 
`Kevin <kwang@irell.com>; Holland, Eileen <EHolland@irell.com>; ~Manes, Austin <amanes@kramerlevin.com>; Curran, 
`Casey <ccurran@irell.com>; ~Manes, Austin <amanes@kramerlevin.com>; ~Lee, Michael <mhlee@kramerlevin.com> 
`Subject: RE: Finjan v. Juniper ‐ Discovery 
` 
`Josh, 
`Regarding third party confidentiality, we would like to discuss the scope of Juniper’s requests so we can provide notice 
`to third parties.  This relates primarily to Juniper’s RFP Nos. 71‐85, which request a broad range of material that 
`implicates third party confidential information. 
` 
`We would also like to discuss third party requests to restrict “Designated House Counsel” from accessing certain 
`licenses. 
` 
`Sincerely, 
`Kris 
` 
`
`
`Kris Kastens
`Associate
`
`
`Kramer Levin Naftalis & Frankel LLP
`990 Marsh Road, Menlo Park, California 94025
`T 650.752.1715 F 650.752.1815
`
`This communication (including any attachments) is intended solely for the recipient(s) named above and may contain information that is
`confidential, privileged or legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received
`this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication.
`Thank you for your cooperation.
`
`
`
`From: Glucoft, Josh [mailto:JGlucoft@irell.com]
`Sent: Friday, March 16, 2018 3:40 PM
`To: Kastens, Kris
`Cc: Andre, Paul; Kobialka, Lisa; Hannah, James; Kagan, Jonathan; Carson, Rebecca; Wang, Kevin; Holland, Eileen;
`Manes, Austin; Curran, Casey; Manes, Austin; Lee, Michael H.; #Juniper/Finjan [Int]
`Subject: [EXTERNAL] RE: Finjan v. Juniper - Discovery
` 
`Kris,
`
`We are not sure what you mean by “indexed searching,” but UltraEdit has substantial searching capabilities, including but
`not limited to: “Search huge log files, generate a list of all lines containing your search string, do pattern-based find and
`replace with regular expression support, search in columns and selected text.” See:
`
`4
`
`

`

`Case 3:17-cv-05659-WHA Document 67-18 Filed 04/19/18 Page 6 of 11
`
`https://www.ultraedit.com/products/ultraedit/ultraedit-feature-map/. When Juniper has produced source code in the past,
`Juniper has provided UltraEdit as a search tool and it has always been sufficient to facilitate effective searching.
`
`Separately, in order to make our meet-and-confer on Monday regarding third party confidentiality issues most effective,
`please let us know in advance which third parties’ confidential information may be covered by our requests and when you
`provided those third parties with notice.
`
`Lastly, with respect to the potential deposition of Mr. Baltasar, thank you for the productive meet and confer yesterday,
`and thank you for confirming that Mr. Baltasar’s deposition is off calendar until the parties are able to determine whether
`and when his deposition will move forward. I can confirm that, as I mentioned on our call, Mr. Baltasar’s role is to
`support sales representatives for sales of Juniper products only in the Europe/Middle East/Africa region. Mr. Baltasar has
`not been involved in any of the development or engineering of Sky ATP or any of the other accused products (e.g., did not
`write any of the code in those products). Additionally, Mr. Baltasar does not regularly travel to the U.S. and has no plans
`to travel to the U.S. Accordingly, we believe that bringing Mr. Baltasar all the way from the Netherlands is not
`proportional to the needs of the case, given that he has no unique knowledge of Sky ATP or any other accused
`product. Please confirm whether you are withdrawing your notice of deposition.
`
`Thanks,
`Josh
`
`
`
`From: Kastens, Kris [mailto:KKastens@KRAMERLEVIN.com]  
`Sent: Friday, March 16, 2018 10:56 AM 
`To: Glucoft, Josh <JGlucoft@irell.com> 
`Cc: ~Andre, Paul <pandre@kramerlevin.com>; ~Kobialka, Lisa <lkobialka@kramerlevin.com>; ~Hannah, James 
`<jhannah@kramerlevin.com>; Kagan, Jonathan <JKagan@irell.com>; Carson, Rebecca <RCarson@irell.com>; Wang, 
`Kevin <kwang@irell.com>; Holland, Eileen <EHolland@irell.com>; ~Manes, Austin <amanes@kramerlevin.com>; Curran, 
`Casey <ccurran@irell.com>; ~Manes, Austin <amanes@kramerlevin.com>; ~Lee, Michael <mhlee@kramerlevin.com> 
`Subject: RE: Finjan v. Juniper ‐ Discovery 
` 
`Josh, 
` 
`Can you confirm that UltraEdit performs indexed searching? 
` 
`Sincerely, 
`Kris 
` 
`
`
`Kris Kastens
`Associate
`
`
`Kramer Levin Naftalis & Frankel LLP
`990 Marsh Road, Menlo Park, California 94025
`T 650.752.1715 F 650.752.1815
`
`This communication (including any attachments) is intended solely for the recipient(s) named above and may contain information that is
`confidential, privileged or legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received
`this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication.
`Thank you for your cooperation.
`
`
`
`From: Glucoft, Josh [mailto:JGlucoft@irell.com]
`Sent: Thursday, March 15, 2018 5:49 PM
`
`5
`
`

`

`Case 3:17-cv-05659-WHA Document 67-18 Filed 04/19/18 Page 7 of 11
`
`To: Kastens, Kris
`Cc: Andre, Paul; Kobialka, Lisa; Hannah, James; Kagan, Jonathan; Carson, Rebecca; Wang, Kevin; Holland, Eileen;
`Manes, Austin; Curran, Casey; Manes, Austin; Lee, Michael H.
`Subject: [EXTERNAL] RE: Finjan v. Juniper - Discovery
` 
`Kris,  
`
` 
`Thank you for confirming that you will abide by the terms of the Interim Model Protective Order. 
`
` 
`With respect to the source code, we will produce it organized by directory and sub-directory so that you can easily
`navigate between different products and files. We will not make any modifications to the code relative to how it has been
`kept in the ordinary course of business, although the code will of course be read-only to prevent modification. We also
`will not create any additional files, including any dummy files or additional index, that are not part of the existing
`codebase. 
`
` 
`As for review tools, we will provide NotePad++, Vim, Emacs, and Grep, as you have requested. We will also provide
`UltraEdit, which includes substantial searching capabilities. These tools will allow you to reasonably review and search
`the entire codebase. We are not, however, going to provide tools that could compromise the integrity of the code by
`facilitating writing to the code, changing file permissions, or connecting the secured computer to a network. For that
`reason, we are not going to provide Cygwin or Coreutils or enable the Windows CLI. 
`
` 
`We will provide Microsoft’s read-only viewers for Word, Excel, and PowerPoint, and you may take notes on the review
`tools that we have provided, such as Notepadd++. We are not, however, going to provide the versions of Microsoft Office
`that allow macros, as those versions present a security concern. Please remember that per the terms of the Interim Model
`Protective Order, you many not copy, remove, or otherwise transfer any portion of the source code, which precludes
`copying the source code into a note-taking application. If you would like us to print out any electronic notes that you
`take, we would be happy to do so provided that we determine the notes do not contain any embedded copies of the source
`code. 
`
` 
`Best, 
`Josh 
`
`
`From: Kastens, Kris [mailto:KKastens@KRAMERLEVIN.com]
`Sent: Wednesday, March 14, 2018 2:11 PM
`To: Glucoft, Josh
`Cc: ~Andre, Paul; ~Kobialka, Lisa; ~Hannah, James; Kagan, Jonathan; Carson, Rebecca; Wang, Kevin; Holland, Eileen;
`~Manes, Austin; Curran, Casey; ~Manes, Austin; ~Lee, Michael
`Subject: RE: Finjan v. Juniper - Discovery
` 
`Josh, 
`Finjan agrees that the Interim Model Protective Order is in place for this case until the parties finalize a protective 
`order.  Please let us know who to ask for at the front desk when we arrive. 
` 
`We also request that the source code be indexed for searching, that the Windows command line be enabled, and 
`MSOffice or OpenOffice installed.  In addition, we request the appropriate tools be installed to review the source 
`code.  The links to download these tools can be found here: 
`  
`
` https://notepad‐plus‐plus.org/download/ 
` http://www.cygwin.com/ 
` http://www.gnu.org/software/emacs/ 
` http://www.vim.org/ 
` http://www.gnu.org/software/grep/ 
` http://www.gnu.org/software/coreutils/ 
`
`6
`
`

`

`Case 3:17-cv-05659-WHA Document 67-18 Filed 04/19/18 Page 8 of 11
`
` 
`Sincerely, 
`Kris 
` 
`
`
`Kris Kastens
`Associate
`
`
`Kramer Levin Naftalis & Frankel LLP
`990 Marsh Road, Menlo Park, California 94025
`T 650.752.1715 F 650.752.1815
`
`This communication (including any attachments) is intended solely for the recipient(s) named above and may contain information that is
`confidential, privileged or legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received
`this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication.
`Thank you for your cooperation.
`
`
`
`From: Glucoft, Josh [mailto:JGlucoft@irell.com]
`Sent: Tuesday, March 13, 2018 2:58 PM
`To: Kastens, Kris
`Cc: Andre, Paul; Kobialka, Lisa; Hannah, James; Kagan, Jonathan; Carson, Rebecca; Wang, Kevin; Holland, Eileen;
`Manes, Austin; Curran, Casey; Manes, Austin; Lee, Michael H.; #Juniper/Finjan [Int]
`Subject: [EXTERNAL] RE: Finjan v. Juniper - Discovery
` 
`Kris,
`
`Finjan chose to serve its infringement contentions on the last day possible, March 8. Until Finjan chose to serve its
`infringement contentions (and even still), Juniper was left largely guessing as to what functionality in the accused
`products is actually at issue. Nonetheless, we have offered to make the source code available for review just 11 days after
`Finjan served its infringement contentions, which demonstrates Juniper’s diligence. Please confirm that for the review
`starting this Monday, March 19, Finjan agrees to abide by the terms of the Interim Model Protective Order pending
`finalization of the parties’ stipulated protective order. Assuming Finjan agrees, the review may begin each day next week
`at 9:00 a.m. and continue until 5:00 p.m., with a break for lunch to accommodate our proctor.
`
`We will respond to the remainder of the issues in your email in due course.
`
`Thanks,
`Josh
`
`
`From: Kastens, Kris [mailto:KKastens@KRAMERLEVIN.com]
`Sent: Monday, March 12, 2018 3:42 PM
`To: Glucoft, Josh
`Cc: ~Andre, Paul; ~Kobialka, Lisa; ~Hannah, James; Kagan, Jonathan; Carson, Rebecca; Wang, Kevin; Holland, Eileen;
`~Manes, Austin; Curran, Casey; ~Manes, Austin; ~Lee, Michael
`Subject: RE: Finjan v. Juniper - Discovery
` 
`Josh, 
` 
`Thank you for confirming that the source code is available for inspection on March 19th.  While this leaves little time for 
`Finjan to review the code before claim selection, Finjan identifies Michael Lee and Kris Kastens as reviewing the code on 
`March 19th‐20th.  Furthermore, we disagree that Juniper can make this production contingent on Finjan’s production of 
`certain unrelated material by March 19th.  Finjan requested production of Juniper’s source code, which is relevant, since 
`
`7
`
`

`

`Case 3:17-cv-05659-WHA Document 67-18 Filed 04/19/18 Page 9 of 11
`
`the day after Judge Alsup ordered that the “shootout” procedure for this case.  As such, Finjan will proceed with a 
`review on March 19th as indicated. 
` 
`In regards to the documents that Juniper is requesting, Finjan will serve its objections and responses to Juniper’s 
`Requests for Production in due course.  However, as a showing of good faith, Finjan can agree to start producing the 
`following on a rolling basis beginning on March 19th: 
` 
`
` Documents showing marking; 
` Non‐confidential invalidity contentions addressed to asserted patents; 
` Non‐confidential expert reports; and 
` Deposition transcripts of Finjan employees that do not include third party confidential information. 
`
` 
`We note that some of this was already produced, as some of it is part of the file history of the asserted patents.  In 
`regards to the other material requested, production by March 19th is impossible, as much the majority of these 
`documents were marked confidential by a third party.  Let us know when you are available to meet and confer on the 
`scope of these requests.   
` 
`To the extent that Juniper is alleging that Finjan’s production has been deficient, Finjan has already produced tens of 
`thousands of pages of its highly confidential documents (including documents showing marking with the patents), first 
`with its initial disclosures and then more with its infringement contentions.  Finjan has also already made its source code 
`available for inspection under the interim protective order.   
` 
`Sincerely, 
`Kris 
` 
`
`
`Kris Kastens
`Associate
`
`
`Kramer Levin Naftalis & Frankel LLP
`990 Marsh Road, Menlo Park, California 94025
`T 650.752.1715 F 650.752.1815
`
`This communication (including any attachments) is intended solely for the recipient(s) named above and may contain information that is
`confidential, privileged or legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received
`this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication.
`Thank you for your cooperation.
`
`
`
`From: Glucoft, Josh [mailto:JGlucoft@irell.com]
`Sent: Monday, March 12, 2018 12:48 PM
`To: Kastens, Kris
`Cc: Andre, Paul; Kobialka, Lisa; Hannah, James; Kagan, Jonathan; Carson, Rebecca; Wang, Kevin; Holland, Eileen;
`Manes, Austin; Curran, Casey; Manes, Austin; #Juniper/Finjan [Int]
`Subject: [EXTERNAL] RE: Finjan v. Juniper - Discovery
` 
`Kris,
`
`It appears our emails have crossed. Last week we offered to make the source code of the products identified in the
`Complaint available for review by Monday, March 19 provided that, while the parties negotiate a stipulated protective
`order, Finjan agree to abide by the terms of the Interim Model Protective Order and to produce the limited categories of
`documents listed in my email. Please confirm.
`
`
`8
`
`

`

`Case 3:17-cv-05659-WHA Document 67-18 Filed 04/19/18 Page 10 of 11
`
`We will respond to the remainder of the issues in your email in due course.
`
`Thanks,
`Josh
`
`
`From: Kastens, Kris [mailto:KKastens@KRAMERLEVIN.com]  
`Sent: Monday, March 12, 2018 11:43 AM 
`To: Glucoft, Josh <JGlucoft@irell.com> 
`Cc: ~Andre, Paul <pandre@kramerlevin.com>; ~Kobialka, Lisa <lkobialka@kramerlevin.com>; ~Hannah, James 
`<jhannah@kramerlevin.com>; Kagan, Jonathan <JKagan@irell.com>; Carson, Rebecca <RCarson@irell.com>; Wang, 
`Kevin <kwang@irell.com>; Holland, Eileen <EHolland@irell.com>; ~Manes, Austin <amanes@kramerlevin.com>; Curran, 
`Casey <ccurran@irell.com>; ~Manes, Austin <amanes@kramerlevin.com> 
`Subject: Finjan v. Juniper ‐ Discovery 
` 
`Josh, 
` 
`We write on a number of outstanding discovery issues. 
` 
`First, Finjan intends to identify a claim for summary judgment briefing on March 22.  However, we note that Juniper has 
`still not identified when its source code is available for inspection, despite the Court’s order for expedited 
`discovery.  Further, as we’ve stated on several occasions, that the parties are still negotiating a protective order for the 
`case cannot be the basis for withholding the source code.  Patent L.R. 2‐2.  If Juniper does not agree to make the code 
`available by this Wednesday, March 14, let us know today so we can raise this with the Court.  Juniper has had more 
`than two weeks to collect this information and has no basis to continue stonewalling.  We have also reviewed Juniper’s 
`recent document production, and it does not appear to include any internal design documents.   Confirm that Juniper 
`will produce its internal design documents by this Wednesday as well.   
` 
`Second, Juniper’s initial disclosures include four individuals having the same description: ���May have technical 
`information about accused Juniper products.”  Confirm that you will provide information on which Juniper products 
`each individual has information on by this Wednesday. 
` 
`Third, we’ve attached a draft of the ESI order with Finjan’s revisions.  When can we expect Juniper’s edits to the draft 
`protective order we sent on March 7th? 
` 
`Sincerely, 
`Kris 
` 
` 
`
`
`Kris Kastens
`Associate
`
`
`Kramer Levin Naftalis & Frankel LLP
`990 Marsh Road, Menlo Park, California 94025
`T 650.752.1715 F 650.752.1815
`kkastens@kramerlevin.com
`
`
`Bio
`
`This communication (including any attachments) is intended solely for the recipient(s) named above and may contain information that is
`confidential, privileged or legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received
`
`9
`
`

`

`Case 3:17-cv-05659-WHA Document 67-18 Filed 04/19/18 Page 11 of 11
`
`this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication.
`Thank you for your cooperation.
`
`
`From: Glucoft, Josh [mailto:JGlucoft@irell.com]
`Sent: Friday, March 09, 2018 11:16 AM
`To: Andre, Paul; Kobialka, Lisa; Kastens, Kris; Hannah, James; Manes, Austin
`Cc: #Juniper/Finjan [Int]
`Subject: [EXTERNAL] March 22
` 
`Counsel, 
`
` 
`Although not expressly reflected in the Court’s Case Management Order, the Court ordered the parties at the Case
`Management Conference to provide notice by March 22 as to which claim each party will move on for the upcoming
`summary judgment briefing. See CMC Transcript at 7:11-18. Please confirm that Finjan will provide notice of its elected
`claim on or before March 22. 
`
` 
`Thanks,
`Josh  
`  
`  
`__________________________________________________________________
`Joshua P. Glucoft | Irell & Manella LLP | 310.203.7189 | www.irell.com 
`  
`
`
`
`PLEASE NOTE: This message, including any attachments, may include privileged, confidential and/or inside
`information. Any distribution or use of this communication by anyone other than the intended recipient(s) is
`strictly prohibited and may be unlawful. If you are not the intended recipient, please notify the sender by
`replying to this message and then delete it from your system. Thank you.
`
`10
`
`