Design Considerations for Session Initiation Protocol (SIP) Overload Control, August 2011
- File formats:
- V. Hilt
- soc (rai)
Discuss this RFC: Send questions or comments to the mailing list firstname.lastname@example.org
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 Status, see RFC 2026.
For the definition of Stream, see RFC 8729.