Sign in
Version 5.13.0, 2015-03-25
Report a bug

Diameter Overload Control Requirements

Document type: Replaced Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2012-10-30 (latest revision 2012-08-28)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Replaced by draft-ietf-dime-overload-reqs
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:


When a Diameter server or agent becomes overloaded, it needs to be able to gracefully reduce its load, typically by informing clients to reduce sending traffic for some period of time. Otherwise, it must continue to expend resources parsing and responding to Diameter messages, possibly resulting in congestion collapse. The existing mechanisms provided by Diameter are not sufficient for this purpose. This document describes the limitations of the existing mechanisms, and provides requirements for new overload management mechanisms.


Eric McMurry <>
Ben Campbell <>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)