During a workshop I spoke in at Mobile Backhaul Asia, it was quickly apparent that the crowd had large variation in experience with IP and Ethernet. Peers jumped into deep dive IP jargon without consideration that much of the crowd came to the workshop to learn about IP value – how were they expected to understand an onslaught of specialized jargon? This experience got me thinking …
·Specialized communities develop specialized vocabulary often to a fault
·Members have varying degrees of knowledge
·Using too much jargon too fast excludes broader participation in discussions
It was great to help the audience break through barriers of fear in asking their questions. This gave us all a chance to begin discussing real concerns triggered from questions like …
“I don’t see routing in my RAN. Isn’t IP overkill?”
“What’s better, Ethernet or IP?”
“How is Metro Ethernet Forum (MEF) relevant to me?”
There aren’t simplistic answers to these. Rather, these trigger dialogue that helps clarify problems and optional solutions. I use the jargon “MEF 22” in my latest blog to catch eyes, and to trigger dialogue to answer a specific question, not to exclude more generic questions. The blog opens related questions ...
Does a forum like MEF bring value to our industry?
Which is more important to you, IP MPLS Forum or MEF?
Has anyone seen MEF 18 put into practice?
Which of these questions, or related question/topic would you like to see discussed? IP is worthy of discussion.
Crosswork Cloud - Crosswork Traffic Analysis - FAQ
Crosswork Cloud - Crosswork Traffic Analysis is a Cloud-hosted Software as a Service platform that provides Netflow based Traffic Analytics. The Crosswork Traffic Analysis platform Traffic Analysis, Peeri...
Cisco Champion Radio · S8|E9 Innovations to Achieve a Trustworthy Infrastructure
How do you know for certain that a router in your network has not been altered with since you deployed it? Wouldn’t it be great if you can cryptographically challenge your r...
IOS upgrade on asr9xx mandates rommon upgrades sometimes while they can be optional at other times. You may land up in unwanted situation if proper procedure is not followed during upgrades.
This article will include complete details about rommon ...
In some situation NCS560 RP become unresponsive after reload or powercycle.
In many NCS560 deployments are in remote location, deployment might be large and human intervention should be kept at minimum
Engineering team have been working on a str...
In simple terms, 'Route Churn' is defined as the 'rate of change of prefixes'. Different XR versions across 4.x to 7.x have differing behavior & support for the BGP churn handling and some enhancements made from 6.5.3 onwards (listed in appendix) mak...