In the old westerns (often actually shot in Italy or Mexico, rather than the Western United States), when a new gunfighter strolls into town there will always be that fateful moment when someone will say, “this town ain’t big enough for the two of us.” Then some arrangement will be made to meet at dawn on the main street. In the routing world, the problem is often not too many gunfighters, but too few, particularly when it comes to routing stacks. There are a few, of course, including Cisco, Juniper, IP Infusion, Ericsson, and some other well-known names.
For those that don’t know SGTech, it is a conference focused on power companies, both distribution (DSOs) and energy transmission (TSOs). The conference focuses on how these companies can move to embrace the smart grid with substation automation, SCADA, control room technology, smart meters and telecommunications.
The original Path Computation Element Protocol (PCEP) work dates from the early 2000’s, with the first IETF RFC (4655) being made informational in 2006—which means PCEP predates the time when SDNs were “cool.” PCEP was originally, because of the increasingly complex nature of computing Traffic Engineering (TE) paths through (primarily), Service Provider (SP) networks. Three specific developments drove the design, standardization, and deployment of PCEP—
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.
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.
At several recent trade shows, most notably the NFV and Carrier SDN Event, Heavy Reading Analyst Sterling Perrin showed a slide demonstrating the industry’s long history with IP and Optical integration. One of the images on that slide is an article in LightReading from April, 2000 entitled “IP over Glass, Who Cares?”, a very interesting article to re-read from a historical perspective to see just how far the industry has progressed in 16 ½ years.
Those familiar with France’s Orange and their stated goal to transition to an all-IP network by 2020 might be confused by statements at the Next Generation Optical event in Nice in June about their trials of OTN technology. After all, how can an “all IP” network include OTN? In actuality, OTN can be a very important part of an all IP network, depending on how “all IP” is defined.
If someone wants to surf web pages, download MP3s, share photographs or watch streaming video, then the currently offered broadband services are good enough. But, this is going to change – or at least that’s what is being predicted.
It’s true, we’ve been hearing about IP address exhaustion for years. But last month, we heard an additional warning siren: the last available IPv4 addresses were allocated this month by Icann, the international body responsible for the distribution of IP addresses to Regional Internet Registries. Our local ISPs are expected to allocate all remaining addresses by 2014.