Session Initiation Protocol (SIP) Overload Control
draft-gurbani-soc-overload-control-02

Document Type Replaced Internet-Draft (individual)
Last updated 2010-11-19 (latest revision 2010-08-23)
Replaces draft-hilt-sipping-overload
Replaced by RFC 7339
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-soc-overload-control
Telechat date
Responsible AD (None)
Send notices to (None)

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-gurbani-soc-overload-control-02.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 defines an overload control mechanism for SIP.

Authors

Henning Schulzrinne (hgs@cs.columbia.edu)
Volker Hilt (volkerh@bell-labs.com)
Vijay Gurbani (vkg@bell-labs.com)

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