[sip-overload] Document Action: 'Design Considerations for Session Initiation Protocol (SIP) Overload Control' to Informational RFC (draft-ietf-soc-overload-design-08.txt)
The IESG <iesg-secretary@ietf.org> Wed, 13 July 2011 20:05 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: sip-overload@ietfa.amsl.com
Delivered-To: sip-overload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id 385B721F8532; Wed, 13 Jul 2011 13:05:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.508
X-Spam-Level:
X-Spam-Status: No, score=-102.508 tagged_above=-999 required=5 tests=[AWL=0.091,
BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eN4+bLn23-MY;
Wed, 13 Jul 2011 13:05:47 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com
(Postfix) with ESMTP id 8ACE621F853D; Wed, 13 Jul 2011 13:05:47 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.55
Message-ID: <20110713200547.26576.32049.idtracker@ietfa.amsl.com>
Date: Wed, 13 Jul 2011 13:05:47 -0700
Cc: soc chair <soc-chairs@tools.ietf.org>,
soc mailing list <sip-overload@ietf.org>,
RFC Editor <rfc-editor@rfc-editor.org>
Subject: [sip-overload] Document Action: 'Design Considerations for Session
Initiation Protocol (SIP) Overload Control' to Informational
RFC (draft-ietf-soc-overload-design-08.txt)
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-overload>,
<mailto:sip-overload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-overload>
List-Post: <mailto:sip-overload@ietf.org>
List-Help: <mailto:sip-overload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-overload>,
<mailto:sip-overload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 20:05:48 -0000
The IESG has approved the following document: - 'Design Considerations for Session Initiation Protocol (SIP) Overload Control' (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: http://datatracker.ietf.org/doc/draft-ietf-soc-overload-design/ 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. Personnel Salvatore Loreto is the Document Shepherd Robert Sparks is the Responsible RAI AD