Over the years, Cisco has been very instrumental in the design and standardization of many networking protocols. There are lots of examples where a need for a protocol was identified and Cisco filled the need with a Cisco-proprietary protocol. Cisco-proprietary can sound bad, but it really isn’t. Let’s give them some credit here – network equipment vendors are in competition and don’t typically play well together. Often times vendors pitch proprietary solutions in an attempt to carve out a niche that delineates them from their competitors.
There are several standards organizations in existence today (IEEE, IETF, CableLabs, etc.) which many vendors work with and closely follow. While this sounds ideal (and is very beneficial), standards often take a significant amount of time to be ratified, leaving any current needs unaddressed from a standards perspective. The only alternative (for a quick resolution) is a proprietary solution, while the standards process is given time to complete. Read more »