Collection of useful, relevant or just fun places on the Internets for 6th June 2012 and a bit commentary about what I’ve found interesting about them:
Cyclomatic Complexity of OpenFlow-Based SDN May Drive Market Innovation – Don;t know what Cyclomatic Complexity is ? Me either. But Lori uses it to makes a case against controller based networking (even though that’s fundamental to F5 products)
This particular pseudocode has a cyclomatic complexity score of 3, as there are three distinct paths through the logic. Needless to say, the actual cyclomatic complexity of a real implementation is likely to be much, much higher as the matching and classification of packets is likely to be far more detailed and require more inspection of data.
TRILL:Fine Grained Labelling (DRAFT Proposed Standard) – There are many ways to have more than 4096 VLANs. Here is another, more likely solution instead of software overlay networks. Also, a key talking point for SPB protocol – this is a feature parity from what I can understand.
RFC 6478 – Pseudowire Status for Static Pseudowires – Because the telco’s and service providers just can’t forget about point to point dedicated circuits. Lets go back to the good ol’ days.
Choose your networking equipment with RIPE-554 « ipSpace.net by @ioshints – Tips on how to select equipment that supports IPv6 – yes please.
Jan didn’t stop there – he gathered a great team of co-authors, they spent over a year polishing RIPE-501-bis, included tons of comments from the RIPE IPv6 mailing list, and the result has just been published: RIPE-544, a document that you can use during the equipment evaluation and in the RFP creation process.
Juniper Lab Experiences – My second attempt at JNCIE-ENT « Network Janitor – Kurt talks about his recent JNCIE experiences.
Big Switch Networks – OpenFlow interoperability testing suite from Big Switch. Given that you might want buy Ethernet hardware from different vendors. more useful – validating that your Cisco or Brocade switch is _really_ OpenFlow compliant ……… because it might be OF1.0 compliant but not OF1.1 and there are really big differences between these standards.
Moral of the story: don’t say “Class B network” or “Class C network” if what you really mean is “slash sixteen” or “slash twenty-four.” You will sound like you know what you’re talking about.
HP’s Latest Cuts: Will It Be Any Different This Time? | Twilight in the Valley of the Nerds – Brad Casemore looks at HP and it’s seemingly intractable business problems. In spite of great engineering, the leadership is still struggling to get things right:
Unfortunately, it hasn’t only been restructuring. HP also has been an acquisitive spendthrift, investing and operating like a drunken, peyote-slathered sailor. The situation must change. The people who run HP need to formulate and execute a coherent strategy this time so that other stakeholders, including those who still work for the company, don’t have to pay for their sins.
HP has every chance to get back in the networking game and they have some great technology to compete with. I trust that the future is improving because they deserve to be there.
What does Arista, Insieme & Vyatta have in common? Implications to SDN – Interesting point of view about Vyatta and Arista:
Cisco is not the only company with a spin-in strategy. Clearly, Arista is one. While I don’t have any inside knowledge of Arista plans, I suspect that it’s only a matter of time (and maybe IPO) before Andy spin’s Vyatta into Arista to become the Arista Security Services Software Module on their switching platform or use Vyatta to expand their software offerings for Cloud Service Providers.
Jon Rafman – Collection of extraordinary images from Google Maps – life, death,sex and everything inbetween. Too much humanity for me to comprehend.