[e2e] [Fwd: State of MPLS deployments today]

[Ping Pan]

David,

You're right. I take that back. In fact, given that MPLS path setup is 
pre-determined at edge (or an "end"), there are a number of methods that 
you can apply to compute the "best" route across the network. Or the 
"ends" can monitor end-to-end traffic pattern and feed such information 
to operators for future traffic management. Or the "ends" can perform 
traffic flow aggregation into MPLS trunks. If you don't have to worry 
about 50 msec circuit recovery constraints, you can interface with 
routing protocols to fast-reroute traffic...

BTW, stop thinking it as an ATM technology. Think of it as a logical 
interface that you can pump IP traffic into. :-)

Take care!

- Ping

David P. Reed wrote:
> At 11:30 AM 10/3/2002 -0700, Ping Pan wrote:
> How did this topic get into this list anyway? It has nothing to do with 
> e2e. ;-)
> 
> Yes and no.   It has nothing to do with e2e, because MPLS is putting 
> function into the network.  It has everything to do with e2e, because 
> the function in the network probably is better done outside the network 
> in most cases (especially when deriving the labels is predicated on 
> reading the content of end-to-end streams that should not be interpreted 
> by the transport layers).