Session Initiation Protocol (SIP) Resource availability Event package
draft-partha-sip-overload-resource-availability-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Parthasarathi R , Sheshadri Shalya | ||
| Last updated | 2010-04-19 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 B2BUA, proxies, and user agents have insufficient resources like CPU, memory, DSP, or bandwidth to complete the processing of a request. SIP provides limited support for overload handling through its 503 response code, which tells an upstream element that it is overloaded. This document defines explicit SIP based resource monitoring and overload avoidance mechanism based on the resource availability of the entity.
Authors
Parthasarathi R
Sheshadri Shalya
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)