<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="Tahoma">I think it's less about just the forwarding
chips and more about an entire solution that someone can go and
buy without having to fiddle with it.<br>
<br>
You remember the saying, "Gone are the days when men were men and
wrote their own drivers"? Well, running a network is a full-time
job, without having to learn how to code for hardware and
protocols.<br>
<br>
There are many start-ups that are working off of commodity chips
and commodity face plates. Building software for those disparate
hardware systems, and then developing the software so that it can
be used in commercial deployments is non-trivial. That is the
leverage Cisco, Juniper, Nokia... even Huawei, have, and they
won't let us forget it.<br>
<br>
Then again, if one's vision is bold enough, they could play the
long game, start now, patiently build, and then come at us in 8 or
so years. Because the market, surely, can't continue at the rate
we are currently going. Everything else around us is dropping in
price and revenue, and yet traditional routing and switching
equipment continues to stay the same, if not increase. That's
broken!`<br>
<br>
Mark.<br>
</font><br>
<div class="moz-cite-prefix">On 19/Jun/20 13:25, Robert Raszuk
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAOj+MMGLzg5TpGEQxNENgWo22ez27+=PDoxyJn_KFy=2VDyyFQ@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">But talking about commodity isn't this mainly Broadcom ? And is there
single chip there which does not support line rate IP ? Or is there any
chip which supports MPLS and cost less then IP/MPLS one ?
On Fri, Jun 19, 2020 at 1:22 PM Benny Lyne Amorsen via cisco-nsp <
<a class="moz-txt-link-abbreviated" href="mailto:cisco-nsp@puck.nether.net">cisco-nsp@puck.nether.net</a>> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
---------- Forwarded message ----------
From: Benny Lyne Amorsen <a class="moz-txt-link-rfc2396E" href="mailto:benny+usenet@amorsen.dk"><benny+usenet@amorsen.dk></a>
To: <a class="moz-txt-link-abbreviated" href="mailto:cisco-nsp@puck.nether.net">cisco-nsp@puck.nether.net</a>
Cc:
Bcc:
Date: Fri, 19 Jun 2020 13:12:06 +0200
Subject: Re: [c-nsp] Devil's Advocate - Segment Routing, Why?
Saku Ytti <a class="moz-txt-link-rfc2396E" href="mailto:saku@ytti.fi"><saku@ytti.fi></a> writes:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">This is simply not fundamentally true, it may be true due to market
perversion. But give student homework to design label switching chip
and IPv6 switching chip, and you'll use less silicon for the label
switching chip. And of course you spend less overhead on the tunnel.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
What you say is obviously true.
However, no one AFAIK makes an MPLS switch at prices comparable to basic
layer 3 IPv6 switches. You can argue that it is a market failure as much
as you want, but I can only buy what is on the market. According to the
market, MPLS is strictly Service Provider, with the accompanying Service
Provider markup (and then ridiculous discounts to make the prices seem
reasonable). Enterprise and datacenter are not generally using MPLS, and
I can only look on in envy at the prices of their equipment.
There is room for a startup to rethink the service provider market by
using commodity enterprise equipment. Right now that means dumping MPLS,
since that is only available (if at all) at the most expensive license
level. Meanwhile you can get get low-scale BGPv6 and line-speed GRE with
commodity hardware without extra licenses.
I am not saying that it will be easy to manage such a network, the
tooling for MPLS is vastly superior. I am merely saying that with just a
simple IPv6-to-the-edge network you can deliver similar services to an
MPLS-to-the-edge network at lower cost, if you can figure out how to
build the tooling.
Per-packet overhead is hefty. Is that a problem today?
---------- Forwarded message ----------
From: Benny Lyne Amorsen via cisco-nsp <a class="moz-txt-link-rfc2396E" href="mailto:cisco-nsp@puck.nether.net"><cisco-nsp@puck.nether.net></a>
To: <a class="moz-txt-link-abbreviated" href="mailto:cisco-nsp@puck.nether.net">cisco-nsp@puck.nether.net</a>
Cc:
Bcc:
Date: Fri, 19 Jun 2020 13:12:06 +0200
Subject: Re: [c-nsp] Devil's Advocate - Segment Routing, Why?
_______________________________________________
cisco-nsp mailing list <a class="moz-txt-link-abbreviated" href="mailto:cisco-nsp@puck.nether.net">cisco-nsp@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-nsp">https://puck.nether.net/mailman/listinfo/cisco-nsp</a>
archive at <a class="moz-txt-link-freetext" href="http://puck.nether.net/pipermail/cisco-nsp/">http://puck.nether.net/pipermail/cisco-nsp/</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">_______________________________________________
cisco-nsp mailing list <a class="moz-txt-link-abbreviated" href="mailto:cisco-nsp@puck.nether.net">cisco-nsp@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-nsp">https://puck.nether.net/mailman/listinfo/cisco-nsp</a>
archive at <a class="moz-txt-link-freetext" href="http://puck.nether.net/pipermail/cisco-nsp/">http://puck.nether.net/pipermail/cisco-nsp/</a>
.
</pre>
</blockquote>
<br>
</body>
</html>