The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2000-Jun> msg00403



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

parameter QoS in mpls network

  • From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
  • Date: Mon, 19 Jun 2000 11:15:41 -0400
  • Cc: "'From MountIsland With Love'" <ahsanul@students.itb.ac.id>, <mpls@UU.NET>
  • Importance: Normal


Curtis writes:

> -----Original Message-----
> > In other words MPLS signaling (RSVP-TE, CR-LDP) gives you
> the ability to
> > signal BW, but there are other protocol layers that provide
> the QoS, not
> > MPLS. In other words MPLS in orthogonal to QoS but it
> facilitates providing
> > QoS.
> >
> > -Shahram
>
> You are making very strong statements regarding features that you
> claim that MPLS doesn't have.
>
> <snip>
> Although so far bandwidths on MPLS tunnels have been based on
> configured values based on historic data, bandwidths could also be
set
> based on (filtered) measurements of traffic.
>
> The statement that MPLS is orthogonal to QoS is simply not true.

Curtis,

I can't understand why you have a problem with what Shahram says. As
you know, there are three distinct aspects relevant to QoS
provisioning:

1. Signaling for QoS (on per packet, or per traffic aggregate basis)
2. Packet queueing and Scheduling to Provide QoS (the services are
actually provided at the IS)
3. Provisioning paths capable of providing needed QoS ( a: Routing
with TE support + b: Path signaling)

MPLS only does part (b) of 3. Steps 1 and 2 are done by Diff-Serv
specs (though signaling of 1 is also re-mapped, and joined with 3(b)
in mpls diff-serv draft). I think that's what Shahram was saying.

Cheers,

--brijesh
Ennovate Networks Inc.