The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2002-Jun> msg00006



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

Basic LDP Question

  • From: jh@lohi.eng.song.fi
  • Date: Sat, 1 Jun 2002 08:56:44 +0300
  • 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>

Ajay Simha writes:

 > For instance I did
 > not see anyone mention things like QoS transparency that MPLS can
 > achieve. 

diffserv is a much simpler and more scalable way to achieve qos than
mpls.  if you want to use mpls for qoq, you need to start playing atm
style vc came with p-to-p subscriber resource reservations.  and if you
want to really do it properly, like some atm switches from cisco did,
you need to implement per lsp queueing in your routers.  this is 2002
and i don't want to go back to 1995.

 > 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 :).

i don't have any reason to start mimicking mpls with ip.

 > 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?

because mpls is another control plane with all the complexity that comes
with it.  check this out:

harjus:/home/ftp/internet-drafts% ls *mpls* | wc
    146     146    5619

-- juha