Response To The USDOJ-Microsoft Settlement 17
icanoop writes: "I haven't heard much about whether or not people are taking advantage of the Tunney Act and commenting on the settlement. Here is my letter to the DOJ in pdf and html. Remember these are my opinions, I'm not trying to represent open source or anything. I hope it will inspire others to send comments to the DOJ."
'comment' is an insufficient word (Score:1)
"hey, i know! why don't we force them to sign something that says they'll be good little monopolies and at the same time make them pay their damages by expanding their marketshare in education...every one's a winner!"
--
Nice (Score:2)
Cheers,
jw
Background and where to send comments (Score:4, Informative)
http://www.usdoj.gov/atr/cases/ms-settle.htm [usdoj.gov]
Re:Background and where to send comments (Score:1)
The danger of public comments (Score:1)
Public agencies tend to get flooded with written public comments. I'm with a local law enforcement agency which has occasionally solicited public commentary. Sometimes, we get good, valuable comments and (even better) useful and intelligent criticism. More often, we get sub-literate scrawled rants about how "pigs suck." Needless to say, the letters with poor grammar and spelling or little useful information tend to get passed around for comic relief rather than taken seriously.
The point I'm trying to make is, if you get defensive about being told to use a spell-checker, keep your mouth shut or you'll make MS look better. If your idea of commentary is 'M$ 5uX0Rz,' then stick to some IRC channel or you'll do more harm than good. And for God's sake, don't get into pointless esoterica about licensing or 'free speech/free beer.' If you go beyond the scope of the case at hand, you run a risk of not being taken seriously.
And AC's: I imagine they've already gotten their first letter. It's too late to get f15T pR05T.
This inspired me (Score:2)
Here's mine:
\documentclass{letter}
\begin{document}
\address{Robert G. Ristroph \\
11612 Hidden Quail \\
Austin, TX 78758 }
\signature{Robert G. Ristroph}
\begin{letter}{ Renata B. Hesse \\
Antitrust Division \\
U.S. Department of Justice \\
601 D Street NW \\
Suite 1200 \\
Washington, DC 20530-0001 }
\opening{Dear Ms. Hesse,}
I am writing with regard to the Justice Department's proposed settlement with
Microsoft. I believe that this settlement should be scrapped and completely
rewritten. Most of the ``restrictions'' placed on Microsoft are already
illegal; what few restrictions are left are impossible to enforce and seem
designed to produce more legal disputes rather than resolve them; and the
proposed enforcement mechanism is a ludicrous embarrassment. In addition to
scrapping this proposed settlement, any payment or further employment of the
authors should be re-evaluated in light of this idiocy.
I have read the original complaint of United States and the several States at
\texttt{http://www.usdoj.gov/atr/cases/f1700/17
at \texttt{http://www.usdoj.gov/atr/cases/f9400/9495
Impact Statement at \texttt{http://www.usdoj.gov/atr/cases/f9400/9495
well as numerous other sources including the findings of fact and other
documents.
My own injury by Microsoft's illegal actions comes from Microsoft's agreements
with OEM's which forced my employer to pay for Windows when buying a new
computer from Dell, which we had no plans to use Windows, intending it for
Linux. This was supposedly addressed in a prior case to the present one, and
yet to this day the same hardware without a Microsoft license has the same cost.
I wish to examine the elements of the proposed agreement item by item, and then
propose an outline of an alternative settlement.
A. That Microsoft will not retaliate against OEMs for distributing non-Microsoft
software. This is already prohibited by law, given Microsoft's monopoly.
The proposed settlement can not consist of Microsoft agreeing to follow the
law in the future; like other companies in the United States, it has to
follow the law regardless of this settlement.
B. That Microsoft make public it's licensing agreements and offer the same terms
to everyone. This is the only part of the proposed settlement makes sense,
however, OEMs have shown in the past they were willing to collaborate in
Microsoft's illegal activities. Should Microsoft offer an OEM a secrete
payback or special deal, the cooperation of the OEM will make this section
difficult to enforce.
C. That Microsoft cannot restrict certain OEM software through agreements. This
is already illegal, like A.
D. Some meaningless nonsense not worthy of comment or the paper it is printed
on.
E. That communications protocols in Microsoft software be publicly available.
In light of Microsoft's previous behavior in exploiting secrete calls in
it's software, all of it's source code should be available for public
examination. The suggestion that only ``communications protocols'' be public
is problematic because it leaves open to dispute what consists of a
communications protocol. This is foolish given Microsoft's previous
self-serving interpretations of court orders.
F. That Microsoft will not retaliate against software vendors for competing
against them. This is already against the law given that Microsoft is a
monopoly.
G. That fixed percentage distribution agreements be banned. This is already
against the law. The exceptions listed in this paragraph are also against
the law, creating the suggestion that the United States will enter into an
agreement with Microsoft to allow it to break the law in some cases.
H. That OEMs and users are allowed to configure the Microsoft software they
buy. This is vague and confusing because it is difficult to precisely
describe what consists of configuring software, and thus impossible to
reliably enforce. In a competitive market it would be the natural case, and
the proposed settlement should focus on restoring competition.
I. That Microsoft offer licenses to ``intellectual property'' necessary to allow
others to exercise ``alternatives provided under this final judgment.''
The reference to alternatives provided to others contradicts the final
section of the proposed settlement, which explicitly denies that the final
settlement gives any rights to third parties. Even aside from that, this
section probably denies behavior already illegal, is riddled with
exceptions, vague, and seems designed to produce legal action rather than
remedy.
J. A section devoted wholly to exceptions for Microsoft, as if there where not
enough already.
The Enforcement Authority:
A. Access to source code is probably one of the best remedies. The exceptions
and limitation of this access to a committee are silly.
B. The Technical Committee. It has too few members, it should be composed of
Officers of a United States Federal Court in order to make it's requests
immediately enforceable through Contempt hearings, and the gag on public
statements renders the whole committee useless. The further restriction that
the testimony of this muzzled and hobbled committee not be admissible in
court is a bit like shooting the deer after it's tied down with it's throat
cut.
C. The Microsoft Compliance Officer. This section is nonsense. Other
companies manage to obey the law without the use of a special office. If
Microsoft needs one they can implement it without a judgment.
D. Voluntary Dispute Resolution. This section seems dedicated to stipulating
that various parties send each other letters before seeking court hearings, a
common practice. 4(d) guts all enforcement power from the proposed
judgment, and suggests that the Attorneys for the Justice Department don't
believe in their own system of courts.
Third Party Rights:
This section is in contradiction with other references to the submission of
complaints to the Technical Committee and the requirement that Microsoft offer
``intellectual property'' licenses to the third parties so that they can pursue
the alternatives guaranteed them in this proposed final judgment.
In summary, this proposed final judgment is a poor sham for a capitulation by
the Plaintiffs. It's not even a good surrender, because it's vagueness and
self-contradictions guarantee more legal action; if we must capitulate, at least
we should save on legal costs. It also completely fails to disguise the
capitulation in any way. This is why whoever wrote it should be fired, even if
the Justice Department unwisely chooses to fail to enforce the law as applies to
Microsoft.
A real final judgment, which might have the chance of remedying the situation,
would have to be in some way ``self enforcing.'' By ``self enforcing'' I mean
that the remedy by it's nature should preclude further legal wrangling and
evasion efforts by Microsoft. Stipulations on Microsoft's future behavior
inherently have to be enforced, and thus are not well suited to this case.
Furthermore, when the proposed judgment stipulates that behavior already
illegal be banned and then suggests exceptions, the Plaintiffs are acquiescing in
further law breaking by Microsoft.
An example of a ``self enforcing'' remedy would be denying Microsoft copyright
protection. No Technical Committee is required; all that is needed is to reject
out of hand cases of copyright enforcement that Microsoft brings. Thus,
revoking copyright privileges for some portion of the works that Microsoft used
to violate the law might be an appropriate remedy. Or perhaps Microsoft could
post substantial bonds against it's future behavior.
Many of the major flaws in this proposed final settlement result from the
needless use of vague and disputable terms, when simple and undisputable ones
would do.
Replace all references to ``Microsoft Middleware'' ``Windows Operating System
Product'' and such with the simple phrases ``products of Microsoft'' and
``products of third parties.'' Avoid even the use the term ``software
products,'' as Microsoft would produce hardware required to run their products
and then violate the agreement. Be sure the phrase ``products'' is defined to
mean anything Microsoft does, including services.
Replace all references to ``ISVs, IHVs, ICDs, OEMs'' and such with the phrase
``any third party.'' Quibbling over which member of the alphabet soup a
particular entity fell under is thus eliminated. The final judgment should
require no differentiation between the various consumers and companies
interacting with Microsoft. This also remedies the fault that the current
proposed judgment allows Microsoft to exempt any third party from the benefits
of what legal behavior is required by claiming they do not have a viable
business plan.
I hope you find these suggestions helpful in writing a real judgment.
\closing{Sincerely,}
\end{letter}
\end{document}
Re:This inspired me (Score:1)
GPL-ing Windows as punishment? (Score:1)
one simple solution: open source the next version of "Windows" under the GPL
i.e. whatever version of windows comes after xp - anything that is sold in that box gets released as opensource
this will:
1 punish microsoft for all their convicted wrongdoings - the idea is to simply take away the leverage that they have misused time and again to elbow their way into new markets
2 effectively splits the OS from the apps without the pain of splitting up the company itself
3 expose all the APIs and communication protocols so other companies are on a level field
4 cause them to immediately un-bundle anything from the "operating system" that they do not want opensourced
it will be interesting to see microsoft backpedaling - e.g. declaring explorer and mediaplayer NOT part of OS anymore
5 will make windows itself better in the long run - more eyes, etc., no hidden backdoors, bugs exposed, etc.
6 benefit all mankind - windows could be ported to PowerPC, Sparc.
7 anticompetetive bootloader issues will disappear
another company could simply release a dual-boot-capable version of windows
is this too naive? would this cause more problems? please think carefully before responding
some things to watch out for:
them trying to sell service packs as closed source and never releasing a new OS
them stripping down the OS to a bare minimum and hiding the rest of it as binary-only service packs
Re:GPL-ing Windows as punishment? (Score:2)
Re:GPL-ing Windows as punishment? (Score:1)
I believe that rules should be put in place to keep them from abusing their monopoly ever again, and on top of that, financial penalties should be charged so that the money they have gained while abusing their monopoly is taken from them and placed back into the industry as a whole. As we all seem to agree, the proposed settlement fails to meet either of these criteria.
If these criteria are met, it would cause Microsoft to drop the ball on supplying product to the meet the demand they have. Then it would be picked up by competitors, both closed source and open source alike, to fight for the market. I think that in a fair fight the open source code would prevail.
I've been working on a detailed response (Score:1)
Please have a look at it, and let me know if you think I'm on the right track.
Also, I've set up a mailing list on this topic; to subscribe, go to http://groups.yahoo.com/group/ms-remedy/ or send a message to ms-remedy-subscribe@yahoogroups.com
Looking forward to your feedback. I'm hoping that I can come up with a document that a significant number of Free Software supporters can sign on to, which will get the attention of the States' attournys-general, and which has a good chance of influencing the judge to impose a settlement which won't leave the Free Software community out in the cold.
- Dan
Does anyone remember the FSF's proposed remedies? (Score:1)
Re:Does anyone remember the FSF's proposed remedie (Score:1)
More Microsoft bullying (Score:1)
Should we allow one company to force their software on the entire computing community? The government thinks so because they have sponsored Microsoft's business practices, which have made it so other companies can not compete with Microsoft desktop office and Internet software, which in turn will make these forced Microsoft upgrades policies possible. Maybe the government should allow every company in the world to come to your home or place of business to force you to show them receipts for every item that you have in your possession. If you don't have a receipt for the item in your possession than the manufacturing company can confiscate any and all items and can willfully impose a fine unless you buy the companies latest product. Looks like the government loves this idea.
The reason I'm writing to you guys about this is because these actions will have direct or indirect impact to our chosen professions. Who knows maybe IT budgets will have to shrink even more than they have in the past year to meet new upgrade requirements. Maybe that will mean less money for you, me, and your family. Take five minutes of your time to write to the judge in this matter.
To e-mail judge Kollar-Kotally do so at microsoft.atr@usdoj.gov and put in the Subject line of the e-mail, type Microsoft Settlement.
Be sure to bcc: microsoftsettlement@yahoo.com so that a hard copy is printed and delivered to the judge to ensure receipt.. The court will carefully review each and every submission made before the deadline (Jan 28, 2002) - so your voice will be heard.
Also depending on the state you work in send a copy to the one of these attorneys:
California: microsoftcomments@doj.ca.gov
Florida: craig_farringer@oag.state.fl.us
Connecticut: steven.rutstein@po.state.ct.us
Iowa: tormist@ag.state.ia.us
Kansas: beasleyr@ksag.org
Massachusetts: sara.Hinchey@ago.state.ma.us
Minnesota: attorney.general@state.mn.us
Utah: uag@att.state.ut.us
West Virginia: davisdo@mail.wvnet.edu