This document is available in three formats: this web page (for browsing content), PDF (comparable to original document formatting), and WordPerfect.

1

1UNITED STATES FEDERAL TRADE COMMISSION

2and

3UNITED STATES DEPARTMENT OF JUSTICE

4

5

6

7SHERMAN ACT SECTION 2 JOINT HEARINGS

8UNDERSTANDING SINGLE-FIRM BEHAVIOR:

9REMEDIES

10THURSDAY, MARCH 29, 2007

11

12

13

14

15HELD AT:

16UNITED STATES FEDERAL TRADE COMMISSION

176TH & PENNSYLVANIA AVENUE, N.W.

18WASHINGTON, D.C.

19

20

21

22

23

24

25

2

1A P P E A R A N C E S

2

3

4

5REMEDY IN THE FACE OF TECHNOLOGICAL CHANGE

6

7

8MODERATORS:

9Douglas Hilleboe, Federal Trade Commission

10Ed Eliasberg, U.S. Department of Justice

11

12

13PANELISTS:

14Michael Cunningham, Red Hat, Inc.

15Renata B. Hesse, Wilson Sonsini

16Marina Lao, Seton Hall Law School

17William H. Page, University of Florida

18Howard A. Shelanski, UC Berkeley

19

20

21

22

23

24

25

3

1P R O C E E D I N G S

2 - - - - -

3MR. HILLEBOE: Good morning, everyone, thank you

4for coming. I'm Doug Hilleboe, attorney with the

5Federal Trade Commission, Office of the General Counsel,

6I'm going to be one of the moderators here today for

7this third session on remedies. My co-moderator is Ed

8Eliasberg, he's an attorney with the U.S. Department of

9Justice, Legal Policy Section of the Antitrust Division.

10Before we start, I need to go over a few

11housekeeping matters. As a courtesy to our speakers,

12please turn off your cell phones, Blackberries and other

13devices that make a noise, and I'll ask the speakers to

14do the same, they actually interfere with the

15microphones and we had a little problem with that.

16Second, the restrooms are located down the hall,

17through the double doors that you came through. Third,

18in the unlikely event that the building alarms go off,

19please proceed calmly and quickly, as instructed. If we

20must leave the building, take the stairway which is to

21the right, on Pennsylvania -- on the Pennsylvania side,

22and after leaving the building, follow the stream of FTC

23people and meet at the sculpture garden, which is across

24from the intersection of Constitution Avenue and 7th

25Street.

4

1Also, we must enforce our rule that there's no

2questions or comments that come from the audience during

3the session. Thank you.

4We're honored today to have assembled a

5distinguished group of panelists that have agreed to

6offer their testimony in connection with this hearing on

7remedies in the face of technology change.

8Howard Shelanski is an associate dean and

9professor of law at the University of California,

10Berkeley, and the director of the Berkeley Center For

11Law and Technology.

12Renata Hesse is a partner at Wilson Sonsini

13Goodrich and Rosati, and formerly was a chief of the

14Networks and Technology Enforcement Section At the

15Antitrust Division.

16Michael Cunningham is general counsel at Red

17Hat, Inc.

18William Page is a Marshall M. Criser eminent

19scholar at the University of Florida's Levin College of

20Law.

21And Marina Lao is a professor of law at Seton

22Hall Law School.

23We plan to hear from each of the speakers for

24about 15 minutes each and then take a ten-minute break

25and then we'll hear from the remaining speakers. We

5

1will then have the speakers comment upon what they've

2heard, and then have a moderated discussion among the

3speakers with Ed and I leading the discussion.

4Before starting, I would just like to state by

5way of introduction that many of the product markets in

6which the United States enjoys a comparative advantage,

7vis-a-vis the rest of the world, are fast-changing

8dynamic markets, including high technology markets.

9Some critics of the antitrust laws have claimed that the

10laws, including Section 2, are not nimble enough for

11effective use in these types of markets. Others

12disagree. We will explore this issue and others in this

13 session.

14Some commentators have suggested that the

15potential for error in antitrust enforcement may be

16 greater in these dynamic markets; however, other

17commentators have suggested that due to network effects

18and other possible factors, these markets may tend

19towards monopolization to a greater agree and therefore

20perhaps deserve particular antitrust scrutiny.

21We are interested to learn what these panelists

22believe about these and other issues, and their

23implications for antitrust enforcement in Section 2

24cases.

25Before beginning with the speakers, my

6

1co-moderator, Ed Eliasberg has some words about the

2hearing.

3MR. ELIASBERG: Thank you, Doug. I very briefly

4on behalf of the Antitrust Division plan to welcome our

5panelists, thank you for coming and we look -- we're

6very much looking forward to hearing what you have to

7say.

8So, with that, Ed, let me turn back to you.

9MR. HILLEBOE: Thank you, Doug. Howard

10Shelanski is the Associate Dean and Professor of Law,

11Boalt Hall, University of California, Berkeley and the

12Director of the Berkeley Center for Law and Technology.

13From 1999 to 2000, he served as chief economist of the

14Federal Trade Commission -- Federal Communications

15Commission, excuse me, and from 1998 to 1999, he served

16as senior economist for the President's Council of

17Economic Advisors At the White House.

18Howard?

19MR. SHELANSKI: Thanks, Doug, and I appreciate

20the promotion. Well, I have a few main points that I

21want to make and the points that I am going to make I

22hope connect to what my co-panelists are going to say.

23We had a call a week ago and I just want to set

24up a few ideas here about the implications of the

25implementation of remedies for monopolization in a

7

1high-tech or technologically dynamic markets. And I

2think my main point, my overall point would be this:

3Remedies are hard in the best of circumstances, and I

4think they become more complicated in technologically

5dynamic settings, but I also think that innovation and

6the presence of ongoing innovation in a market may

7affect remedies in somewhat unpredictable ways, and may

8create opportunities along with the challenges.

9In particular, I think while innovation makes

10structural remedies more difficult, it may in some cases

11make conduct remedies particularly valuable. So, I

12think while innovative markets are cause for agencies

13and courts to be more cautious about remedies, I think

14innovation is not cause for systematic retreat from

15enforcement or from behavioral injunctions.

16So, let me explain a little bit why I think this

17is the case. You'll hear, and I think one often hears

18that structural remedies are preferable to conduct

19remedies or behavioral remedies in monopolization cases.

20But, there are some caveats to this. First I would say

21that structural remedies are not always available.

22Where a firm is so integrated that there are not obvious

23divisions, it's very hard to know how to implement a

24structural remedy. Just as a classic example, the

