<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DCB on Network Janitor</title><link>https://network-janitor.net/tags/dcb/</link><description>Recent content in DCB on Network Janitor</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 02 Feb 2011 02:29:12 +0000</lastBuildDate><atom:link href="https://network-janitor.net/tags/dcb/index.xml" rel="self" type="application/rss+xml"/><item><title>DCB: How to Engineer your way out of a poor architecture decision!</title><link>https://network-janitor.net/2011/02/dcb-how-to-engineer-your-way-out-of-a-poor-architecture-decision/</link><pubDate>Wed, 02 Feb 2011 02:29:12 +0000</pubDate><guid>https://network-janitor.net/2011/02/dcb-how-to-engineer-your-way-out-of-a-poor-architecture-decision/</guid><description>&lt;p&gt;I recently gave a presentation to the New Zealand Network Operators Group (NZNOG) 2011 conference on &amp;ldquo;Data Centre 3.0&amp;rdquo;. During my research over the last 8 months coupled with the fact checking I had been following up during the creation of the slides, I kept asking myself:&lt;/p&gt;
&lt;blockquote&gt;"Would we need all these protocols if we, as an industry, had made better technology implementation decisions?"&lt;/blockquote&gt;
&lt;p&gt;I understand the background and requirements for some of the different technology proposals, particularly Layer 2 Multi-path and the various Data Centre Bridging (DCB) QoS standards, but I cant help but feel that we are trying to bring features of the higher layer protocols down into Layer 2.&lt;/p&gt;</description></item></channel></rss>