Your points are interesting, Ken, and I'm enjoying this discussion between you and James, et al. I'll concede that much of this is open to interpretation of vendor spin, and keeping track of the evolving lexicon of the industry, not to mention the actual underlying technologies ;)
In one statement you speak of multi-service switching. Here, I suspect you are speaking of those services which folks can and have actually used, such as legacy ATM, MPLS, and I'll alsoo include basic IP, albeit at very high speeds (POS) as a part of that suite.
In your next point, however, you speak to 000. IMO, you can't have it both ways right now. Maybe later, but not now.
If you want multi-service legacy application switching and routing, then you will, during the near to intermediate terms, at least, find plenty of very-ultra-dense silicon working overtime, electronically in the background, and in many cases doing the same things as a very-large digital cross connect (a la Tellabs) on the back ends of these things. In fact Tellabs actually has a DCS that does this using optical interfaces, too. I believe it's their 6700 box.
In any event, the front ends to these boxes may appear to be oo, and in many cases they are (on the i/o side) but in the background there is a lot of 'e' going on, to be sure.
That's why in an earlier post on nFCTF I stated that ooo may actually be coming into its own in some boxes, but it really requires that you specify the part of the architecture (as opposed to the vendor's marketecture;) being addressed. FWIW.
See my introductory statements at:
Message 15466167
FAC |
