[c-nsp] Multihomed OTV on CSR Lab - Mac Address Issue

[adamv0025 at netconsultings.com]

> From: Mark Tinka [mailto:mark.tinka at seacom.mu]
> Sent: Monday, February 05, 2018 3:35 PM
> 
> Use the technology long enough for a specific application, and that use gets a
> new name (and acronym to boot). Once a new name/acronym has been
> established, vendors and other interested parties find a new way to re-
> describe the same technology as being applicable to a specific use-case, and
> re-build it in such a way to suit that particular application at a much more
> fundamental level - purpose-built software and hardware in tow.
> 
Yeah like RFC3107 used in Inter-AS Opt.C since ever and then all of a sudden "Seamless MPLS" came to save the world (well the "MPLS all the way down to each cell site" world anyways).  
  

> The talent is amongst operators knowing when a technology is just a fad, and
> not buying into it. For me, that was, and always has been, VPLS. Segment
> Routing is another one, but let me not start a war.
> 
Agreed, tell me one thing I can't do with RSVP signalled LSPs, well other than scale out related stuff -oh and I'm talking biblical per flow LSPs type of scale out. 

 
> The trick is not about knowing which technologies will actually help your
> operations and/or business, but rather, knowing which ones won't. It's a fun
> game :-)...
> 
Oh yeah a fun game it is indeed that's why most of us are in (I hope). 
But then there's also the HW side of things and my observations are that while there's a bunch of architects well versed in SW, only a handful of them invest time and effort to tell a good routing system architecture from a bad one. 
(Honestly who knows why correct settings for pre-classification, backpressure, VOQs, etc... are essential). 
I mean I can have CP doing all sorts of fantastic stuff but if the DP can't deliver datagrams in desired order or not at all if overloaded then the CP bit is useless. After all the end game is to transport data reliably and efficiently not to do fancy stuff in CP.
(The CP bit is there just to make it ever easier for Ops or AI to program the DP). 
How I see it we came a long way from manually defining exactly "what" using static routes, through defining just "how" using variety of dynamic protocols and then back to static routes/labels -now programmed by AI from a centralized controller, to close that circle soon. 

adam


netconsultings.com
::carrier-class solutions for the telecommunications industry::