[sip-overload] Last Call: <draft-ietf-soc-overload-control-14.txt> (Session Initiation Protocol (SIP) Overload Control) to Internet Standard

The IESG <iesg-secretary@ietf.org> Mon, 09 December 2013 20:24 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA0AD1AE07A; Mon, 9 Dec 2013 12:24:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YTL9TT1DFaWo; Mon, 9 Dec 2013 12:24:54 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D0CAA1AE2B4; Mon, 9 Dec 2013 12:24:54 -0800 (PST)
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: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20131209202454.23223.88002.idtracker@ietfa.amsl.com>
Date: Mon, 09 Dec 2013 12:24:54 -0800
Cc: sip-overload@ietf.org
Subject: [sip-overload] Last Call: <draft-ietf-soc-overload-control-14.txt> (Session Initiation Protocol (SIP) Overload Control) to Internet Standard
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 09 Dec 2013 20:24:58 -0000

The IESG has received a request from the SIP Overload Control WG (soc) to
consider the following document:
- 'Session Initiation Protocol (SIP) Overload Control'
  <draft-ietf-soc-overload-control-14.txt> as Internet Standard

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 2013-12-23. 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 defines the behaviour of SIP servers involved in overload
   control, and in addition, it specifies a loss-based overload scheme
   for SIP.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-soc-overload-control/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-soc-overload-control/ballot/


The following IPR Declarations may be related to this I-D:

   http://datatracker.ietf.org/ipr/1364/