Diameter Overload Control Requirements, November 2013
- Canonical URL:
- File formats:
- E. McMurry
- dime (ops)
Discuss this RFC: Send questions or comments to firstname.lastname@example.org
When a Diameter server or agent becomes overloaded, it needs to be able to gracefully reduce its load, typically by advising clients to reduce traffic for some period of time. Otherwise, it must continue to expend resources parsing and responding to Diameter messages, possibly resulting in a progressively severe overload condition. The existing Diameter mechanisms are not sufficient for managing overload conditions. This document describes the limitations of the existing mechanisms. Requirements for new overload management mechanisms are also provided.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.