Router nets face new challenges

Phoenix - Administrators of large router networks shouldn't expect a quick, standards-based solution to scalability woes.

That was the outlook from a session at the North American Network Operators Group yesterday.

Representatives from router companies Ascend Communications, Inc., Cisco Systems, Inc. and Juniper Networks, Inc. told NANOG that the Internet Engineering Task Force has no plans in the works for a solution to the problems network operators are facing.

"The sky isn't falling, but it is lowering perceptively," said Dave Katz of Juniper Networks. "The existing protocols are 10 years old. They were designed for a simpler, gentler time."

He added that the current protocols are "naïve" and are showing signs of cracking because they were not built to support "Web URLs on TV commercials."

Curtis Villanizar of ANS Communications, Inc., said that while backbone providers have largely solved problems related to overall network stability and congestion, they now have to deal with a new set of issues.

These include real-time multimedia applications and implementation of IPv6. Also, new designs such as the inclusion of Layer 2 technology and underlying switched technologies require different solutions, he said.

One possible answer on the horizon is Multi-Protocol Label Switching (MPLS), which applies a label so that internal routers do not have to analyze traffic. According to attendees, an actual MPLS standard could be two years down the road. Cisco's Tag Switching is based on this proposed standard.

However, some attendees were skeptical whether MPLS and Tag Switching will help the problem of congested routers and route traffic more efficiently or if they will simply create more overhead, further clogging networks.

"It's not the golden egg," said Jeff Wabik, principal network architect with Ascend. "There are so many problems that need to be solved, [MPLS] could be just changing the problem."

"There are no direct replacement of current IP protocols," said panelist Dave O'Leary of Cisco. He attributed the problems with research and development in this area to "the underinvestment in building fast router technology."

O'Leary added there is also a critical need for better tools for managing and monitoring routing protocols and quality of service."It needs to be more coordinated," he said, adding that network managers dealing with one area of a network do not communicate with other managers in charge of other areas.