Collection of useful, relevant or just fun places on the Internets for 16th March 2014 and a bit commentary about what I’ve found interesting about them:
Mozilla scraps Firefox for Windows 8′s Metro citing low adoption of the platform – The Next Web – Mozilla Foundation is abandoning development of Firefox for Windows 8 Metro:
Unfortunately, Nightingale says that as the team built, tested, and refined the product, Metro’s adoption has remained “pretty flat” and that Mozilla should focus its efforts “in places where we can reach more people.” While millions of people test pre-release versions of Firefox desktop on any given day, he notes the company has “never seen more than 1000 active daily users in the Metro environment.”
Possible has Internet Explorer better acceptance in Windows 8 or maybe there are so few actual users that no one needs it. Either way, another sign the Windows 8 is not popular. What interesting is that many Enterprise companies have Firefox as the corporate standard and I wonder if they will switch back to Internet Explorer which would require Enterprise IT to overcome the perception that IE is insecure.
Best of Interop – Look at the Categorisation | LINDSAY HILL – Lindsay Hill points out that SDN is already part of normal networking in the Interop “best of” awards.
The first two I expect to see there – a core (but innovative) networking technology, and a new hardware device. But what about HP’s SDN/Lync application? Doesn’t that belong under the SDN category? I think we’re going to see more of this in future – the controller and related parts falls under the SDN category, but the applications will be in a more specific category
White Boxes Don’t Scale | Light Reading – Seeing articles in mainstream media with anti-whitebox opinion probably indicates whitebox is serious threat, real challengers & incumbents are fighting back.
White-box switches, built using commodity components and running OpenFlow software, don’t scale and won’t replace proprietary switches from Cisco Systems Inc. (Nasdaq: CSCO), Juniper Networks Inc. (NYSE: JNPR), Alcatel-Lucent (NYSE: ALU), and so on, according to Randy Nicklas, executive vice president for engineering and chief technology officer for Windstream Communications Inc. (NYSE: WIN). Nicklas spoke at a panel discussion on “The ‘IT-ization’ of Telecom and Its Implications” here.
Weighing AWS VPN Options | Herding Packets – Bob McCouch writes about his options:
Earlier this week, a client asked for some assistance in building a VPN from their corporate office to Amazon Web Services for a project they were doing. I’ve done this a few times before, a few different ways, so I proceeded to give my client some pros and cons of the two most common methods I’ve used. After putting that analysis together, I realized it could be helpful for others so here it is (with the addition of a few snazzy diagrams!).
Random technical bits and thoughts: OVS Acceleration – Are you reading between the lines? – Srini writes the Net Sec Info blog about OVS performance.
Note that isolation using firewall, tuntap interfaces & VxLAN-over-IPsec today use Linux Kernel capabilities. If OVS datapath is in user space, then packets anyway have to traverse through the Kernel (some times twice) to avail these capabilities, which even may have lot more performance issues over having OVS datapath in Kernel. I will not be surprised, if the performance is lot lower than native OVS kernel datapath.
RFC 7149 – Software-Defined Networking: A Perspective from within a Service Provider Environment – Some of the dumbest, overblown and least informed writing I’ve seen on SDN in quite some time. The IETF continues to go downhill into mediocrity.
It is not meant to endlessly discuss what SDN truly means but rather to suggest a functional taxonomy of the techniques that can be used under an SDN umbrella and to elaborate on the various pending issues the combined activation of such techniques inevitably raises. As such, a definition of SDN is only mentioned for the sake of clarification.
Technician vs Consultant Writing | LINDSAY HILL – Lindsay Hill continues his blogging blitz with a piece on technical writing
Many engineers struggle with business writing. They get easily lost in detail, and produce tortured documents that are technically correct, but of little business value. This is classic “technician” or “engineer” writing. Here’s some guidance for producing “Consultant”-style documents will be far more use to the organisations you’re working with.