25District Court's second opinion in the United Shoe

8

1machinery case would be an example.

2The second caveat I would have is that

3structural remedies are not always easier than conduct

4or behavioral remedies, and in fact must often include

5some supporting behavioral remedies, and as an example,

6I would talk about the AT&T vertical divestiture that

7 had to be implemented by open access regulations

8enforced by the FCC and overseen by the District Court.

9And then, finally, I would say as a general

10caveat, the effectiveness of structural remedies in

11Section 2 cases is not assured and there's certainly

12quite a bit of debate of effectiveness historically over

13structural remedies. I'll give you a couple of

14examples. One early quotation, "In administering the

15antitrust acts, a number of great and powerful defenses

16against them have been dissolved. So far as is possible

17to judge the consuming public has not yet greatly

18profited by their dissolution." That's Judge Rose in

19United States against American Can in 1916.

20Okay, now, we haven't had a lot of experience in

21enforcing Section 2 by 1916, so maybe things have

22changed, at least some people disagree. Bob Crandell in

232003 writes, divestitures are "costly exercises in

24futility," but I would point you to the excellent work

25of John Baker and Greg Werden in 2003 providing some

9

1counter arguments. Just a way of saying effective

2remedies structurally offer no guarantee of success.

3Now, I think the structural remedies may

4actually be even harder in technologically dynamic

5markets, and let me offer a couple of reasons. First,

6where a firm or industry is driven by R&D, it may do no

7good to divest a given division or to leave a company in

8two without sending the R&D operations with the divested

9portions of the entity, but R&D operations are often,

10perhaps even likely, to be more integrated and

11 inter-dependent within the firm and not susceptible to

12clean lines of separation.

13The second reason why I think the presence of

14ongoing technological change may make structural

15remedies difficult is that even if divestiture is

16possible, high-tech firms may require more monitoring of

17conduct during after the divestiture, because key assets

18in such divestiture are likely to be intellectual

19property, IP that in some cases may provide joint uses,

20uses across the lines of the new or divested entities,

21disputes are likely to be offered over what items to

22transfer and whether all IP has been disclosed to the

23new entity.

24Moreover, because of the cooperative nature of

25research and development, and in production, in markets

10

1where product life cycles are short, some post

2divestiture monitoring of relationships between newly

3distinct entities may be needed because there may be a

4natural incentive to favor each other as business

5partners, and that was something that came up in the

6wake of the AT&T divestiture, for example.

7The third reason I think that fast technological

8change renders structural remedies more challenging is

9that firm and market structure may be less of an issue,

10in some technologically dynamic markets. To the extent

11that the so-called Schumpeterian School is correct, that

12dynamic markets often display competition that occurs

13sequentially, through periodic waves of creative

14destruction, rather than concurrently, through

15simultaneous production, divestitures may be less

16effective or necessary such markets, although this is

17probably more true for horizontal than for vertical

18divestitures.

19Okay, and my final reason that structural

20remedies are tough in technologically dynamic markets,

21is that where network effects are at issue, structural

22issues might harm consumers by dissipating positive

23network externalities. The fact that it might have been

24better not to have monopoly in the first place does not

25always mean it is better to break up the monopoly later,

11

1and if such divestitures are to preserve network

2externalities, they may have to be accompanied by

3conduct remedies related to interconnection and

4interoperability, doing away with those clean properties

5of structural remedies.

6Okay, let me turn now to conduct remedies, talk

7a little bit about how they might work in high-tech

8markets. As a general matter, we often hear that

9conduct remedies are difficult, but there are some

10caveats here as well. Not all conduct remedies are

11created equal, and as many people have pointed out,

12negative prohibitions, thou shalt not have exclusive

13deals, for example, are probably easier to implement

14than affirmative obligations, thou shall deal with your

15rivals. In part because the negative prohibitions

16entail less involvement of courts or agencies in

17regulating terms of trade.

18The second caveat that I would add is that

19conduct remedies can have beneficial prospective impact,

20even if they cannot roll back illegally accumulated or

21prolonged market power. Some people say, look, conduct

22remedies are closing the barn doors after the cows are

23out, but if there are still some cows inside the barn,

24it's not a bad idea to shut the door.

25Third, even if a conduct remedy is ineffective

12

1or weak in a given case, I think conduct remedies can

2have important deterrent effects on others contemplating

3the illegal behavior, and it's -- in a point that's

4often made, some people say, if you can't be sure that

5your conduct remedy is going to be effective, why bring

6the case? Another reason to bring the case beyond

7deterrence is I think as we get more experience with

8different kinds of conduct, it can become clearer what

9is good and what is bad, and it enables agencies to move

10more quickly in subsequent cases, and perhaps get a

11remedy implemented while the harm is still able to be --

12to be nipped in the bud, so I would not let lack of a

13clearly successful conduct remedy -- I think one needs

14to be clearly articulable at the start of a case, but if

15you can't be sure it will be implemented in time or it

16will be successful in remedying the market power, there

17may be some reasons to go ahead with the case anyway in

18terms of establishing precedent and creating deterrence

19effects.

20And finally, just an observation, I think that

21the effectiveness of conduct remedies are likely to --

22the effectiveness is likely to be tied to the precision

23with which one can define the cause of anticompetitive

24harm, and in some cases, this can be done quite clearly,

25and in those cases, I think behavioral injunctions can

13

1be quite effective.

2So, the overall lesson about conduct remedies, I

3think that it is right to be weary of behavioral

4remedies, particularly those in which the enjoined

5conduct has ambiguous welfare effects, or in which

6courts or agencies will have to become involved that

7were doing terms of trade, but in the right context,

8conduct remedies can work and can send valuable

9deterrent signals.

10 I would just say that inability to articulate a

11structural remedy therefore should not be decisive in

12whether or not to prosecute an argument that is

13sometimes heard.

14Okay. Well, I think that technologically

15dynamic markets create both challenges and opportunities

16for implementing conduct remedies. The first challenge

17is this: If one accepts that remedies may deter

18marginal innovation, and I'll assume for the moment that

19all innovation is good, because private returns are less

20than social returns to innovation. Let's just take that

21as a working assumption, it need not be true in all

22cases, but if one accepts that, and one accepts that

23remedies can marginally deter innovation, then the

24deterrence risk and the costs of such deterrence may be

25much greater in dynamic markets. It needn't be the

14

1case, but I think innovation deterrence becomes a more

2salient issue and a more salient concern in

3technologically dynamic markets.

4The second challenge is that in fast-changing

