United States et al v. Google LLC Document 252: transcript

Virginia Eastern District Court
Case No. 1:23-cv-00108-LMB-JFA
Filed June 5, 2023

TRANSCRIPT of motions hearing held on 6-2-23, before Judge John F. Anderson, Court Reporter Stephanie Austin, Telephone number 571-298-1649. NOTICE RE REDACTION OF TRANSCRIPTS:The parties have thirty(30) calendar days to file with the Court a Notice of Intent to Request Redaction of this transcript. If no such Notice is filed, the transcript will be made remotely electronically available to the public without redaction after 90 calendar days. The policy is located on our website at www.vaed.uscourts.gov Transcript may be viewed at the court public terminal or purchased through the court reporter before the deadline for Release of Transcript Restriction. After that date it may be obtained through PACER Redaction Request due 7/5/2023. Redacted Transcript Deadline set for 8/7/2023. Release of Transcript Restriction set for 9/5/2023.(Austin, Stephanie)

BackBack to United States et al v. Google LLC

Tags No tags have been applied so far. Sign in to add some.
  Formatted Text Tab Overlap Raw Text Right End
Page 1 PageID#
UNITED STATES DISTRICT COURT
EASTERN DISTRICT OF VIRGINIA
ALEXANDRIA DIVISION
---------------------------x
UNITED STATES, et al.,
:
:
Plaintiffs, :
versus
:
:
GOOGLE LLC,
:
:
Defendant.
:
---------------------------x
Civil Action No.:
1:23-cv-Friday, June 2, Alexandria, Virginia
Pages 1-
The above-entitled motions hearing was heard before
the Honorable John F. Anderson, United States Magistrate
Judge. This proceeding commenced at 11:02 a.m.
A P P E A R A N C E S:
FOR THE PLAINTIFFS:
KRISTIN STARR, ESQUIRE
OFFICE OF THE UNITED STATES ATTORNEY
2100 Jamieson Avenue
Alexandria, Virginia (703) 299-
KELLY GARCIA, ESQUIRE
JULIA TARVER WOOD, ESQUIRE
UNITED STATES DEPARTMENT OF JUSTICE
ANTITRUST DIVISION
450 Fifth Street, NW
Washington, D.C. (202) 894-
TYLER HENRY, ESQUIRE
OFFICE OF THE ATTORNEY GENERAL
OFFICE OF THE SOLICITOR GENERAL
202 North Ninth Street
Richmond, Virginia (804) 786-
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 2 PageID#
A P P E A R A N C E S:
FOR THE DEFENDANT:

ANDREW EWALT, ESQUIRE
SARA SALEM, ESQUIRE
FRESHFIELDS BRUCKHAUS DERINGER, LLP
700 13th Street, NW
10th Floor
Washington, D.C. (202) 777-JOSEPH BIAL, ESQUIRE
AMY MAUSER, ESQUIRE
PAUL, WEISS, RIFKIND,
WHARTON & GARRISON LLP
2001 K Street, NW
Washington, D.C. (202) 223-
CRAIG REILLY, ESQUIRE
LAW OFFICE OF CRAIG C. REILLY
209 Madison Street
Suite Alexandria, Virginia (703) 549-
COURT REPORTER:
STEPHANIE M. AUSTIN, RPR, CRR
Official Court Reporter
United States District Court
401 Courthouse Square
Alexandria, Virginia (571) 298-S.AustinReporting@gmail.com
COMPUTERIZED TRANSCRIPTION OF STENOGRAPHIC NOTES
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 3 PageID#
P R O C E E D I N G S
THE DEPUTY CLERK:
United States of America, et
al. versus Google LLC, Civil Action Number 23-cv-108.
MS. STARR:
Good morning, Judge Anderson.

Kristin Starr from the U.S. Attorney's Office.

are my colleagues from the Department of Justice, Kelly

Garcia and Julia Tarver Wood.

And with me
I'll let the counsel from the State AG's Office
introduce themselves.
THE COURT:
Who's going to be arguing for the
United States?
MS. STARR:
Kelly Garcia will be arguing for the
United States, Your Honor.

THE COURT:
Thank you.

MS. GARCIA:

THE COURT:

MS. TARVER WOOD:

MR. HENRY:
Good morning, Your Honor.
Good morning.
Good morning, Your Honor.
Good morning, Your Honor.
Ty Henry

from the Virginia Attorney General's Office on behalf of the

plaintiff states.

THE COURT:
Thank you.

MR. EWALT:
Good morning, Your Honor.

Andrew Ewalt from Freshfields on behalf of Google.
I'm

joined by Joseph Bial from Paul, Weiss, who will be arguing

this morning; as well as Sara Salem from Freshfields;
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 4 PageID#
Amy Mauser from Paul, Weiss; and, of course, Craig Reilly.

THE COURT:
Okay.
Thank you.
All right.

Well, I got a motion that has two parts in front

of it.

deal with that completely, and then we'll get to the other

issue after that.

