Skip to main content

Design Considerations for Session Initiation Protocol (SIP) Overload Control

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: RFC Editor <>,
    soc mailing list <>,
    soc chair <>
Subject: Document Action: 'Design Considerations for Session Initiation Protocol (SIP) Overload Control' to Informational RFC (draft-ietf-soc-overload-design-08.txt)

The IESG has approved the following document:
- 'Design Considerations for Session Initiation Protocol (SIP) Overload
  (draft-ietf-soc-overload-design-08.txt) as an Informational RFC

This document is the product of the SIP Overload Control Working Group.

The IESG contact persons are Robert Sparks and Gonzalo Camarillo.

A URL of this Internet Draft is:

Ballot Text

Technical Summary

   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.

Working Group Summary

  This document was originally started by an ad-hoc Design Team within the SIPPING wg.
  The document was then adopted by the SIP  Overload Control WG once it has been created.

Document Quality

  The draft is a design considerations document and therefore there are no implementations.
  There are implementations of drafts that are based on the design considerations draft.
  The document was reviewed in an early stage by the transport area.
  Version 04 of the draft has also received a second review by Pasi Lassila, an
  expert on control theory at Aalto university (in Finland) identified by Lars Eggert.


  Salvatore Loreto is the Document Shepherd
  Robert Sparks is the Responsible RAI AD

RFC Editor Note