Packet inspection/traffic management

Caspian Soaks Up $55M More

Caspian Networks Inc. received a $55 million infusion of venture capital for its “aggregation routing” and traffic shaping business, bringing its total funding to date up to $300 million (see Caspian Gets an Extra $55M).

Caspian CEO Brad Wurtz says the new funding will be used to increase the company’s sales, marketing, and customer service presence in the U.S. and Europe.

Caspian’s business comes mainly from Asia (60 percent), with lesser portions from the Middle East and Europe (30 percent) and the U.S. (10 percent), a mix Wurtz would like to be more evenly distributed. “We are very well staffed in Asia, and we will be making the majority of our investment in the U.S. and in Europe,” he says.

Caspian’s VC investors bet its "flow-based" traffic management routers will be hugely appealing now that so many different types of traffic are traversing converged IP networks. Caspian's gear can, for example, allow a network operator to recognize and assign “best-effort” service to P2P traffic, while reserving “mission-critical” bandwidth for real-time applications like VOIP and interactive gaming.

Wurtz says he expects the company to reach profitability in the second half of 2006, “depending on the markets.”

Caspian began life as a core routing company, but later retreated from the space in the face of stiff competition from larger suppliers such as Cisco Systems Inc. (Nasdaq: CSCO) and Juniper Networks Inc. (Nasdaq: JNPR). The company now has focused its efforts on what it calls “aggregation routing” and its flow-state IP QOS systems.

“Our customers have told us that they want to use us in a different place in the network, at the aggregation points where they’re aggregating lots of edge devices and then shaping the traffic –- applying congestion control and QOS mechanisms –- before it goes over the MPLS core,” Wurtz explains.

But Caspian recently scored a substantial core routing win with the Korean government; and Heavy Reading analyst Scott Clavenna believes there may yet be room in the core router marketplace for Caspian (see Caspian Scores in Korea).

“The key thing to focus on is that core routing is actually coming back, globally, as operators move to VOIP and IPTV,” Clavenna says. “So they need real QOS in their core routers, and in some cases are looking outside the duopoly of Cisco and Juniper for that.”

But while traffic management is an important and growing focus in networks supporting next-gen applications, Caspian’s “flow-state” method of traffic management is just one way to do it (see Ellacoya Stands Alone).

“I do think flow-state routing is a very hot thing; the problem is there are some competing paradigms out there,” says RHK Inc. analyst Mark Seery.

Traffic management technology from Ellacoya Networks Inc. and Cisco use “deep packet inspection” to identify exactly what applications are generating traffic in the network. Caspian’s routers, on the other hand, take a more cursory look at the traffic, examining such things as its flow rate and packet size, Seery says.

“Ultimately I think the deep packet inspection that Cisco and Ellacoya are doing is what's really needed,” he says, adding that there is currently more market demand for deep packet inspection (see Ellacoya Sees Deep Packets at Shaw). “They [Caspian] are in a very interesting space, they’re in a hot space, but they’re really the only ones that are taking the approach they are taking.”

Caspian’s Wurtz says the new funding round comprised investments from the company’s existing VC partners, and was led by Oak Investment Partners, U.S. Venture Partners, and Morgenthaler.

"It’s unlikely they can recover the whole $300 million for their investors, but maybe they can get the $55 million back that they have just put in," RHK’s Seery says.

Caspian is headquartered in San Jose, Calif., and has offices in Research Triangle Park, N.C.; Tokyo, Hong Kong, Seoul, and London.

— Mark Sullivan, Reporter, Light Reading

<<   <   Page 2 / 2
craymundo 12/5/2012 | 3:13:16 AM
re: Caspian Soaks Up $55M More As far as I understand the normal behavior of IP is to burst, so you need to add a lot of bandwidth in order to alleviate congestion.

"Bandwidth is cheap", it depends, on internet peering points and iternational links I dont think so.

Deep packet inpection boxes will achieve 10G? on a cost effective way will be difficult

Why people is more confident installing appliances on their netwoks and not better routers?
Mark Seery 12/5/2012 | 3:13:16 AM
re: Caspian Soaks Up $55M More Hi pro Caspian.

Caspian definitely has some interesting technology and as you rightly point out, there is every reason to believe it is more scalable today than deep packet inspection - that is a definite plus.

The question I think that is being missed in the dialog on this thread, is that the fundamental focus needs not to be on solving an end to end QoS problem (because no approach scales end to end today for microflows - and BTW, the comments that Caspian only operates in this mode is not true), but on unleashing revenue generating opportunities.

Some aspects of this can clearly be done with the Caspian solution, and perhaps in the short term, some of the most important aspects. The question you then have to ask is can deep packet inspection unleash a broader, more specific, and more targeted set of revenue generating opportunities. Perhaps it is the case that both approaches are complimentary. We will have to see.....

sgan201 12/5/2012 | 3:13:13 AM
re: Caspian Soaks Up $55M More Hi,

Firstly, I do not know whether Caspian router solve this particular problem that I am going to describe. But, so far all the discussion miss a very major problem in the core to access direction. Even if you make the core bandwidth as large as possible, you had just the traffic burst from core to access side worst. The core bandwidth is 10 to 100 times the access. The traffic burst will either overrun the buffer of the edge router (packet drops) or if the buffer of the edge router is very big, it will result in jitter and delay. So, there is value in have a box traffic shape the flow before it enter the edge. By doing this, you will result in less packet drop and better good throughput (goodput) of the network.

turing 12/5/2012 | 3:13:12 AM
re: Caspian Soaks Up $55M More I claim that the provider has two choices: pay to provision about 10% more bandwidth, or pay for shphisticated QoS management. In general, I contedn that the bandwidth is a wiser and cheaper choice.
The "10%" is my made-up upper bound of the maximum theoretical gain you can get using the best theoretical QoS versus a trivial diffserv-based QoS in the core.

Maybe we're saying the same thing then. I had thought you meant just increase bandwidth vs. any QoS handling. But here you sound like you're saying it's not worth the extra to pay for more than just diffserv, right? (not sure) i agree with that.

My response to no Qos at all is that even when you look at a 15-minute peak window of say 70% link utilization, if you actually zoom in to the 50-100ms window intervals inside the 15-minute, there will be 100% line rate for the whole 100ms all over the place. But even more important is that is how the 100% bursts came about - by the aggregation of lower or same-speed links. Since the aggregation happens in somewhat random bursts, there are periods during which, for example, 2 uplinks will each be feeding >50% line rate and so their sum will fill the aggregate. Any more than 100% of the aggregate and there wil be congestion and if the router doesn't have big buffers there wil be loss. So the 100% you see on the core link is of delayed traffic and some lost you dont see. The only way to buy enough BW to get out of that happening is to buy enough for all the uplinks BW put together, which is far too expensive.

My only point here is every time i hear "its only 50% or 70% utilized" i cringe.
<<   <   Page 2 / 2
Sign In