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

 
Document Type Replaced Internet-Draft (individual)
Last updated 2010-08-24 (latest revision 2010-05-28)
Replaces draft-ietf-sipping-overload-design
Replaced by draft-ietf-soc-overload-design
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-soc-overload-design
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-hilt-soc-overload-design-00.txt

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 (volker.hilt@alcatel-lucent.com)
Eric Noel (eric.noel@att.com)
Charles Shen (charles@cs.columbia.edu)
Ahmed Abdelal (aabdelal@sonusnet.com)

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