Skip to main content

Requirements for Management of Overload in the Session Initiation Protocol

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Jonathan Rosenberg
Last updated 2008-04-16 (Latest revision 2006-10-23)
Replaced by RFC 5390
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-sipping-overload-reqs
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Overload occurs in Session Initiation Protocol (SIP) networks when proxies and user agents have insuffient resources to complete the processing of a request. SIP provides limited support for overload handling through its 503 response code, which tells an upstream element that it is overloaded. However, numerous problems have been identified with this mechanism. This draft summarizes the problems with the existing 503 mechanism, and provides some requirements for a solution.


Jonathan Rosenberg

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