Diameter Overload Control Requirements

Document Type Replaced Internet-Draft (individual)
Authors Eric McMurry  , Ben Campbell 
Last updated 2012-10-30 (latest revision 2012-08-28)
Replaced by RFC 7068
Stream (None)
Intended RFC status (None)
Expired & archived
plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-dime-overload-reqs
Telechat date
Responsible AD (None)
Send notices to (None)

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


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 (emcmurry@estacado.net)
Ben Campbell (ben@nostrum.com)

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