[Dime] #52: Throttling not needed to be based on previous history - conclusion

[Maria Cruz Bartolome <[e-mail]>]

#52: Throttling not needed to be based on previous history
 
Following agreement is reached:

 Now (chapter 4.7):
    The OC-Reduction-Percentage AVP (AVP code TBD8) is type of Unsigned32
    and describes the percentage of the traffic that the sender is
    requested to reduce, compared to what it otherwise would have sent.
 
 Proposal:
   The OC-Reduction-Percentage AVP (AVP code TBD8) is type of Unsigned32  
   and describes the percentage of the traffic that the sender is  
   requested to reduce, compared to what it otherwise would send.                  <----
 
 
 Now (chapter 5.5.2):
      Indicates that the reporting node urges the reacting node to
      reduce its traffic by a given percentage.  For example if the
      reacting node has been sending 100 packets per second to the
      reporting node, then a reception of OC-Reduction-Percentage value
      of 10 would mean that from now on the reacting node MUST only send
      90 packets per second.  How the reacting node achieves the "true
      reduction" transactions leading to the sent request messages is up
      to the implementation.  The reacting node MAY simply drop every
      10th packet from its output queue and let the generic application
      logic try to recover from it.0 < value < 100

  Proposal:
 Indicates that the reporting node urges the reacting node to reduce 
 its traffic by a given percentage. For example if the
 reacting node would send 100 packets to the				<---
 reporting node, then a reception of OC-Reduction-Percentage value of 
 10 would mean that from now on the reacting node MUST only send
 90 packets instead of 100. How the reacting node achieves the "true       <---
 reduction" transactions leading to the sent request messages is up to 
 the implementation. The reacting node MAY simply drop every 10th 
 packet from its output queue and let the generic application logic try 
 to recover from it.