Slashdot Mirror
More Details of MS/DOJ Deal
There are various news articles out at most major news sites, but they're all based on this press release from the Department of Justice. The actual terms of the settlement will probably become public shortly, so I wouldn't spend a whole lot of time trying to dissect this press release. Just read it for generalities. In sum: for this whole multi-year case, which you will recall started when Microsoft refused to obey its earlier behavior restrictions, we have more behavior restrictions, lasting only five years. And if MS doesn't obey those, they'll ... be in effect longer. Update: 11/02 15:07 GMT by M : Here are the promised terms of the settlement. Now you can dissect them. :) Update: 11/02 15:53 GMT by M : The states are refusing to sign on.
The settlement says they need to have open server protocols. This is great for SAMBA, and it seems like it would have to include exchange. Maybe Microsoft will go away from everything runs from the network.
The deal is for five years, but it takes Microsoft around 2 or 3 years to come out with a new version of Winows and other software. So... the deal doesn't seem like it will have much of a lasting effect.
.doc and .xls, don't think for a minute that offices wouldn't switch to something else.
Also, there is a section about disclosure of server protocols, they left out what is the most important part: Document Formats. If Microsoft didn't have a monopoly on
So XYZ Computer Company decided to take this anti-trust thing seriously and offer Netscape on the desktop, eh? No problem - we will just "forget" to renew their Windows license at the end of the year. Nothing deliberate; just an oversight. Of course, since they are no longer a licensee, when they do renew, they will be in a 200% higher price bracket. Sorry about that, but we enforce those rules on everyone. And by the way, the BSA will be around to audit you and your customers next week.
Anyone who has worked for a major corporation knows how these things are done. As did Judge Jackson, which is why he recommneded breakup. Oh well.
sPh
I read somewhere (i think NYTimes) that one area the DoJ was pushing for was to force MS to publish their specs for things like file formats and their other propritary "standards." MS was very resistant to that, as they would about publishing anything prorietary.
Thiking about this, I actually think it would be in MS's better interest to publish those specs. Some of their products are already de facto standards in the business world. Publishing those specs would allow competitors to write competing software (ie- StarOffice) that's compatible more easily, but that would be MS's consequence for abusing a monopoly. But by publishing the spec, that would make MS the "setter of the standard," something that they have always wanted to be.
The One Rule Of Chess You'll Ever Need: Don't play someone who carries a kit in their bookbag.
From the press release:
.. well, urm, software? Where along the line did those types of componants somehow become referred to as 'middleware' .. is that just a euphamism for 'applications that get shipped with an os'?
> Broad Scope of Middleware Products- The proposed Final Judgment applies a broad definition of middleware products which is wide ranging and will cover all the technologies that have the potential to be middleware threats to Microsoft's operating system monopoly. It includes browser, e-mail clients, media players, instant messaging software, and future new middleware developments.
Since when is a media player middleware? Or an IM client? Arn't these just pieces of
Being a developer, I'm used to middleware being your glue code between back (business logic) and front (view logic) ends.
"Old man yells at systemd"
The claim with regard to closing the SMB protocol was that the new password-exchange system (implemented in XP I think) was covered by a method patent. This raises two questions. First, will Microsoft be required to either relinquish this patent or agree not to pursue claims based on this patent (since it's not strictly a patent on a protocol)? Second, What does this mean for Microsoft's other Intellectual Property?
--CTH
--Got Lists? | Top 95 Star Wars Line
I have to agree, even if the poster is a bad speller. If we can execute human beings (something Dubya loves to do anyway) why not execute corporations? After Microsoft, the next candidates IMHO would be tobacco companies. After, their products have caused the death of millions, so they could be classified as mass murderers. Hell, they've killed 500 times as many people as Osama bin Laden. We should just bomb the fuck out of them. (Anyone got numbers on how many people Microsoft has killed?)
Reality has a liberal bias
I heard (from the VP of sales at Logitech at the time) that MS went to Logitech and said they were interested at branding Logitech mice with MS's logo. Of course, the Logitech guys got dollar-signs in their eyes and put their best sales people on the job.
Six months later, after much negotiation, Logitech had widdled away their price estimates, and it came time for MS to sign the paperwork. The MS rep never showed.
A couple of months later, MS released their first mouse, undercutting Logitech because they knew every detail about Logitech's production costs.
I dunno'. That sounds shadey to me.
PS - I will admit that the MS optical mouse is the best mouse I've ever used.
I'd rather have someone respond than be modded up.
...they are in comtempt of court and get hauled back over the coals. The agreement is extended for another two year BUT they also have to face a new trial on contempt charges.
Please get your facts a little straight, michael.
Fear: When you see B8 00 4C CD 21 and know what it means
Woohoo! I hope that means what I think it means!
It's 10 PM. Do you know if you're un-American?
That's no moon.
In III.A: 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.
Put that together with III.J: J. No provision of this Final Judgment shall... 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
We've all seen the proposed text of the SSSCA. That says that everything which processes digital information must have security protocols for enforcing digital "rights", i.e. copyrights. Even though signs are promising that the SSSCA per se will go down in flames, it's not too much of a stretch to suppose that some legislation, at some point, will get passed which does define anything capable of processing digital data as capable of illegally copying intellectual property-- since it, of course, is. So, put that together with this loophole up here, and suddenly Microsoft can argue that they don't have to tell anybody absolutely anything about any of their protocols because it would "compromise anti-piracy systems".
Never mind the whole Microsoft "security through obscurity" argument: they're always saying that Windows is more secure because nobody sees its source code, so therefore it's harder to hack into those systems. We know it's bull$#!+, but they argue it a lot. It doesn't take much of a stretch for them to argue that their protocols are more secure if they are hidden... and then they can rest nicely in this loophole right again. They can continue "embrace and extend" monopolistic policies, making their own protocols and keeping them hidden, while claiming to maintain full compliance with this judgement, since after all they're only keeping the stuff hidden for "security reasons."
Microsoft has been slapped with a wet noodle. This is ridiculous.
Foo.
-Rob
You make a good point about enforceability: any settlement that depends upon executive branch agencies like the DOJ is a "walk" for Microsoft. No executive branch agency in the Bush pro-business-at-any-cost administration will actually enforce the terms of this agreement beyond the bare minimum necessary to avoid gross misconduct.
:-)
Any such settlement agreement must be enforced by a non-executive-branch body. (Perhaps the ITAA would like to help.
Moreover, Microsoft have demonstrated a total disregard for the law, and offering them the benefit of "good faith" is irresponsible. The fact that Microsoft is "powerful" should not prevent the DOJ from imposing proper sanctions and relief on their behaviour - in fact, it argues for a stronger and more enforceable penalty.
There are some major gifts in this agreement. For example, see III(A)(2). Microsoft may not retaliate against OEMs that sell Linux, or that ship PCs with multiple OSes or multi-boot capability, but the language allows Microsoft to retaliate against vendors of OS-less PCs or PCs that do not have Windows on them (e.g., PCs with only Linux installed).
Microsoft can also continue to roll functionality into its OS and kernel, or use proprietary APIs, as long as it does not put the entirety of the "middleware" into the OS. Only "Internet Explorer, Microsoft's Java Virtual Machine, Windows Media Player, Windows Messenger, Outlook Express and their successors" are covered by the middleware restrictions anyway. IIS, SQL Server, and other enterprise products can continue to use secret kernel-mode APIs to enhance their performance and maintain an unfair advantage for Microsoft middleware over non-Microsoft middleware.
There's a beautiful escape clause in III(H) which allows Microsoft to bypass third-party software (browser, JVM, media player, etc.) if it "fails to implement a reasonable technical requirement... that is necessary for valid technical reasons to supply the end user with functionality consistent with a Windows Operating System Product."
And there's the spectacular III(J), which allows Microsoft to hide APIs, documentation or "layers of Communications Protocols" if it "would compromise the security of anti-piracy, anti-virus, software licensing, digital rights management, encryption or authentication systems." That's rather broad.
As others have no doubt noted, there is no mention of the "embrace and extend" techniques Microsoft uses to take over open protocols under the guise of improved functionality. There's also no mention of tying Microsoft content to Microsoft products distributed with the OS and thereby creating a substantial barrier to entry for third parties (as they are doing now with MSN).
I would love to see a coordinated campaign to fight this settlement agreement. Congress gets very grumpy if executive branch agencies ignore public comments, and many state attorneys-general will have to sign off on the agreement (many of them do not like it, and even a small amount of public disapproval will help them). This means there is something that people everywhere within the US, or who do business in the US, can do to fight this agreement. Please write me at the email address given if you are interested in this effort.