Index: draft-flows-00c.nroff =================================================================== RCS file: /usr/local/share/doc/apache/cvs/red-pd/draft/draft-flows-00c.nroff,v retrieving revision 1.9 diff -r1.9 draft-flows-00c.nroff 122c122 < been presented in [MFW01a] and [MBF+01]. --- > been presented in [MF01] and [MBF+01]. 147,149c147,159 < policy box. This box looks at all incoming packets, and decides which < of those belongs to a rate-limited flow or aggregate. Those that do < might be dropped or ECN-marked as part of the rate-limiting strategy. --- > policy box. This box looks at each incoming packet, and decides > whether to drop or mark this packet before forwarding it > to the output queue, based on the past history of the > specific flow or aggregate containing that packet. > The rate-limiter includes no queues, but merely looks at > each arriving packet one at a time. > > For example, the rate-limiter could determine if the arriving > packet belongs to a rate-limited flow or aggregate, > dropping or ECN-marking some of these packets as part of the > rate-limiting strategy [MFW01, ECB01]. > There are other proposals for rate-limiters that do not > include the explicit identification of flows [PBPS01]. 154c164,165 < not dropped here are passed onto the output queue. --- > not dropped in the rate-limiter are passed to the output queue. > 160,162c171,179 < We make no assumption about the Active Queue Management (AQM) mechanisms < in the router; it < could even be Drop-Tail (particularly if we don't use the packet drop --- > The output queue is assumed to be FIFO output queue, > optionally preceded by an Active Queue Management (AQM) > module that decides whether > to drop the arriving packet, ECN-mark it, or forward it to the > output queue unmarked. > We make no assumption about the AQM mechanism > in the output queue; it would even be a Drop-Tail queue > with no AQM mechanism at all > (particularly if we don't use the packet drop 163a181,185 > The assumption is that the > AQM module in the output queue makes drop or marking decisions > based on the level of congestion in the output queue, > rather than on the past history of the specific flow or aggregate > containing that packet. 392a415,419 > [ECB01] F. Ertemalp, D. Cheriton, A. Bechtolsheim, > Using Dynamic Buffer Limiting to Protect against Belligerent Flows in > High-Speed Networks, International > Conference on Network Protocols (ICNP), November 2001. > 407c434 < [MFW01a] Mahajan, R., Floyd, S., and Wetherall, D., "Controlling --- > [MF01] Mahajan, R., and Floyd, S., "Controlling 419a447,450 > [PBPS01] Rong Pan, Lee Breslau, Balaji Prabhakar, Scott Shenker, > Approximate Fairness through Differential Dropping, > 2001. > 463a495 >