Documentation Compliance Means MS Can Resume Collecting Protocol Royalties

angry tapir writes "Microsoft may begin collecting royalties again for licensing some protocols because clear technical documentation is now available, according to the US Department of Justice. The change comes after the DOJ issued its latest joint status report regarding its 2002 antitrust settlement with Microsoft. The settlement required Microsoft to make available technical documentation that would allow other vendors to make products that are interoperable with Windows."

Comments

Outrageous

[PizzaAnalogyGuy]

This is outrageous, and I have two examples why. First, protocols are like food recipes. The pizza you sell is yours, but the ingredients to make it is not. Here the protocol is your ham, pineapple, salami and shrimps on a barbeque sauce large size pan pizza. You have not stolen the app from your competitor, you're just making yours compatible with theirs. Like the third party IM clients can connect to MSN network. Secondly, how would any of those open source apps pay for the royalties? But maybe this is Microsoft's plan. Let me tell you what is happening here. Microsoft is paying for the local BBQ Sauce factory to include a license agreement before you can use their sauce in your pizzas. The license agreement says you are only allowed to use their BBQ sauce on Microsoft approved pizzas. And before you know, these pizzas will be degraded. Forget your ham, forget your pineapples, forget you bacon and forget your cheese. THIS is the pizza we offer, and this will be the pizza you like.

Just in time, too!

[Weaselmancer]

And it only took them ten years.

Funny how the government doesn't even give you ten days past the due date of a parking violation though, isn't it?

Re:protocols

[phantomfive]

It is extremely rare that a protocol becomes a competitive advantage because of their quality, mainly because designing a protocol in most cases isn't really very hard. Usually the only reason to keep a protocol secret is to keep competitors from interoperating with your software, which is why Microsoft was convicted of being a monopolist in the first place.

In fact I can't think of any protocol that was kept secret because it performed better at the time. Maybe some old networking protocol or something. I can think of a ton of protocols that were kept secret purposely to prevent interoperability. Here's a few:

SMB/CIFS
CDMA diagnostic port protocol
Blizzard online game protocols
IPodITunes protocol
Skype
AIM protocol
MSN chat protocol
Yahoo chat protocol

There are others. Fortunately reverse engineering a product for the purpose of interoperability is allowed under the DMCA. That is one of the bright spots of that legislation.

Re:protocols

[symbolset]

Protocols are not code. Protocols are methods of interaction between pieces of code, even if the code is methods of interaction embedded in hardware. That these methods could possibly be considered as something that should be protected by some sort of intellectual property agreement is a testament to how far we've fallen from the root assumption of Unix: that all things should be able to connect to all other things whenever physically possible.

This is the mindset that brought us DRM, all of Sony's stupid proprietary media formats, and an iPhone that won't tether.

I'm sick of it. I have enough stuff that doesn't connect to my other stuff. I'm not buying any more stuff that doesn't connect to the stuff that I already have. I'm not using any systems that require proprietary licensing to connect the stuff I have to the new stuff I buy. I'm done with all that stupidness.