Browse Prior Art Database

Session Initiation Protocol (SIP) Overload Control (RFC7339)

IP.com Disclosure Number: IPCOM000238893D
Original Publication Date: 2014-Sep-01
Included in the Prior Art Database: 2014-Sep-24
Document File: 76 page(s) / 90K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

V. Gurbani: AUTHOR [+4]

Abstract

As with any network element, a Session Initiation Protocol (SIP) [RFC3261] server can suffer from overload when the number of SIP messages it receives exceeds the number of messages it can process. Overload can pose a serious problem for a network of SIP servers. During periods of overload, the throughput of a network of SIP servers can be significantly degraded. In fact, overload may lead to a situation where the retransmissions of dropped SIP messages may overwhelm the capacity of the network. This is often called "congestion collapse".

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 3% of the total text.

Internet Engineering Task Force (IETF)                   V. Gurbani, Ed. Request for Comments: 7339                                       V. Hilt Category: Standards Track                      Bell Labs, Alcatel-Lucent ISSN: 2070-1721                                           H. Schulzrinne                                                      Columbia University                                                           September 2014

            Session Initiation Protocol (SIP) Overload Control

Abstract

   Overload occurs in Session Initiation Protocol (SIP) networks when    SIP servers have insufficient resources to handle all the 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 the behavior of SIP servers involved    in overload control and also specifies a loss-based overload scheme    for SIP.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7339.

Gurbani, et al.              Standards Track                    [Page 1]
 RFC 7339                    Overload Control              September 2014

 Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Gurbani, et al.              Standards Track                    [Page 2]
 RFC 7339                    Overload Control        ...