To be consistent with the pseudo code and avoids the confusion of "turning on/off". How about we retitle it to “Setting PIE inactive”
-Rong ------------------------------------------ 5.3 Setting PIE active and inactive Traffic naturally fluctuates in a network. It would be preferable not to unnecessarily drop packets due to a spurious uptick in queueing latency. PIE has an optional feature of automatically turning active/inactive. To implement this feature, PIE SHOULD only become active when the buffer occupancy is over a certain threshold, which SHOULD be set to 1/3 of the tail drop threshold. PIE SHOULD become inactive when congestion is over, i.e. when the drop probability reaches 0, current and previous delay samples are all below half of QDELAY_REF. On 5/24/16, 7:40 AM, "Suresh Krishnan" <suresh.krish...@ericsson.com> wrote: >Hi Rong, > Sounds good. All your proposed changes look good but one. Please see >inline. > >On 05/23/2016 08:28 PM, Rong Pan (ropan) wrote: >>> Section 5.3: >>> >>> What does the following text intend to say? Do you mean when it is >>>turned >>> off? >>> >>> "When PIE is optionally turned on and off, ..." >> >> How about ³PIE can automatically turn on and off"? > >Not sure if this new text will make it any clearer. I was guessing more >"When >PIE is turned off,..." but was not sure. Does that make sense to you? > >Thanks >Suresh > > _______________________________________________ aqm mailing list aqm@ietf.org https://www.ietf.org/mailman/listinfo/aqm
