[sip-overload] Last Call: <draft-ietf-soc-overload-design-06.txt> (Design Considerations for Session Initiation Protocol (SIP) Overload Control) to Informational RFC
The IESG <iesg-secretary@ietf.org> Tue, 31 May 2011 18:44 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 455ECE07F2; Tue, 31 May 2011 11:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.467
X-Spam-Level:
X-Spam-Status: No, score=-102.467 tagged_above=-999 required=5 tests=[AWL=0.132, 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 X1alv8u6mZ+x; Tue, 31 May 2011 11:44:07 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6D14E0780; Tue, 31 May 2011 11:44:07 -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: <20110531184407.453.55068.idtracker@ietfa.amsl.com>
Date: Tue, 31 May 2011 11:44:07 -0700
Cc: sip-overload@ietf.org
Subject: [sip-overload] Last Call: <draft-ietf-soc-overload-design-06.txt> (Design Considerations for Session Initiation Protocol (SIP) Overload Control) to Informational RFC
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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: Tue, 31 May 2011 18:44:08 -0000
The IESG has received a request from the SIP Overload Control WG (soc) to consider the following document: - 'Design Considerations for Session Initiation Protocol (SIP) Overload Control' <draft-ietf-soc-overload-design-06.txt> as an Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2011-06-14. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract 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. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-soc-overload-design/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-soc-overload-design/ No IPR declarations have been submitted directly on this I-D.