5markets, it is more likely than it is in more static

6settings that the conduct at issue in the case will be

7moot by the time antitrust liability is established.

8And in such cases, neither conduct nor structural

9remedies are likely to be effective, and perhaps

10something else like disgorgement might be called for if

11such a remedy can be created.

12But there are also opportunities in high

13technology settings, I think, for conduct remedies to be

14particularly effective. In some cases, technological

15dynamics can render conduct remedies effective where

16they would not be in more static markets.

17In some cases, monopoly once obtain may not be

18easily eroded, even if exclusionary or predatory conduct

19that contributed to that monopoly is stopped. Whether

20because of brand recognition, economies of scale, or

21customer switching costs, new entrants will be slow to

22appear or succeed, even when other barriers to entry,

23such as the exclusionary or predatory conduct at issue

24in the case, even when those barriers are eliminated,

25 you might not see competition arising.

15

1But I think where competition is more innovation

2based and where product life cycles are short, an

3injunction against the behavior that led to the

4establishment or maintenance of monopoly power may prove

5very effective, as it is the latter set of barriers,

6rather than any brand or economic advantage, that might

7have kept the incumbent dominant.

8As new waves of innovation come forward, how did

9they stop someone else from being the innovator who came

10in with the new product? Well, through the exclusionary

11or predatory conduct, and branded here and switching

12costs, other things like that, may be very, very

13different in the high-tech environment. So, merely

14eliminating the harmful conduct may open the door for

15new entry and the conduct or remedy, particularly

16negative injunctions, I think, can be very successful

17and very helpful.

18I would like to just raise an additional point

19about the overall question of whether or not the cycles

20of innovation move so quickly and the innovation process

21moves in such different a way from the standard

22competitive process that we should step back generally

23from antitrust enforcement, and this is an argument that

24one hears quite often.

25I think when one looks at the kinds of behavior

16

1that limit innovation, and that stop people -- that stop

2competitors from innovating, it's very unclear to me

3whether or not monopoly has anything particular to

4recognize it, nor is it clear to me that new waves of

5innovation are always going to be sufficiently powerful

6to overcome artificial barriers to entry like

7exclusionary -- exclusionary kinds of behavior like

8exclusive deals when it is a monopolist that has that

9exclusive deal, contractual terms that bar competitors'

10products from ever being used, tying that prevents

11consumers from ever having access to products.

12It's unclear to me no innovation will always be

13so great that it can overcome those barriers, those

14barriers can lead to slower product life cycles, and

15greatly harm consumers, and I think that there's a lot

16of evidence of benefits from antitrust enforcement in

17high-tech areas. And when one looks at the studies that

18have said there are no benefits to Section 2

19enforcement, or in a more nuance way, no benefits to

20Section 2 enforcement in technologically dynamic

21markets, there's a counterfactual, all of these papers

22acknowledge the counterfactual, and we can't tell what

23would have happened absent the antitrust enforcement, we

24can't tell what would have happened in other markets had

25there been antitrust enforcement, and then those

17

1arguments are sort of dismissed, tucked under the

2carpet.

3 I wouldn't dismiss them so easily. And, so, my

4overall argument would be, be very cautious, be very

5case-by-case in the application of Section 2 remedies in

6high-tech markets, I think structural remedies are

7likely to be harder to implement, but there may be good

8opportunities for conduct remedies to be very effective.

9Thanks.

10(Applause.)

11MR. HILLEBOE: Thank you very much, Howard. Our

12next speaker, excuse me, is Renata Hesse, who is a

13partner at Wilson Sonsini Goodrich and Rosati. Prior to

14joining Wilson Sonsini, Renata served as the chief of

15the Networks and Technology Enforcement Section at the

16Antitrust Division and oversaw much of the division's

17technology litigation, including the Oracle/Peoplesoft

18and First Data/Concord matters. In addition, Renata

19worked extensively on both the American Airlines and the

20Microsoft case.

21Renata?

22MS. HESSE: Getting myself around is a little

23harder these days.

24So, Howard covered a lot of ground which I think

25fundamentally I agree with almost everything he said.

18

1In fact, I think I probably agree with everything he

2said, but wanted to pick up where he was leaving off,

3which was I think in talking about the notion that you

4shouldn't back away from Section 2 enforcement in high

5technology markets, and the main reason why I think

6that's true is that despite all of the innovation and

7the fast pace of change in those markets, there is an

8opportunity for durable market power to exist in them,

9and you do want to make sure that you're not overlooking

10that possibility and potentially addressing it.

11So, I wanted to start with just a few basic

12points about Section 2 remedies that I think are

13important, and some of these overlap with some of the

14things that Howard said and I'm sure that will happen as

15we go along down the line of speakers, but the first

16thing that I wanted to talk about is the importance of

17focusing on remedy early, and the main reason -- there

18are several reasons for that, but the biggest reason is

19that it helps you try to figure out what your goal is.

20What's the violation that you're really thinking about,

21what do you think has really happened that's harmful,

22and how can you address it? That isn't to say that if

23you can't come up with a perfect solution to the problem

24that you shouldn't go ahead and try and do something

25 about it.

19

1I think Howard is right that there's a good

2deterrent effect in enforcing the law, even if you're

3not 100 percent sure that the way that you think you can

4fix it will be successful, but I do think it will -- it

5helps you focus your investigation, and here again, I'm

6speaking as if I were a government lawyer, but focus

7your investigation and theories so that you can really

8figure out whether or not you've got a case that is

9worth allocating resources to, and pursuing.

10And I just think it gives you a much better

11sense of the definition of the harm that you're trying

12to alleviate.

13The second point is that I think when you start

14with thinking about remedy, or at least you think about

15remedy relatively early in the process, you can get a

16better sense for whether or not you actually can come up

17with a remedy that is really going to leave the

18marketplace in a better place than it was when you

19started.

20And I would sort of call this the first do no

21harm rule, and it is one of these things which you

22always need to bear in mind, which is that you don't

23always want to make things worse, you don't want to

24deter innovation or take an action in the marketplace

25which stifles productivity, and I think in technology

20

1markets, that's something that you really need to keep

2in mind.

3But if you were stepping back and thinking about

4that early, you can think about whether or not there are

5ways to achieve the goal that you want to achieve

6without having at least a large countervailing harmful

7effect.

8The third point is related to the resource

9allocation point that I made. I think fundamentally

10it's just a basic responsibility that particularly

11government enforcers have to think about how you're

12going to fix the problem, and whether or not the problem

13is subject to a fix that's worth the investment of

14resources in not only the investigation and prosecution