I want to deal with the custodian issue first and
So let's go ahead -- and I've read what everybody

submitted.
You know, it -- I appreciate your trying to keep

the briefs brief, but there's -- and this goes to both of

the issues, but it relates a little less so to the custodian

issue.

A significant amount of substantive information

really hasn't been provided to me.

identified 63 custodians.

relating -- at least provided to me, I assume you all know

it -- as to, you know, who these custodians really were,

what they really did, what their role really was based on

the information that you provided.

provided some information as to those 63, and you've gotten

some information, you haven't gotten some information.

They've agreed to produce custodians or follow-on custodians

for some but not the others.

You talk about we
There's no information
And, you know, they
But I don't have any real substance behind the

numbers, and that's a little concerning.
And I know your

argument is, you know, they had information back in -- or
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 5 PageID#
the person who was in this position back in 2020, it was

agreed that they had substantive information and their

material issue had been reviewed and looked at.

take it from your argument it is -- I am to assume that that

position, or whatever the person did in that position in

2020, has an ongoing relationship, need or involvement in

the issues in this case.

not something that has really been shown to me at this

point.

And I -- I
But, I mean, that's an assumption;
You know, clearly, Google has acknowledged that in

some respects, and that some of the successor custodians

they've agreed to either are already on the list and are

currently doing jobs, functions, responsibilities that

are -- they acknowledge are -- but I'm at a little bit of a

loss as to how is it that I just assume a custodian in 2020,

a new person in that job duties and responsibilities is

going to have information between October of 2020 and now.

MS. GARCIA:
Your Honor, good morning.
Kelly Garcia for the United States.
So today we're coming before you on only one

remaining issue.
With respect to the issue of successor

custodians, this morning we received an email from Google's

counsel in which they agreed to identify the remaining

successor custodians in order to cover the post-October
time period and add those custodians to their list.
As we
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 6 PageID#
responded this morning, we consider this issue resolved.

THE COURT:
Okay.
Well then, that whole

discussion was for nothing.
I guess I should have asked if

there any updates on that issue before I came in.

Well, that's -- so they're going to provide you

the information on the 18 of the 63 that you didn't have.

The 11 that they said, you know, we have successors for,

they're going to be looking at their documents and providing

information from October of 2020 to the present; is that

your understanding?

MS. GARCIA:

THE COURT:
Exactly, Your Honor.
Is that consistent with what -- I had

a hearing at 10.
I didn't see any filings or anything to

indicate that that got worked out.

But is that the agreement for --

MR. BIAL:

Google.
Your Honor, yes.
Joseph Bial for
That is the agreement.

THE COURT:
Okay.
Well, thank you very much.

Let's move to the next issue, which is, honestly,

even more confusing to me.

in front of me today, you know, you've got the document

requests, you've got an -- well, first of all, have you

worked it out, I guess should be my first question, and if

not, then I'll continue to have some discussions.

MS. GARCIA:
And my concerns with what I have
I appreciate that, Your Honor.
We're
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 7 PageID#
still at an impasse, so this is still an issue that we would

like resolution on today.

THE COURT:
Okay.
Well, whether you're able to
get a decision from me today will be -- we'll find out.
But the thing that I am -- again, I'm not sure I

fully understand based on the briefing.

recognize you've got a lot of people who are dedicating

their full time and attention to this case and know a lot

more about this case than I do.

And, again, I
The issue -- overarching issue is they have agreed

to provide you with 9 of the 12 source code requests.

three, the last three, they've said, you know, either we

understand, we don't think it's relevant, we don't really --

you know, too hard to figure out what it is.

The
I don't understand when they say they're going to

be producing all the source code as to a particular project,

tool, whatever, what it is that's in the remaining amounts

that is not included in the first amount here.

So, help me understand what it is in those three

areas that seem to be at issue.

than just that, but I think that's a key issue that we need

to address.

And I know there are more
So -- and, again, you know, the first nine are

pretty specific.
"This project," they know what that

project is, they can go look.
The others are a little
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 8 PageID#
bit -- you know, source code that relates to -- pretty

amorphous.

particular project, proposal, whatever.
You know, how you do X, Y, Z, as opposed to a

So let me hear about that; okay?

MS. GARCIA:

As counsel acknowledged on a meet-and-confer
Yes, Your Honor.

yesterday, the way in which we described the last three

categories of our RFP may not be how Google's own engineers

describe it.
What we've tried is -- tried to do is

describe, with good-faith efforts, other information that we

believe would be relevant, although we have no code name or

specific other identifier in order to be able to give more

information at this time.

THE COURT:
Well, you know, this Project Bernanke

or Poirot or the dynamic revenue share or the predictive

highest bidder, the Smart Bidding, do they encompass what

you're asking for in any other requests or not?

MS. GARCIA:
Your Honor, they may.
And if I --

with this opportunity, I would like to be able to describe

those three remaining requests in plain language.

So with respect to -- with respect to RFP
Part 10, we've given a functional description here asking

for the source code or algorithms that choose what

