CurrentINFORMATIONALIETF stream

RFC 5390: Requirements for Management of Overload in the Session Initiation Protocol

In plain English — editorial summary, not part of the RFC

Overload occurs in Session Initiation Protocol (SIP) networks when proxies and user agents have insufficient 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 document summarizes the problems with the existing 503 mechanism, and provides some requirements for a solution. This memo provides information for the Internet community.

Document record

Document ID
RFC5390
Published
December 2008
Authors
J. Rosenberg
Status
INFORMATIONAL
Stream
IETF
Area
rai
Pages
14
Also known as

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/5390-requirements-for-management-of-overload-in-the-session-initiation-protocol