15of the matter, but also the compliance and enforcement

16activities that will happen post judgment, and those

17are, I think, much more complicated when you're talking

18about conduct remedies and structural remedies, but,

19again, Howard correctly notes that when you do a

20structural remedy in these markets, very often there are

21going to be conduct remedies associated with it in any

22event.

23But I think you really do want to have in your

24mind whether or not the consumption of the resource is

25likely to result in some improvement to the competitive

21

1conditions in the marketplace.

2And then there's a fourth point which is that

3sort of the question of if you have a good idea of what

4you think the remedy that you want to put into place is,

5then I think you'll have a better idea of whether or not

6the -- again, the pursuit of the investigation or

7prosecution is worth while, and by that I mean that

8there are some kinds of Section 2 violations that are

9easier to remedy than others.

10So, one example might be you can think of

11exclusive dealing or vertical foreclosure, for example,

12where you have fairly easily identifiable concrete types

13of conduct that you can undo. I think monopoly

14maintenance, to a certain degree, monopoly acquisition

15cases are much harder.

16So, if you're in the situation where you're

17balancing these things out, and you've got a choice

18between two matters that you want to devote your

19resources to and one of them has a reasonably good

20likelihood of being able to be fixed, and the other is a

21little tougher, then you've got to figure out how to

22allocate your resources, then you might want to think

23about going towards the one that actually has a solution

24that you can identify and that you think will be likely

25to result in an improvement in the competitive

22

1conditions.

2And this just goes back to something that I

3think people often think about in the context of -- of

4the -- when you're trying to come up with a remedy, what

5is it that you're trying to achieve, are you looking at

6a monopoly that you believe has been illegally created

7and are you trying to undo that, or are you looking at

8conduct that has maintained a monopoly and are you

9trying to restore the conditions of the competitive

10marketplace to the pre-exclusionary conduct state? And

11depending on which of those two things you're looking

12at, you're going to have a pretty different, I think,

13idea about what's the right way to go about recommending

14the harm.

15The second thing I wanted to talk about was just

16the point that Howard started with, which is structural

17remedies and the general point that generally I think

18structural remedies should be preferred. I think it's

19clearly true that they are not always possible, and

20that's certainly more true in Section 2 cases than in

21other kinds of cases, but I wouldn't advise sort of

22ignoring them as possible ways of recommending harm,

23because I think they do have a number of benefits.

24One of the benefits is that developing a

25functional set of conduct restrictions that are likely

23

1to have a beneficial effect, without having this sort of

2countervailing, potentially negative effect on the

3marketplace is an extremely complicated and resource

4intensive process. It took a really long time to come

5up with the conduct restrictions that we developed in

6the Microsoft case, and I think, you know, you can --

7it's open for debate whether or not those were worked

8well or not well, but it took a long time to figure them

9out, and to just evaluate all the different

10possibilities and try to develop language that's

11concrete enough and understandable enough in a legal

12document for people to actually then be able to

13implement it and understand it and understand what the

14rules of the road are. It's just an inherently

15difficult process to do, and I think that isn't just

16Microsoft, that's any time when you're trying to come up

17with a set of conduct restrictions where you're dealing

18with complex technology.

19It's also hard to judge their success, I think,

20and that's also true in structural remedies, in some

21situations, but it's very hard to know when conduct

22restrictions have succeeded. I think you can know when

23they've failed, but I don't think you can know as easily

24when they've succeeded. How do you measure success with

25conduct restrictions?

24

1I think structural remedies generally eliminate,

2although not entirely, the need for ongoing enforcement

3in compliance activity, which also can be an extremely

4time consuming and resource intensive process. It can

5require, and this is something else I can talk about a

6little bit later, but it can require a lot of assistance

7from people who know more about technology and business

8and licensing and all these things that come up in

9technology markets work, and structural remedies tend to

10need a lot less of that.

11I think structural remedies are generally less

12easy to evade. It's pretty clear what you're supposed

13to do, and you've either done it or you haven't done it.

14You've either divested the plant or the asset or

15whatever it is, or you haven't. You know, there are

16issues associated with those kinds of things, whether or

17not you found an adequate buyer and all of those other

18sorts of issues, but at least there's a very clear line

19about what you are supposed to have done.

20I think they have a potentially greater

21deterrent effect, because they have the capability at

22least of really restructuring a business in a way that

23most businesses don't want to have happen. So, that can

24discourage people from engaging in conduct that folks

25think violates Section 2.

25

1And I think generally, again with some of the

2caveats that Howard laid out, they're more likely to

3work. The lines are clearer, and if you've actually

4proven a violation where you can support imposition of a

5structural remedy, I think the likelihood of that

6structural remedy having an effect is probably higher.

7So, those are some kind of basic points. A few

8points that are more directly connected, just to sort of

9the technology markets, and the first is, you know,

10everybody always talks about technology markets are fast

11changing and innovation changes everything, and as

12Howard said, sometimes people say, maybe you don't need

13to worry about them because they're just going to be

14self correcting. I tend not to agree with that latter

15viewpoint, for the reason that I started with, which is

16that it's clear that there's a possibility for the

17existence of durable market power in these markets, so I

18think just leaving them alone and hoping that the

19exclusionary conduct somehow magically stops and things

20correct themselves is not likely to lead to a lot of

21success.

22I do think that the fact that they can sometimes

23be slow and that the antitrust enforcement process can

24sometimes be slow is a down side in these markets, a

25greater down side in these markets than in other

26

1markets, because sometimes you feel like you get to the

2end and you're addressing the problem when it's actually

3a little bit too late.

4As a consequence, I think you need, when you're

5thinking about conduct remedies in technology markets,

6to be a little bit more flexible about how you think

7about them. And to address categories or types of

8conduct relating to types or categories of products or

9services as opposed to saying, well, this -- you did

10this particular thing with this particular kind of

11product, and you should do that -- you shouldn't do that

12anymore. This is the negative prohibition point versus

13an affirmative obligation point.

14If the conduct remedy is too narrowly focused,

15it runs the risk of being ineffective, and I think in

16most cases is likely to be ineffective, particularly,

17again, if you're talking about undoing some sort of harm

18that has occurred.

19You know, Microsoft is a simple example of this,

20the consent decree doesn't just talk about browsers,

21which was the primary focus of the case, but it talks

22about other products which were potential platform

23threats and has some construct restrictions in it that

24are designed to try to go after those particular -- or

25not go after them, but to try and make sure that the

27

1conduct relating to those other kind of potential

2platform threats were restrained.

