datatracker.ietf.org
Sign in
Version 5.12.0, 2015-02-26
Report a bug

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

Document type: Replaced Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2010-08-24 (latest revision 2010-05-28)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html
Stream State:No stream defined
Document shepherd: No shepherd assigned
IESG State: Replaced by draft-ietf-soc-overload-design
Responsible AD: (None)
Send notices to: No addresses provided
Email Authors | IPR Disclosures | References | Referenced By | Check nits | History feed | Search Mailing Lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:
http://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)