The last post on the topic of interface to the routing system (I2RS) discussed use cases; this one will provide an overview of the I2RS architecture, and then consider some challenges in the neighborhood of I2RS. The architecture of I2RS is considered in the illustration below.
This is the sixth in a series of blogs on the topic of the evolving enterprise WAN that is based on a survey that was completed in May 2016 by 110 network professionals. The previous blogs were:
Whether for economic reasons, political reasons, and social reasons, every industry is working towards lowering overall energy consumption and carbon footprint. In the telecom industry, the increasing demand for bandwidth has made this a difficult goal. However, the modern networking industry can make a strong claim towards being a leader in the green movement.
Every time I read a trade article or go to an event, it’s always about some new breakthrough in telecoms technology or service delivery: NFV, SDN, 400G, SD-WAN, E-VPN, Alien Superchannels, CDC-F. The list goes on and on. You’d think consumers are more demanding than ever and that service providers are rapidly evolving their networks to keep up.
Topics: Enhancing Network Efficiency
Through this (probably far too long) series on SDNs, we have looked at BGP, Fibbing, and Openflow. BGP and Fibbing would be described as augmented control planes; the distributed control plane is not replaced, but rather augmented with a controller that modifies the best path decisions of the control plane by interacting with the control itself in a somewhat “native” way.
This is the fifth in a series of blogs on the topic of the evolving enterprise WAN that is based on a survey that was completed in May 2016 by 110 network professionals. The previous blogs were:
The recent announcement that Facebook has developed an open-source, white-box optical transmission platform has led some pundits in the industry to predict the imminent death of traditional optical vendors. While there will certainly be an impact, that prediction is significantly premature.
In 2012, an executive who worked for one of the largest European service providers shared his dream with the attendees of Layer123’s first software-defined networking (SDN) & OpenFlow World Congress in Darmstadt, Germany. According to him, the reason for all the misery in carrier-land were not permanent price battles, flat-rates, and cut-throat competition; it was us, the vendors.
Openflow is the “father of software defined networks” in the minds of many engineers. To understand Openflow, however, you cannot just look at the protocol itself; rather you must go back to the beginning, in the mists of old networking.