3There's a possibility in technology markets that

4they should be of shorter duration. Again, Microsoft is

5another example, it was a five-year consent decree, it's

6now been extended in some pieces for longer than that,

7but I think there's a reasonable basis for at least

8looking at the question of whether or not you really

9need something to last ten, 20, some decrees in the past

10have lasted for hundreds of years, some of them very

11perpetual, and whether or not that makes sense

12particularly in the context of technology markets is I

13think something that people -- it's worth looking at.

14I also think if you're going to think about

15decrees of shorter durations, or remedies of shorter

16durations, that including some mechanism for revisiting

17that question before the term of the decree expires is a

18good idea. I think it's just these markets are

19inherently unpredictable, and given the complication of

20structuring conduct provisions in them, that giving

21yourself an opportunity to take a second look and having

22a standard for how you would be able to convince a court

23that you need to extend a decree in these kinds of

24markets is something that should be given some

25consideration.

28

1And the final point on this area is that I think

2conduct remedies in Section 2, Section 2 remedies in

3technology markets may need to be more forward looking,

4and this is a little slightly basically the same thing

5with a slightly different pitch on it, but you do have

6to think about what it is that you can predict about the

7marketplace and changes in the marketplace going forward

8and whether or not what you've devised in the context of

9the conduct remedy is adequate to address the changing

10technology in the marketplace.

11The last piece about technology markets that I

12think makes them different is that they're hard, and

13it's hard to understand them, and they're particularly

14hard for people who are not educated in technology.

15And, so, compliance monitoring enforcement can be a

16difficult thing to do.

17As a consequence, I think if you're looking at

18these markets and you're looking at behavioral

19restrictions, particularly ones that relate to licensing

20of intellectual property or access to technology or

21just, you know, you're requiring a company to stop doing

22a particular activity with a particular type of

23technology, that you really need to anticipate getting

24some technical help, and when I think of technical help

25in this context, I don't think just of software

29

1engineers or hardware engineers, but I also think of

2licensing expertise, business expertise, you know,

3trying to figure out whether a royalty ran is a

4difficult problem, and it's not a problem that most

5antitrust lawyers deal with on a day-to-day basis.

6And having the ability to have access to people

7who actually do that kind of work for a living, who know

8what particular types of technologies, what kinds of

9royalties particular types of technologies command is, I

10think, critical to the ability to actually do an

11adequate job of monitoring and enforcing compliance.

12Again, I started with sort of a more broad

13definition of technical assistance, but a narrow

14definition of technical assistance, which is just

15actually having somebody who knows how software code is

16written, and what to look for and how to evaluate

17whether or not something has been done in the code is

18very important. I think one of the really unusual and

19innovative things that was in the Microsoft decree was

20the technical committee provision, which allowed the

21Department of Justice and the states to have access to

22basically a full-time group of technical consultants who

23were hired to work for those people and the cost of

24which was borne and continues to be borne by Microsoft.

25I think it was an unusual idea, but it really

30

1has become, I think, a key component to the United

2States enforcement and monitoring, compliance monitoring

3efforts of the Microsoft decree, and it was essentially

4copied by the European Commission in the work that

5they're doing in Microsoft as well.

6And it had not been done before. There were

7lots of times where in complicated markets people had

8used monitoring trustees, I shouldn't say there were

9lots of times, but there were examples of monitoring

10trustees being used, usually they were in things like

11prison condition litigation, where there was some pretty

12complicated oversight that was needed, but hiring

13technical experts to help out was an innovative thing to

14do and I think has proven to be a pretty successful

15component of the Microsoft decree.

16Now, you also may need technical assistance when

17you're trying to figure out whether or not somebody has

18violated the decree and you actually want to go after

19them for contempt. I think the Microsoft model doesn't

20quite fit so well in that context, because it's a little

21hard to see how you can justify the party who you're

22going to be pursuing in contempt actually paying for the

23expert that you're going to be using, to go after them

24in contempt, but it's something that people -- you want

25to think about, and at least have the resources and

31

1capability to get that kind of help on board.

2So, I have probably 30 seconds at this point

3left. The last thing I would say is that licensing

4remedies are incredibly common in technology markets.

5They can be useful, and I think can work well, but I

6think they work particularly well in the context where

7you know or have a very good idea of what the

8intellectual property is or what the asset is that needs

9to be licensed, are there particular patents who needs

10them, and again, if you go back at the very beginning,

11to those are things that you can think about early on

12and figure out and they'll help you determine whether or

13not a licensing remedy is likely to be successful.

14And of course when you're doing that, you need

15to think about the policy issues that are associated

16with compulsory licensing of intellectual property,

17which is a hot topic these days.

18(Applause.)

19MR. HILLEBOE: Thank you so much, Renata, for

20those comments.

21Michael Cunningham is general counsel at Red

22Hat, Inc. Prior to joining Red Hat, he served as

23associate general counsel at IBM, where he had legal

24advisory responsibilities for the Business Consulting

25Services Division for Europe, the Middle East and

32

1Africa. He was also a partner and associate general

2counsel at PricewaterhouseCoopers.

3 Michael?

4MR. CUNNINGHAM: Thank you, and good morning.

5I'm pleased to have the opportunity to participate in

6this important consideration of Section 2 remedies, to

7do so before distinguished representatives of the

8government, as well as with this particularly

9knowledgeable panel.

10I'm the general counsel of Red Hat. I'm going

11to make a little disclaimer, I'm a technology lawyer,

12I'm not principally an antitrust lawyer. I hope that I

13can offer some comments, however, as an executive of a

14technology company that are relevant to these inquiries.

15With your indulgence, I would like to describe a

16bit about our business that I think is relevant

17innovation, given the debate about antitrust remedies

18stifling innovation, I think it's particularly

19appropriate this morning.

20The software solutions that Red Hat offers, and

21for which we provide services, are developed by very

22broad horizontal communities that are without

23geographic, organizational or political boundaries. The

24community of innovators that unleash the value of open

25source are not contained within Red Hat. Some of its

33

1contributors are, but it's not.

2The contributors include the customers and

3vendors of hardware and software. It includes

4academics, it includes many, many motivated individuals

5that we call hackers, it includes persons from every

6continent and from multiple political subdivisions.

7The development environment is also not

8controlled by any single individual company or political

9entity, it is instead a free, meritocratic marketplace

10of ideas. Individuals take these ideas and they place

11these ideas with their individual name and reputation

12into the marketplace in a particular software

13development project to which their idea is relevant.

14There are literally thousands of these projects

