[sip-overload] Protocol Action: 'Session Initiation Protocol (SIP) Overload Control' to Proposed Standard (draft-ietf-soc-overload-control-15.txt)

The IESG <iesg-secretary@ietf.org> Wed, 14 May 2014 13:16 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 8CBD41A0090; Wed, 14 May 2014 06:16:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level:
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_34=0.6] autolearn=no
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 Fil6Mn2zo-La; Wed, 14 May 2014 06:16:04 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EE6C1A0097; Wed, 14 May 2014 06:16:02 -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: 5.4.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140514131602.18006.38508.idtracker@ietfa.amsl.com>
Date: Wed, 14 May 2014 06:16:02 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/sip-overload/lHZcMx-01z0LL3WeGDMvbq1h6rQ
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] Protocol Action: 'Session Initiation Protocol (SIP) Overload Control' to Proposed Standard (draft-ietf-soc-overload-control-15.txt)
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.15
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, 14 May 2014 13:16:05 -0000

The IESG has approved the following document:
- 'Session Initiation Protocol (SIP) Overload Control'
  (draft-ietf-soc-overload-control-15.txt) as Proposed Standard

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

The IESG contact persons are Richard Barnes and Alissa Cooper.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-soc-overload-control/




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 defines the protocol for communicating overload information
    between SIP servers and clients, so that clients can reduce the
    volume of traffic sent to overloaded servers, avoiding congestion
    collapse and increasing useful throughput.


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.
    There has been 13 versions of the document of the document since it
    has?been adopted as WG item, and the document has passed two
    WGLC?one in March 2012
    (http://www.ietf.org/mail-archive/web/sip-overload/current/msg00731.html)
    and a second one in February 2013
    (http://www.ietf.org/mail-archive/web/sip-overload/current/msg00911.html).
    All the issues and the feedback raised have been addressed, and the
    wg is now happy with the status.


Document Quality:
Are there existing implementations of the protocol?

    I am not aware of any.

Have a significant number of vendors indicated their plan to implement 
the specification?

    Yes, all the major vendors have indicated they have a plan to
    implement it.
    Moreover also 3GPP is supporting it and it will be referenced in its
    spec.

Are there any reviewers that merit special mention as having done a 
thorough review, e.g., one that resulted in important changes or a 
conclusion that the document had no substantive issues? If there was a 
MIB Doctor, Media Type or other expert review, what was its course 
(briefly)? In the case of a Media Type review, on what date was the 
request posted?

    No


Personnel:
Who is the Document Shepherd?

    Salvatore Loreto <salvatore.loreto@ericsson.com>;

Who is the Responsible Area Director?

    Richard Barnes <rlb@ipv.sx>;