Any thoughts?
- Check "Simon" on LinkedIn, to verify his credentials.
- Wear a tinfoil hat.
Any thoughts?
Apple do not like critiscm and now you have posted the emails on a public forum it could potentially open a rather large can of worms.
When you start talking lawyers, I would think it is best to leave it to the Cisco engineer and his attourney to decide whether it is worth continuing on this path. Apple do not like critiscm and now you have posted the emails on a public forum it could potentially open a rather large can of worms. Your friend would need to have a good lot of money backing him, along with concrete evidence to take Apple on with this matter.
Cisco guy spoke with an attorney who told him to watch out - that this may be some type of trap...
Ok, my Cisco engineer is more specific below:
======================
It's a public forum for public opinions.
There's no disclaimer in Apple's emails, are there?
Unless there's small print saying that the information given is only for the intended recipient, etc then there's no issue.
People need to stop being so paranoid.
'Cisco' certs are hardly something to brag about. They give them away like candy.
When it comes down to Cisco yes, but when it comes to more general topics they are completely in the dark. This is a big problem with something like CCNA. It pretends to teach people networking but it doesn't. It teaches you how to use and configure Cisco switches and routers. I've seen too many Cisco certified engineers lacking basic networking knowledge. In other words, it's not about having certifications, it's about having actual knowledge. Being a Cisco engineer can look very cool but they don't hire you for your coolness. Nowadays the market gets flooded with Cisco certified people which devaluated the Cisco certification a lot. Where I live being Cisco certified doesn't mean much because of that.BTW, Cisco engineers tend to know their stuff. I went to a pretty good engineering school, and the EE/CMPE's were lining up to try to get interviews with them.
When it comes down to Cisco yes, but when it comes to more general topics they are completely in the dark. This is a big problem with something like CCNA. It pretends to teach people networking but it doesn't. It teaches you how to use and configure Cisco switches and routers. I've seen too many Cisco certified engineers lacking basic networking knowledge. In other words, it's not about having certifications, it's about having actual knowledge. Being a Cisco engineer can look very cool but they don't hire you for your coolness. Nowadays the market gets flooded with Cisco certified people which devaluated the Cisco certification a lot. Where I live being Cisco certified doesn't mean much because of that.
Cisco is also known for a lot of incompatibility problems and other very strange networking problems (their ios is known for this). It's also very likely the Cisco equipment is causing the problems. In the world of wireless networking one needs to remember that wireless signals are very unreliable and very unstable. If something is a bit wonky it can cause a lot of very strange problems or things simply don't work properly for some strange mysterious reason.
Umm.....you may want to do a bit of research on what it takes to get the CCIE certification before you further stick your foot in your mouth. Its not your typical read a book and take a test on a computer scenario. What level of education do you have in the wireless networking field that makes it so easy to knock down and marginalize this guy's experience? My guess would be none or barely better. Please feel free to correct me if I'm wrong.'Cisco' certs are hardly something to brag about. They give them away like candy.
When it comes down to Cisco yes, but when it comes to more general topics they are completely in the dark. This is a big problem with something like CCNA. It pretends to teach people networking but it doesn't. It teaches you how to use and configure Cisco switches and routers. I've seen too many Cisco certified engineers lacking basic networking knowledge. In other words, it's not about having certifications, it's about having actual knowledge. Being a Cisco engineer can look very cool but they don't hire you for your coolness. Nowadays the market gets flooded with Cisco certified people which devaluated the Cisco certification a lot. Where I live being Cisco certified doesn't mean much because of that.
The Cisco guy with the complaint further explained to me how he has solidly demonstrated that the iPhone will not upload more than about 6Mbps on TCP over wifi, whereas UDP works fine. Above the 6Mbps tcp he shows at least 50% packet drop every time. Can anyone confirm this?
Also, Apple's Vice President of Core OS Software Engineering, Simon P., keeps emailing me asking me to help him get in touch with my Cisco guy to help address his iPhone complaint. Cisco guy spoke with an attorney who told him to watch out - that this may be some type of trap... if apple feels threatened they could sue Cisco guy for knocking their product, and if Apple finds out who the contact is it could even lead to the pulling of a certain app from the App Store - severely affecting a certain app dev (not the Cisco guy).
Any thoughts?
I didn't get sued, harassed or anything by Apple when I shared "Steve's" email he wrote to me telling me to hold my iPhone 4 differently. And I think that email/incident blew up a little more than this technical issue would.
If the Cisco guy felt he had to get an attorney involved for what should have been a very simple bug report, then that's unfortunate. If he's going to stop the dialog on what could have been a productive conversation between two vendors who inevitably will have to work together to solve any interoperability issues becuase he feels it's a "trap," then I guess Cisco engineers can't be as awesome as we think.
People criticize Apple all the time and don't get sued for it, and never consult an attorney about it.
Can anyone here with an iPhone confirm or deny my Cisco guy's complaint (see original post) with iPhone - complaint being that the iPhone begins to show about 50% packet loss at around 6Mbps throughput under TCP, effectively limiting TCP throughput to 5-6Mbps on the iPhone. UDP shows no such issue.
And I don't know what version of hardware he was testing on but he says it's an issue with the "TCP stack" which would be software.
I'm just curious if anyone else has noticed this. I don't have an iPhone to test. I might get an iPhone 4 in the next few days though.
Can anyone here with an iPhone confirm or deny my Cisco guy's complaint (see original post) with iPhone - complaint being that the iPhone begins to show about 50% packet loss at around 6Mbps throughput under TCP, effectively limiting TCP throughput to 5-6Mbps on the iPhone. UDP shows no such issue.