15out there. In one of our offerings, Red Hat Enterprise

16Linux, hundreds of projects are represented. These

17ideas are then reviewed by that development community,

18for that project, and only those ideas that can handle

19the open scrutiny of this open source community are then

20adopted.

21In this way, the best ideas and the bets bits of

22ideas bubble up. Moreover, if there happen to be a

23serendipitous discovery that is made in one of those

24projects that's relevant to another project or might be

25an entirely new approach, the contributor or any other

34

1person is free to contribute it to that project or

2indeed to go out and start a new project to take the

3technology in a new direction.

4This model has produced and continues to produce

5copious innovation. It also accelerates and multiplies

6innovation, I would argue, by providing tools of

7innovation, such as information ideas to a broader and

8more diverse community than development within any one

9firm is possible could provide.

10The open exchange of information and ideas is an

11innovation force multiplier. For example, sophisticated

12business and other users of software frequently take the

13modular pieces of well crafted software that's developed

14in the open source community, cobble bits and pieces of

15it together, modify it, append to it and create

16solutions for problems that heretofore were not solved,

17or new problems that arise in their business.

18Similarly, the creative juices of the lone

19teenager in North Dakota in some remote location can

20contribute to that process, so can a Cal Tech physicist

21who is wondering why there hasn't been a software

22development that would help in his or her research. And

23so are many, many others unleashed in the creative

24process through this open development and collaboration

25model.

35

1The modular and open nature of open source

2software has fueled much innovation, but it is by no

3means limited to software. It is not a software-only

4phenomena. No, I would submit to you that the relative

5ubiquity and low cost of the Internet, and collaboration

6tools like email and dedicated web sites portends for

7joint collaboration that is unleashing all sorts of

8innovation across the world.

9If you've read the best selling book by Tom

10Friedman, The World is Flat, you will get a very good

11sense of some of these trends, I think. I would also be

12happy to comment on some other areas where that

13innovation is being unleashed in the questioning, if

14that's helpful.

15With that bit of an introduction, maybe I should

16turn my attention now more directly to remedies. First,

17I believe that in the software space at least, the

18relevance of the antitrust law hangs on the issue of

19remedies. I can think of no way as a practitioner and

20an executive in a company in the industry to more

21starkly illustrate that point than to disclose my actual

22advice to my client in pursuing whether to participate

23in or pursue any monopoly-related case, whether that be

24in a government-related case or in private litigation.

25I would tell my client, it's too expensive for

36

1you to fully embrace and do that. You cannot do it.

2You don't have enough money to pursue it, it's certainly

3over $10 million, it will be a long time, and it is

4likely, I would submit to you, at least this would be my

5advice, it is likely and substantially likely that the

6remedy that will result will be of limited utility. So,

7therefore, those sorts of expenditures would not be

8justified.

9And guess what? Those that the government

10representatives seek to regulate know this, and they

11know it well. By way of illustration, a high-ranking

12representative, indeed a very high-ranking

13representative of a party found to have market power by

14multiple international competitive authorities has

15aggressively and indeed smugly advised Red Hat that

16there is no competition authority in the world that this

17firm will not outspend, outlast, and seek to thwart.

18In short, the system seems broken in terms of

19speed, cost, and effectiveness of remedies, at least

20from my little corner of the world. You know, why is

21this the case? Well, as others have said, technological

22change is very rapid and litigation is not. The rate of

23change at least in information technology is in very

24short cycles, three to five years, maybe six to eight

25years, certainly not longer than that in many, many

37

1areas of information technology.

2Remedies that only address a particular market

3complained of, and established at great expense, will

4often be too late to provide meaningful relief. A

5remedy focused on future conduct would address some of

6those limitations and in many instances I think is

7necessary.

8 I also am intrigued by the idea of smaller

9simpler cases with speedier trial times that would focus

10on future contact to make the law more relevant.

11Clearly cost and delay undermine the perceived and

12actual effectiveness of the antitrust laws in our

13competitive zone.

14In that way, some of Professor's Lao's writing

15on the role of the intent in finding liability seem a

16fruitful avenue for further inquiry to me.

17Second, technology can be manipulated. The

18speed with which information technology moves and can be

19molded provides real opportunity for conscious

20manipulation by the monopolist away from the market

21complained of. The government enforcement actions

22against Microsoft are an example of the timing

23challenges, I'm thinking now about the European Union,

24even the most aggressive threats by the EC are mired in

25delay, seemingly extended without limit.

38

1According to the most recent statistics we've

2seen, Microsoft continues to gain in the operating

3system worker group server market, meanwhile the market

4continues its very rapid evolution, probably reducing

5the relevance of any remedy that may eventually be

6enforced and/or issued.

7I guess I should also point out that private

8enforcement actions have not solved the problem either,

9this won't be a surprise from my earlier comment. The

10antitrust law, like the Ritz Carlton, is open to the

11rich and poor alike. The most entrepreneurial and the

12most innovative firms, the small fledgling ones are

13without means to mount private antitrust cases.

14Let me turn my attention for a few moments to

15innovation. Protecting competition does not mean

16stifling innovation, I don't believe. While there is an

17inevitable tension between the intellectual property law

18and the antitrust law, competition law cannot achieve

19its purpose if regulators and courts are preoccupied

20with a concern that remedies affecting some intellectual

21property rights will necessarily stifle innovation.

22That focus on IP, that is intellectual property,

23a legal concept, is misguided. The focus should be on

24true innovation, not patents and copyrights, public

25grants of a monopoly.

39

1Why is that the case? Well, first I think

2equating innovation to the accumulation of intellectual

3property is suspect, at least in the software world.

4The software patent approach in the United States is

5being broadly questioned, and that's the case for at

6least two or three different reasons.

7First of all, the software industry in

8particular survived for almost 20 years with very

9limited forms of software patents, not the broad range

10that we now see following State Street and other court

11decisions.

12Second, I would submit to you the relationship

13of software patents to innovation is suspect. I

14regularly review the academic literature in this area

15and I am aware of no convincing argument that software

16patents have unleashed -- and no empirical study --

17that they have unleashed and spurred additional

18innovation.

19Third, the news is regularly filled with stories

20of highly suspect software patents, patents that are not

21new and innovative, ones that are anticipated by prior

22art and ones that common sense tell us lack sufficient

23novelty to warrant 20 years of protection.

24Of course that shouldn't be surprising, there

25are well publicized challenges in the Patent & Trademark

40

1Office, there's no effective and searchable database on

2prior art for software. There's also serious challenges

3in retracting and retaining the kinds of experts that

