The MPLS WG Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] CR-LDP traffic parameter TLV and RSVP
Hi, > -----Original Message----- > From: David Charlap [mailto:david.charlap@marconi.com] > Sent: Tuesday, September 26, 2000 10:34 AM > To: mpls@UU.NET > Cc: rsvp@ISI.EDU; int-serv@ISI.EDU > Subject: Re: CR-LDP traffic parameter TLV and RSVP > > > Curtis Villamizar wrote: > > David Charlap writes: > >> > >> (And if you want to only use one LSP per DiffServ class, then you > >> don't have to signal the class at all - you can just > signal QoS for a > >> bunch of LSPs and let the edge routers do all the DiffServ work.) > > > > This is a unique idea. How does the router at the edge do WFQ or > > implement the three drop preferences for an AF class? :-) > > It doesn't. It picks IntServ parameters that approximate the > QoS level > required for each DS class and uses them when signalling the tunnels. > If the LSPs are signalled using the COS-type of TSpec and > FlowSpec, then > the switches in the cloud will have to have some sort of > agreement about > what the non-zero classes are supposed to mean. > > All the edge router does on the data plane is use the DS bits to pick > which tunnel to forward the traffic into. If the tunnels > have different > QoS or priority levels, then the different DS classes will end up with > those levels as well. It seems that you are mapping Diffserv PHBs to Intserv classes. In other words you want an Intserv network to behave like a PHB. This seems odd to me, and probably of no real world use. > > In this setup, the MPLS cloud is not actually using DS at all - it's > simply mapping the DS classes onto tunnels have their own > QoS/COS levels > that are signalled independantly of any DS signalling. > > -- David >
|
|