exchanges, DSPs and Ad Networks are called on by each of the

Google products at issue in this case, Google Ad Manager,
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 9 PageID#
DV360 and Google Ads.
To the extent those are covered by any of the code

names that we've identified, we appreciate Google's efforts

to search for and identify responsive information, but our

concern is that if we don't already know a certain name of a

project, particularly a newer project that perhaps postdates

several documents and depositions that happened during the

investigation, we don't want to suggest that those -- that

source code or those algorithms are not relevant here.

THE COURT:
So, I mean, the document request that

you have served -- and that's what's in front of me, to some

extent -- and looking at 10:

related products that determine which exchanges, DSPs and Ad

Networks to call."

MS. GARCIA:

THE COURT:

"Any curation function for the
Yes, Your Honor.
So go back and tell me again what that
really means.
MS. GARCIA:
So by "curation function," we're

simply referring to the function of the algorithm that

chooses which exchanges, DSPs or Ad Networks are called by

the program.

source code that are specific to Google Ad Manager, DV
and Google Ads.

We're limiting our request to algorithms and
THE COURT:
Okay.
All right.
What about 11?
"Any bid, price floor or auction optimization algorithm" -Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-164
Page 10 PageID#
any -- "product or feature."

MS. GARCIA:

With respect to Subsection 11, we believe we've --

we're asking for source code for any Google bid, price floor

or auction optimization algorithm, product or feature, and

we've provided counsel and in the papers some references to

complaint paragraphs in an attempt to give as much

information as we possibly could.

THE COURT:
Yes, Your Honor.
Why don't you think that's already

included in the, you know, other project information and

other things that you've asked for in 1 through 9?

MS. GARCIA:
Your Honor, it may very well be

included in those responses, but given the information that

we have to date and the information that we have from

Google, we cannot say for sure that it is.

THE COURT:

MS. GARCIA:
All right.
And 12.
Twelve asks for source code

pertaining to any automated means or manner of bidding,

whether on individual bids or a campaign-level basis.

Again, the complaint discusses these issues, and,

unfortunately, we don't have specific code names or other

identifiers that we can provide to Google based on the

information that we've been able to gather up to this point;

however, we believe that this is sufficient information for

Google to be able to take back to its client.
You know, the
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 11 PageID#
teams of engineers that work at Google, we suspect that they

have more information on what exactly these automated means

are called, and, unfortunately, we cannot provide any more

information other than what we have.

THE COURT:
Okay.
Well, what efforts have you

taken, other than good-faith consultation with counsel, to

figure out what it is?

a very narrow area as to, you know, what is it that we need

to do to, you know, figure out about, you know, curation
I mean, have you taken a 30(b)(6) on

function for products that determine the exchanges?

bid floor price auction optimization algorithm, product or

feature?

Or the
Or try and figure out something specific?
I mean, the problem is, if you're asking me to

order them to do something that is vague -- well, if it's

something they're already going to be providing, that's not

a problem, and I'll hear whether it really is, these three

things are subsumed in 1 through 9 or not.

your concerns.

some of these projects or programs or code names is limited,

if they limit it to that particular thing, and it also does

or relates to other things that you want to get some other

information that relates to that, but 1 through 9 seem very

specific; 10, 11 and 12 seem pretty broad, maybe vague,

sometimes catch-all.

when you read those three compared to the first nine.
And I understand
If a -- you know, if a directed reading of
Those are all terms that come to mind
And I
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 12 PageID#
don't want to be in a position of ordering somebody to do

something that isn't specific.

So what have you done in order to get specific

information from Google other than through lawyers and

communications with counsel?

MS. GARCIA:
Your Honor, during the course of our

investigation, we took several depositions, as you know.
We

posed these questions to individuals who we understood were

involved in the creation of this code, and those individuals

were not able to give us a complete understanding of the

code itself.

suggested that there are several engineers across Google who

work on issues like this.

pursued a 30(b)(6) at this time.
A lot of the testimony that we received
For that reason, we have not

This case is -- at its core, it's about

programmatic digital advertising tools, which is its code.

We've done our best to identify code names, and we have in
through 9, but, otherwise, we've done our best to articulate

what we are looking for.

What we told Google yesterday on a meet-and-confer

was that if Google's engineering teams have made good-faith

efforts to find responsive source code and cannot find it,

we would accept an affidavit from a Google employee with

knowledge explaining that they've taken steps to identify

this information and that it doesn't exist.
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 13 PageID#
We've also made clear that, in addition to the

affidavit, we would ask that Google stipulate that neither

party would rely on source code if it comes to light later

on that this information does, in fact, exist.

THE COURT:
Okay.
There's a fair amount of

discussion in your papers about your experts, him or her,

needing additional information and needing roadmaps and

guidelines and those kinds of things.

from an expert; I only have you saying your experts may need

I don't have anything
this kind of information.
What's the basis for your statement, and why is it

that you think what they have agreed to provide -- and they

have, you know, outlined in their opposition some

information they've agreed to search for and provide