4Renata talked about to actually evaluate what is seeking

5to be patented.

6I say that just to suggest that the innovation

7reflected in software patents is questionable at times.

8Therefore, giving, you know, complete deference to

9intellectual property in that context seems misguided.

10Even more important to this debate, as my

11opening remarks sought to illustrate, there are broad

12communities of collaboration that are massively

13innovative. Please note that their style of

14collaboration is not readily or naturally susceptible to

15patent protection, given the open and collaborative

16nature of their exchanges.

17Thus, innovation of the firm is not the only or

18even the most effective form of innovation to be

19considered or protected when facing the market

20disruptive effects of monopolists. Powerful new

21innovation paradigms are upon us now and they're growing

22and they need to be considered and measured in balance.

23But even if we were to assume that the firm is

24the epicenter of innovation, the smallest and perhaps

25most innovative are without the means to challenge the

41

1innovation of the monopolist that is purported to be

2reflected in intellectual property. The combination of

3suspect software patent quality and the disparity of the

4cost to acquire a patent versus the cost to defend

5against it skew IP protection in favor of larger

6enterprises with market power.

7Cost of acquiring a patent, let's say, is

8$25,000 to $35,000. It absolutely pales in contrast to

9the cost of a proper infringement defense. That is

10variously $3 to $5 to $7 million, and by all accounts is

11growing at present.

12Moreover, the monopolist can disrupt the

13business of smaller competitors merely by suggesting to

14consumers that its IP is infringed, without any proof

15whatsoever. If you consider Steven Bommer's recent

16statements that the users of Linux have an undisclosed

17off balance sheet liability to Microsoft, which were

18offered without any substantiation whatsoever. And the

19SCO litigation that is ongoing I think offers some

20interesting and vicarious variance on the same theme,

21which I would also be happy to comment on in the

22question and answer period.

23Keeping on the intellectual property theme, an

24effective remedy needs to prevent the extension of

25market power. A company who has acquired market power

42

1through anticompetitive conduct shall not be permitted

2to be able to hide behind intellectual property

3protection to reinforce and extend its market power. I

4think there is an interesting lesson in history on this

5that deals with data formats.

6In particular, I would like to contrast how

7Microsoft came to compete in word processing, versus how

8it now competes. The background is as follows:

9Software products manipulate and ultimately store

10customer data after that manipulation. To the extent

11this data is then placed into storage formats, that are

12claimed as either proprietary or protected by

13intellectual property of the software vendor, then the

14ability of a competing product to make effective use of

15the stored customer data and break into and compete in

16that market, which is likely reinforced by very strong

17network effects, can be precluded.

18Take, for example, Microsoft's word processor

19competition against the then-important market position

20of the WordPerfect product in the 1980s. Because the

21data format's inability to represent the data with

22substantial fidelity was possible, Microsoft could

23compete at the enterprise level by saying, give me a try

24in parallel with WordPerfect. If I do better, then

25incur the cost of switching out your old technology and

43

1taking on our technology.

2In contrast today, I would submit to you the

3formats of Microsoft alphus data have been and are

4increasingly being obscured by Microsoft and cannot be

5presented, that is the data cannot be presented with

6true fidelity by any competitor, like OpenOffice, which

7thereby extends the time of their dominant position and

8permits extension of power into adjacent markets.

9It is the case that Red Hat cannot effectively

10compete with open source personal productivity

11applications, like word processors and other things, at

12the enterprise level against Microsoft, it can't get its

13foot in the door. If a client wants to give someone a

14try and you can't render their existing data in a

15meaningful fashion, that prevents anyone from entering

16into that market, I would submit to you, or doing so

17easily, anyway.

18Microsoft controls, I would submit to you, a

19facility of competition through the extension of IP and

20proprietary formats that is needed to meaningfully

21render and manipulate customer data. I have no doubt

22that's why you're seeing states like Massachusetts

23aggressively consider the open document format, a truly

24open standard in format in its procurement processes.

25The mono type litigation of Red Hat is another

44

1example that illustrates that that I would be happy to

2comment on later.

3In summary, I guess I would say that innovation

4does not equate to intellectual property, and therefore

5greater focus on preserving and promoting true

6innovation in the marketplace is warranted. Further,

7there are numerous ways in which the use and assertion

8of intellectual property rights can be a pretext that

9chills competition and extends monopoly power.

10Thank you.

11(Applause.)

12MR. HILLEBOE: Thank you very much, Michael, for

13that, and I think we will take about a ten-minute break

14now.

15(Whereupon, there was a recess in the

16proceedings.)

17MR. HILLEBOE: Thank you, everyone. William

18Page is a Marshall M. Criser eminent scholar at the

19University of Florida Levin College of Law and he is

20also an alumnus of the Antitrust Division, where he

21served as a trial attorney in the 1970s.

22Bill?

23MR. PAGE: Thank you. Rather than speak in

24generalities about Section 2 remedies in high-tech

25markets, I want to zero in on one highly technical and

45

1seemingly obscure provision in the final judgments in

2the government's Microsoft case that has turned out to

3be the most difficult and the most problematic in its

4enforcement.

5The provision requires Microsoft to license to

6software developers communications protocols that

7Microsoft uses in its Windows Client operating systems

8to interoperate with Microsoft server operating systems,

9either in corporate networks or over the Internet.

10Communications protocols are the rules for transmitting

11information between different devices.

12So, in a computer network, the protocols allow a

13user of a client computer, for example, to store

14information on a network drive or send an email or

15display a web page, among many other things.

16This sort of interoperation is relatively easy

17when the client computer's operating system and the

18server operating system share a common base in code.

19It's like they speak the same language, so they can

20interoperate easily.

21Where the client computer, usually a Windows

22client, has to interoperate with servers from other

23vendors, then the problem with interoperability becomes

24much more difficult, but there are ways of solving them.

25There are recognized ways of solving them. Some involve

46

1installing a client on Windows that would allow

2interoperation with the non-Windows server and

3applications running on it.

4There are also standard protocols that are

5available and supported in Windows. This provision

6requires another way of assuring interoperation, that is

7requires Microsoft to disclose its proprietary

8protocols, to license them to software developers so

9that they can interoperate. The near-term goal would be

10for them to be able to write programs that will

11interoperate as well with Windows clients as

12applications running on Microsoft servers.

13The long-term goal is to allow -- is to preserve

14in this network context the so-called middleware threat

15that was the focus of the government case. The

16middleware applications running on servers, the concern

17is, may eventually evolve into platforms that could

