Collection of useful, relevant or just fun places on the Internets for 16th February and a bit commentary about what I’ve found interesting about them:
Does FCoE require DCB Ethernet? – Brass Tacks – If you don’t understand this answer, you don’t want FCoE. You would be better off with a protocol that can reliably handle a bad design.
From a practical point of view, I wouldn’t even consider using a FIP Snooping Bridge, ENode or FCF that does not support PFC, ETS and DCBX. To figure out why, you’ll need to read the theoretical answer…
Google’s Free Public DNS Load Tops VeriSign, Raising Dot-Com Contract Tender Question – Thanks American taxpayers!
With more than 100 million dot-com domain names registered, VeriSign generates nearly $800 million per year in revenues from the public, with infrastructure costs and load that are comparable to a service provided by Google absolutely free. This should clarify the extent to which ICANN and VeriSign are gouging the public. It certainly does not cost Google $800 million/yr to run their Public DNS service.
The topic of ownership of DNS root servers is a recurring theme. And with Media companies appear to be using and influencing the US Government to enforce protection of their business models, it’s probably going to get worse before it gets better.
10 Omnigraffle tips you might not know (plus one bonus!) | Viget Advance – If you’re a grizzled ‘graffle veteran or someone who reads manuals, some of these might be old hat. But maybe not – so check them out. If you’ve got any of your own, post them in the comments.
The birth of a new revision: 802.11-2012 – The story behind the 802.11-2012 standard. Just to remind you that there were real people who write the standards.
The Junosphere Experience, Part One – Getting Access | My Network Stories – A personal experience with Junosphere. I had the similar problems and have given up even considering using it for study. If you plan to study Junos (and you should), the barrier is that you will have to locate some hardware and software to make that happen. It’s my view the Junosphere is for well funded Service Providers to test their network designs – it’s not for normal people to use.
Strategists and chief technology officers (CTO) will be concerned that this will mark a seismic shift in the data centre and that the era of the stand-alone storage supplier is coming to an end. The stand-alone storage suppliers have got to get deep into the converged stack platform business or face the same fate as mammoths and sabre tooth tigers.
Customers are going to buy storage as part of a system, like a car, and not as their own selected and integrated best-of-breed parts. Of course they might rent the system – from the cloud data centre equivalent of Hertz and Avis rent-a-car – but that doesn’t alter the basic fact.
I’m having thoughts that EMC is attempting to tighten it’s control over VMware. If the convergence continues and affects EMC storage revenue I guess they could close the stack completely, like Oracle does, with their own servers. That’s not too far from the Greenplum / Data Domain model already. Interesting times.
Cisco Nexus Hardware – Graffletopia – This is a stencil with the current Cisco Nexus Models, Linecards, and Extra Card add-ons.
writes Reginald Braithwaite, (5 stories to read this weekend) – Excellent take on how old industryies attempt to prevent death
They tell us that only a “managed economy” for intellectual “property” will preserve jobs, and that ifthe serfs have more “freedom,” this will actually lead to slavery. The warn us that roving bands of pirates are living it up like drug barons on movie downloads. They explain how they need the senate to grant them special, temporary powers to download the contents of your phone or laptop when you cross the border, they explain why they need to send violent special forces police to arrest and extradite the owners of a file downloading business, they explain why they need to monitor the entire world’s tweets looking for jokes in poor taste.
Let’s make TCP faster – The official Google Code blog – Google based research is proposing some enhancements to the TCP protocol to improve the performance of the network. It’s probably about time that we started to consider this type of changes -TCP was deisgned when 64K lossy circuits were the norm.
Our research shows that the key to reducing latency is saving round trips. We’re experimenting with several improvements to TCP. Here’s a summary of some of our recommendations to make TCP faster:
Most exciting changes to TCP in years and long overdue. Microsoft or Cisco has never taken leadership on this topic so it’s up to a software company to drive this change. I find this sad – Networkers should be leading this change, not operating systems or web software.