The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2002-May> msg00276



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Basic LDP Question

  • From: Ajay Simha <asimha@cisco.com>
  • Date: Fri, 31 May 2002 23:15:02 -0400 (EDT)
  • cc: raszuk@cisco.com, Shahram Davari <Shahram_Davari@pmc-sierra.com>, "'Giles Heron'" <giles@packetexchange.net>, "'Yakov Rekhter'" <yakov@juniper.net>, "'mpls@uu.net'" <mpls@UU.NET>, "'ppvpn@ppvpn.francetelecom.com'" <ppvpn@ppvpn.francetelecom.com>

On Fri, 31 May 2002 jh@lohi.eng.song.fi wrote:

The point is MPLS effectively decouples the forwarding portion from the
routing. This makes MPLS a service enabler. For instance I did not see anyone
mention things like QoS transparency that MPLS can achieve. Sure you can
monkey around with IP to make IP have everything that MPLS has. May be even a
fixed length tag and call it something else :).

Why do it when this extension already exists as an IETF based standards where
folks like us can debate issues and come up with solutions that are acceptable
to most?

-ajay


>:Robert Raszuk writes:
>:
>: > Currently deployed hardware & software.
>:
>:your current router hardware can't do many other things either, like
>:learning mac addresses.  so when you re-spin it, you could also consider
>:adding real support for ip tunneling for those who don't like the
>:complexity of mpls control plane.
>:
>:-- juha
>:

--