18rival the Windows desktop and thereby erode the

19application's barrier to entry. Essentially the theory

20of the government case.

21In spite of its apparent obscurity, this

22provision has been given an unusual amount of importance

23by the District Court enforcing the Microsoft judgment.

24She's referred to it as the most forward looking

25provision in the final judgments and as necessary to

47

1assure that the other provisions don't become

2prematurely obsolete. It's now being implemented by the

3two sets of plaintiffs in the Microsoft litigation, the

4Antitrust Division and the nine settling states, and

5also by the group of non-settling plaintiffs who were

6awarded essentially the same relief, but there are

7different enforcement mechanisms.

8There's the technical committee that Renata

9referred to in the Antitrust Divisions's consent decree

10and there's a technical consultant to the non-settling

11states under their decree, but they're coordinating

12their enforcement efforts. Both of these judgments went

13into effect in 2002.

14And the plaintiffs in both cases and Microsoft

15has been filing status reports every two months about

16the enforcement of both of the judgments, and I have

17studied these reports with the help of a research

18assistant, who was also a software developer and a

19management consultant, and so he has been sort of my

20technical consultant. He provided all of the technical

21expertise in this study, because I certainly claim none.

22 The enforcement of this provision, this one

23provision in these judgments has dominated these

24reports, particularly in recent years. It by far

25occupies most of the reports and certainly most of the

48

1time of the technical committee. And I'll argue that

2this provision has not accomplished its purpose, and

3that we can draw some lessons from that experience.

4So, I want to first describe what I take to be

5the principles of Section 2 remedies, I'll then suggest

6that most of the provisions in the Microsoft judgments

7adhere to these principles, but that this provision, the

8protocol licensing provision, departs from the

9principles and that is part of the reason why it has not

10been successful.

11I'll describe briefly how it has been

12implemented and then in the end I'll try to draw some

13lessons. And incidentally, this is a very brief summary

14of a much longer article which I hope to post on SSRN

15shortly.

16The goals of Section 2 remedies should be to

17restore competitive conditions that would have existed

18but for the illegal conduct. They should not be to try

19to restore or to create some sort of ideal competitive

20condition or to supervise market outcomes. I take the

21primary antitrust remedy to be deterrence, through fines

22and covered damages. If deterrence can be effective, if

23an optimal penalty can be imposed, that's always going

24to be preferable to having an administrative structure

25imposing remedies. It's simply the direct costs of

49

1imposing those remedies will be -- will impose a greater

2cost than effective deterrence.

3Assuming that some sort of injunctive relief is

4required, I would suggest that injunctions should be

5limited to preventing reoccurrence of proven

6anticompetitive behavior. The Sherman Act, unlike

7sector-specific regulation, I believe reflects the

8assumption that if specific impediments to competition

9are removed, then private contracting within the market

10will lead to the efficient outcome. And if that would

11not be the case, then that would argue that the market

12should be regulated.

13Beyond that, I would suggest that injunctions

14are problematic. First, divestiture, at least in the

15case of a unitary company, should be a last resort,

16primarily appropriate to dissolve recent combinations.

17Regulatory decrees also, as many have observed, should

18be avoided. As the Supreme Court said in Trinko, they

19require antitrust courts to act as central planners,

20identify improper price policy and other terms of

21dealing in roles for which they are well suited.

22Most of the Microsoft final judgment provisions

23reflect these principles. They do not require any form

24of divestiture, and most provisions respond more or less

25directly to the liability holdings in the case that were

50

1affirmed by the D.C. Circuit in 2001, prohibiting

2retaliation against computer manufacturers for promoting

3rival software, requiring uniform licensing terms,

4giving computer manufacturers the flexibility to remove

5the visible means of access to Microsoft middleware

6products and so forth.

7The protocol licensing provision does not

8respond directly to any illegal conduct. Server-based

9applications were mentioned in the findings of fact,

10only to exclude them from the market.

11Interoperability in networks was not an issue in

12the case, and in fact developing and refusing to license

13incompatible proprietary software was not held illegal,

14in fact, it was specifically held to be legal, if

15nothing more than that were shown.

16So, where did this come from? The idea for this

17provision actually arose, according to Ken Alletta's

18book on the Microsoft litigation, after the findings of

19fact had been issued. In other words, after the record

20was closed in the case. The feeling was that Microsoft

21essentially was not going to continue the conduct that

22was actually the subject of the litigation, the browser

23wars were over, Microsoft had already stopped the

24discriminatory pricing, it had gotten rid of the

25exclusive terms in its contracts, so we needed to be

51

1more forward looking and what was forward was this

2network environment.

3The fear was that in this -- you've got to, you

4know, as the computer market moved toward networks, both

5local corporate networks and the Internet, it was

6necessary to assure that Microsoft would not

7discriminate in allowing rivals to interoperate with the

8dominant Windows client.

9And, so, various proposals for various

10interfaces by Microsoft were made. After the original

11judgment was reversed, of course the Antitrust Division

12reached an agreement with Microsoft on the consent

13decree and it included a version of this. The protocol

14licensing provision, which essentially we now have, in

15both that consent decree and in this -- the states'

16judgment.

17Judge Kollar-Kotelly approved this provision,

18even though she recognized that the government was not

19strictly entitled to it, because it was not responsive

20to proven illegality, and she also recognized that there

21were these other ways in networks of achieving

22interoperability besides requiring Microsoft to license

23its proprietary protocols.

24Nevertheless, she found that -- and here's the

25key language, it's closely connected to the theory of

52

1liability in this case, and furthers efforts to prevent

2future monopolization.

3So, under this program, Microsoft has developed

4the Microsoft communications protocol program, which is

5an extension of its Microsoft developers network, and

6under this program, it offers a license to these

7protocols, and technical documentation. In the initial

8response in August 2002, actually before the consent

9decree was approved, but nine months after it was

10originally agreed to by the parties, Microsoft produced

115,000 pages of technical information, documentation, on

12the protocols, which it reported with a product of the

13work of five technical writers working essentially

14full-time for nine months.

15By July 2003, however, eight months after the

16entry of the final judgments, only four developers had

17licensed these protocols. And Judge Kollar-Kotelly told

18the parties in a status conference, this is reported in

19the report, that she was very, very concerned that

20nobody was taking these licenses. And both Microsoft

21and the government responded to this by various efforts

22to promote them. Microsoft took out ads, they

23evangelized these protocols, but with very little

24success. And finally the government conducted a survey

25of developers asking them why aren't you licensing this

53

1material, and they gave a list of reasons, some of which

<