The IESG has approved the following document:
- 'Diameter Overload Rate Control'
  (draft-ietf-dime-doic-rate-control-11.txt) as Proposed Standard

This document is the product of the Diameter Maintenance and Extensions
Working Group.

The IESG contact persons are Warren Kumari, Ignas Bagdonas and Ben Campbell.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dime-doic-rate-control/





Technical Summary

In the Diameter Overload Indication Conveyance (DOIC) base solution, the 
default algorithm to support is the "loss" algorithm, used to request a 
percentage reduction in the amount of traffic received. The present document 
defines a new algorihtm, "rate", that is used to announce a maximum rate 
instead of a percentage of requested traffic reduction. Highlighting the limits 
of the loss algorithm, this new algorithm is designed to better handle spikes 
in traffic. It heavily relies on the rate-based algorithm defined by the SIP 
Overload Control working group adapting to the DOIC solution and the Diameter 
protocol.

The algorithm used to estimate a target maximum Diameter request rate is left 
out of scope of this document but some recommendations are given.
Any algorithm can be used to limit the message rate to comply with requested 
maximum sending rate. However, a default algorithm is described in the document.

Working Group Summary

The document received a large support for adoption when initiated and it has 
been reviewed multiple times, with detailed comments and corrections.  There is 
a strong WG consensus on the content of this document, with a broad range of 
people, including key experts. 

Document Quality

The proposed solution has not been implemented yet, as vendors are waiting for 
IANA AVP code value assignment before implementing.  However, no issues are 
expected with implementation. Moreover, the solution defined in this document 
inherits from the work done for SIP. It is known that 3GPP operators want to 
use this rate-based mechanism instead of the loss algo in their network, using 
a similar mechanism in SIP/IMS. 

Personnel

The document shepherd is Lionel Morand. The responsible AD is Ben Campbell.

Reply via email to