datatracker.ietf.org
Sign In
Version 4.45, 2013-05-14
Report a bug

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

RFC
Document Stream: IETF
Last updated: 2011-07-11
Replaces: draft-hilt-soc-overload-design
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (soc)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6357
IANA Action State: No IC 
Responsible AD: Robert Sparks
IESG Note: Salvatore Loreto (Salvatore.Loreto@ericsson.com) is the document shepherd.
Send notices to: soc-chairs@tools.ietf.org, draft-ietf-soc-overload-design@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-soc-overload-design.

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. This document is not an Internet Standards Track specification; it is published for informational purposes.

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)