Skip to main content

Design Considerations for Session Initiation Protocol (SIP) Overload Control
draft-hilt-soc-overload-design-00

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Volker Hilt , Eric Noel , Charles Shen , Ahmed Abdelal
Last updated 2010-08-24 (Latest revision 2010-05-28)
Replaces draft-ietf-sipping-overload-design
Replaced by draft-ietf-soc-overload-design
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-soc-overload-design
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:

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.

Authors

Volker Hilt
Eric Noel
Charles Shen
Ahmed Abdelal

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