relating to source code that they've agreed to provide, and

why is any more necessary?

MS. GARCIA:
Your Honor, the basis for this

request was from -- it was a request from our expert teams

and their consultation teams.

How they explained it to us -- I'm not someone who

has a degree in computer science, so I can't pretend to have

firsthand knowledge of this.

explained it to us was that they expect, having done this

type of work before, that there exists data dictionaries,

user manuals and other explanatory materials in the ordinary
But the way that they
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 14 PageID#
course of business at Google.

Google is a large organization and no one person is likely

to have a full understanding of all of the relevant code

across the company, they expect manuals exist to explain

these materials to someone within the organization who works

in a different department or someone who is new to the

organization, for example, a new hire.

THE COURT:
information?
They told us that since
Well, why do they need that
I understand they say they may have that

information, they're a big company, and they may have

guidelines and things, but why is it that your experienced

team of experts would need, you know, a roadmap from Google

to look at the information that they --

MS. GARCIA:
Your Honor --

THE COURT:

MS. GARCIA:

From what we have agreed to with plaintiffs in
-- have gotten or will be getting?
Thank you, Your Honor.

order to protect source code and respect the confidentiality

of the source code, our experts will be subject to

significantly restrictive provisions when they do access the

source code.

the morning to a certain point in the night.

go in and be observed by someone else.

but they can't write down any portion of the source code.

All of these strict conditions are agreed to already by the
They can only go in from a certain point in
They can only
They can take notes,
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 15 PageID#
parties in the protective order.

THE COURT:
And they're usual.
I mean, there's

nothing really unusual about that when you're dealing with

source codes.

MS. GARCIA:
So, Your Honor, what we're attempting

to do is arm our experts with the information that they've

told us they would need in order to understand, as

outsiders, not as Google engineers, the information that

they're reviewing when they go in to look at the source

code.

They are also doing this rather quickly.

of the reason why we've asked for Your Honor's intervention

at this stage is that we've -- you know, to date, we haven't

had a discussion about concrete timing, when our experts

will have access to this source code, when everything will

be up and ready.

ambiguous with respect to whether Google has identified any

of the source code to this date.

And part
The proposal that we've seen was a bit
Yesterday on the meet-and-confer, I put the

question to Google and was told that they cannot confirm

that they've identified any of the responsive source code.

THE COURT:
Not even for the nine items that
they've agreed?

MS. GARCIA:

THE COURT:
That's my understanding, Your Honor.
Okay.
Well -- all right.
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 16 PageID#
Well, what else would you like to say before I
hear from Google's counsel?

MS. GARCIA:
Your Honor, I'd like the opportunity

to address any other specific questions you have with

respect to, you know, our efforts to reach agreement up to

this point, any questions you have with respect to why we

believe the source code is so crucial to our case, or any

other questions you have in general.

THE COURT:
Well, I mean, I need to hear from

Google's counsel about what is not in 1 through 9 that may

be covered by the -- if you give a fair reading to 10,
and 12 and not a broad interpretation of that.

you've tried to explain to them what it really is that

you're looking for and want to have, and I think, you know,

are entitled to get that kind of information.

MS. GARCIA:

THE COURT:

I think
Thank you, Your Honor.
So let me hear from counsel.
Thank
you.

MS. GARCIA:

THE COURT:
Thank you.
First, I want to hear about the --

there are nine areas in which you have agreed to provide

source code from.

MR. BIAL:

THE COURT:

That's correct, Your Honor.
And where are you in the process of
getting that so that can start being looked at?
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 17 PageID#
MR. BIAL:
Sure.
So let me just take a step back.

The way that we identify that, and you mentioned

those seem to be less vague, and that's Request for

Production Number 39 that includes the 12 categories.

THE COURT:

MR. BIAL:
Right.
So we work with the folks at the

company to, you know, find out what does that mean, and, in

those instances, as you mentioned, those are projects and so

forth.
So we're able to identify those.
And then it's

still -- obviously it's the company's secret sauce, if you

will, but we've got the protocol here for source code.

think it's just going through the mechanics of that in order

to produce 1 through 9.
Okay.
So I

THE COURT:
I understand that.

Where are we in the mechanics of doing that --

MR. BIAL:

THE COURT:
Oh, it's --- so that we can actually, you know,

start doing something -- that is, the plaintiffs can start

seeing that information and making a determination as to

whether, you know, the information that you're providing is

going to be sufficient or not?

MR. BIAL:

Correct.
No, Your Honor.
That's a
fair question.
So that's actually -- right now we're in the
process of getting that prepared for production, but we're
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 18 PageID#
still going to have to figure out who is going to receive

it, and that might take, you know, a bit of time because

we've got to go through paragraphs 2 and 3 of the --

THE COURT:
"Prepared for production," let's focus
on that issue now.

MR. BIAL:

THE COURT:
Right.
When is it that you are anticipating,

if all of the other items get worked out, that you will be

in a position to allow somebody to go into the room and

start looking at this source code?

MR. BIAL:

