Skip to main content

Session Initiation Protocol (SIP) Load balancing survey
draft-partha-dispatch-siploadbalancing-survey-00

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Parthasarathi Ravindran , Vijay K. Gurbani , Paul Erkkila
Last updated 2012-07-30 (Latest revision 2012-01-23)
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

SIP Load balancing across a farm of SIP servers can be done today, but without generally agreed upon principles on how to best do accomplish this. Confounding the problem is that a SIP farm may consist of hosts with varying capabilities, example, a SIP proxy, a back-to-back user agent (B2BUA), a public-switched telephone system (PSTN) gateway, SIP Media servers etc. The capabilities and processing capacity on hosts in the farm may be different, sometimes vastly, from each other. This document present the survey of existing literature and common practice on SIP load balancing.

Authors

Parthasarathi Ravindran
Vijay K. Gurbani
Paul Erkkila

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)