RE: [RPRWG] a problem about B-CIR
Jiangzhou,
Don't think of the "shapers" in the MAC as maintaining shaping queues. Think of them as shaping the traffic based on queues maintained in the client. (Whether the client maintains 1 queue for all B and C, 1 for all B and 1 for C, or 1 each for B-CIR, C-EIR, and C does not matter to the MAC or to this discussion.)
The prioritization of B-EIR over C is done by the stage queue state machine which accepts B-EIR frames in preference to C frames.
There is no advertisement of rateA1 or rateB. The algorithm has been designed to guarantee that each station gets their allocated rateA1 and rateB without them being advertised, as long as the sum of all allocated traffic does not exceed the capacity of the links over which they flow.
jl
-----Original Message-----
From: Jiang zhou [mailto:zjiang@xxxxxxxxxxxxxxxxxxx]
Sent: Saturday, March 29, 2003 12:15 AM
To: RPRWG (E-mail)
Subject: [RPRWG] a problem about B-CIR
Hi,ALL
I have two simple problem on the draft2.1.
If the client's traffic B-CIR enter the shaperB and B-EIR enter the
shperC. How to guarantee the class B traffic in shaperC has high priority
than class C in shapeC?
The classA0 can be informationed to other stations by TLV message on the
ringlet. But how to information the B-CIR rate? If the other station don't
konw the each station B-CIR like the rateA0, how to guarantee the allocated
B-CIR for a station?
Best Regards
Jiangzhou