RFC 6357

"Design Considerations for Session Initiation Protocol (SIP) Overload Control", August 2011

Canonical URL:

http://www.rfc-editor.org/rfc/rfc6357.txt
This document is also available in this non-normative format: PDF.

Status:

INFORMATIONAL

Authors:

V. Hilt
E. Noel
C. Shen
A. Abdelal

Stream:

IETF

Source:

soc (rai)

Please refer here for any errata for this document. To submit a new errata report, go to the main errata page.

Abstract

Overload occurs in Session Initiation Protocol (SIP) networks when SIP servers have insufficient resources to handle all SIP messages they receive. Even though the SIP protocol provides a limited overload control mechanism through its 503 (Service Unavailable) response code, SIP servers are still vulnerable to overload. This document discusses models and design considerations for a SIP overload control mechanism. This document is not an Internet Standards Track specification; it is published for informational purposes.

For the definition of Stream, see RFC 4844.