THE COURT:

MR. BIAL:

THE COURT:

A couple weeks.
A couple of weeks?
Well, here's the thing, Your Honor -You've had these requests for how long
now?

MR. BIAL:
Yeah, no.
And it's really not that

part of it; it's really Sections 2 and 3 of the protocol.

They have to provide names to us, and then we have to vet

those names.

THE COURT:
You may not have understood my
question.
Assuming all -- and I want to know on the Google

side, when has that -- when will you be prepared to have all

the source code that you have agreed to produce available to

be reviewed?
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 19 PageID#
MR. BIAL:

THE COURT:

being acceptable.

weeks or months --
Within a week.
Okay.
All right.
So, that, I see as
You know, the idea that it's going to be

MR. BIAL:

THE COURT:
No, I didn't intend to -You know, we've got a process, we've

got a procedure, we've got to work through things, we're

preparing.

case to not be doing what you have agreed to do.
You know, I -- we don't have enough time in this
You know,

if we talk about a timetable for things that I order you to

do that you agreed to do, it may be different than that.

But -- okay.

So assuming the other issues, you know, who's

going to look at it, get the room set up and those kinds of

things, you would be in a position to have their experts be

able to start the process of looking at this information

within around a week; is that accurate?

MR. BIAL:
That's correct.

THE COURT:

problem is with 10, 11 and 12.

MR. BIAL:
All right.
Yeah.
So tell me what the
It's -- the question on 10,
and 12, I think is, it's not that -- I mean, these are

intelligent individuals that are trying to help identify

what we would be producing.

in the meet-and-confer that we had yesterday, Ms. Garcia
And let me give an example.
So
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 20 PageID#
mentioned bidding, which -- for 10, 11 and 12.

the client yesterday, and we're in a position to produce

that, if that's what they're actually intending to receive.

I think a meet-and-confer was probably the way to go, but we

are where we are.

We went to
But that -- once we understood it's, you know,

potentially bidding, then we were in a position to go and

start collecting that for production.

question about is that all they want, or are there other

But, again, that is a
things they want, and we don't know.

THE COURT:
Okay.
In these meet-and-confer

sessions, is it just the lawyers, or are technical people

involved?

technical skills and capabilities, but I'm talking about

in-house technical people involved in the discussions to try

and have a fair exchange of information as to what we need

and how can you get it together.
And I don't mean that lawyers can't also have

MR. BIAL:

THE COURT:
These have been counsel.
Okay.
Have you all explored the

possibility of having the people who really understand

things completely -- without things being lost in

translation to some extent -- having a discussion with

counsel to try and flesh some of these issues out?

MR. BIAL:
No, we have not yet done that.
we would be open to doing that.
I think
I think to the extent that
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 21 PageID#
they have more information or can give us more color, then

we could find the right individual.

probably do that in a very short order as well.

THE COURT:
But I think we could
Well, I assume, not only before this

motion got filed, but certainly after this motion got filed,

there have been some efforts to try and figure out what

could be captured in 10, 11 and 12 that isn't already

captured in 1 through 9.

MR. BIAL:
Right.
And I think if you look at some

of what's cited in the reply brief to the complaint, it

does, for some of those, when we're talking about 10, 11 and

12, cite back to precisely the ones that you mentioned

earlier, Bernanke, Poirot.

11 and 12.

government's position is that they're not limiting it to

that kind of thing.

mentioned, so that's the one that's on the table right now,

and we've gotten that one cleared.

So there is some of that in 10,
But I don't believe -- my understanding of the
THE COURT:
I think, you know, again, bidding was
Well, bidding is mentioned in 11 and

12.

automated means or manner of bidding, whether on individual

bids or on a campaign-level basis."

bidding.

It seems to be the primary focus of 12.
Eleven is:
It says:
"Any
So that seems to be
"Bid, price floor or auction
optimization algorithm, product or feature."
So 11 seems to
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 22 PageID#
be -- I don't know whether price floor or auction

optimization is part of bid or not.

relating to products that determine which exchanges are.

that isn't -- is that -- how does that relate to bidding?

MR. BIAL:
But 10 just talks about
Well, I don't know that it does.
So
I

mean, we had a conversation yesterday about those three, and

that was the one thing that was identified.

discussion of the three as a whole rather than going one by

one.

THE COURT:

MR. BIAL:

THE COURT:

MR. BIAL:

THE COURT:

MR. BIAL:
And it was a
Okay.
And I should just mention -Where are you on -I didn't mean to interrupt.
Go ahead.
It's never been the case that we don't

want to provide the information; it's really more of having

the back-and-forth, which we were having until -- or we

continue to have it, actually, after the motion to compel

was filed.

accomplish.

step at that because we now heard bidding was of interest,

and we were able to actually go with something specific like

you see in 1 through 9.

And I think that's what we were trying to
And I thought yesterday was a very productive
THE COURT:
Well, it's a little hard to understand
how bidding just came to light as something of interest when
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 23 PageID#
you look at 10 -- or certainly 11 and 12 that you've had in

