Full text of proposed final judgment in United States v. Microsoft
IN THE UNITED STATES DISTRICT COURT
Plaintiff United States of America ("United States") and Defendant Microsoft Corporation ("Microsoft"), by and through their respective attorneys, having agreed to the entry of this Stipulation, it is hereby stipulated and agreed that:
1. A Final Judgment in the form attached hereto may be filed and entered by the Court, upon the motion of any party or upon the Court?s own motion, at any time after compliance with the requirements of the Antitrust Procedures and Penalties Act, 15 U.S.C. ? 16, and without further notice to any party or other proceedings, provided that the United States has not withdrawn its consent, which it may do at any time before the entry of the proposed Final Judgment by serving notice thereof on Microsoft and by filing that notice with the Court.
2. Unless otherwise provided in the proposed Final Judgment, Microsoft shall begin complying with the proposed Final Judgment as if it was in full force and effect starting 45 days after the date the proposed Final Judgment is submitted to the Court. Subject to the foregoing, Microsoft agrees to be bound by the provisions of the proposed Final Judgment pending its entry by the Court. If the United States withdraws its consent, or if (a) the proposed Final Judgment is not entered pursuant to the terms of the Stipulation, (b) the time has expired for all appeals of any Court ruling declining to enter the proposed Final Judgment, and (c) the Court has not otherwise ordered continued compliance with the terms and provisions of the proposed Final Judgment, then the parties shall be released from all further obligations under this Stipulation, and the making of this Stipulation shall be without prejudice to any party in this or any other proceeding.
3. Pursuant to 15 U.S.C. ? 16(g), within ten (10) days of the submission of the proposed Final Judgment, Microsoft will file with the Court a description of any and all written or oral communications by or on behalf of Microsoft, or other person, with any officer or employee of the United States concerning or relevant to the proposed Final Judgment, except that any such communications made by counsel of record alone with the Attorney General or the employees of the United States Department of Justice alone shall be excluded from this requirement.
4. Pursuant to 15 U.S.C. ? 16(b), on or before November 16, 2001, the United States will file with the Court a Competitive Impact Statement explaining the terms of the proposed Final Judgment. The United States will publish the proposed Final Judgment and Competitive Impact Statement in the Federal Register.
5. The United States will publish a notice informing the public of the proposed Final Judgment and public comment period in the Washington Post and the San Jose Mercury News, for seven days over a period of two weeks commencing no later than November 15, 2001.
6. Members of the public may submit written comments about the proposed Final Judgment to a designated official of the Antitrust Division of the United States Department of Justice for a period of 60 days after publication of the proposed Final Judgment and Competitive Impact Statement in the Federal Register.
7. Within 30 days after the close of the 60-day public comment period, the United States will file with the Court and publish in the Federal Register any comments it receives and its response to those comments.
8. Once the aforementioned procedures have been compiled with, the United States will file with the Court a certification of compliance with the requirements of 15 U.S.C. ? 16, and a Motion for Entry of the Proposed Final Judgment, unless it withdraws its consent to entry of the proposed Final Judgment pursuant to paragraph 2, above. At any time thereafter, and at the conclusion of any further proceedings ordered by the court pursuant to 15 U.S.C. ? 16(f), the Court may then enter the proposed Final Judgment, provided that the Court determines that entry of the proposed Final Judgment will serve the public interest.
DATED this 2nd day of November, 2001
FOR PLAINTIFF THE UNITED STATES OF AMERICA:
CHARLES A. JAMES (Bar No. 292201)
FOR DEFENDANT MICROSOFT CORPORATION:
JOHN L. WARDEN (Bar No. 222083)
PROPOSED FINAL JUDGMENT
WHEREAS, plaintiff United States of America ("United States") and defendant Microsoft Corporation ("Microsoft"), by their respective attorneys, have consented to the entry of this Final Judgment;
AND WHEREAS, this Final Judgment does not constitute any admission by any party regarding any issue of fact or law;
AND WHEREAS, Microsoft agrees to be bound by the provisions of this Final Judgment pending its approval by the Court;
NOW THEREFORE, upon remand from the United States Court of Appeals for the District of Columbia Circuit, and upon the consent of the aforementioned parties, it is hereby ORDERED, ADJUDGED, AND DECREED:
This Court has jurisdiction of the subject matter of this action and of the person of Microsoft.
This Final Judgment applies to Microsoft and to each of its officers, directors, agents, employees, subsidiaries, successors and assigns; and to all other persons in active concert or participation with any of them who shall have received actual notice of this Final Judgment by personal service or otherwise.
III. Prohibited Conduct
A. Microsoft shall not retaliate against an OEM by altering Microsoft?s commercial relations with that OEM, or by withholding newly introduced forms of non-monetary Consideration (including but not limited to new versions of existing forms of non-monetary Consideration) from that OEM, because it is known to Microsoft that the OEM is or is contemplating:
1. developing, distributing, promoting, using, selling, or licensing any software that competes with Microsoft Platform Software or any product or service that distributes or promotes any Non-Microsoft Middleware;
2. shipping a Personal Computer that (a) includes both a Windows Operating System Product and a non-Microsoft Operating System, or (b) will boot with more than one Operating System; or
3. exercising any of the options or alternatives provided for under this Final Judgment.
Nothing in this provision shall prohibit Microsoft from enforcing any provision of any license with any OEM or any intellectual property right that is not inconsistent with this Final Judgment. Microsoft shall not terminate a Covered OEM?s license for a Windows Operating System Product without having first given the Covered OEM written notice of the reasons for the proposed termination and not less than thirty days? opportunity to cure. Notwithstanding the foregoing, Microsoft shall have no obligation to provide such a termination notice and opportunity to cure to any Covered OEM that has received two or more such notices during the term of its Windows Operating System Product license.
Nothing in this provision shall prohibit Microsoft from providing Consideration to any OEM with respect to any Microsoft product or service where that Consideration is commensurate with the absolute level or amount of that OEM?s development, distribution, promotion, or licensing of that Microsoft product or service.
B. Microsoft?s provision of Windows Operating System Products to Covered OEMs shall be pursuant to uniform license agreements with uniform terms and conditions. Without limiting the foregoing, Microsoft shall charge each Covered OEM the applicable royalty for Windows Operating System Products as set forth on a schedule, to be established by Microsoft and published on a web site accessible to the United States and all Covered OEMs, that provides for uniform royalties for Windows Operating System Products, except that:
1. the schedule may specify different royalties for different language versions;
2. the schedule may specify reasonable volume discounts based upon the actual volume of licenses of any Windows Operating System Product or any group of such products; and
3. the schedule may include market development allowances, programs, or other discounts in connection with Windows Operating System Products, provided that:
a. such discounts are offered and available uniformly to all Covered OEMs, except that Microsoft may establish one uniform discount schedule for the ten largest Covered OEMs and a second uniform discount schedule for the eleventh through twentieth largest Covered OEMs, where the size of the OEM is measured by volume of licenses;
b. such discounts are based on objective, verifiable criteria that shall be applied and enforced on a uniform basis for all Covered OEMs; and
c. such discounts or their award shall not be based on or impose any criterion or requirement that is otherwise inconsistent with any portion of this Final Judgment.
C. Microsoft shall not restrict by agreement any OEM licensee from exercising any of the following options or alternatives:
D. Starting at the earlier of the release of Service Pack 1 for Windows XP or 12 months after the submission of this Final Judgment to the Court, Microsoft shall disclose to ISVs, IHVs, IAPs, ICPs, and OEMs, for the sole purpose of interoperating with a Windows Operating System Product, via the Microsoft Developer Network ("MSDN") or similar mechanisms, the APIs and related Documentation that are used by Microsoft Middleware to interoperate with a Windows Operating System Product. In the case of a new major version of Microsoft Middleware, the disclosures required by this Section III.D shall occur no later than the last major beta test release of that Microsoft Middleware. In the case of a new version of a Windows Operating System Product, the obligations imposed by this Section III.D shall occur in a Timely Manner.
E. Starting nine months after the submission of this proposed Final Judgment to the Court, Microsoft shall make available for use by third parties, for the sole purpose of interoperating with a Windows Operating System Product, on reasonable and non-discriminatory terms (consistent with Section III.I), any Communications Protocol that is, on or after the date this Final Judgment is submitted to the Court, (i) implemented in a Windows Operating System Product installed on a client computer, and (ii) used to interoperate natively (i.e., without the addition of software code to the client or server operating system products) with Windows 2000 Server or products marketed as its successors installed on a server computer.
F. 1. Microsoft shall not retaliate against any ISV or IHV because of that ISV?s or IHV?s:
a. developing, using, distributing, promoting or supporting any software that competes with Microsoft Platform Software or any software that runs on any software that competes with Microsoft Platform Software, or
b. exercising any of the options or alternatives provided for under this Final Judgment.
2. Microsoft shall not enter into any agreement relating to a Windows Operating System Product that conditions the grant of any Consideration on an ISV?s refraining from developing, using, distributing, or promoting any software that competes with Microsoft Platform Software or any software that runs on any software that competes with Microsoft Platform Software, except that Microsoft may enter into agreements that place limitations on an ISV?s development, use, distribution or promotion of any such software if those limitations are reasonably necessary to and of reasonable scope and duration in relation to a bona fide contractual obligation of the ISV to use, distribute or promote any Microsoft software or to develop software for, or in conjunction with, Microsoft.
3. Nothing in this section shall prohibit Microsoft from enforcing any provision of any agreement with any ISV or IHV, or any intellectual property right, that is not inconsistent with this Final Judgment.
G. Microsoft shall not enter into any agreement with:
1. any IAP, ICP, ISV, IHV or OEM that grants Consideration on the condition that such entity distributes, promotes, uses, or supports, exclusively or in a fixed percentage, any Microsoft Platform Software, except that Microsoft may enter into agreements in which such an entity agrees to distribute, promote, use or support Microsoft Platform Software in a fixed percentage whenever Microsoft in good faith obtains a representation that it is commercially practicable for the entity to provide equal or greater distribution, promotion, use or support for software that competes with Microsoft Platform Software, or
2. any IAP or ICP that grants placement on the desktop or elsewhere in any Windows Operating System Product to that IAP or ICP on the condition that the IAP or ICP refrain from distributing, promoting or using any software that competes with Microsoft Middleware.
Nothing in this section shall prohibit Microsoft from entering into (a) any bona fide joint venture or (b) any joint development or joint services arrangement with any ISV, IHV, IAP, ICP, or OEM for a new product, technology or service, or any material value-add to an existing product, technology or service, in which both Microsoft and the ISV, IHV, IAP, ICP, or OEM contribute significant developer or other resources, that prohibits such entity from competing with the object of the joint venture or other arrangement for a reasonable period of time.
This Section does not apply to any agreements in which Microsoft licenses intellectual property in from a third party.
H. Starting at the earlier of the release of Service Pack 1 for Windows XP or 12 months after the submission of this Final Judgment to the Court, Microsoft shall:
1. Allow end users (via a mechanism readily accessible from the desktop or Start menu such as an Add/Remove icon) and OEMs (via standard preinstallation kits) to enable or remove access to each Microsoft Middleware Product or Non-Microsoft Middleware Product by (a) displaying or removing icons, shortcuts, or menu entries on the desktop or Start menu, or anywhere else in a Windows Operating System Product where a list of icons, shortcuts, or menu entries for applications are generally displayed, except that Microsoft may restrict the display of icons, shortcuts, or menu entries for any product in any list of such icons, shortcuts, or menu entries specified in the Windows documentation as being limited to products that provide particular types of functionality, provided that the restrictions are non-discriminatory with respect to non-Microsoft and Microsoft products; and (b) enabling or disabling automatic invocations pursuant to Section III.C.3 of this Final Judgment that are used to launch Non-Microsoft Middleware Products or Microsoft Middleware Products. The mechanism shall offer the end user a separate and unbiased choice with respect to enabling or removing access (as described in this subsection III.H.1) and altering default invocations (as described in the following subsection III.H.2) with regard to each such Microsoft Middleware Product or Non-Microsoft Middleware Product and may offer the end-user a separate and unbiased choice of enabling or removing access and altering default configurations as to all Microsoft Middleware Products as a group or all Non-Microsoft Middleware Products as a group.
2. Allow end users (via a mechanism readily available from the desktop or Start menu), OEMs (via standard OEM preinstallation kits), and Non-Microsoft Middleware Products (via a mechanism which may, at Microsoft?s option, require confirmation from the end user) to designate a Non-Microsoft Middleware Product to be invoked in place of that Microsoft Middleware Product (or vice versa) in any case where the Windows Operating System Product would otherwise launch the Microsoft Middleware Product in a separate Top-Level Window and display either (i) all of the user interface elements or (ii) the Trademark of the Microsoft Middleware Product.
3. Ensure that a Windows Operating System Product does not (a) automatically alter an OEM?s configuration of icons, shortcuts or menu entries installed or displayed by the OEM pursuant to Section III.C of this Final Judgment without first seeking confirmation from the user and (b) seek such confirmation from the end user for an automatic (as opposed to user-initiated) alteration of the OEM?s configuration until 14 days after the initial boot up of a new Personal Computer. Microsoft shall not alter the manner in which a Windows Operating System Product automatically alters an OEM?s configuration of icons, shortcuts or menu entries other than in a new version of a Windows Operating System Product.
Notwithstanding the foregoing Section III.H.2, the Windows Operating System Product may invoke a Microsoft Middleware Product in any instance in which:
Microsoft?s obligations under this Section III.H as to any new Windows Operating System Product shall be determined based on the Microsoft Middleware Products which exist seven months prior to the last beta test version (i.e., the one immediately preceding the first release candidate) of that Windows Operating System Product.
I. Microsoft shall offer to license to ISVs, IHVs, IAPs, ICPs, and OEMs any intellectual property rights owned or licensable by Microsoft that are required to exercise any of the options or alternatives expressly provided to them under this Final Judgment, provided that
1. all terms, including royalties or other payment of monetary consideration, are reasonable and non-discriminatory;
2. the scope of any such license (and the intellectual property rights licensed thereunder) need be no broader than is necessary to ensure that an ISV, IHV, IAP, ICP or OEM is able to exercise the options or alternatives expressly provided under this Final Judgment (e.g., an ISV?s, IHV?s, IAP?s, ICP?s and OEM?s option to promote Non-Microsoft Middleware Products shall not confer any rights to any Microsoft intellectual property rights infringed by that Non-Microsoft Middleware Product);
3. an ISV?s, IHV?s, IAP?s, ICP?s, or OEM?s rights may be conditioned on its not assigning, transferring or sublicensing its rights under any license granted under this provision;
4. the terms of any license granted under this section are in all respects consistent with the express terms of this Final Judgment; and
5. an ISV, IHV, IAP, ICP, or OEM may be required to grant to Microsoft on reasonable and nondiscriminatory terms a license to any intellectual property rights it may have relating to the exercise of their options or alternatives provided by this Final Judgment; the scope of such license shall be no broader than is necessary to insure that Microsoft can provide such options or alternatives.
Beyond the express terms of any license granted by Microsoft pursuant to this section, this Final Judgment does not, directly or by implication, estoppel or otherwise, confer any rights, licenses, covenants or immunities with regard to any Microsoft intellectual property to anyone.
J. No provision of this Final Judgment shall:
1. Require Microsoft to document, disclose or license to third parties: (a) portions of APIs or Documentation or portions or layers of Communications Protocols the disclosure of which would compromise the security of anti-piracy, anti-virus, software licensing, digital rights management, encryption or authentication systems, including without limitation, keys, authorization tokens or enforcement criteria; or (b) any API, interface or other information related to any Microsoft product if lawfully directed not to do so by a governmental agency of competent jurisdiction.
2. Prevent Microsoft from conditioning any license of any API, Documentation or Communications Protocol related to anti-piracy systems, anti-virus technologies, license enforcement mechanisms, authentication/authorization security, or third party intellectual property protection mechanisms of any Microsoft product to any person or entity on the requirement that the licensee: (a) has no history of software counterfeiting or piracy or willful violation of intellectual property rights, (b) has a reasonable business need for the API, Documentation or Communications Protocol for a planned or shipping product, (c) meets reasonable, objective standards established by Microsoft for certifying the authenticity and viability of its business, (d) agrees to submit, at its own expense, any computer program using such APIs, Documentation or Communication Protocols to third-party verification, approved by Microsoft, to test for and ensure verification and compliance with Microsoft specifications for use of the API or interface, which specifications shall be related to proper operation and integrity of the systems and mechanisms identified in this paragraph.