Slashdot Log In
Red Hat Patenting Around Open Standards
Posted by
Soulskill
on Sun Mar 15, 2009 11:58 AM
from the tread-lightly dept.
from the tread-lightly dept.
I Believe in Unicorns writes "Red Hat's patent policy says 'In an attempt to protect and promote the open source community, Red Hat has elected to... develop a corresponding portfolio of software patents for defensive purposes. We do so reluctantly...' Meanwhile, USPTO Application #: 20090063418, 'Method and an apparatus to deliver messages between applications,' claims a patent on routing messages using an XQuery match, which is an extension of the 'unencumbered' AMQP protocol that Red Hat is helping to make. Is this a defensive patent, or is Red Hat cynically staking out a software patent claim to an obvious extension of AMQP? Is Red Hat's promise to 'refrain from enforcing the infringed patent' against open source a reliable contract, or a trap for the unwary? Given the Microsoft-Red Hat deal in February, are we seeing Red Hat's 'Novell Moment?'"
Reader Defeat_Globalism contributes a related story about an international research team who conducted experiments to "quantify the ways patent systems and market forces might influence someone to invent and solve intellectual problems." Their conclusion was that a system which doesn't restrict prizes to the winner provides more motivation for innovation.
Related Stories
[+]
Linux: Microsoft and Red Hat Team Up On Virtualization 168 comments
mjasay writes "For years Microsoft has insisted that open-source vendors acknowledge its patent portfolio as a precursor to interoperability discussions. Today, Microsoft shed that charade and announced an interoperability alliance with Red Hat for virtualization. The nuts-and-bolts of the agreement are somewhat pedantic, providing for Red Hat to validate Windows Server guests to be supported on Red Hat Enterprise virtualization technologies, and other technical support details. But the real crux of the agreement is what isn't there: patents. Red Hat has long held that open standards and open APIs are the key to interoperability, even as Microsoft insisted patents play a critical role in working together, and got Novell to buy in. Today, Red Hat's vision seems to have won out with an interoperability deal heavy on technical integration and light on lawyers."
Firehose:Red Hat patenting around open standards by Anonymous Coward
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
Defensive Patents (Score:4, Interesting)
Haven't we heard this before? That has worked out for us rather well hasn't it.
What company would not turn to offensive attacks if threatened?
Re:Defensive Patents (Score:5, Interesting)
This would appear to be a 'wolf in sheeps clothing' situation and a very dangerous one. A good idea for anti-patent people (and I have a few of these things and don't like them) is for the eff or somebody to create a easily search-able list of 'good ideas' top protect the ideas from being patented.
To stop commercial exploitation of an idea (like sticking the idea into an operating system thats very popular) thereby effectively banning all other operating systems or companies competing, is a completely different matter, and this is where defensive patents would help, but then you have to decide who can use the tech - and were back at square 1 again - very few people have the mental capacity to decide on this point.
Parent
Re:Defensive Patents (Score:5, Insightful)
It's not about that. It's about mutually assured destruction. You can sue me, sure, but I can sue you too, so do you really want to start this dance?
If you just posted prior art, all you're doing is protecting stuff that you came up with yourself, and even then, you may still have to prove your prior art in court. It doesn't help in a situation where another company has patented some BS that they claim applies to everything you do.
Parent
Re: (Score:3)
That's exactly what it is, which is why the laws and their interpretation at the patent office and the courts must change.
Re:Defensive Patents (Score:5, Insightful)
Mutually-assured destruction worked exactly as intended, in preventing nuclear war for over 50 years. I see no reason why those lessons can't be exported to business... a diplomacy of a different kind.
Parent
Re:Defensive Patents (Score:5, Insightful)
Not really.
After WWII, the US had several years as the only nuclear-armed nation, and yet didn't attack the Soviet Union.
The US developed the fusion bomb before the USSR, making it the first with the "assured-destruction" scale weapons, where little if any retaliation would have been possible, and yet didn't use that opportunity.
From the 50s through the 60s, the US was pretty well assured that, with a full nuclear first strike, it could almost entirely eliminate the retaliatory threat from the USSR. Again, it didn't happen.
The USSR had to adapt it's nuclear submarine fleet for extended operation under the Arctic polar ice cap just to establish a guaranteed retaliatory capability.
At best, there was about 20 years of MAD.
Parent
Re:Defensive Patents (Score:4, Informative)
Why not simply publish the spec in wikipedia and as many lists as possible (including your own web site).
That's probably the cheapest route, but the safest route (if all you want in terms of defense is publication rather than a war chest of patents for warding off lawsuits) is called a Statutory Invention Registration. It's cheaper than filing a patent, and it doesn't stake out any invention territory (meaning that if someone duplicates the invention laid out in the SIR, you can't sue them for infringement based on the SIR). But it will show up in the search tools used by US patent examiners, and it establishes a prior art date, so that it can easily be found by examiners for the purpose of rejecting future applications.
Actually, IBM did something similar back in the 70s - they published a series of Technical Disclosure Bulletins, where they disclosed a bunch of things they had come up with but that they weren't interested in patenting. They just didn't want anybody else patenting it and then suing them over it. The USPTO has all of that IBM stuff in its search databases as well.
Parent
Re:Defensive Patents (Score:5, Interesting)
> That's the key behind defensive patents. Other companies won't want to sue you for patent infringement, because they know that you can respond in kind.
That works till RedHat falls into the wrong hands. If it goes titsup in a bad economy and the receivers sell off its assets to the patent trolls all bets are off.
Parent
Re:Defensive Patents (Score:4, Informative)
Exactly. It does not work because it does not protect against patent trolls and normal business players won't sue you as they patent for defensive purposes and maybe just want licensing fees.
With your portfolio you could countersue IBM but what to do against Eolas and Sisvel? Oh, and a patent lawsuit costs 500k.
Parent
Re:Defensive Patents (Score:4, Funny)
Translating the patent jargon for you:
If your s/invention/patent/ is not
1: s/Novel/freshly written/
2: s/Inventive/written in complex lawyer language/
3: s/Industrially applicable/says "machine" a few times/
it will simply not be granted
ftfy.
Parent
The Red Hat Patent Promise and Estoppel (Score:4, Informative)
"Red Hat has commited not to sue. So what? Does that mean that they'll remain true to whatever they said?"
Yes, actually, because of the legal principle of estoppel by representation of fact [wikipedia.org], also known in American law as "equitable estoppel". To wit:
"In general, estoppel protects an aggrieved party, if the counter-party induced an expectation from the aggrieved party, and the aggrieved party reasonably relied on the expectation and would suffer detriment if the expectation is not met."
Red Hat, with its patent promise, induces an expectation: that Red Hat will not sue an open source developer for patent violations. If Red Hat then violates that expectation, a judge would basically throw out any such lawsuit immediately on grounds of estoppel.
Parent
I'm not a prognosticator, but.... (Score:5, Insightful)
If the patent systems are to be beaten into submission, and put in their place, it will take many such protective patents. That is to say, patents which are granted but the patent holder never uses against anyone, thus over time forcing the patented issue into the public domain by virtue of failure to enforce it.
There will have to be huge portfolios of these and events such as IBM or other big portfolio holders simply refusing to litigate against anyone. It will get tricky but needs to be done. If IBM et al decided that they would only enforce those that are crucial to their own viability/survival, and not litigate against little guys, it would change how things are done. No matter, it will still be messy till the market settles on what is a 'normal' and 'don't be evil' way of doing things despite what the USPTO or any other might say is legal.
It always starts out with good intentions (Score:5, Insightful)
These kinds of efforts always start out with the best intentions. Then the company gets sold or new management comes on board, money gets tight and it's not long before they're taking another look at monetizing their patent portfolio.
If RedHat was really serious about the patents being defensive, wouldn't it make sense for them to donate them to an open source patent pool?
Re:It always starts out with good intentions (Score:5, Insightful)
Parent
Re:It always starts out with good intentions (Score:4, Insightful)
That isn't the purpose of a defensive patent. The idea is that if Company X tries to sue Red Hat for patent infringement, then Red Hat can countersue for the infringement of Company X on one of RH's defensive patents. Either that or RH and Company X simply agree on cross-licensing their respective patents to each other.
Parent
Re:It always starts out with good intentions (Score:5, Insightful)
Then the company gets sold or new management comes on board, money gets tight and it's not long before they're taking another look at monetizing their patent portfolio.
Aye, there's the rub! Particularly when the sorts of companies the patents might be used defensively against could probably afford to bankroll a hostile takeover if Red Hat got too anoying.
Obtaining patents and then releasing them under an irrevocable public license seems like the only way to avoid this - but then you'd still need a clever, bulletproof "GPL-for-patents" public license to ensure that they could still be used defensively. The first test case of such a license would be, er, fun... (Unlike GPL, it could end up being infectiously viral, because you don't have to consciously copy anything to violate a patent).
My suspicion is that the the mutually assured patent portfolio destruction concept only really works for superpowers with very deep litigation pockets. Part of the problem is, the patent system is so broken and full of invalid patents or patents on minor variations of other patents, nobody really knows whether they are holding a doomsday device or a shiny casing full of pinball machine parts...
Parent
Re:It always starts out with good intentions (Score:5, Insightful)
Parent
Re:It always starts out with good intentions (Score:4, Interesting)
It's a good question and is answered in the license:
However the companies involved in the OIN would have to ensure that they disentangle all their technology assets from the patents held by other members if they did not want to be sued. Rather a large undertaking and one that would disrupt most of the profitable enterprise revenue. So it's kind of a flypaper that gets more effective the longer its around and the more that its used.
Parent
Re:It always starts out with good intentions (Score:5, Informative)
If RedHat was really serious about the patents being defensive, wouldn't it make sense for them to donate them to an open source patent pool?
As Red Hat is a member of the Open Invention Network [openinventionnetwork.com], a group dedicated to creating a pool of defensive patents, that is likely to happen.
Parent
could run afoul of Microsoft actually.. (Score:3, Interesting)
'Method and an apparatus to deliver messages between applications,' claims a patent on routing messages using an XQuery match
Biztalk has routed messages using XQuery matching now for at least 5 years. The irony is, that, it seems like such a good idea to build a messaging system around XML, which Biztalk does, but in practice, it actually totally sucks.
Defeat_Globalism ? (Score:5, Funny)
Offtopic but, am I the only one who finds it ironic, and funny, that a person with the username "Defeat_Globalism" is using the World Wide Web?
Red Hat's deal is nearly the complete opposite (Score:5, Informative)
Novell agreed that Microsoft had a valid claim that Linux infringed Microsoft patents and paid Microsoft for the use of said (unspecified, undisclosed, vaporware) patents.
Red Hat by contrast did not sign a joint agreement with microsoft [redhat.com] but set up co-ordinated support for customers who use either Red Hat guest instances on Microsoft servers or Microsoft guests on Red Hat servers. They explicitly " ... have nothing to do with patents, and there are no patent rights or other open source licensing rights implications provided under these agreements. The agreements contain no financial clauses other than test fees for industry-standard certification and validation."
Microsoft realized that they would be frustrating customers if they did not do this. Red Hat realizes the same thing. Neither Microsoft nor Red Hat conceded anything about patents in this relationship.
The difference between the Novell-Microsoft pact and the current story is so vast that the original post is either a troll or a very confused person.
GPL a pretty good shield. (Score:4, Interesting)
If Red Hat should ever go after FOSS, their extensive contributions to GPL projects should prevent them from doing anything malicious with these patents.
Though I would worry for those with more permissive licenses, the second that Red Hat contributes a line of code related to this patent to a FOSS project, that should be sufficient to argue that Red Hat placed the patent out for similar free use. I'd say this is more a question of preventing patent trolls from patenting something mind-numbingly obvious.
Of course, placing the patents under a GPL restriction would allow them to enforce the patents against proprietary use. That would be quite a turn.
Re:GPL a pretty good shield. (Score:4, Interesting)
This is not a question of preventing patent trolls from patenting the same thing.
Firstly, because AMQP has hundreds or thousands of areas that could be similarly patented: failover, federation, many types of exchange, remote administration, etc. It only takes one patent to hold the whole standard to ransom. Red Hat would have to patent every single technical aspect of the standard, which would be impossible in practical terms.
Secondly, because there are much cheaper ways of stopping patent trolls from patenting obvious things: publish them, register them as prior art at the USPTO.
It's naive to think that the only way patents are used is to 'go after' projects. 99% of the time, patents of this sort are used in discrete discussions with potential clients. "You know, we hold a patent on that... (hint hint)". This is enough to scare the customer into at least not using a rival product, open source or not. Indeed, patents that make it to court tend to die rather faster than patents used under the table.
The irony of this patent is that technically, it's not that interesting. Dynamic message routing on XML is not difficult, but not efficient. It's much faster to pre-calculate routing keys and indices, as the existing AMQP exchanges do.
So I think Red Hat are simply playing the game of collecting software patents like points.
However, I really expected better from Red Hat.
Parent
Re:Why not simply establish a 'prior art' portfoli (Score:4, Insightful)
Not really. A patent portfolio doesn't help against patent trolls. A patent troll, by definition, doesn't produce anything, and therefore doesn't infringe any patents.
Patents are purely negative. All they allow you to do is prevent other people from making and distributing something. I can file a patent which requires a patent you own to work, and I can license it to other people without your permission. The people I license it to may need your patent as well, but how they get it (cross-licensing deals, buying it outright, or whatever) is not my problem.
If a patent troll sues Red Hat for infringing their patent, then a parent portfolio doesn't help. Red Hat can't say 'you can't sue us, we have loads of patents.' The other company will just say 'what do we need patents for?' and continue with the suit.
Defensive patents only work against big companies like IBM or Microsoft who are almost certainly infringing your patents for something.
Parent