your possession for a couple of months now; right?

they were interested in bidding information.

obviously seems to be something that is more focused at this

point.

But that
What about the guidebooks, dictionaries, that kind
of information?

Where are you on that issue?
MR. BIAL:
Yes.
So let me answer that in two
ways.

First, we have a set of search terms.

didn't -- we didn't attach it to our complaint.

20 pages and smaller than single-spaced.

Size 8 font.

That
THE COURT:
I mean, I
It's
It's probably
I probably wouldn't understand them
either.

MR. BIAL:
So it's pretty comprehensive.

We have that, and so they can run that.

would think that those would hit on these manuals.

that's Number 1.

So I
So
I think Number 2 -- and Your Honor put your finger

on this.
For better or for worse, I do antitrust; that's

all I do.
So when I'm working with an expert, I'm seeing

their models, their code.

how-to guide.

I've never heard them ask for a
I mean, they're the experts.
So, you know, I think they could be -- they have
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 24 PageID#
that skill set.
And I think Your Honor said in the

March 26th hearing that experts can be working before they

get the information.

THE COURT:
So presumably they can do that.
Yeah.
But that, to some extent,

counters your argument, that if an expert has some roadmap

as to what this source code is intended to do or doing, when

they get into the, you know, safe space room or whatever it

is that they are limited in access and having information,

they have a base of knowledge to start work on and they're

not going in cold.

So there is some substance behind the request of,

you know, help me understand -- give me a primer on what I'm

going to be going in and looking at when I go in and start

seeing -- I assume it's not a small set of information in

the source code documents.

But it's something that, you know, an expert probably would

want to have some general familiarity with what the process

is or what terminology is being used or those kinds of

things.

I don't know how large it is.
Why wouldn't that be of help to them and of need
to them?
MR. BIAL:
Well, I think it could be.
And I'm not

denying that a guidebook before you -- you know, you go into

the secure room wouldn't be helpful to get you up to speed

in advance.
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 25 PageID#
We were asked that question, and we did run it to

ground, and it was not this kind of guidebook.

guess there's -- I don't think they're talking about a basic

guidebook; I think they're talking about something more

complex than that to go into that room and be looking at the

code in a short amount of time.

I mean, I
For that exercise, at least in the back-and-forth

that we had, which was not insignificant, we were not able

to locate those.
Again, I would point back to the search

terms, which I think -- if that doesn't turn something up, I

think it probably really doesn't exist.

the purposes of our collection and talking to the various

individuals who we thought would have knowledge of that, we

did not come across such a how-to guide.

THE COURT:
Okay.
But at least for
Well, give me your

understanding of where the parties are based on the

conversation that you had yesterday.

MR. BIAL:
Sure.
I think in terms of the overall

motion to compel, clearly we've resolved the successor

custodians.

going to tell you exactly that I thought we did and we

would.

irrespective of the fact that we got it done this morning.

And had we not done that this morning, I was
So that was always going to be taken care of
With respect to the source code, I think 1 through
9, I think we can also agree that those are -- you know,
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 26 PageID#
those are behind us.

minds on those nine.

I think those are a meeting of the
And 10 through 12, as I mentioned earlier, I

think, you know, additional discussions between the parties

on a short leash -- because I understand from what you said

earlier, we don't have time for that -- would probably make

the most sense.

successful, that you'll hear from the government in very

short order.

And I think if that meet-and-confer is not
THE COURT:
Okay.
What about in -- you know,

you're talking I think more directly about 39, but the other

requests that are part of the guidebook dictionary --

MR. BIAL:
Right.

THE COURT:

MR. BIAL:

Again, same thing.
The materials.
-- and the materials.
Right.
Right.
I mean, originally I think the

search terms were more geared toward that, but I think

obviously if they collect that material, then the

guidebooks, it would be helpful to them.

pointed out, if they had something like that, it's helpful;

it's not unhelpful.

THE COURT:
And, as you
That process would turn that up.
Well, explain to me why it would be

difficult for Google to find out whether there are -- and

absent -- putting search terms aside and, you know,

automatic -- you know, one would -- again, I don't know
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 27 PageID#
Google, don't know how complicated all of this is, but it

doesn't seem that difficult to find somebody at Google that

would know whether they have such things as dictionaries or

guidebooks or other kinds of information that one would, you

know, want to -- even if they don't get hit on search terms,

would be in a position to produce if they're there and

exist.

MR. BIAL:
example.
Right.
Well, let me give you an
So pseudocode -- they asked for pseudocode central

repository, and if that existed -- I mean, we absolutely

went to the client, and they were not aware of such a thing.

And so I think, you know, the best answer to that

is really going to those search terms.

were to turn up and we found out about it, we didn't know

about it -- I think they're obviously doing good-faith

searches -- we would turn it over immediately.

it clear that they want that sort of information.

came across it, we would turn it over immediately.

THE COURT:
And if something
They've made
If we
Well, the problem you face -- and,

again, I'm giving you a scenario that I hope would never

