Cisco Blogs

World Telecom 2011 October 24-27 2011

October 24, 2011 - 0 Comments

I chaired a panel at MPLS 2011 on October 17 in Washington D.C. with

  1. Scott Whyte, Senior Network Engineer, Future Networks, Google
  2. Sergei Gerasmachouk, Network Engineer, Core Wide Works, 
  3. Ning So, Data Packet Network Arch Design Lead, Verizon
  4. Guneter Honish, Senior Fellow at DT and overall Disruptor at DT

The discussion was lively to say the least! . To summarize:

  • Scott and Sergei targeted the discussion around Traffic Engineering–TEbin packing problem, TE Tool update from the past several years, creating tunnel on demand, regionalizing TE flows and so on
  • Scott spoke about an internal project he had done at Google–LSR function with Quagga for the purpose of multiplexing paths e.g. as
opposed to point-to-point constructs, e.g. data center traffic; networking
 traffic. You view the Scott’s presentation on Open Source LSR here
  • Guenter spoke about IPv6 for mobile end point addressability and implementing the FIB in a standard way for OpenSource LSR to the question “which technology has the potential to disrupt the industry,
and why?”
  • The panelists agreed that MPLS, IP, and TE are tools for specific problem areas.

The call to industry from my fellow panelists was clear:

One technology does not fit all; it’s about a dialogue on best ways to approach a problem.

Next week (October 24-27), 

I am looking forward to participating at ITU World Telecom 2011 in Geneva, Switzerland along with Cisco colleagues Wim Elfrink, Edzard Overbeek, and RM Pepper. ITU World Telecom is an event that occurs every two years. 

I will start out my week on October 25 at the third CTO meeting hosted by the ITU-T.  I’m really excited about a great panel that I will be on titled, “Girls in ICT” to be held on October 27. This session plans to be dynamic as the topic is so very important to our world.

I hope to see you all at World Telecom 2011 in Geneva!

In an effort to keep conversations fresh, Cisco Blogs closes comments after 60 days. Please visit the Cisco Blogs hub page for the latest content.