Cisco VP Explains Lawsuit Against Apple
Dekortage writes "The day after Apple announced its iPhone, Cisco sued over the name. Mark Chandler, Cisco's SVP and General Counsel, has posted an explanation of the suit on his blog: 'For the last few weeks, we have been in serious discussions with Apple over how the two companies could work together and share the iPhone trademark. ...I was surprised and disappointed when Apple decided to go ahead and announce their new product with our trademarked name without reaching an agreement. It was essentially the equivalent of "we're too busy."' What did Cisco want? '[We] wanted an open approach. We hoped our products could interoperate in the future.'" Another reader wrote to mention that already, Cisco's trademark might be in trouble in Europe.
"' What did Cisco want? '[We] wanted an open approach. We hoped our products could interoperate in the future.'"
Oooh! this is so cool - all the macfanboys are hiding in caves while their god is being grilled by just about every geek and slashdottian in the universe. Steve Jobs is not just the enemy of opensource - he's actually so evil and greedy that he doesn't want anyone else to make third party apps for the thing and is proudly bragging about it.
Where are you now oh macfanboys! Come and defend your hero
www.tribalnetworks.org - helping tribal people around the world to own their own means of high-tech communications
I'm sure that with such a bold statement you have facts to back them up?
EIGRP is Cisco Proprietary and it actually outperforms OSPF for scalability and convergence (albeit slightly)
CDP is a licensed technology that other LAN switching companies have in fact licensed. There is a workgroup underway to standardize such technology but it doesn't exist today. Guess what its going to be based off of?
ISL/HSRP-> Both of these fall into the same category. Nothing standardized existed at the time they were developed. Cisco created their own version and submitted how they did things to the workgroup. As their became a standard (VRRP/Dot1q) Cisco has added support and even switched to those for default. Most if not all NEW Cisco LAN products only support dot1q.
Why not talk about EAP-FAST, which was submitted as an RFC and implemented by many other Authentication systems.
Oh, lets talk about TKIP/MIC. Guess who did it first? (TKIP was based off of what is now now as CKIP. Primary difference is the length of the IV)
Oh, you want OPEN as is show me the code? Nope not what he meant. Opened as in interoperability , yep see above.
Next time some apple fan boy or Cisco/Microsoft(Or insert Large Corporate entity of your choice) hater wants to post something, at least take the time to learn what the fuck your talking about.
You talkin' to me? You talkin' to me? Then who the hell else are you talkin' to? You talkin' to me? Well I'm the only one here. Now laugh...that was funny...
That is not a defense. If there are equivalent open standard alternatives, why did they feel the need to create closed ones? Answer: Because they want to institute lock-in. It's just that simple.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
You have in no way invalidated my point, and the person who modded me as a troll is a dumbfuck. If Cisco were actually interested in openness, then they would have simply published RFCs for the protocols they created and made them freely available to all. Instead, workalikes which are more or less equivalent (but are often not direct equivalents) have been developed.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Every day I manage to find moderators who serve as an object lesson for why moderation doesn't work. If I were trolling, you'd know. But I don't troll. I'm not saying that a company HAS to believe in openness - I'm saying Cisco doesn't. Implementing workalikes for protocols you've kept closed and kept control of simply to avoid the market passing you by is not equivalent to promoting openness. It's having your hand forced by the rest of the market to prevent you from taking and holding a monopoly. I know some of you can't tell the difference, but if you can't figure out what "Troll" means, then you probably can't figure this out either. Why don't you just go install Vista on your Vaios and leave me alone?
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
>What complete and utter bullshit.
>> -DRM
> I'm not going to rehash the extensive comments from this story earlier today.
So what if their DRM isn't "very strong". I can't play my legally purcahsed music under Linux. Telling the judge that it's OK for you to rape someone because you were flaccid isn't going to hold up. If Apple doesn't want to do DRM, they shouldn't. They do do it, so they're evil. End of story.
>> -Proprietary hardware
> Such as? *crickets* Surely the fact that on installing Windows on a shiny Intel Mac, all of
> the drivers outside of the keyboard backlight are from other well-known vendors like
> Atheros, Intel, ATI, etc, should disprove THAT turd.
Those three manufacturers are some of the most widely known for proprietary drivers (and buggy hardware that their drivers don't even work around very well).
>> -Proprietary software
> And who isn't, other than Linux and BSD? They are the exceptions, not the rule. Windows, AIX,
> Solaris, BeOS, PalmOS, etc - you name it, it's most likely proprietary. At least Apple makes
> a good chunk of its base open, and has contributed other useful projects like WebKit and
> launchd.
WebKit was Open Source already. launchd is useless. Apple consistently avoids giving back to the community. With a lot of crying they will release some useless code just to get everyone to shut up.
They do take a lot though, and that's what they call a commitment to open source. I guess that's fine to market it that way (Samba is better than anything Apple could come up with), but it is misleading. Without Apple, all of the open source projects that OS X uses would still be doing fine. Apple needs them, not the other way around.
>> -Closed protocols
> Such as? Hell, even protocols they've pushed (like Rendezvous/Bonjour/ZeroConf) are standardized.
Oh yeah, it's really easy to buy music from iTunes with my standard-issue web browser. It's also very easy to build custom apps for the iPod, because Apple publishes an SDK! Oh wait, that's completely false.
>> -selected compatibility
> Again, who doesn't? I'm not even sure what you mean, unless you're upset you can't play a Divx on an iPod Video or something...
iRiver manages to do this, and their products are less expensive.
>> It's CEO is also know for pulling tantrums.
> Its CEO is known for having a VERY sharp idea of what he wants, and yes, being very difficult and arbitrary to get it sometimes. Those are not tantrums. Throwing a chair, that's a tamtrum.
Yes, Microsoft and Apple are both led by small children. You're allowed to hate MS and Apple, ya know.
My other car is first.