happen -- is that you don't produce that kind of

information, and that in the middle of a deposition,

somebody talks about a dictionary, glossary or cultural

guide that is well known within the Google team and the

plaintiffs look at each other and say, did we get that?
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-
And
Page 28 PageID#
they say, no.
I mean, that's why I'm asking you.

this is to make sure that you don't get yourself in

trouble --

MR. BIAL:

THE COURT:
Again,
Correct.
-- is not just relying on these, you

know, pages of search terms, but on some specific

information, going out and making an individualized inquiry

about does that kind of information exist, and, if so, where

is it.

MR. BIAL:
Right.
Understood.

I mean, again, we would know as well once we do

those searches and before the depositions begin.

something turns up, they would get it.

made very clear that that's something that is expected and

that would be something ordinarily pursued in discovery.

THE COURT:
Okay.
All right.
And if
But I think you've
Well, let me just
hear a little bit more from government counsel.

MR. BIAL:

THE COURT:

Was the meet-and-confer yesterday in person or

Thank you, Your Honor.
Thank you.
over the phone or Zoom or how was that done?
MS. GARCIA:
Yesterday's meet-and-confer was on
Microsoft Teams, Your Honor.

THE COURT:

MS. GARCIA:
Okay.
It was the, I want to say ninth
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 29 PageID#
meet-and-confer we have had since the outset of our

litigation since we were -- since we received Google's

objections to our RFPs, including our source code RFPs in

mid-April.

counsel -- not counsel from this firm, but counsel from

another firm representing Google -- and began good-faith

discussions about how Google could go about responding to

this -- these requests.

That same week, we met and conferred with
During the course of that time, we had discussions

about how Google's concerns with respect to source code had

to do a lot with the fact that it was very highly sensitive,

and we proposed an alternative if it existed.

We asked that Google go back to its client -- this

was in early May -- and search for and ask if there was a

central repository for pseudocode.

that pseudocode is a plain-language explanation of source

code.

Our understanding is
We proposed that if Google could do this within a

reasonable time and get our experts that material within a

reasonable time -- which we would have discussed had they

discovered a central repository -- we would take only two

weeks with that source code and come back to them and say

whether or not there is more information that we need or

whether or not what they've provided should suffice.

three weeks, we were told there was no central repository
After
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 30 PageID#
for pseudocode.
We continued to have good-faith discussions.

Yesterday's discussion with Mr. Bial was the first that he

had joined, but it was not the first time that we have

discussed this.

earlier point, we told counsel that we would be prepared --

if they told us that they were prepared to have our experts

come in and examine the source code, that same day we would

get them a list of names of individuals who could come in as

We told counsel that -- going back to an
soon as possible.
We would welcome the opportunity to speak with

their data scientists about these issues.

anything from counsel about that opportunity.

extent they're willing to have data scientists -- and I say

"scientists" because I strongly believe that there's not

going to be one person at the company who has this

information.

THE COURT:

MS. GARCIA:
We haven't heard
But to the
Right.
But if they're willing to have prompt

discussions with those individuals, we would welcome that

opportunity.

The first time that they told us that there wasn't

clarity with respect to 10 -- Numbers 10 through 12 was

May 26th in a letter that was --

THE COURT:
What did the objections to those
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 31 PageID#
requests say?

MS. GARCIA:
Well, the objections, I'll say
without looking, did describe -- object that they are vague.

THE COURT:
I don't have the objections in front

of me, but I suspect I know that they would talk about being

vague or indefinite --

MS. GARCIA:

THE COURT:

MS. GARCIA:

THE COURT:
Yes, they're --- or whatever; so ...
Pardon me, Your Honor.
Yes.
So, I mean, obviously you were put on

notice within 15 days after you served it that that was a

potential issue relating to what you had served.

MS. GARCIA:
That's fair, Your Honor.

What we've tried to do is get to the heart of --

to the extent that these vagueness objections were

objections made to every single RFP that we posed, what it

is that we can do in order to come to a meeting of the minds

as to what these terms mean.

with respect to several other RFPs.

THE COURT:

MS. GARCIA:
And we've made good efforts
All right.
We haven't received a single document

from anyone's custodial files responsive to any search terms

to date.

dictionaries and other important information that our

experts need in order to have sufficient context to read the
This information about manuals and data
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 32 PageID#
code may not be in custodial files.

not be.

It may be, but it may
One concern that we raised yesterday was that we

do not know when we will receive a production from Google of

any documents that hit on any of the search terms in the

exhibit that Mr. Bial brought today.

one way or the other whether or not the search terms are

going to be sufficient.

So we can't tell you
We suspect that, given the tight timeline that our

experts will be facing and the very strict rules in which

they have to oblige in order to review the code, that

they'll want this information more quickly than we would

be -- otherwise be able to get if we waited for a production

from Google responsive to search terms.

With respect to the central repository, that was

part of our attempt to reach resolution and have a

compromise that perhaps would have worked for Google.

unfortunate that there is no central repository, but we

