Design Considerations for Session Initiation Protocol (SIP) Overload Control
draft-ietf-sipping-overload-design-02
| Document | Type |
Replaced Internet-Draft
(6lowpan WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Volker Hilt , Eric Noel , Charles Shen , Ahmed Abdelal | ||
| Last updated | 2017-03-20 (Latest revision 2009-07-11) | ||
| Replaced by | draft-hilt-soc-overload-design | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-hilt-soc-overload-design | |
| Consensus boilerplate | Unknown | ||
| 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.)