To: ahhaha who wrote (3383 ) 7/20/2001 10:29:02 PM From: Frank A. Coluccio Read Replies (1) | Respond to of 46821 The street cuts that are done to create rings in metro settings can be leveraged to satisfy numerous customers along the circumferences of those rigns (and physical ring circumferences in metros usually interlock with one another on at least one side, leaving mutlipe paths of egress for any user), whose locations adjace them. In order to create a physical mesh in the metro that is unuiquely tailored for each individual end users end points, discreet street cuts have to be made for every location, or discreet locations need to backhaul their traffic - in a Pyrrhic victory sense - to metro fiber pops in an awkward and costly manner. It's the railroad station syndrome that we're dealing with here. People take their cars or car pool to the train station. Railroads don't lay track to every passenger's home. Rings have self-healing technologies. They restore themselves within so many miliseconds (typically 50 ms terrestrially). Meshes usually take much longer to converge if they are entirely dependent on IP for doing so, which results in lost sessions and SLA penalties, because they time out <read: the session is lost> before convergence <read: recovery> takes place. To satisfy your assertion and implied questions concerning recovery... in the railroad analogy, the railroad would have to lay track to every passenger's home, and then have a second route to get there in case there is a blockage along the first route. In order to achieve this, we're talking street cuts. To achieve the same thing in the WAN (using, say, an Avici <or anyone else's, for that matter> router> we're only talking about leveraging long haul carriers existing routes. The grief is amortized across greater distances and a far greater number of users. Which, in turn, translates to the capability of satisfying the diversity needs of many, as opposed to those of just one or two users at a higher unit cost per. Let me know how you make out with Duffy. Tell him I said hello. In case you didn't notice, I left his forwarding information at the bottom of the post for this very reason: From the bottom of my original post, "... to contact Jim Duffy... he can be reached at jduffy@nww.com " I can't answer on his behalf for all of his asertions, although I think he's right on most of them.