don't mean to suggest that that should be the end of the

inquiry.

Google can and should take in order to identify any manuals

or documents, which may not be one specific manual but may

be a series of manuals or may be a series of dictionaries,

or, you know, a compendium of information that other -- that

others at Google have access to but that we just don't know
It's
I think there are other good-faith steps that
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 33 PageID#
whether or not it exists.

We hope that the search terms we've agreed to in

good faith with Google will be an effective and efficient

way to obtain the information we need, but we don't

understand why it is burdensome for Google to ask its own

people whether or not this information exists and run that

to ground.

So we have concerns about timing.
THE COURT:
And we all have concerns about timing.
I mean, I think we all know the schedule that Judge Brinkema

has set for us, and we all have to work within that

schedule.

And I mean that.

to present a very large case against a very large company,

and a very large company has a lot at stake in defending

this case.

And, you know, honestly, you all have worked together really

very well to date.

the Court's appreciation for you all continuing to work

together.

order yesterday that I need to look at before I enter it.

But, you know, those are the kinds of things that the

parties should be doing.

United States to do that; it's in the interests of Google to

do that, and I want to encourage you all to continue to do

that.
And I'm sympathetic to both sides in this case.
You have a lot on your plate getting ready
But it's got to be done fairly and efficiently.
And I want to express my personal and
I mean, I know I've got requests for a joint
It's in the interests of the
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 34 PageID#
This one, while I think very substantive

meet-and-confers -- sometimes the numbers don't mean much;

it's more of how the substance is going.

substance of the meet-and-confer sounds like it started late

last week and continued into this week, I mean, the real

back-and-forth on exchanging some information.

You know, the
You know, I've expressed to you all some concerns

that I had on what was presented to me in the pleadings

themselves as to not having a clear understanding of

what's -- what you're moving to have them do that they

haven't already agreed to produce, and I think you've

provided me with some explanation as to that.

explained why, you know, that kind of information is

important and needs to be produced.

word what you have asked for in your document requests or

not, I'm still uncomfortable with saying.

I think I've
Whether it is word for
My suggestion with having more technical people

involved in the discussion -- and, again, this is just -- I

have done it in the past and have seen it to be successful;

I've done it in the past and it hasn't been successful.

just want you to think about it and consider whether that is

a way that -- you know, sometimes technical people

understand what technical people need more than lawyers

hearing from a technical person as to what he or she needs

and then passing that information along and back and forth.
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-
I
Page 35 PageID#
I'm going to defer ruling on this issue today.

I'm going to give you two options, and you all can talk

about which of the two options you want and how we go

forward.

Option 1 is that we have another hearing next

Friday on this issue and that you all report to me by the

end of the day on Wednesday of next week as to where we are,

and then I will decide it next Friday.

other, somebody's going to be happy, and somebody's going to

One way or the
be sad.
The other issue -- and this would give you a

little bit more time -- is that I would hear -- and it's

unrelated but connected.

move the hearing that's set for two weeks from today to the

day before, that is Thursday, at 2:00.

with some conflicts and things like that.

that is a -- it would be specially set at 2:00 and will go

as long as we may need depending on the issues there.

think I'm going to get the opposition to that motion today.

I think I have that calendared right.

come in at the end of next week.

It's probable that I am going to
There's some issues
So -- and I think
And I
So the reply would
So your two options are either decide whether you

want me to hear this next Friday at 10:00 or the following

week on Thursday at 2:00 in conjunction with the other

motion to compel that has already been noticed that I'm
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 36 PageID#
going to be moving to Thursday at 2:00.

problem with that Thursday at 2:00, let me know.

enter the order until Monday.

to that, then maybe let me know by Monday which of the two

options you would rather pursue.

And if there's a
I won't
So if there's some issue as
There are benefits to both, and that's why I'm not

picking one.
I think the earlier, the better, but I'm

giving you the opportunity.

to have technical people involved in the discussions, you've
And, again, if you're inclined

got to schedule it and do it.
So next week may be pushing

it, but, again, we don't want to delay getting a decision so

that we can keep things on track.

Any questions at this point?

MS. GARCIA:

THE COURT:

MS. TARVER WOOD:

No.
Thank you, Your Honor.
Anything else from the government?
Thank you, Your Honor.
appreciate it.

THE COURT:

MR. BIAL:

THE COURT:

I appreciate it.

be adjourned.
Anything else from Google?
No, Your Honor.
Okay.
Well, thank you all very much.
You all have a nice weekend.
Court will

(Proceedings adjourned at 11:53 a.m.)

----------------------------------

We
I certify that the foregoing is a true and accurate
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Page 37 PageID#
transcription of my stenographic notes.

____________________________

Stephanie M. Austin, RPR, CRR
Stephanie Austin, RPR, CRR USDC/EDVA (571) 298-1649
Space
Issues Laws Cases Pro Articles Firms Entities
Issues Laws Cases Pro Articles Firms Entities
 
PlainSite
Sign Up
Need Password Help?