
From volker.hilt@alcatel-lucent.com  Thu Apr  1 17:55:42 2010
Return-Path: <volker.hilt@alcatel-lucent.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF8523A6812; Thu,  1 Apr 2010 17:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.131
X-Spam-Level: *
X-Spam-Status: No, score=1.131 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1JCdq4FgjaHA; Thu,  1 Apr 2010 17:55:41 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id A6DA43A6809; Thu,  1 Apr 2010 17:55:38 -0700 (PDT)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id o320u8Kt018913;  Thu, 1 Apr 2010 19:56:08 -0500 (CDT)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id o320u7Ws003268; Thu, 1 Apr 2010 19:56:08 -0500 (CDT)
Received: from [127.0.0.1] (135.3.63.242) by USNAVSXCHHUB01.ndc.alcatel-lucent.com (135.3.39.110) with Microsoft SMTP Server (TLS) id 8.2.213.0; Thu, 1 Apr 2010 19:56:07 -0500
Message-ID: <4BB5409E.5080108@alcatel-lucent.com>
Date: Thu, 1 Apr 2010 20:55:58 -0400
From: Volker Hilt <volker.hilt@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com>
In-Reply-To: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Mailman-Approved-At: Thu, 01 Apr 2010 17:57:18 -0700
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Lars Eggert <lars.eggert@nokia.com>, Robert Sparks <rjsparks@nostrum.com>
Subject: [sip-overload] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 02 Apr 2010 00:55:42 -0000

All,

below is an updated charter proposal for a SIP Overload Control WG. It 
has additional text that specifications developed by the proposed WG 
need to define scope and limitations (see below).

Thanks,

Volker



SIP Overload Control WG Charter
-------------------------------

As with any network element, a Session Initiation Protocol (SIP) server
can suffer from overload when the number of SIP messages it receives
exceeds the number of messages it can process. Overload is said to occur
when a SIP server does not have sufficient resources to process all
incoming SIP messages.  These resources can include CPU, memory, network
bandwidth, input/output, or disk resources.

Overload can pose a serious problem for a network of SIP servers. During
periods of overload, the throughput of a network of SIP servers can be
significantly degraded.  In fact, overload may lead to a situation in
which the throughput drops down to zero or a small fraction of the
original processing capacity.  This is often called congestion collapse.

The objective of a SIP overload control mechanism is to enable SIP
servers to operate close to their capacity limit during times of overload.

The SIP protocol provides a limited mechanism for overload control
through its 503 (Service Unavailable) response code and the Retry-After
header.  However, this mechanism cannot fully prevent overload of a SIP
server and it cannot prevent congestion collapse.  In fact, its on/off
behavior may cause traffic to oscillate and shift between SIP servers
and thereby worsen an overload condition.  A detailed discussion of the
SIP overload problem, the problems with the 503 (Service Unavailable)
response code and the Retry-After header and the requirements for a SIP
overload control mechanism can be found in RFC5390.

The objective of the proposed working group is to develop mechanisms for
SIP overload control. The problem domain of SIP overload control can be 
split into i) overload control between a user agent and a SIP server and 
overload control between SIP servers. A specification developed by the 
proposed working group needs to clearly specify its scope. A 
specification also needs to clearly state any limitations in performance 
or otherwise the proposed overload control mechanism may have.

Two complementary approaches exist for handling overload situations:
- The first mechanism aims at preventing overload in SIP servers by
adjusting the incoming load to a level that is acceptable for this
server. This mechanism uses implicit and/or explicit feedback to
determine when an overload condition occurs in a SIP server and a
reduction in load is required.
- The second mechanism aims at preventing overload in SIP servers by
distributing load control filters to SIP servers that throttle calls
based on their destination domain, telephone number prefix or for a
specific user. Such filters can be used, for example, to throttle calls
to a hotline during a ticket-giveaway event.

Specifically, the proposed working group will develop the following
deliverables:
1. A document describing key design considerations for a SIP overload
control mechanism.
2. A specification for an SIP overload control mechanism based on
implicit/explicit feedback.
3. A specification for a SIP load filtering mechanism.



From jgunn6@csc.com  Fri Apr  2 08:11:15 2010
Return-Path: <jgunn6@csc.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B13343A6936; Fri,  2 Apr 2010 08:11:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.352
X-Spam-Level: 
X-Spam-Status: No, score=-5.352 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gDJPoqW2OnpE; Fri,  2 Apr 2010 08:11:14 -0700 (PDT)
Received: from mail145.messagelabs.com (mail145.messagelabs.com [216.82.242.163]) by core3.amsl.com (Postfix) with ESMTP id 895F33A6907; Fri,  2 Apr 2010 08:11:13 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-7.tower-145.messagelabs.com!1270221104!10026971!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [20.137.2.88]
Received: (qmail 22229 invoked from network); 2 Apr 2010 15:11:45 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-7.tower-145.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Apr 2010 15:11:45 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (Switch-3.3.3mp/Switch-3.3.3mp) with ESMTP id o32FBiBm017623; Fri, 2 Apr 2010 11:11:44 -0400
In-Reply-To: <4BB5409E.5080108@alcatel-lucent.com>
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com> <4BB5409E.5080108@alcatel-lucent.com>
To: Volker Hilt <volker.hilt@alcatel-lucent.com>
MIME-Version: 1.0
X-KeepSent: 15B89DE4:C12B307F-852576F9:0052B459; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2FP1  CCH2 April 23, 2009
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF15B89DE4.C12B307F-ON852576F9.0052B459-852576F9.0053784D@csc.com>
Date: Fri, 2 Apr 2010 11:11:35 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.0.1 HF996|December 23, 2008) at 04/02/2010 11:12:38 AM, Serialize complete at 04/02/2010 11:12:38 AM
Content-Type: multipart/alternative; boundary="=_alternative 0053752B852576F9_="
Cc: sip-overload-bounces@ietf.org, DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Lars Eggert <lars.eggert@nokia.com>, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 02 Apr 2010 15:11:16 -0000

This is a multipart message in MIME format.
--=_alternative 0053752B852576F9_=
Content-Type: text/plain; charset="US-ASCII"

 > 
> [sip-overload] Proposed SIP Overload Control Charter
> 
> Volker Hilt 
> 

This text

> Two complementary approaches exist for handling overload situations:
> - The first mechanism aims at preventing overload in SIP servers by
> adjusting the incoming load to a level that is acceptable for this
> server. This mechanism uses implicit and/or explicit feedback to
> determine when an overload condition occurs in a SIP server and a
> reduction in load is required.
> - The second mechanism aims at preventing overload in SIP servers by
> distributing load control filters to SIP servers that throttle calls
> based on their destination domain, telephone number prefix or for a
> specific user. Such filters can be used, for example, to throttle calls
> to a hotline during a ticket-giveaway event.

seems to imply that there are ONLY TWO complementary approaches. 

There are, in fact, a much larger number of possible approaches.

Filters based on the SOURCE domain, telephone number prefix or for a 
specific user are the most obvious omission, but I am sure there are many 
more.

Perhaps better wording would be 

"At least two complementary approaches exist for handling overload 
situations:..."

Janet





> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload

--=_alternative 0053752B852576F9_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif"><br>
</font><tt><font size=2> </font></tt>
<br><tt><font size=2>&gt; <br>
&gt; [sip-overload] Proposed SIP Overload Control Charter</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Volker Hilt </font></tt>
<br><tt><font size=2>&gt; <br>
</font></tt>
<br><tt><font size=2>This text</font></tt>
<br><tt><font size=2><br>
&gt; Two complementary approaches exist for handling overload situations:<br>
&gt; - The first mechanism aims at preventing overload in SIP servers by<br>
&gt; adjusting the incoming load to a level that is acceptable for this<br>
&gt; server. This mechanism uses implicit and/or explicit feedback to<br>
&gt; determine when an overload condition occurs in a SIP server and a<br>
&gt; reduction in load is required.<br>
&gt; - The second mechanism aims at preventing overload in SIP servers
by<br>
&gt; distributing load control filters to SIP servers that throttle calls<br>
&gt; based on their destination domain, telephone number prefix or for
a<br>
&gt; specific user. Such filters can be used, for example, to throttle
calls<br>
&gt; to a hotline during a ticket-giveaway event.</font></tt>
<br>
<br><tt><font size=2>seems to imply that there are ONLY TWO complementary
approaches. &nbsp;</font></tt>
<br>
<br><tt><font size=2>There are, in fact, a much larger number of possible
approaches.</font></tt>
<br>
<br><tt><font size=2>Filters based on the SOURCE domain, telephone number
prefix or for a specific user are the most obvious omission, but I am sure
there are many more.</font></tt>
<br>
<br><tt><font size=2>Perhaps better wording would be </font></tt>
<br>
<br><tt><font size=2>&quot;At least two complementary approaches exist
for handling overload situations:...&quot;</font></tt>
<br>
<br><tt><font size=2>Janet</font></tt>
<br>
<br>
<br>
<br>
<br><tt><font size=2><br>
&gt; _______________________________________________<br>
&gt; sip-overload mailing list<br>
&gt; sip-overload@ietf.org<br>
&gt; </font></tt><a href="https://www.ietf.org/mailman/listinfo/sip-overload"><tt><font size=2>https://www.ietf.org/mailman/listinfo/sip-overload</font></tt></a><tt><font size=2><br>
</font></tt>
--=_alternative 0053752B852576F9_=--

From charles.newyork@gmail.com  Fri Apr  2 08:28:06 2010
Return-Path: <charles.newyork@gmail.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2CAB03A6821; Fri,  2 Apr 2010 08:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.847
X-Spam-Level: 
X-Spam-Status: No, score=-0.847 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y3s4xkV6N2jt; Fri,  2 Apr 2010 08:28:05 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id 5396D3A67DA; Fri,  2 Apr 2010 08:28:05 -0700 (PDT)
Received: by pvd12 with SMTP id 12so579214pvd.31 for <multiple recipients>; Fri, 02 Apr 2010 08:28:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:received:message-id:subject :from:to:cc:content-type; bh=8pJoQxJXjsm85q3NhcBUw13zpIc5PIsF8KEgC6WChTM=; b=mtMA+EdqPRKUZ7TVcDuKLOjQjqqu+AZGT5yk4cc3zUsDThfwuFbp4sVE9YjDueeBO5 aM8q5F9vVj27c8fgOAGv/zb0UIKeAyzTy6KeJnuZfUZz6JWxdEWCJ8aB6jwpzKKx+9LN uHEXe5Oe1vqUSIHqzGEd3Vjvy/GzHeXxfESVU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=ty92i7z8RRy/ra9yAeTBzRc+0mtT1etmlYBRTVXzZ9y5y1Fr3V8/+5LQ6e/mHLfd9l i13VHH7WZheltZqp/Jc5iH2nXPimghP+QNKUueSonz7nWX/AUGBjTnYzat4jPPTwC/tD K74LIAopuTb3f7D8vh6W8CjAAyVi9V/KYAtcY=
MIME-Version: 1.0
Sender: charles.newyork@gmail.com
Received: by 10.142.174.20 with HTTP; Fri, 2 Apr 2010 08:28:36 -0700 (PDT)
In-Reply-To: <OF15B89DE4.C12B307F-ON852576F9.0052B459-852576F9.0053784D@csc.com>
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com> <4BB5409E.5080108@alcatel-lucent.com> <OF15B89DE4.C12B307F-ON852576F9.0052B459-852576F9.0053784D@csc.com>
Date: Fri, 2 Apr 2010 11:28:36 -0400
X-Google-Sender-Auth: 61474804afd52de3
Received: by 10.143.153.24 with SMTP id f24mr815821wfo.292.1270222116535; Fri,  02 Apr 2010 08:28:36 -0700 (PDT)
Message-ID: <r2oe7df28361004020828maf2cc9ddw7f9818f69818ce53@mail.gmail.com>
From: Charles Shen <charles@cs.columbia.edu>
To: Janet P Gunn <jgunn6@csc.com>
Content-Type: text/plain; charset=UTF-8
Cc: sip-overload-bounces@ietf.org, DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Lars Eggert <lars.eggert@nokia.com>, Volker Hilt <volker.hilt@alcatel-lucent.com>, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 02 Apr 2010 15:28:06 -0000

On Fri, Apr 2, 2010 at 11:11 AM, Janet P Gunn <jgunn6@csc.com> wrote:
>
>
>
>>
>> [sip-overload] Proposed SIP Overload Control Charter
>>
>> Volker Hilt
>>
>
> This text
>
>> Two complementary approaches exist for handling overload situations:
>> - The first mechanism aims at preventing overload in SIP servers by
>> adjusting the incoming load to a level that is acceptable for this
>> server. This mechanism uses implicit and/or explicit feedback to
>> determine when an overload condition occurs in a SIP server and a
>> reduction in load is required.
>> - The second mechanism aims at preventing overload in SIP servers by
>> distributing load control filters to SIP servers that throttle calls
>> based on their destination domain, telephone number prefix or for a
>> specific user. Such filters can be used, for example, to throttle calls
>> to a hotline during a ticket-giveaway event.
>
> seems to imply that there are ONLY TWO complementary approaches.
>
> There are, in fact, a much larger number of possible approaches.
>
> Filters based on the SOURCE domain, telephone number prefix or for a
> specific user are the most obvious omission,


"Filters based on the SOURCE domain, telephone number prefix or for a
specific user" are still part of (and included in) the filter-based
approach.

Maybe what we are talking about is either a single user or a group of
users specified by URIs (e.g., SIP, Tel), and the grouping can be
based on domains or telephone number prefixes?

Thanks

Charles





> but I am sure there are many
> more.
>
> Perhaps better wording would be
>
> "At least two complementary approaches exist for handling overload
> situations:..."
>
> Janet
>
>
>
>
>
>> _______________________________________________
>> sip-overload mailing list
>> sip-overload@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-overload
>
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload
>
>

From rjsparks@nostrum.com  Fri Apr 16 08:57:08 2010
Return-Path: <rjsparks@nostrum.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9FEA3A6817; Fri, 16 Apr 2010 08:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level: 
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=-1.206, BAYES_40=-0.185, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id STRZ-sUVnTmw; Fri, 16 Apr 2010 08:57:07 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 633A53A69EA; Fri, 16 Apr 2010 08:57:04 -0700 (PDT)
Received: from [192.168.2.105] (pool-173-71-51-142.dllstx.fios.verizon.net [173.71.51.142]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o3GFupGr024146 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 16 Apr 2010 10:56:52 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <4BB5409E.5080108@alcatel-lucent.com>
Date: Fri, 16 Apr 2010 10:56:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com>
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com> <4BB5409E.5080108@alcatel-lucent.com>
To: Volker Hilt <volker.hilt@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1078)
Received-SPF: pass (nostrum.com: 173.71.51.142 is authenticated by a trusted mechanism)
Cc: DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 16 Apr 2010 15:57:08 -0000

I have made some tweaks based on the list discussion and conversations =
with IESG members.
This is my current working text. Please comment if you disagree with the =
changes I've made.

The changes are in the description of overload in the first paragraph, =
changing the term throughput=20
to goodput, and clarifying the discussion of scope and limitations. I've =
also added some strawman
milestones. Please comment on those dates.

SIP Overload Control WG Charter
-------------------------------

As with any network element, a Session Initiation Protocol (SIP) server
can suffer from overload when the number of SIP messages it receives
exceeds the number of messages it can process. Overload is said to occur
when a SIP server does not have sufficient resources to complete the
processing of all incoming SIP messages within the required time.
These resources can include CPU, memory, network bandwidth, =
input/output,=20
or disk resources.

Overload can pose a serious problem for a network of SIP servers. During
periods of overload, the goodput of a network of SIP servers can be
significantly degraded.  In fact, overload may lead to a situation in
which the goodput drops down to zero or a small fraction of the
original processing capacity.  This is often called congestion collapse.

The objective of a SIP overload control mechanism is to enable SIP
servers to operate close to their capacity limit during times of =
overload.

The SIP protocol provides a limited mechanism for overload control
through its 503 (Service Unavailable) response code and the Retry-After
header.  However, this mechanism cannot fully prevent overload of a SIP
server and it cannot prevent congestion collapse.  In fact, its on/off
behavior may cause traffic to oscillate and shift between SIP servers
and thereby worsen an overload condition.  A detailed discussion of the
SIP overload problem, the problems with the 503 (Service Unavailable)
response code and the Retry-After header and the requirements for a SIP
overload control mechanism can be found in RFC5390.

The objective of the working group is to develop mechanisms for SIP
overload control. The problem domain of SIP overload control can be =
split into
overload control between a user agent and a SIP server and overload =
control
between SIP servers.=20

Any specification developed by the working group needs to clearly =
specify its
scope. A specification also needs to clearly state any limitations, in
performance or otherwise, the specified overload control mechanism may =
have.  In
particular, the working group shall carefully define the deployment
considerations for the effective operation of the specified mechanisms =
and
discuss, for example, when a mechanism requires coordinated deployment =
and
operation (if all servers need to deploy the same mechanism, certain
configuration values need to be identical on all servers, etc), when a
mechanism can become less effective or ineffective under some =
conditions, or
especially if there are cases when a mechanism can reduce goodput =
compared to
no overload protection. The intent of these considerations is to allow
potential deployers to make the best use of these mechanism in their =
particular
networks.

The working group will consider two complementary approaches for=20
handling overload situations:
- The first mechanism aims at preventing overload in SIP servers by
  adjusting the incoming load to a level that is acceptable for this
  server. This mechanism uses implicit and/or explicit feedback to
  determine when an overload condition occurs in a SIP server and a
  reduction in load is required.
- The second mechanism aims at preventing overload in SIP servers by
  distributing load control filters to SIP servers that throttle calls
  based on their destination domain, telephone number prefix or for a
  specific user. Such filters can be used, for example, to throttle =
calls
  to a hotline during a ticket-giveaway event.

The working group will develop the following deliverables:

  1. A document describing key design considerations for a SIP overload
     control mechanism.
  2. A specification for an SIP overload control mechanism based on
     implicit/explicit feedback.
  3. A specification for a SIP load filtering mechanism.

Milestones:

Sep 2010 Design Considerations to IESG for publication as Informational
Dec 2010 Specification for a SIP overload control mechanism based on =
implicit/explicit feedback to IESG for publication as Proposed Standard
May 2011 Specification for a SIP load filtering mechaism to IESG for =
publication as Proposed Standard


On Apr 1, 2010, at 7:55 PM, Volker Hilt wrote:

> All,
>=20
> below is an updated charter proposal for a SIP Overload Control WG. It =
has additional text that specifications developed by the proposed WG =
need to define scope and limitations (see below).
>=20
> Thanks,
>=20
> Volker
>=20
>=20
>=20
> SIP Overload Control WG Charter
> -------------------------------
>=20
> As with any network element, a Session Initiation Protocol (SIP) =
server
> can suffer from overload when the number of SIP messages it receives
> exceeds the number of messages it can process. Overload is said to =
occur
> when a SIP server does not have sufficient resources to process all
> incoming SIP messages.  These resources can include CPU, memory, =
network
> bandwidth, input/output, or disk resources.
>=20
> Overload can pose a serious problem for a network of SIP servers. =
During
> periods of overload, the throughput of a network of SIP servers can be
> significantly degraded.  In fact, overload may lead to a situation in
> which the throughput drops down to zero or a small fraction of the
> original processing capacity.  This is often called congestion =
collapse.
>=20
> The objective of a SIP overload control mechanism is to enable SIP
> servers to operate close to their capacity limit during times of =
overload.
>=20
> The SIP protocol provides a limited mechanism for overload control
> through its 503 (Service Unavailable) response code and the =
Retry-After
> header.  However, this mechanism cannot fully prevent overload of a =
SIP
> server and it cannot prevent congestion collapse.  In fact, its on/off
> behavior may cause traffic to oscillate and shift between SIP servers
> and thereby worsen an overload condition.  A detailed discussion of =
the
> SIP overload problem, the problems with the 503 (Service Unavailable)
> response code and the Retry-After header and the requirements for a =
SIP
> overload control mechanism can be found in RFC5390.
>=20
> The objective of the proposed working group is to develop mechanisms =
for
> SIP overload control. The problem domain of SIP overload control can =
be split into i) overload control between a user agent and a SIP server =
and overload control between SIP servers. A specification developed by =
the proposed working group needs to clearly specify its scope. A =
specification also needs to clearly state any limitations in performance =
or otherwise the proposed overload control mechanism may have.
>=20
> Two complementary approaches exist for handling overload situations:
> - The first mechanism aims at preventing overload in SIP servers by
> adjusting the incoming load to a level that is acceptable for this
> server. This mechanism uses implicit and/or explicit feedback to
> determine when an overload condition occurs in a SIP server and a
> reduction in load is required.
> - The second mechanism aims at preventing overload in SIP servers by
> distributing load control filters to SIP servers that throttle calls
> based on their destination domain, telephone number prefix or for a
> specific user. Such filters can be used, for example, to throttle =
calls
> to a hotline during a ticket-giveaway event.
>=20
> Specifically, the proposed working group will develop the following
> deliverables:
> 1. A document describing key design considerations for a SIP overload
> control mechanism.
> 2. A specification for an SIP overload control mechanism based on
> implicit/explicit feedback.
> 3. A specification for a SIP load filtering mechanism.
>=20
>=20


From jgunn6@csc.com  Fri Apr 16 09:43:13 2010
Return-Path: <jgunn6@csc.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7593C28C100; Fri, 16 Apr 2010 09:43:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.124
X-Spam-Level: 
X-Spam-Status: No, score=-6.124 tagged_above=-999 required=5 tests=[AWL=0.474,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ohu6Z-F4pVIF; Fri, 16 Apr 2010 09:43:11 -0700 (PDT)
Received: from mail171.messagelabs.com (mail171.messagelabs.com [216.82.253.243]) by core3.amsl.com (Postfix) with ESMTP id A21333A693E; Fri, 16 Apr 2010 09:43:07 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-6.tower-171.messagelabs.com!1271436178!17991221!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [20.137.2.88]
Received: (qmail 2853 invoked from network); 16 Apr 2010 16:42:59 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-6.tower-171.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Apr 2010 16:42:59 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (Switch-3.3.3mp/Switch-3.3.3mp) with ESMTP id o3GGgvLx004174; Fri, 16 Apr 2010 12:42:58 -0400
In-Reply-To: <0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com>
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com>	<4BB5409E.5080108@alcatel-lucent.com> <0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
MIME-Version: 1.0
X-KeepSent: 77234340:6D07CD75-85257707:005B114B; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2FP1  CCH2 April 23, 2009
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF77234340.6D07CD75-ON85257707.005B114B-85257707.005BD6FD@csc.com>
Date: Fri, 16 Apr 2010 12:42:54 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.0.1 HF996|December 23, 2008) at 04/16/2010 12:43:44 PM, Serialize complete at 04/16/2010 12:43:44 PM
Content-Type: multipart/alternative; boundary="=_alternative 005BD65F85257707_="
X-Mailman-Approved-At: Fri, 16 Apr 2010 11:36:05 -0700
Cc: sip-overload-bounces@ietf.org, DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Richard F Kaczmarek <rkaczmarek@csc.com>, Lars Eggert <lars.eggert@nokia.com>, Volker Hilt <volker.hilt@alcatel-lucent.com>
Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 16 Apr 2010 16:43:13 -0000

This is a multipart message in MIME format.
--=_alternative 005BD65F85257707_=
Content-Type: text/plain; charset="US-ASCII"

I know I said it before, but I am going to say it again.

First, the "second mechanism" should explicitly mention filtering based on 
SOURCE "domain, telephone number prefix or specific user", not just 
DESTINATION.

Second, I would like to see an explicit statement that the work will be 
consistent with the requirements in RFC 5390.

Thanks

Janet


sip-overload-bounces@ietf.org wrote on 04/16/2010 11:56:51 AM:

> [image removed] 
> 
> Re: [sip-overload] Proposed SIP Overload Control Charter
> 
> Robert Sparks 
> 
> to:
> 
> Volker Hilt
> 
> 04/16/2010 11:57 AM
> 
> Sent by:
> 
> sip-overload-bounces@ietf.org
> 
> Cc:
> 
> DISPATCH, "sip-overload@ietf.org", Gonzalo Camarillo, Lars Eggert
> 
> I have made some tweaks based on the list discussion and 
> conversations with IESG members.
> This is my current working text. Please comment if you disagree with
> the changes I've made.
> 
> The changes are in the description of overload in the first 
> paragraph, changing the term throughput 
> to goodput, and clarifying the discussion of scope and limitations. 
> I've also added some strawman
> milestones. Please comment on those dates.
> 
> SIP Overload Control WG Charter
> -------------------------------
> 
> As with any network element, a Session Initiation Protocol (SIP) server
> can suffer from overload when the number of SIP messages it receives
> exceeds the number of messages it can process. Overload is said to occur
> when a SIP server does not have sufficient resources to complete the
> processing of all incoming SIP messages within the required time.
> These resources can include CPU, memory, network bandwidth, 
input/output, 
> or disk resources.
> 
> Overload can pose a serious problem for a network of SIP servers. During
> periods of overload, the goodput of a network of SIP servers can be
> significantly degraded.  In fact, overload may lead to a situation in
> which the goodput drops down to zero or a small fraction of the
> original processing capacity.  This is often called congestion collapse.
> 
> The objective of a SIP overload control mechanism is to enable SIP
> servers to operate close to their capacity limit during times of 
overload.
> 
> The SIP protocol provides a limited mechanism for overload control
> through its 503 (Service Unavailable) response code and the Retry-After
> header.  However, this mechanism cannot fully prevent overload of a SIP
> server and it cannot prevent congestion collapse.  In fact, its on/off
> behavior may cause traffic to oscillate and shift between SIP servers
> and thereby worsen an overload condition.  A detailed discussion of the
> SIP overload problem, the problems with the 503 (Service Unavailable)
> response code and the Retry-After header and the requirements for a SIP
> overload control mechanism can be found in RFC5390.
> 
> The objective of the working group is to develop mechanisms for SIP
> overload control. The problem domain of SIP overload control can be 
split into
> overload control between a user agent and a SIP server and overload 
control
> between SIP servers. 
> 
> Any specification developed by the working group needs to clearly 
specify its
> scope. A specification also needs to clearly state any limitations, in
> performance or otherwise, the specified overload control mechanism 
> may have.  In
> particular, the working group shall carefully define the deployment
> considerations for the effective operation of the specified mechanisms 
and
> discuss, for example, when a mechanism requires coordinated deployment 
and
> operation (if all servers need to deploy the same mechanism, certain
> configuration values need to be identical on all servers, etc), when a
> mechanism can become less effective or ineffective under some 
conditions, or
> especially if there are cases when a mechanism can reduce goodput 
compared to
> no overload protection. The intent of these considerations is to allow
> potential deployers to make the best use of these mechanism in 
theirparticular
> networks.
> 
> The working group will consider two complementary approaches for 
> handling overload situations:
> - The first mechanism aims at preventing overload in SIP servers by
>   adjusting the incoming load to a level that is acceptable for this
>   server. This mechanism uses implicit and/or explicit feedback to
>   determine when an overload condition occurs in a SIP server and a
>   reduction in load is required.
> - The second mechanism aims at preventing overload in SIP servers by
>   distributing load control filters to SIP servers that throttle calls
>   based on their destination domain, telephone number prefix or for a
>   specific user. Such filters can be used, for example, to throttle 
calls
>   to a hotline during a ticket-giveaway event.
> 
> The working group will develop the following deliverables:
> 
>   1. A document describing key design considerations for a SIP overload
>      control mechanism.
>   2. A specification for an SIP overload control mechanism based on
>      implicit/explicit feedback.
>   3. A specification for a SIP load filtering mechanism.
> 
> Milestones:
> 
> Sep 2010 Design Considerations to IESG for publication as Informational
> Dec 2010 Specification for a SIP overload control mechanism based on
> implicit/explicit feedback to IESG for publication as Proposed Standard
> May 2011 Specification for a SIP load filtering mechaism to IESG for
> publication as Proposed Standard
> 
> 
> On Apr 1, 2010, at 7:55 PM, Volker Hilt wrote:
> 
> > All,
> > 
> > below is an updated charter proposal for a SIP Overload Control 
> WG. It has additional text that specifications developed by the 
> proposed WG need to define scope and limitations (see below).
> > 
> > Thanks,
> > 
> > Volker
> > 
> > 
> > 
> > SIP Overload Control WG Charter
> > -------------------------------
> > 
> > As with any network element, a Session Initiation Protocol (SIP) 
server
> > can suffer from overload when the number of SIP messages it receives
> > exceeds the number of messages it can process. Overload is said to 
occur
> > when a SIP server does not have sufficient resources to process all
> > incoming SIP messages.  These resources can include CPU, memory, 
network
> > bandwidth, input/output, or disk resources.
> > 
> > Overload can pose a serious problem for a network of SIP servers. 
During
> > periods of overload, the throughput of a network of SIP servers can be
> > significantly degraded.  In fact, overload may lead to a situation in
> > which the throughput drops down to zero or a small fraction of the
> > original processing capacity.  This is often called congestion 
collapse.
> > 
> > The objective of a SIP overload control mechanism is to enable SIP
> > servers to operate close to their capacity limit during times of 
overload.
> > 
> > The SIP protocol provides a limited mechanism for overload control
> > through its 503 (Service Unavailable) response code and the 
Retry-After
> > header.  However, this mechanism cannot fully prevent overload of a 
SIP
> > server and it cannot prevent congestion collapse.  In fact, its on/off
> > behavior may cause traffic to oscillate and shift between SIP servers
> > and thereby worsen an overload condition.  A detailed discussion of 
the
> > SIP overload problem, the problems with the 503 (Service Unavailable)
> > response code and the Retry-After header and the requirements for a 
SIP
> > overload control mechanism can be found in RFC5390.
> > 
> > The objective of the proposed working group is to develop mechanisms 
for
> > SIP overload control. The problem domain of SIP overload control 
> can be split into i) overload control between a user agent and a SIP
> server and overload control between SIP servers. A specification 
> developed by the proposed working group needs to clearly specify its
> scope. A specification also needs to clearly state any limitations 
> in performance or otherwise the proposed overload control mechanism may 
have.
> > 
> > Two complementary approaches exist for handling overload situations:
> > - The first mechanism aims at preventing overload in SIP servers by
> > adjusting the incoming load to a level that is acceptable for this
> > server. This mechanism uses implicit and/or explicit feedback to
> > determine when an overload condition occurs in a SIP server and a
> > reduction in load is required.
> > - The second mechanism aims at preventing overload in SIP servers by
> > distributing load control filters to SIP servers that throttle calls
> > based on their destination domain, telephone number prefix or for a
> > specific user. Such filters can be used, for example, to throttle 
calls
> > to a hotline during a ticket-giveaway event.
> > 
> > Specifically, the proposed working group will develop the following
> > deliverables:
> > 1. A document describing key design considerations for a SIP overload
> > control mechanism.
> > 2. A specification for an SIP overload control mechanism based on
> > implicit/explicit feedback.
> > 3. A specification for a SIP load filtering mechanism.
> > 
> > 
> 
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload

--=_alternative 005BD65F85257707_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif"><br>
I know I said it before, but I am going to say it again.</font>
<br>
<br><font size=2 face="sans-serif">First, the &quot;second mechanism&quot;
should explicitly mention filtering based on SOURCE &quot;</font><tt><font size=2>domain,
telephone number prefix or specific user&quot;, not just DESTINATION.</font></tt>
<br>
<br><tt><font size=2>Second, I would like to see an explicit statement
that the work will be consistent with the requirements in RFC 5390.</font></tt>
<br>
<br><tt><font size=2>Thanks</font></tt>
<br>
<br><tt><font size=2>Janet</font></tt>
<br>
<br>
<br><tt><font size=2>sip-overload-bounces@ietf.org wrote on 04/16/2010
11:56:51 AM:<br>
<br>
&gt; [image removed] </font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Re: [sip-overload] Proposed SIP Overload Control Charter</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Robert Sparks </font></tt>
<br><tt><font size=2>&gt; <br>
&gt; to:</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Volker Hilt</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; 04/16/2010 11:57 AM</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Sent by:</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; sip-overload-bounces@ietf.org</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Cc:</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; DISPATCH, &quot;sip-overload@ietf.org&quot;, Gonzalo Camarillo, Lars
Eggert</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; I have made some tweaks based on the list discussion and <br>
&gt; conversations with IESG members.<br>
&gt; This is my current working text. Please comment if you disagree with<br>
&gt; the changes I've made.<br>
&gt; <br>
&gt; The changes are in the description of overload in the first <br>
&gt; paragraph, changing the term throughput <br>
&gt; to goodput, and clarifying the discussion of scope and limitations.
<br>
&gt; I've also added some strawman<br>
&gt; milestones. Please comment on those dates.<br>
&gt; <br>
&gt; SIP Overload Control WG Charter<br>
&gt; -------------------------------<br>
&gt; <br>
&gt; As with any network element, a Session Initiation Protocol (SIP) server<br>
&gt; can suffer from overload when the number of SIP messages it receives<br>
&gt; exceeds the number of messages it can process. Overload is said to
occur<br>
&gt; when a SIP server does not have sufficient resources to complete the<br>
&gt; processing of all incoming SIP messages within the required time.<br>
&gt; These resources can include CPU, memory, network bandwidth, input/output,
<br>
&gt; or disk resources.<br>
&gt; <br>
&gt; Overload can pose a serious problem for a network of SIP servers.
During<br>
&gt; periods of overload, the goodput of a network of SIP servers can be<br>
&gt; significantly degraded. &nbsp;In fact, overload may lead to a situation
in<br>
&gt; which the goodput drops down to zero or a small fraction of the<br>
&gt; original processing capacity. &nbsp;This is often called congestion
collapse.<br>
&gt; <br>
&gt; The objective of a SIP overload control mechanism is to enable SIP<br>
&gt; servers to operate close to their capacity limit during times of overload.<br>
&gt; <br>
&gt; The SIP protocol provides a limited mechanism for overload control<br>
&gt; through its 503 (Service Unavailable) response code and the Retry-After<br>
&gt; header. &nbsp;However, this mechanism cannot fully prevent overload
of a SIP<br>
&gt; server and it cannot prevent congestion collapse. &nbsp;In fact, its
on/off<br>
&gt; behavior may cause traffic to oscillate and shift between SIP servers<br>
&gt; and thereby worsen an overload condition. &nbsp;A detailed discussion
of the<br>
&gt; SIP overload problem, the problems with the 503 (Service Unavailable)<br>
&gt; response code and the Retry-After header and the requirements for
a SIP<br>
&gt; overload control mechanism can be found in RFC5390.<br>
&gt; <br>
&gt; The objective of the working group is to develop mechanisms for SIP<br>
&gt; overload control. The problem domain of SIP overload control can be
split into<br>
&gt; overload control between a user agent and a SIP server and overload
control<br>
&gt; between SIP servers. <br>
&gt; <br>
&gt; Any specification developed by the working group needs to clearly
specify its<br>
&gt; scope. A specification also needs to clearly state any limitations,
in<br>
&gt; performance or otherwise, the specified overload control mechanism
<br>
&gt; may have. &nbsp;In<br>
&gt; particular, the working group shall carefully define the deployment<br>
&gt; considerations for the effective operation of the specified mechanisms
and<br>
&gt; discuss, for example, when a mechanism requires coordinated deployment
and<br>
&gt; operation (if all servers need to deploy the same mechanism, certain<br>
&gt; configuration values need to be identical on all servers, etc), when
a<br>
&gt; mechanism can become less effective or ineffective under some conditions,
or<br>
&gt; especially if there are cases when a mechanism can reduce goodput
compared to<br>
&gt; no overload protection. The intent of these considerations is to allow<br>
&gt; potential deployers to make the best use of these mechanism in theirparticular<br>
&gt; networks.<br>
&gt; <br>
&gt; The working group will consider two complementary approaches for <br>
&gt; handling overload situations:<br>
&gt; - The first mechanism aims at preventing overload in SIP servers by<br>
&gt; &nbsp; adjusting the incoming load to a level that is acceptable for
this<br>
&gt; &nbsp; server. This mechanism uses implicit and/or explicit feedback
to<br>
&gt; &nbsp; determine when an overload condition occurs in a SIP server
and a<br>
&gt; &nbsp; reduction in load is required.<br>
&gt; - The second mechanism aims at preventing overload in SIP servers
by<br>
&gt; &nbsp; distributing load control filters to SIP servers that throttle
calls<br>
&gt; &nbsp; based on their destination domain, telephone number prefix
or for a<br>
&gt; &nbsp; specific user. Such filters can be used, for example, to throttle
calls<br>
&gt; &nbsp; to a hotline during a ticket-giveaway event.<br>
&gt; <br>
&gt; The working group will develop the following deliverables:<br>
&gt; <br>
&gt; &nbsp; 1. A document describing key design considerations for a SIP
overload<br>
&gt; &nbsp; &nbsp; &nbsp;control mechanism.<br>
&gt; &nbsp; 2. A specification for an SIP overload control mechanism based
on<br>
&gt; &nbsp; &nbsp; &nbsp;implicit/explicit feedback.<br>
&gt; &nbsp; 3. A specification for a SIP load filtering mechanism.<br>
&gt; <br>
&gt; Milestones:<br>
&gt; <br>
&gt; Sep 2010 Design Considerations to IESG for publication as Informational<br>
&gt; Dec 2010 Specification for a SIP overload control mechanism based
on<br>
&gt; implicit/explicit feedback to IESG for publication as Proposed Standard<br>
&gt; May 2011 Specification for a SIP load filtering mechaism to IESG for<br>
&gt; publication as Proposed Standard<br>
&gt; <br>
&gt; <br>
&gt; On Apr 1, 2010, at 7:55 PM, Volker Hilt wrote:<br>
&gt; <br>
&gt; &gt; All,<br>
&gt; &gt; <br>
&gt; &gt; below is an updated charter proposal for a SIP Overload Control
<br>
&gt; WG. It has additional text that specifications developed by the <br>
&gt; proposed WG need to define scope and limitations (see below).<br>
&gt; &gt; <br>
&gt; &gt; Thanks,<br>
&gt; &gt; <br>
&gt; &gt; Volker<br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; SIP Overload Control WG Charter<br>
&gt; &gt; -------------------------------<br>
&gt; &gt; <br>
&gt; &gt; As with any network element, a Session Initiation Protocol (SIP)
server<br>
&gt; &gt; can suffer from overload when the number of SIP messages it receives<br>
&gt; &gt; exceeds the number of messages it can process. Overload is said
to occur<br>
&gt; &gt; when a SIP server does not have sufficient resources to process
all<br>
&gt; &gt; incoming SIP messages. &nbsp;These resources can include CPU,
memory, network<br>
&gt; &gt; bandwidth, input/output, or disk resources.<br>
&gt; &gt; <br>
&gt; &gt; Overload can pose a serious problem for a network of SIP servers.
During<br>
&gt; &gt; periods of overload, the throughput of a network of SIP servers
can be<br>
&gt; &gt; significantly degraded. &nbsp;In fact, overload may lead to a
situation in<br>
&gt; &gt; which the throughput drops down to zero or a small fraction of
the<br>
&gt; &gt; original processing capacity. &nbsp;This is often called congestion
collapse.<br>
&gt; &gt; <br>
&gt; &gt; The objective of a SIP overload control mechanism is to enable
SIP<br>
&gt; &gt; servers to operate close to their capacity limit during times
of overload.<br>
&gt; &gt; <br>
&gt; &gt; The SIP protocol provides a limited mechanism for overload control<br>
&gt; &gt; through its 503 (Service Unavailable) response code and the Retry-After<br>
&gt; &gt; header. &nbsp;However, this mechanism cannot fully prevent overload
of a SIP<br>
&gt; &gt; server and it cannot prevent congestion collapse. &nbsp;In fact,
its on/off<br>
&gt; &gt; behavior may cause traffic to oscillate and shift between SIP
servers<br>
&gt; &gt; and thereby worsen an overload condition. &nbsp;A detailed discussion
of the<br>
&gt; &gt; SIP overload problem, the problems with the 503 (Service Unavailable)<br>
&gt; &gt; response code and the Retry-After header and the requirements
for a SIP<br>
&gt; &gt; overload control mechanism can be found in RFC5390.<br>
&gt; &gt; <br>
&gt; &gt; The objective of the proposed working group is to develop mechanisms
for<br>
&gt; &gt; SIP overload control. The problem domain of SIP overload control
<br>
&gt; can be split into i) overload control between a user agent and a SIP<br>
&gt; server and overload control between SIP servers. A specification <br>
&gt; developed by the proposed working group needs to clearly specify its<br>
&gt; scope. A specification also needs to clearly state any limitations
<br>
&gt; in performance or otherwise the proposed overload control mechanism
may have.<br>
&gt; &gt; <br>
&gt; &gt; Two complementary approaches exist for handling overload situations:<br>
&gt; &gt; - The first mechanism aims at preventing overload in SIP servers
by<br>
&gt; &gt; adjusting the incoming load to a level that is acceptable for
this<br>
&gt; &gt; server. This mechanism uses implicit and/or explicit feedback
to<br>
&gt; &gt; determine when an overload condition occurs in a SIP server and
a<br>
&gt; &gt; reduction in load is required.<br>
&gt; &gt; - The second mechanism aims at preventing overload in SIP servers
by<br>
&gt; &gt; distributing load control filters to SIP servers that throttle
calls<br>
&gt; &gt; based on their destination domain, telephone number prefix or
for a<br>
&gt; &gt; specific user. Such filters can be used, for example, to throttle
calls<br>
&gt; &gt; to a hotline during a ticket-giveaway event.<br>
&gt; &gt; <br>
&gt; &gt; Specifically, the proposed working group will develop the following<br>
&gt; &gt; deliverables:<br>
&gt; &gt; 1. A document describing key design considerations for a SIP
overload<br>
&gt; &gt; control mechanism.<br>
&gt; &gt; 2. A specification for an SIP overload control mechanism based
on<br>
&gt; &gt; implicit/explicit feedback.<br>
&gt; &gt; 3. A specification for a SIP load filtering mechanism.<br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; sip-overload mailing list<br>
&gt; sip-overload@ietf.org<br>
&gt; </font></tt><a href="https://www.ietf.org/mailman/listinfo/sip-overload"><tt><font size=2>https://www.ietf.org/mailman/listinfo/sip-overload</font></tt></a><tt><font size=2><br>
</font></tt>
--=_alternative 005BD65F85257707_=--

From volker.hilt@alcatel-lucent.com  Fri Apr 16 11:50:37 2010
Return-Path: <volker.hilt@alcatel-lucent.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 240E628C0D9; Fri, 16 Apr 2010 11:50:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.005
X-Spam-Level: 
X-Spam-Status: No, score=-1.005 tagged_above=-999 required=5 tests=[AWL=-0.265, BAYES_20=-0.74]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hzJ49jDJeDpU; Fri, 16 Apr 2010 11:50:35 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 73DFA3A6A9D; Fri, 16 Apr 2010 11:50:35 -0700 (PDT)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id o3GIoPmX015162;  Fri, 16 Apr 2010 13:50:25 -0500 (CDT)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id o3GIoLKC008973; Fri, 16 Apr 2010 13:50:24 -0500 (CDT)
Received: from [135.112.131.79] (135.3.63.241) by USNAVSXCHHUB01.ndc.alcatel-lucent.com (135.3.39.110) with Microsoft SMTP Server (TLS) id 8.2.213.0; Fri, 16 Apr 2010 13:50:23 -0500
Message-ID: <4BC8B1CF.3000303@bell-labs.com>
Date: Fri, 16 Apr 2010 14:51:59 -0400
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com> <4BB5409E.5080108@alcatel-lucent.com> <0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com>
In-Reply-To: <0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Cc: DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Gonzalo, Lars Eggert <lars.eggert@nokia.com>, Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 16 Apr 2010 18:50:37 -0000

I think the updated charter and the milestones look good.

Volker




On 4/16/2010 11:56 AM, Robert Sparks wrote:
> I have made some tweaks based on the list discussion and conversations with IESG members.
> This is my current working text. Please comment if you disagree with the changes I've made.
>
> The changes are in the description of overload in the first paragraph, changing the term throughput
> to goodput, and clarifying the discussion of scope and limitations. I've also added some strawman
> milestones. Please comment on those dates.
>
> SIP Overload Control WG Charter
> -------------------------------
>
> As with any network element, a Session Initiation Protocol (SIP) server
> can suffer from overload when the number of SIP messages it receives
> exceeds the number of messages it can process. Overload is said to occur
> when a SIP server does not have sufficient resources to complete the
> processing of all incoming SIP messages within the required time.
> These resources can include CPU, memory, network bandwidth, input/output,
> or disk resources.
>
> Overload can pose a serious problem for a network of SIP servers. During
> periods of overload, the goodput of a network of SIP servers can be
> significantly degraded.  In fact, overload may lead to a situation in
> which the goodput drops down to zero or a small fraction of the
> original processing capacity.  This is often called congestion collapse.
>
> The objective of a SIP overload control mechanism is to enable SIP
> servers to operate close to their capacity limit during times of overload.
>
> The SIP protocol provides a limited mechanism for overload control
> through its 503 (Service Unavailable) response code and the Retry-After
> header.  However, this mechanism cannot fully prevent overload of a SIP
> server and it cannot prevent congestion collapse.  In fact, its on/off
> behavior may cause traffic to oscillate and shift between SIP servers
> and thereby worsen an overload condition.  A detailed discussion of the
> SIP overload problem, the problems with the 503 (Service Unavailable)
> response code and the Retry-After header and the requirements for a SIP
> overload control mechanism can be found in RFC5390.
>
> The objective of the working group is to develop mechanisms for SIP
> overload control. The problem domain of SIP overload control can be split into
> overload control between a user agent and a SIP server and overload control
> between SIP servers.
>
> Any specification developed by the working group needs to clearly specify its
> scope. A specification also needs to clearly state any limitations, in
> performance or otherwise, the specified overload control mechanism may have.  In
> particular, the working group shall carefully define the deployment
> considerations for the effective operation of the specified mechanisms and
> discuss, for example, when a mechanism requires coordinated deployment and
> operation (if all servers need to deploy the same mechanism, certain
> configuration values need to be identical on all servers, etc), when a
> mechanism can become less effective or ineffective under some conditions, or
> especially if there are cases when a mechanism can reduce goodput compared to
> no overload protection. The intent of these considerations is to allow
> potential deployers to make the best use of these mechanism in their particular
> networks.
>
> The working group will consider two complementary approaches for
> handling overload situations:
> - The first mechanism aims at preventing overload in SIP servers by
>    adjusting the incoming load to a level that is acceptable for this
>    server. This mechanism uses implicit and/or explicit feedback to
>    determine when an overload condition occurs in a SIP server and a
>    reduction in load is required.
> - The second mechanism aims at preventing overload in SIP servers by
>    distributing load control filters to SIP servers that throttle calls
>    based on their destination domain, telephone number prefix or for a
>    specific user. Such filters can be used, for example, to throttle calls
>    to a hotline during a ticket-giveaway event.
>
> The working group will develop the following deliverables:
>
>    1. A document describing key design considerations for a SIP overload
>       control mechanism.
>    2. A specification for an SIP overload control mechanism based on
>       implicit/explicit feedback.
>    3. A specification for a SIP load filtering mechanism.
>
> Milestones:
>
> Sep 2010 Design Considerations to IESG for publication as Informational
> Dec 2010 Specification for a SIP overload control mechanism based on implicit/explicit feedback to IESG for publication as Proposed Standard
> May 2011 Specification for a SIP load filtering mechaism to IESG for publication as Proposed Standard
>
>
> On Apr 1, 2010, at 7:55 PM, Volker Hilt wrote:
>
>> All,
>>
>> below is an updated charter proposal for a SIP Overload Control WG. It has additional text that specifications developed by the proposed WG need to define scope and limitations (see below).
>>
>> Thanks,
>>
>> Volker
>>
>>
>>
>> SIP Overload Control WG Charter
>> -------------------------------
>>
>> As with any network element, a Session Initiation Protocol (SIP) server
>> can suffer from overload when the number of SIP messages it receives
>> exceeds the number of messages it can process. Overload is said to occur
>> when a SIP server does not have sufficient resources to process all
>> incoming SIP messages.  These resources can include CPU, memory, network
>> bandwidth, input/output, or disk resources.
>>
>> Overload can pose a serious problem for a network of SIP servers. During
>> periods of overload, the throughput of a network of SIP servers can be
>> significantly degraded.  In fact, overload may lead to a situation in
>> which the throughput drops down to zero or a small fraction of the
>> original processing capacity.  This is often called congestion collapse.
>>
>> The objective of a SIP overload control mechanism is to enable SIP
>> servers to operate close to their capacity limit during times of overload.
>>
>> The SIP protocol provides a limited mechanism for overload control
>> through its 503 (Service Unavailable) response code and the Retry-After
>> header.  However, this mechanism cannot fully prevent overload of a SIP
>> server and it cannot prevent congestion collapse.  In fact, its on/off
>> behavior may cause traffic to oscillate and shift between SIP servers
>> and thereby worsen an overload condition.  A detailed discussion of the
>> SIP overload problem, the problems with the 503 (Service Unavailable)
>> response code and the Retry-After header and the requirements for a SIP
>> overload control mechanism can be found in RFC5390.
>>
>> The objective of the proposed working group is to develop mechanisms for
>> SIP overload control. The problem domain of SIP overload control can be split into i) overload control between a user agent and a SIP server and overload control between SIP servers. A specification developed by the proposed working group needs to clearly specify its scope. A specification also needs to clearly state any limitations in performance or otherwise the proposed overload control mechanism may have.
>>
>> Two complementary approaches exist for handling overload situations:
>> - The first mechanism aims at preventing overload in SIP servers by
>> adjusting the incoming load to a level that is acceptable for this
>> server. This mechanism uses implicit and/or explicit feedback to
>> determine when an overload condition occurs in a SIP server and a
>> reduction in load is required.
>> - The second mechanism aims at preventing overload in SIP servers by
>> distributing load control filters to SIP servers that throttle calls
>> based on their destination domain, telephone number prefix or for a
>> specific user. Such filters can be used, for example, to throttle calls
>> to a hotline during a ticket-giveaway event.
>>
>> Specifically, the proposed working group will develop the following
>> deliverables:
>> 1. A document describing key design considerations for a SIP overload
>> control mechanism.
>> 2. A specification for an SIP overload control mechanism based on
>> implicit/explicit feedback.
>> 3. A specification for a SIP load filtering mechanism.
>>
>>
>


From volker.hilt@alcatel-lucent.com  Fri Apr 16 12:57:06 2010
Return-Path: <volker.hilt@alcatel-lucent.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 995FD3A6855; Fri, 16 Apr 2010 12:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.9
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 tagged_above=-999 required=5 tests=[AWL=1.700, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eh7IGocMUBiW; Fri, 16 Apr 2010 12:57:05 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 9C76828C1A3; Fri, 16 Apr 2010 12:57:04 -0700 (PDT)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id o3GJuqOa009619;  Fri, 16 Apr 2010 14:56:52 -0500 (CDT)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id o3GJupq6013016; Fri, 16 Apr 2010 14:56:52 -0500 (CDT)
Received: from [135.112.131.79] (135.3.63.241) by USNAVSXCHHUB01.ndc.alcatel-lucent.com (135.3.39.110) with Microsoft SMTP Server (TLS) id 8.2.213.0; Fri, 16 Apr 2010 14:56:51 -0500
Message-ID: <4BC8C163.9070202@alcatel-lucent.com>
Date: Fri, 16 Apr 2010 15:58:27 -0400
From: Volker Hilt <volker.hilt@alcatel-lucent.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com> <4BB5409E.5080108@alcatel-lucent.com> <0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com>
In-Reply-To: <0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Gonzalo, Lars Eggert <lars.eggert@nokia.com>, Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 16 Apr 2010 19:57:06 -0000

On 4/16/2010 11:56 AM, Robert Sparks wrote:
> I have made some tweaks based on the list discussion and conversations with IESG members.
> This is my current working text. Please comment if you disagree with the changes I've made.
>
> The changes are in the description of overload in the first paragraph, changing the term throughput
> to goodput, and clarifying the discussion of scope and limitations. I've also added some strawman
> milestones. Please comment on those dates.
>
> SIP Overload Control WG Charter
> -------------------------------
>
> As with any network element, a Session Initiation Protocol (SIP) server
> can suffer from overload when the number of SIP messages it receives
> exceeds the number of messages it can process. Overload is said to occur
> when a SIP server does not have sufficient resources to complete the
> processing of all incoming SIP messages within the required time.
> These resources can include CPU, memory, network bandwidth, input/output,
> or disk resources.
>
> Overload can pose a serious problem for a network of SIP servers. During
> periods of overload, the goodput of a network of SIP servers can be
> significantly degraded.  In fact, overload may lead to a situation in
> which the goodput drops down to zero or a small fraction of the
> original processing capacity.  This is often called congestion collapse.
>
> The objective of a SIP overload control mechanism is to enable SIP
> servers to operate close to their capacity limit during times of overload.
>
> The SIP protocol provides a limited mechanism for overload control
> through its 503 (Service Unavailable) response code and the Retry-After
> header.  However, this mechanism cannot fully prevent overload of a SIP
> server and it cannot prevent congestion collapse.  In fact, its on/off
> behavior may cause traffic to oscillate and shift between SIP servers
> and thereby worsen an overload condition.  A detailed discussion of the
> SIP overload problem, the problems with the 503 (Service Unavailable)
> response code and the Retry-After header and the requirements for a SIP
> overload control mechanism can be found in RFC5390.
>
> The objective of the working group is to develop mechanisms for SIP
> overload control. The problem domain of SIP overload control can be split into
> overload control between a user agent and a SIP server and overload control
> between SIP servers.
>
> Any specification developed by the working group needs to clearly specify its
> scope. A specification also needs to clearly state any limitations, in
> performance or otherwise, the specified overload control mechanism may have.  In
> particular, the working group shall carefully define the deployment
> considerations for the effective operation of the specified mechanisms and
> discuss, for example, when a mechanism requires coordinated deployment and
> operation (if all servers need to deploy the same mechanism, certain
> configuration values need to be identical on all servers, etc), when a
> mechanism can become less effective or ineffective under some conditions, or
> especially if there are cases when a mechanism can reduce goodput compared to
> no overload protection. The intent of these considerations is to allow
> potential deployers to make the best use of these mechanism in their particular
> networks.
>
> The working group will consider two complementary approaches for
> handling overload situations:
> - The first mechanism aims at preventing overload in SIP servers by
>    adjusting the incoming load to a level that is acceptable for this
>    server. This mechanism uses implicit and/or explicit feedback to
>    determine when an overload condition occurs in a SIP server and a
>    reduction in load is required.
> - The second mechanism aims at preventing overload in SIP servers by
>    distributing load control filters to SIP servers that throttle calls
>    based on their destination domain, telephone number prefix or for a
>    specific user. Such filters can be used, for example, to throttle calls
>    to a hotline during a ticket-giveaway event.
>
> The working group will develop the following deliverables:
>
>    1. A document describing key design considerations for a SIP overload
>       control mechanism.
>    2. A specification for an SIP overload control mechanism based on
>       implicit/explicit feedback.
>    3. A specification for a SIP load filtering mechanism.
>
> Milestones:
>
> Sep 2010 Design Considerations to IESG for publication as Informational
> Dec 2010 Specification for a SIP overload control mechanism based on implicit/explicit feedback to IESG for publication as Proposed Standard
> May 2011 Specification for a SIP load filtering mechaism to IESG for publication as Proposed Standard
>
>
> On Apr 1, 2010, at 7:55 PM, Volker Hilt wrote:
>
>> All,
>>
>> below is an updated charter proposal for a SIP Overload Control WG. It has additional text that specifications developed by the proposed WG need to define scope and limitations (see below).
>>
>> Thanks,
>>
>> Volker
>>
>>
>>
>> SIP Overload Control WG Charter
>> -------------------------------
>>
>> As with any network element, a Session Initiation Protocol (SIP) server
>> can suffer from overload when the number of SIP messages it receives
>> exceeds the number of messages it can process. Overload is said to occur
>> when a SIP server does not have sufficient resources to process all
>> incoming SIP messages.  These resources can include CPU, memory, network
>> bandwidth, input/output, or disk resources.
>>
>> Overload can pose a serious problem for a network of SIP servers. During
>> periods of overload, the throughput of a network of SIP servers can be
>> significantly degraded.  In fact, overload may lead to a situation in
>> which the throughput drops down to zero or a small fraction of the
>> original processing capacity.  This is often called congestion collapse.
>>
>> The objective of a SIP overload control mechanism is to enable SIP
>> servers to operate close to their capacity limit during times of overload.
>>
>> The SIP protocol provides a limited mechanism for overload control
>> through its 503 (Service Unavailable) response code and the Retry-After
>> header.  However, this mechanism cannot fully prevent overload of a SIP
>> server and it cannot prevent congestion collapse.  In fact, its on/off
>> behavior may cause traffic to oscillate and shift between SIP servers
>> and thereby worsen an overload condition.  A detailed discussion of the
>> SIP overload problem, the problems with the 503 (Service Unavailable)
>> response code and the Retry-After header and the requirements for a SIP
>> overload control mechanism can be found in RFC5390.
>>
>> The objective of the proposed working group is to develop mechanisms for
>> SIP overload control. The problem domain of SIP overload control can be split into i) overload control between a user agent and a SIP server and overload control between SIP servers. A specification developed by the proposed working group needs to clearly specify its scope. A specification also needs to clearly state any limitations in performance or otherwise the proposed overload control mechanism may have.
>>
>> Two complementary approaches exist for handling overload situations:
>> - The first mechanism aims at preventing overload in SIP servers by
>> adjusting the incoming load to a level that is acceptable for this
>> server. This mechanism uses implicit and/or explicit feedback to
>> determine when an overload condition occurs in a SIP server and a
>> reduction in load is required.
>> - The second mechanism aims at preventing overload in SIP servers by
>> distributing load control filters to SIP servers that throttle calls
>> based on their destination domain, telephone number prefix or for a
>> specific user. Such filters can be used, for example, to throttle calls
>> to a hotline during a ticket-giveaway event.
>>
>> Specifically, the proposed working group will develop the following
>> deliverables:
>> 1. A document describing key design considerations for a SIP overload
>> control mechanism.
>> 2. A specification for an SIP overload control mechanism based on
>> implicit/explicit feedback.
>> 3. A specification for a SIP load filtering mechanism.
>>
>>
>


From volker.hilt@alcatel-lucent.com  Fri Apr 16 13:00:48 2010
Return-Path: <volker.hilt@alcatel-lucent.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E0B4A3A68AA; Fri, 16 Apr 2010 13:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[AWL=0.850,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y2-v6c-eRXLt; Fri, 16 Apr 2010 13:00:47 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 5DA893A69D0; Fri, 16 Apr 2010 13:00:47 -0700 (PDT)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id o3GK0acb017644;  Fri, 16 Apr 2010 15:00:36 -0500 (CDT)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id o3GJxtNT015860; Fri, 16 Apr 2010 15:00:36 -0500 (CDT)
Received: from [135.112.131.79] (135.3.63.241) by USNAVSXCHHUB01.ndc.alcatel-lucent.com (135.3.39.110) with Microsoft SMTP Server (TLS) id 8.2.213.0; Fri, 16 Apr 2010 15:00:36 -0500
Message-ID: <4BC8C243.3040405@alcatel-lucent.com>
Date: Fri, 16 Apr 2010 16:02:11 -0400
From: Volker Hilt <volker.hilt@alcatel-lucent.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>, DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Lars Eggert <lars.eggert@nokia.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com> <4BB5409E.5080108@alcatel-lucent.com> <0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com>
In-Reply-To: <0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 16 Apr 2010 20:00:49 -0000

An slight update to the charter Robert has sent out to address Janet's 
comment.

Volker



SIP Overload Control WG Charter
-------------------------------

As with any network element, a Session Initiation Protocol (SIP) server 
can suffer from overload when the number of SIP messages it receives 
exceeds the number of messages it can process. Overload is said to occur 
when a SIP server does not have sufficient resources to complete the 
processing of all incoming SIP messages within the required time. These 
resources can include CPU, memory, network bandwidth, input/output, or 
disk resources.

Overload can pose a serious problem for a network of SIP servers. During 
periods of overload, the goodput of a network of SIP servers can be 
significantly degraded.  In fact, overload may lead to a situation in 
which the goodput drops down to zero or a small fraction of the original 
processing capacity.  This is often called congestion collapse.

The objective of a SIP overload control mechanism is to enable SIP 
servers to operate close to their capacity limit during times of overload.

The SIP protocol provides a limited mechanism for overload control 
through its 503 (Service Unavailable) response code and the Retry-After 
header.  However, this mechanism cannot fully prevent overload of a SIP 
server and it cannot prevent congestion collapse.  In fact, its on/off 
behavior may cause traffic to oscillate and shift between SIP servers 
and thereby worsen an overload condition.  A detailed discussion of the 
SIP overload problem, the problems with the 503 (Service Unavailable) 
response code and the Retry-After header and the requirements for a SIP 
overload control mechanism can be found in RFC5390.

The objective of the working group is to develop mechanisms for SIP 
overload control. The problem domain of SIP overload control can be 
split into overload control between a user agent and a SIP server and 
overload control between SIP servers.

Any specification developed by the working group needs to clearly 
specify its scope. A specification also needs to clearly state any 
limitations, in performance or otherwise, the specified overload control 
mechanism may have.  In particular, the working group shall carefully 
define the deployment considerations for the effective operation of the 
specified mechanisms and discuss, for example, when a mechanism requires 
coordinated deployment and operation (if all servers need to deploy the 
same mechanism, certain configuration values need to be identical on all 
servers, etc), when a mechanism can become less effective or ineffective 
under some conditions, or especially if there are cases when a mechanism 
can reduce goodput compared to no overload protection. The intent of 
these considerations is to allow potential deployers to make the best 
use of these mechanism in their particular
networks.

The working group will consider two complementary approaches for 
handling overload situations:
- The first mechanism aims at preventing overload in SIP servers by
   adjusting the incoming load to a level that is acceptable for this
   server. This mechanism uses implicit and/or explicit feedback to
   determine when an overload condition occurs in a SIP server and a
   reduction in load is required.
- The second mechanism aims at preventing overload in SIP servers by
   distributing load control filters to SIP servers that throttle calls
   based on their source or destination domain, telephone number prefix
   or for a specific user. Such filters can be used, for example, to
   throttle calls to a hotline during a ticket-giveaway event.

The working group will develop the following deliverables:

   1. A document describing key design considerations for a SIP overload
      control mechanism.
   2. A specification for an SIP overload control mechanism based on
      implicit/explicit feedback.
   3. A specification for a SIP load filtering mechanism.

Milestones:

Sep 2010 Design Considerations to IESG for publication as Informational
Dec 2010 Specification for a SIP overload control mechanism based on 
implicit/explicit feedback to IESG for publication as Proposed Standard
May 2011 Specification for a SIP load filtering mechaism to IESG for 
publication as Proposed Standard





On 4/16/2010 11:56 AM, Robert Sparks wrote:
> I have made some tweaks based on the list discussion and conversations with IESG members.
> This is my current working text. Please comment if you disagree with the changes I've made.
>
> The changes are in the description of overload in the first paragraph, changing the term throughput
> to goodput, and clarifying the discussion of scope and limitations. I've also added some strawman
> milestones. Please comment on those dates.
>
> SIP Overload Control WG Charter
> -------------------------------
>
> As with any network element, a Session Initiation Protocol (SIP) server
> can suffer from overload when the number of SIP messages it receives
> exceeds the number of messages it can process. Overload is said to occur
> when a SIP server does not have sufficient resources to complete the
> processing of all incoming SIP messages within the required time.
> These resources can include CPU, memory, network bandwidth, input/output,
> or disk resources.
>
> Overload can pose a serious problem for a network of SIP servers. During
> periods of overload, the goodput of a network of SIP servers can be
> significantly degraded.  In fact, overload may lead to a situation in
> which the goodput drops down to zero or a small fraction of the
> original processing capacity.  This is often called congestion collapse.
>
> The objective of a SIP overload control mechanism is to enable SIP
> servers to operate close to their capacity limit during times of overload.
>
> The SIP protocol provides a limited mechanism for overload control
> through its 503 (Service Unavailable) response code and the Retry-After
> header.  However, this mechanism cannot fully prevent overload of a SIP
> server and it cannot prevent congestion collapse.  In fact, its on/off
> behavior may cause traffic to oscillate and shift between SIP servers
> and thereby worsen an overload condition.  A detailed discussion of the
> SIP overload problem, the problems with the 503 (Service Unavailable)
> response code and the Retry-After header and the requirements for a SIP
> overload control mechanism can be found in RFC5390.
>
> The objective of the working group is to develop mechanisms for SIP
> overload control. The problem domain of SIP overload control can be split into
> overload control between a user agent and a SIP server and overload control
> between SIP servers.
>
> Any specification developed by the working group needs to clearly specify its
> scope. A specification also needs to clearly state any limitations, in
> performance or otherwise, the specified overload control mechanism may have.  In
> particular, the working group shall carefully define the deployment
> considerations for the effective operation of the specified mechanisms and
> discuss, for example, when a mechanism requires coordinated deployment and
> operation (if all servers need to deploy the same mechanism, certain
> configuration values need to be identical on all servers, etc), when a
> mechanism can become less effective or ineffective under some conditions, or
> especially if there are cases when a mechanism can reduce goodput compared to
> no overload protection. The intent of these considerations is to allow
> potential deployers to make the best use of these mechanism in their particular
> networks.
>
> The working group will consider two complementary approaches for
> handling overload situations:
> - The first mechanism aims at preventing overload in SIP servers by
>    adjusting the incoming load to a level that is acceptable for this
>    server. This mechanism uses implicit and/or explicit feedback to
>    determine when an overload condition occurs in a SIP server and a
>    reduction in load is required.
> - The second mechanism aims at preventing overload in SIP servers by
>    distributing load control filters to SIP servers that throttle calls
>    based on their destination domain, telephone number prefix or for a
>    specific user. Such filters can be used, for example, to throttle calls
>    to a hotline during a ticket-giveaway event.
>
> The working group will develop the following deliverables:
>
>    1. A document describing key design considerations for a SIP overload
>       control mechanism.
>    2. A specification for an SIP overload control mechanism based on
>       implicit/explicit feedback.
>    3. A specification for a SIP load filtering mechanism.
>
> Milestones:
>
> Sep 2010 Design Considerations to IESG for publication as Informational
> Dec 2010 Specification for a SIP overload control mechanism based on implicit/explicit feedback to IESG for publication as Proposed Standard
> May 2011 Specification for a SIP load filtering mechaism to IESG for publication as Proposed Standard
>
>
> On Apr 1, 2010, at 7:55 PM, Volker Hilt wrote:
>
>> All,
>>
>> below is an updated charter proposal for a SIP Overload Control WG. It has additional text that specifications developed by the proposed WG need to define scope and limitations (see below).
>>
>> Thanks,
>>
>> Volker
>>
>>
>>
>> SIP Overload Control WG Charter
>> -------------------------------
>>
>> As with any network element, a Session Initiation Protocol (SIP) server
>> can suffer from overload when the number of SIP messages it receives
>> exceeds the number of messages it can process. Overload is said to occur
>> when a SIP server does not have sufficient resources to process all
>> incoming SIP messages.  These resources can include CPU, memory, network
>> bandwidth, input/output, or disk resources.
>>
>> Overload can pose a serious problem for a network of SIP servers. During
>> periods of overload, the throughput of a network of SIP servers can be
>> significantly degraded.  In fact, overload may lead to a situation in
>> which the throughput drops down to zero or a small fraction of the
>> original processing capacity.  This is often called congestion collapse.
>>
>> The objective of a SIP overload control mechanism is to enable SIP
>> servers to operate close to their capacity limit during times of overload.
>>
>> The SIP protocol provides a limited mechanism for overload control
>> through its 503 (Service Unavailable) response code and the Retry-After
>> header.  However, this mechanism cannot fully prevent overload of a SIP
>> server and it cannot prevent congestion collapse.  In fact, its on/off
>> behavior may cause traffic to oscillate and shift between SIP servers
>> and thereby worsen an overload condition.  A detailed discussion of the
>> SIP overload problem, the problems with the 503 (Service Unavailable)
>> response code and the Retry-After header and the requirements for a SIP
>> overload control mechanism can be found in RFC5390.
>>
>> The objective of the proposed working group is to develop mechanisms for
>> SIP overload control. The problem domain of SIP overload control can be split into i) overload control between a user agent and a SIP server and overload control between SIP servers. A specification developed by the proposed working group needs to clearly specify its scope. A specification also needs to clearly state any limitations in performance or otherwise the proposed overload control mechanism may have.
>>
>> Two complementary approaches exist for handling overload situations:
>> - The first mechanism aims at preventing overload in SIP servers by
>> adjusting the incoming load to a level that is acceptable for this
>> server. This mechanism uses implicit and/or explicit feedback to
>> determine when an overload condition occurs in a SIP server and a
>> reduction in load is required.
>> - The second mechanism aims at preventing overload in SIP servers by
>> distributing load control filters to SIP servers that throttle calls
>> based on their destination domain, telephone number prefix or for a
>> specific user. Such filters can be used, for example, to throttle calls
>> to a hotline during a ticket-giveaway event.
>>
>> Specifically, the proposed working group will develop the following
>> deliverables:
>> 1. A document describing key design considerations for a SIP overload
>> control mechanism.
>> 2. A specification for an SIP overload control mechanism based on
>> implicit/explicit feedback.
>> 3. A specification for a SIP load filtering mechanism.
>>
>>
>


From md3135@att.com  Fri Apr 16 13:02:04 2010
Return-Path: <md3135@att.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ECE333A6AA5; Fri, 16 Apr 2010 13:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.36
X-Spam-Level: 
X-Spam-Status: No, score=-106.36 tagged_above=-999 required=5 tests=[AWL=0.239, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m9DUfs9Y1bck; Fri, 16 Apr 2010 13:02:03 -0700 (PDT)
Received: from mail129.messagelabs.com (mail129.messagelabs.com [216.82.250.147]) by core3.amsl.com (Postfix) with ESMTP id DB9533A68A2; Fri, 16 Apr 2010 13:02:00 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: md3135@att.com
X-Msg-Ref: server-9.tower-129.messagelabs.com!1271448112!37196892!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 1670 invoked from network); 16 Apr 2010 20:01:52 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-9.tower-129.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Apr 2010 20:01:52 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o3GK1aUA015909; Fri, 16 Apr 2010 16:01:37 -0400
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o3GK1Udo015813; Fri, 16 Apr 2010 16:01:30 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Fri, 16 Apr 2010 16:01:41 -0400
Message-ID: <14C85D6CCBE92743AF33663BF5D24EBA02BD4ED8@gaalpa1msgusr7e.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] Proposed SIP Overload Control Charter
Thread-Index: AcrdnwG1/NdK8qs7TSGUH8mtFCpxOgAAJ92F
From: "DOLLY, MARTIN C (ATTLABS)" <md3135@att.com>
To: <volker.hilt@alcatel-lucent.com>, <rjsparks@nostrum.com>
X-Mailman-Approved-At: Fri, 16 Apr 2010 13:04:37 -0700
Cc: Gonzalo@core3.amsl.com, dispatch@ietf.org, sip-overload@ietf.org, Gonzalo.Camarillo@ericsson.com, lars.eggert@nokia.com
Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 16 Apr 2010 20:02:05 -0000

U28gd2hlcmUgZGlkIHRoZSBjb25mZXJlbmNlIGNhbGxzIGdvIEFMVSBWb2xrZXINCg0KU3BlYWtp
bmcgYXMgQVRUDQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCkZyb206IHNpcC1vdmVy
bG9hZC1ib3VuY2VzQGlldGYub3JnIDxzaXAtb3ZlcmxvYWQtYm91bmNlc0BpZXRmLm9yZz4NClRv
OiBSb2JlcnQgU3BhcmtzIDxyanNwYXJrc0Bub3N0cnVtLmNvbT4NCkNjOiBESVNQQVRDSCA8ZGlz
cGF0Y2hAaWV0Zi5vcmc+OyBzaXAtb3ZlcmxvYWRAaWV0Zi5vcmcgPHNpcC1vdmVybG9hZEBpZXRm
Lm9yZz47IEdvbnphbG9AY29yZTMuYW1zbC5jb20gPEdvbnphbG9AY29yZTMuYW1zbC5jb20+OyBM
YXJzIEVnZ2VydCA8bGFycy5lZ2dlcnRAbm9raWEuY29tPjsgQ2FtYXJpbGxvIDxHb256YWxvLkNh
bWFyaWxsb0Blcmljc3Nvbi5jb20+DQpTZW50OiBGcmkgQXByIDE2IDE1OjU4OjI3IDIwMTANClN1
YmplY3Q6IFJlOiBbc2lwLW92ZXJsb2FkXSBQcm9wb3NlZCBTSVAgT3ZlcmxvYWQgQ29udHJvbCBD
aGFydGVyDQoNCk9uIDQvMTYvMjAxMCAxMTo1NiBBTSwgUm9iZXJ0IFNwYXJrcyB3cm90ZToNCj4g
SSBoYXZlIG1hZGUgc29tZSB0d2Vha3MgYmFzZWQgb24gdGhlIGxpc3QgZGlzY3Vzc2lvbiBhbmQg
Y29udmVyc2F0aW9ucyB3aXRoIElFU0cgbWVtYmVycy4NCj4gVGhpcyBpcyBteSBjdXJyZW50IHdv
cmtpbmcgdGV4dC4gUGxlYXNlIGNvbW1lbnQgaWYgeW91IGRpc2FncmVlIHdpdGggdGhlIGNoYW5n
ZXMgSSd2ZSBtYWRlLg0KPg0KPiBUaGUgY2hhbmdlcyBhcmUgaW4gdGhlIGRlc2NyaXB0aW9uIG9m
IG92ZXJsb2FkIGluIHRoZSBmaXJzdCBwYXJhZ3JhcGgsIGNoYW5naW5nIHRoZSB0ZXJtIHRocm91
Z2hwdXQNCj4gdG8gZ29vZHB1dCwgYW5kIGNsYXJpZnlpbmcgdGhlIGRpc2N1c3Npb24gb2Ygc2Nv
cGUgYW5kIGxpbWl0YXRpb25zLiBJJ3ZlIGFsc28gYWRkZWQgc29tZSBzdHJhd21hbg0KPiBtaWxl
c3RvbmVzLiBQbGVhc2UgY29tbWVudCBvbiB0aG9zZSBkYXRlcy4NCj4NCj4gU0lQIE92ZXJsb2Fk
IENvbnRyb2wgV0cgQ2hhcnRlcg0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+
DQo+IEFzIHdpdGggYW55IG5ldHdvcmsgZWxlbWVudCwgYSBTZXNzaW9uIEluaXRpYXRpb24gUHJv
dG9jb2wgKFNJUCkgc2VydmVyDQo+IGNhbiBzdWZmZXIgZnJvbSBvdmVybG9hZCB3aGVuIHRoZSBu
dW1iZXIgb2YgU0lQIG1lc3NhZ2VzIGl0IHJlY2VpdmVzDQo+IGV4Y2VlZHMgdGhlIG51bWJlciBv
ZiBtZXNzYWdlcyBpdCBjYW4gcHJvY2Vzcy4gT3ZlcmxvYWQgaXMgc2FpZCB0byBvY2N1cg0KPiB3
aGVuIGEgU0lQIHNlcnZlciBkb2VzIG5vdCBoYXZlIHN1ZmZpY2llbnQgcmVzb3VyY2VzIHRvIGNv
bXBsZXRlIHRoZQ0KPiBwcm9jZXNzaW5nIG9mIGFsbCBpbmNvbWluZyBTSVAgbWVzc2FnZXMgd2l0
aGluIHRoZSByZXF1aXJlZCB0aW1lLg0KPiBUaGVzZSByZXNvdXJjZXMgY2FuIGluY2x1ZGUgQ1BV
LCBtZW1vcnksIG5ldHdvcmsgYmFuZHdpZHRoLCBpbnB1dC9vdXRwdXQsDQo+IG9yIGRpc2sgcmVz
b3VyY2VzLg0KPg0KPiBPdmVybG9hZCBjYW4gcG9zZSBhIHNlcmlvdXMgcHJvYmxlbSBmb3IgYSBu
ZXR3b3JrIG9mIFNJUCBzZXJ2ZXJzLiBEdXJpbmcNCj4gcGVyaW9kcyBvZiBvdmVybG9hZCwgdGhl
IGdvb2RwdXQgb2YgYSBuZXR3b3JrIG9mIFNJUCBzZXJ2ZXJzIGNhbiBiZQ0KPiBzaWduaWZpY2Fu
dGx5IGRlZ3JhZGVkLiAgSW4gZmFjdCwgb3ZlcmxvYWQgbWF5IGxlYWQgdG8gYSBzaXR1YXRpb24g
aW4NCj4gd2hpY2ggdGhlIGdvb2RwdXQgZHJvcHMgZG93biB0byB6ZXJvIG9yIGEgc21hbGwgZnJh
Y3Rpb24gb2YgdGhlDQo+IG9yaWdpbmFsIHByb2Nlc3NpbmcgY2FwYWNpdHkuICBUaGlzIGlzIG9m
dGVuIGNhbGxlZCBjb25nZXN0aW9uIGNvbGxhcHNlLg0KPg0KPiBUaGUgb2JqZWN0aXZlIG9mIGEg
U0lQIG92ZXJsb2FkIGNvbnRyb2wgbWVjaGFuaXNtIGlzIHRvIGVuYWJsZSBTSVANCj4gc2VydmVy
cyB0byBvcGVyYXRlIGNsb3NlIHRvIHRoZWlyIGNhcGFjaXR5IGxpbWl0IGR1cmluZyB0aW1lcyBv
ZiBvdmVybG9hZC4NCj4NCj4gVGhlIFNJUCBwcm90b2NvbCBwcm92aWRlcyBhIGxpbWl0ZWQgbWVj
aGFuaXNtIGZvciBvdmVybG9hZCBjb250cm9sDQo+IHRocm91Z2ggaXRzIDUwMyAoU2VydmljZSBV
bmF2YWlsYWJsZSkgcmVzcG9uc2UgY29kZSBhbmQgdGhlIFJldHJ5LUFmdGVyDQo+IGhlYWRlci4g
IEhvd2V2ZXIsIHRoaXMgbWVjaGFuaXNtIGNhbm5vdCBmdWxseSBwcmV2ZW50IG92ZXJsb2FkIG9m
IGEgU0lQDQo+IHNlcnZlciBhbmQgaXQgY2Fubm90IHByZXZlbnQgY29uZ2VzdGlvbiBjb2xsYXBz
ZS4gIEluIGZhY3QsIGl0cyBvbi9vZmYNCj4gYmVoYXZpb3IgbWF5IGNhdXNlIHRyYWZmaWMgdG8g
b3NjaWxsYXRlIGFuZCBzaGlmdCBiZXR3ZWVuIFNJUCBzZXJ2ZXJzDQo+IGFuZCB0aGVyZWJ5IHdv
cnNlbiBhbiBvdmVybG9hZCBjb25kaXRpb24uICBBIGRldGFpbGVkIGRpc2N1c3Npb24gb2YgdGhl
DQo+IFNJUCBvdmVybG9hZCBwcm9ibGVtLCB0aGUgcHJvYmxlbXMgd2l0aCB0aGUgNTAzIChTZXJ2
aWNlIFVuYXZhaWxhYmxlKQ0KPiByZXNwb25zZSBjb2RlIGFuZCB0aGUgUmV0cnktQWZ0ZXIgaGVh
ZGVyIGFuZCB0aGUgcmVxdWlyZW1lbnRzIGZvciBhIFNJUA0KPiBvdmVybG9hZCBjb250cm9sIG1l
Y2hhbmlzbSBjYW4gYmUgZm91bmQgaW4gUkZDNTM5MC4NCj4NCj4gVGhlIG9iamVjdGl2ZSBvZiB0
aGUgd29ya2luZyBncm91cCBpcyB0byBkZXZlbG9wIG1lY2hhbmlzbXMgZm9yIFNJUA0KPiBvdmVy
bG9hZCBjb250cm9sLiBUaGUgcHJvYmxlbSBkb21haW4gb2YgU0lQIG92ZXJsb2FkIGNvbnRyb2wg
Y2FuIGJlIHNwbGl0IGludG8NCj4gb3ZlcmxvYWQgY29udHJvbCBiZXR3ZWVuIGEgdXNlciBhZ2Vu
dCBhbmQgYSBTSVAgc2VydmVyIGFuZCBvdmVybG9hZCBjb250cm9sDQo+IGJldHdlZW4gU0lQIHNl
cnZlcnMuDQo+DQo+IEFueSBzcGVjaWZpY2F0aW9uIGRldmVsb3BlZCBieSB0aGUgd29ya2luZyBn
cm91cCBuZWVkcyB0byBjbGVhcmx5IHNwZWNpZnkgaXRzDQo+IHNjb3BlLiBBIHNwZWNpZmljYXRp
b24gYWxzbyBuZWVkcyB0byBjbGVhcmx5IHN0YXRlIGFueSBsaW1pdGF0aW9ucywgaW4NCj4gcGVy
Zm9ybWFuY2Ugb3Igb3RoZXJ3aXNlLCB0aGUgc3BlY2lmaWVkIG92ZXJsb2FkIGNvbnRyb2wgbWVj
aGFuaXNtIG1heSBoYXZlLiAgSW4NCj4gcGFydGljdWxhciwgdGhlIHdvcmtpbmcgZ3JvdXAgc2hh
bGwgY2FyZWZ1bGx5IGRlZmluZSB0aGUgZGVwbG95bWVudA0KPiBjb25zaWRlcmF0aW9ucyBmb3Ig
dGhlIGVmZmVjdGl2ZSBvcGVyYXRpb24gb2YgdGhlIHNwZWNpZmllZCBtZWNoYW5pc21zIGFuZA0K
PiBkaXNjdXNzLCBmb3IgZXhhbXBsZSwgd2hlbiBhIG1lY2hhbmlzbSByZXF1aXJlcyBjb29yZGlu
YXRlZCBkZXBsb3ltZW50IGFuZA0KPiBvcGVyYXRpb24gKGlmIGFsbCBzZXJ2ZXJzIG5lZWQgdG8g
ZGVwbG95IHRoZSBzYW1lIG1lY2hhbmlzbSwgY2VydGFpbg0KPiBjb25maWd1cmF0aW9uIHZhbHVl
cyBuZWVkIHRvIGJlIGlkZW50aWNhbCBvbiBhbGwgc2VydmVycywgZXRjKSwgd2hlbiBhDQo+IG1l
Y2hhbmlzbSBjYW4gYmVjb21lIGxlc3MgZWZmZWN0aXZlIG9yIGluZWZmZWN0aXZlIHVuZGVyIHNv
bWUgY29uZGl0aW9ucywgb3INCj4gZXNwZWNpYWxseSBpZiB0aGVyZSBhcmUgY2FzZXMgd2hlbiBh
IG1lY2hhbmlzbSBjYW4gcmVkdWNlIGdvb2RwdXQgY29tcGFyZWQgdG8NCj4gbm8gb3ZlcmxvYWQg
cHJvdGVjdGlvbi4gVGhlIGludGVudCBvZiB0aGVzZSBjb25zaWRlcmF0aW9ucyBpcyB0byBhbGxv
dw0KPiBwb3RlbnRpYWwgZGVwbG95ZXJzIHRvIG1ha2UgdGhlIGJlc3QgdXNlIG9mIHRoZXNlIG1l
Y2hhbmlzbSBpbiB0aGVpciBwYXJ0aWN1bGFyDQo+IG5ldHdvcmtzLg0KPg0KPiBUaGUgd29ya2lu
ZyBncm91cCB3aWxsIGNvbnNpZGVyIHR3byBjb21wbGVtZW50YXJ5IGFwcHJvYWNoZXMgZm9yDQo+
IGhhbmRsaW5nIG92ZXJsb2FkIHNpdHVhdGlvbnM6DQo+IC0gVGhlIGZpcnN0IG1lY2hhbmlzbSBh
aW1zIGF0IHByZXZlbnRpbmcgb3ZlcmxvYWQgaW4gU0lQIHNlcnZlcnMgYnkNCj4gICAgYWRqdXN0
aW5nIHRoZSBpbmNvbWluZyBsb2FkIHRvIGEgbGV2ZWwgdGhhdCBpcyBhY2NlcHRhYmxlIGZvciB0
aGlzDQo+ICAgIHNlcnZlci4gVGhpcyBtZWNoYW5pc20gdXNlcyBpbXBsaWNpdCBhbmQvb3IgZXhw
bGljaXQgZmVlZGJhY2sgdG8NCj4gICAgZGV0ZXJtaW5lIHdoZW4gYW4gb3ZlcmxvYWQgY29uZGl0
aW9uIG9jY3VycyBpbiBhIFNJUCBzZXJ2ZXIgYW5kIGENCj4gICAgcmVkdWN0aW9uIGluIGxvYWQg
aXMgcmVxdWlyZWQuDQo+IC0gVGhlIHNlY29uZCBtZWNoYW5pc20gYWltcyBhdCBwcmV2ZW50aW5n
IG92ZXJsb2FkIGluIFNJUCBzZXJ2ZXJzIGJ5DQo+ICAgIGRpc3RyaWJ1dGluZyBsb2FkIGNvbnRy
b2wgZmlsdGVycyB0byBTSVAgc2VydmVycyB0aGF0IHRocm90dGxlIGNhbGxzDQo+ICAgIGJhc2Vk
IG9uIHRoZWlyIGRlc3RpbmF0aW9uIGRvbWFpbiwgdGVsZXBob25lIG51bWJlciBwcmVmaXggb3Ig
Zm9yIGENCj4gICAgc3BlY2lmaWMgdXNlci4gU3VjaCBmaWx0ZXJzIGNhbiBiZSB1c2VkLCBmb3Ig
ZXhhbXBsZSwgdG8gdGhyb3R0bGUgY2FsbHMNCj4gICAgdG8gYSBob3RsaW5lIGR1cmluZyBhIHRp
Y2tldC1naXZlYXdheSBldmVudC4NCj4NCj4gVGhlIHdvcmtpbmcgZ3JvdXAgd2lsbCBkZXZlbG9w
IHRoZSBmb2xsb3dpbmcgZGVsaXZlcmFibGVzOg0KPg0KPiAgICAxLiBBIGRvY3VtZW50IGRlc2Ny
aWJpbmcga2V5IGRlc2lnbiBjb25zaWRlcmF0aW9ucyBmb3IgYSBTSVAgb3ZlcmxvYWQNCj4gICAg
ICAgY29udHJvbCBtZWNoYW5pc20uDQo+ICAgIDIuIEEgc3BlY2lmaWNhdGlvbiBmb3IgYW4gU0lQ
IG92ZXJsb2FkIGNvbnRyb2wgbWVjaGFuaXNtIGJhc2VkIG9uDQo+ICAgICAgIGltcGxpY2l0L2V4
cGxpY2l0IGZlZWRiYWNrLg0KPiAgICAzLiBBIHNwZWNpZmljYXRpb24gZm9yIGEgU0lQIGxvYWQg
ZmlsdGVyaW5nIG1lY2hhbmlzbS4NCj4NCj4gTWlsZXN0b25lczoNCj4NCj4gU2VwIDIwMTAgRGVz
aWduIENvbnNpZGVyYXRpb25zIHRvIElFU0cgZm9yIHB1YmxpY2F0aW9uIGFzIEluZm9ybWF0aW9u
YWwNCj4gRGVjIDIwMTAgU3BlY2lmaWNhdGlvbiBmb3IgYSBTSVAgb3ZlcmxvYWQgY29udHJvbCBt
ZWNoYW5pc20gYmFzZWQgb24gaW1wbGljaXQvZXhwbGljaXQgZmVlZGJhY2sgdG8gSUVTRyBmb3Ig
cHVibGljYXRpb24gYXMgUHJvcG9zZWQgU3RhbmRhcmQNCj4gTWF5IDIwMTEgU3BlY2lmaWNhdGlv
biBmb3IgYSBTSVAgbG9hZCBmaWx0ZXJpbmcgbWVjaGFpc20gdG8gSUVTRyBmb3IgcHVibGljYXRp
b24gYXMgUHJvcG9zZWQgU3RhbmRhcmQNCj4NCj4NCj4gT24gQXByIDEsIDIwMTAsIGF0IDc6NTUg
UE0sIFZvbGtlciBIaWx0IHdyb3RlOg0KPg0KPj4gQWxsLA0KPj4NCj4+IGJlbG93IGlzIGFuIHVw
ZGF0ZWQgY2hhcnRlciBwcm9wb3NhbCBmb3IgYSBTSVAgT3ZlcmxvYWQgQ29udHJvbCBXRy4gSXQg
aGFzIGFkZGl0aW9uYWwgdGV4dCB0aGF0IHNwZWNpZmljYXRpb25zIGRldmVsb3BlZCBieSB0aGUg
cHJvcG9zZWQgV0cgbmVlZCB0byBkZWZpbmUgc2NvcGUgYW5kIGxpbWl0YXRpb25zIChzZWUgYmVs
b3cpLg0KPj4NCj4+IFRoYW5rcywNCj4+DQo+PiBWb2xrZXINCj4+DQo+Pg0KPj4NCj4+IFNJUCBP
dmVybG9hZCBDb250cm9sIFdHIENoYXJ0ZXINCj4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0NCj4+DQo+PiBBcyB3aXRoIGFueSBuZXR3b3JrIGVsZW1lbnQsIGEgU2Vzc2lvbiBJbml0
aWF0aW9uIFByb3RvY29sIChTSVApIHNlcnZlcg0KPj4gY2FuIHN1ZmZlciBmcm9tIG92ZXJsb2Fk
IHdoZW4gdGhlIG51bWJlciBvZiBTSVAgbWVzc2FnZXMgaXQgcmVjZWl2ZXMNCj4+IGV4Y2VlZHMg
dGhlIG51bWJlciBvZiBtZXNzYWdlcyBpdCBjYW4gcHJvY2Vzcy4gT3ZlcmxvYWQgaXMgc2FpZCB0
byBvY2N1cg0KPj4gd2hlbiBhIFNJUCBzZXJ2ZXIgZG9lcyBub3QgaGF2ZSBzdWZmaWNpZW50IHJl
c291cmNlcyB0byBwcm9jZXNzIGFsbA0KPj4gaW5jb21pbmcgU0lQIG1lc3NhZ2VzLiAgVGhlc2Ug
cmVzb3VyY2VzIGNhbiBpbmNsdWRlIENQVSwgbWVtb3J5LCBuZXR3b3JrDQo+PiBiYW5kd2lkdGgs
IGlucHV0L291dHB1dCwgb3IgZGlzayByZXNvdXJjZXMuDQo+Pg0KPj4gT3ZlcmxvYWQgY2FuIHBv
c2UgYSBzZXJpb3VzIHByb2JsZW0gZm9yIGEgbmV0d29yayBvZiBTSVAgc2VydmVycy4gRHVyaW5n
DQo+PiBwZXJpb2RzIG9mIG92ZXJsb2FkLCB0aGUgdGhyb3VnaHB1dCBvZiBhIG5ldHdvcmsgb2Yg
U0lQIHNlcnZlcnMgY2FuIGJlDQo+PiBzaWduaWZpY2FudGx5IGRlZ3JhZGVkLiAgSW4gZmFjdCwg
b3ZlcmxvYWQgbWF5IGxlYWQgdG8gYSBzaXR1YXRpb24gaW4NCj4+IHdoaWNoIHRoZSB0aHJvdWdo
cHV0IGRyb3BzIGRvd24gdG8gemVybyBvciBhIHNtYWxsIGZyYWN0aW9uIG9mIHRoZQ0KPj4gb3Jp
Z2luYWwgcHJvY2Vzc2luZyBjYXBhY2l0eS4gIFRoaXMgaXMgb2Z0ZW4gY2FsbGVkIGNvbmdlc3Rp
b24gY29sbGFwc2UuDQo+Pg0KPj4gVGhlIG9iamVjdGl2ZSBvZiBhIFNJUCBvdmVybG9hZCBjb250
cm9sIG1lY2hhbmlzbSBpcyB0byBlbmFibGUgU0lQDQo+PiBzZXJ2ZXJzIHRvIG9wZXJhdGUgY2xv
c2UgdG8gdGhlaXIgY2FwYWNpdHkgbGltaXQgZHVyaW5nIHRpbWVzIG9mIG92ZXJsb2FkLg0KPj4N
Cj4+IFRoZSBTSVAgcHJvdG9jb2wgcHJvdmlkZXMgYSBsaW1pdGVkIG1lY2hhbmlzbSBmb3Igb3Zl
cmxvYWQgY29udHJvbA0KPj4gdGhyb3VnaCBpdHMgNTAzIChTZXJ2aWNlIFVuYXZhaWxhYmxlKSBy
ZXNwb25zZSBjb2RlIGFuZCB0aGUgUmV0cnktQWZ0ZXINCj4+IGhlYWRlci4gIEhvd2V2ZXIsIHRo
aXMgbWVjaGFuaXNtIGNhbm5vdCBmdWxseSBwcmV2ZW50IG92ZXJsb2FkIG9mIGEgU0lQDQo+PiBz
ZXJ2ZXIgYW5kIGl0IGNhbm5vdCBwcmV2ZW50IGNvbmdlc3Rpb24gY29sbGFwc2UuICBJbiBmYWN0
LCBpdHMgb24vb2ZmDQo+PiBiZWhhdmlvciBtYXkgY2F1c2UgdHJhZmZpYyB0byBvc2NpbGxhdGUg
YW5kIHNoaWZ0IGJldHdlZW4gU0lQIHNlcnZlcnMNCj4+IGFuZCB0aGVyZWJ5IHdvcnNlbiBhbiBv
dmVybG9hZCBjb25kaXRpb24uICBBIGRldGFpbGVkIGRpc2N1c3Npb24gb2YgdGhlDQo+PiBTSVAg
b3ZlcmxvYWQgcHJvYmxlbSwgdGhlIHByb2JsZW1zIHdpdGggdGhlIDUwMyAoU2VydmljZSBVbmF2
YWlsYWJsZSkNCj4+IHJlc3BvbnNlIGNvZGUgYW5kIHRoZSBSZXRyeS1BZnRlciBoZWFkZXIgYW5k
IHRoZSByZXF1aXJlbWVudHMgZm9yIGEgU0lQDQo+PiBvdmVybG9hZCBjb250cm9sIG1lY2hhbmlz
bSBjYW4gYmUgZm91bmQgaW4gUkZDNTM5MC4NCj4+DQo+PiBUaGUgb2JqZWN0aXZlIG9mIHRoZSBw
cm9wb3NlZCB3b3JraW5nIGdyb3VwIGlzIHRvIGRldmVsb3AgbWVjaGFuaXNtcyBmb3INCj4+IFNJ
UCBvdmVybG9hZCBjb250cm9sLiBUaGUgcHJvYmxlbSBkb21haW4gb2YgU0lQIG92ZXJsb2FkIGNv
bnRyb2wgY2FuIGJlIHNwbGl0IGludG8gaSkgb3ZlcmxvYWQgY29udHJvbCBiZXR3ZWVuIGEgdXNl
ciBhZ2VudCBhbmQgYSBTSVAgc2VydmVyIGFuZCBvdmVybG9hZCBjb250cm9sIGJldHdlZW4gU0lQ
IHNlcnZlcnMuIEEgc3BlY2lmaWNhdGlvbiBkZXZlbG9wZWQgYnkgdGhlIHByb3Bvc2VkIHdvcmtp
bmcgZ3JvdXAgbmVlZHMgdG8gY2xlYXJseSBzcGVjaWZ5IGl0cyBzY29wZS4gQSBzcGVjaWZpY2F0
aW9uIGFsc28gbmVlZHMgdG8gY2xlYXJseSBzdGF0ZSBhbnkgbGltaXRhdGlvbnMgaW4gcGVyZm9y
bWFuY2Ugb3Igb3RoZXJ3aXNlIHRoZSBwcm9wb3NlZCBvdmVybG9hZCBjb250cm9sIG1lY2hhbmlz
bSBtYXkgaGF2ZS4NCj4+DQo+PiBUd28gY29tcGxlbWVudGFyeSBhcHByb2FjaGVzIGV4aXN0IGZv
ciBoYW5kbGluZyBvdmVybG9hZCBzaXR1YXRpb25zOg0KPj4gLSBUaGUgZmlyc3QgbWVjaGFuaXNt
IGFpbXMgYXQgcHJldmVudGluZyBvdmVybG9hZCBpbiBTSVAgc2VydmVycyBieQ0KPj4gYWRqdXN0
aW5nIHRoZSBpbmNvbWluZyBsb2FkIHRvIGEgbGV2ZWwgdGhhdCBpcyBhY2NlcHRhYmxlIGZvciB0
aGlzDQo+PiBzZXJ2ZXIuIFRoaXMgbWVjaGFuaXNtIHVzZXMgaW1wbGljaXQgYW5kL29yIGV4cGxp
Y2l0IGZlZWRiYWNrIHRvDQo+PiBkZXRlcm1pbmUgd2hlbiBhbiBvdmVybG9hZCBjb25kaXRpb24g
b2NjdXJzIGluIGEgU0lQIHNlcnZlciBhbmQgYQ0KPj4gcmVkdWN0aW9uIGluIGxvYWQgaXMgcmVx
dWlyZWQuDQo+PiAtIFRoZSBzZWNvbmQgbWVjaGFuaXNtIGFpbXMgYXQgcHJldmVudGluZyBvdmVy
bG9hZCBpbiBTSVAgc2VydmVycyBieQ0KPj4gZGlzdHJpYnV0aW5nIGxvYWQgY29udHJvbCBmaWx0
ZXJzIHRvIFNJUCBzZXJ2ZXJzIHRoYXQgdGhyb3R0bGUgY2FsbHMNCj4+IGJhc2VkIG9uIHRoZWly
IGRlc3RpbmF0aW9uIGRvbWFpbiwgdGVsZXBob25lIG51bWJlciBwcmVmaXggb3IgZm9yIGENCj4+
IHNwZWNpZmljIHVzZXIuIFN1Y2ggZmlsdGVycyBjYW4gYmUgdXNlZCwgZm9yIGV4YW1wbGUsIHRv
IHRocm90dGxlIGNhbGxzDQo+PiB0byBhIGhvdGxpbmUgZHVyaW5nIGEgdGlja2V0LWdpdmVhd2F5
IGV2ZW50Lg0KPj4NCj4+IFNwZWNpZmljYWxseSwgdGhlIHByb3Bvc2VkIHdvcmtpbmcgZ3JvdXAg
d2lsbCBkZXZlbG9wIHRoZSBmb2xsb3dpbmcNCj4+IGRlbGl2ZXJhYmxlczoNCj4+IDEuIEEgZG9j
dW1lbnQgZGVzY3JpYmluZyBrZXkgZGVzaWduIGNvbnNpZGVyYXRpb25zIGZvciBhIFNJUCBvdmVy
bG9hZA0KPj4gY29udHJvbCBtZWNoYW5pc20uDQo+PiAyLiBBIHNwZWNpZmljYXRpb24gZm9yIGFu
IFNJUCBvdmVybG9hZCBjb250cm9sIG1lY2hhbmlzbSBiYXNlZCBvbg0KPj4gaW1wbGljaXQvZXhw
bGljaXQgZmVlZGJhY2suDQo+PiAzLiBBIHNwZWNpZmljYXRpb24gZm9yIGEgU0lQIGxvYWQgZmls
dGVyaW5nIG1lY2hhbmlzbS4NCj4+DQo+Pg0KPg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0Kc2lwLW92ZXJsb2FkIG1haWxpbmcgbGlzdA0Kc2lwLW92
ZXJsb2FkQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Np
cC1vdmVybG9hZA0K

From jgunn6@csc.com  Fri Apr 16 16:20:27 2010
Return-Path: <jgunn6@csc.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A26933A6A74; Fri, 16 Apr 2010 16:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.171
X-Spam-Level: 
X-Spam-Status: No, score=-6.171 tagged_above=-999 required=5 tests=[AWL=0.427,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Izly72P+8k7I; Fri, 16 Apr 2010 16:20:22 -0700 (PDT)
Received: from mail168.messagelabs.com (mail168.messagelabs.com [216.82.253.195]) by core3.amsl.com (Postfix) with ESMTP id 7174F3A68D9; Fri, 16 Apr 2010 16:20:22 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-12.tower-168.messagelabs.com!1271460003!20576079!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [20.137.2.88]
Received: (qmail 14996 invoked from network); 16 Apr 2010 23:20:04 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-12.tower-168.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Apr 2010 23:20:04 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (Switch-3.3.3mp/Switch-3.3.3mp) with ESMTP id o3GNK2mc007849; Fri, 16 Apr 2010 19:20:02 -0400
In-Reply-To: <4BC8C243.3040405@alcatel-lucent.com>
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com>	<4BB5409E.5080108@alcatel-lucent.com> <0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com> <4BC8C243.3040405@alcatel-lucent.com>
To: Volker Hilt <volker.hilt@alcatel-lucent.com>
MIME-Version: 1.0
X-KeepSent: B89D5A3C:35037DD0-85257707:008027C1; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2FP1  CCH2 April 23, 2009
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OFB89D5A3C.35037DD0-ON85257707.008027C1-85257707.00802F0F@csc.com>
Date: Fri, 16 Apr 2010 19:19:53 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.0.1 HF996|December 23, 2008) at 04/16/2010 07:20:49 PM, Serialize complete at 04/16/2010 07:20:49 PM
Content-Type: multipart/alternative; boundary="=_alternative 00802E6D85257707_="
Cc: sip-overload-bounces@ietf.org, DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Lars Eggert <lars.eggert@nokia.com>, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 16 Apr 2010 23:20:27 -0000

This is a multipart message in MIME format.
--=_alternative 00802E6D85257707_=
Content-Type: text/plain; charset="US-ASCII"

Works for me

Janet

sip-overload-bounces@ietf.org wrote on 04/16/2010 04:02:11 PM:

> [image removed] 
> 
> Re: [sip-overload] Proposed SIP Overload Control Charter
> 
> Volker Hilt 
> 
> to:
> 
> Robert Sparks, DISPATCH, sip-overload@ietf.org, Lars Eggert , 
> Gonzalo Camarillo
> 
> 04/16/2010 04:00 PM
> 
> Sent by:
> 
> sip-overload-bounces@ietf.org
> 
> An slight update to the charter Robert has sent out to address Janet's 
> comment.
> 
> Volker
> 
> 
> 
> SIP Overload Control WG Charter
> -------------------------------
> 
> As with any network element, a Session Initiation Protocol (SIP) server 
> can suffer from overload when the number of SIP messages it receives 
> exceeds the number of messages it can process. Overload is said to occur 

> when a SIP server does not have sufficient resources to complete the 
> processing of all incoming SIP messages within the required time. These 
> resources can include CPU, memory, network bandwidth, input/output, or 
> disk resources.
> 
> Overload can pose a serious problem for a network of SIP servers. During 

> periods of overload, the goodput of a network of SIP servers can be 
> significantly degraded.  In fact, overload may lead to a situation in 
> which the goodput drops down to zero or a small fraction of the original 

> processing capacity.  This is often called congestion collapse.
> 
> The objective of a SIP overload control mechanism is to enable SIP 
> servers to operate close to their capacity limit during times of 
overload.
> 
> The SIP protocol provides a limited mechanism for overload control 
> through its 503 (Service Unavailable) response code and the Retry-After 
> header.  However, this mechanism cannot fully prevent overload of a SIP 
> server and it cannot prevent congestion collapse.  In fact, its on/off 
> behavior may cause traffic to oscillate and shift between SIP servers 
> and thereby worsen an overload condition.  A detailed discussion of the 
> SIP overload problem, the problems with the 503 (Service Unavailable) 
> response code and the Retry-After header and the requirements for a SIP 
> overload control mechanism can be found in RFC5390.
> 
> The objective of the working group is to develop mechanisms for SIP 
> overload control. The problem domain of SIP overload control can be 
> split into overload control between a user agent and a SIP server and 
> overload control between SIP servers.
> 
> Any specification developed by the working group needs to clearly 
> specify its scope. A specification also needs to clearly state any 
> limitations, in performance or otherwise, the specified overload control 

> mechanism may have.  In particular, the working group shall carefully 
> define the deployment considerations for the effective operation of the 
> specified mechanisms and discuss, for example, when a mechanism requires 

> coordinated deployment and operation (if all servers need to deploy the 
> same mechanism, certain configuration values need to be identical on all 

> servers, etc), when a mechanism can become less effective or ineffective 

> under some conditions, or especially if there are cases when a mechanism 

> can reduce goodput compared to no overload protection. The intent of 
> these considerations is to allow potential deployers to make the best 
> use of these mechanism in their particular
> networks.
> 
> The working group will consider two complementary approaches for 
> handling overload situations:
> - The first mechanism aims at preventing overload in SIP servers by
>    adjusting the incoming load to a level that is acceptable for this
>    server. This mechanism uses implicit and/or explicit feedback to
>    determine when an overload condition occurs in a SIP server and a
>    reduction in load is required.
> - The second mechanism aims at preventing overload in SIP servers by
>    distributing load control filters to SIP servers that throttle calls
>    based on their source or destination domain, telephone number prefix
>    or for a specific user. Such filters can be used, for example, to
>    throttle calls to a hotline during a ticket-giveaway event.
> 
> The working group will develop the following deliverables:
> 
>    1. A document describing key design considerations for a SIP overload
>       control mechanism.
>    2. A specification for an SIP overload control mechanism based on
>       implicit/explicit feedback.
>    3. A specification for a SIP load filtering mechanism.
> 
> Milestones:
> 
> Sep 2010 Design Considerations to IESG for publication as Informational
> Dec 2010 Specification for a SIP overload control mechanism based on 
> implicit/explicit feedback to IESG for publication as Proposed Standard
> May 2011 Specification for a SIP load filtering mechaism to IESG for 
> publication as Proposed Standard
> 
> 
> 
> 
> 
> On 4/16/2010 11:56 AM, Robert Sparks wrote:
> > I have made some tweaks based on the list discussion and 
> conversations with IESG members.
> > This is my current working text. Please comment if you disagree 
> with the changes I've made.
> >
> > The changes are in the description of overload in the first 
> paragraph, changing the term throughput
> > to goodput, and clarifying the discussion of scope and 
> limitations. I've also added some strawman
> > milestones. Please comment on those dates.
> >
> > SIP Overload Control WG Charter
> > -------------------------------
> >
> > As with any network element, a Session Initiation Protocol (SIP) 
server
> > can suffer from overload when the number of SIP messages it receives
> > exceeds the number of messages it can process. Overload is said to 
occur
> > when a SIP server does not have sufficient resources to complete the
> > processing of all incoming SIP messages within the required time.
> > These resources can include CPU, memory, network bandwidth, 
input/output,
> > or disk resources.
> >
> > Overload can pose a serious problem for a network of SIP servers. 
During
> > periods of overload, the goodput of a network of SIP servers can be
> > significantly degraded.  In fact, overload may lead to a situation in
> > which the goodput drops down to zero or a small fraction of the
> > original processing capacity.  This is often called congestion 
collapse.
> >
> > The objective of a SIP overload control mechanism is to enable SIP
> > servers to operate close to their capacity limit during times of 
overload.
> >
> > The SIP protocol provides a limited mechanism for overload control
> > through its 503 (Service Unavailable) response code and the 
Retry-After
> > header.  However, this mechanism cannot fully prevent overload of a 
SIP
> > server and it cannot prevent congestion collapse.  In fact, its on/off
> > behavior may cause traffic to oscillate and shift between SIP servers
> > and thereby worsen an overload condition.  A detailed discussion of 
the
> > SIP overload problem, the problems with the 503 (Service Unavailable)
> > response code and the Retry-After header and the requirements for a 
SIP
> > overload control mechanism can be found in RFC5390.
> >
> > The objective of the working group is to develop mechanisms for SIP
> > overload control. The problem domain of SIP overload control can 
> be split into
> > overload control between a user agent and a SIP server and overload 
control
> > between SIP servers.
> >
> > Any specification developed by the working group needs to clearly 
> specify its
> > scope. A specification also needs to clearly state any limitations, in
> > performance or otherwise, the specified overload control mechanism
> may have.  In
> > particular, the working group shall carefully define the deployment
> > considerations for the effective operation of the specified mechanisms 
and
> > discuss, for example, when a mechanism requires coordinated deployment 
and
> > operation (if all servers need to deploy the same mechanism, certain
> > configuration values need to be identical on all servers, etc), when a
> > mechanism can become less effective or ineffective under some 
conditions, or
> > especially if there are cases when a mechanism can reduce goodput 
> compared to
> > no overload protection. The intent of these considerations is to allow
> > potential deployers to make the best use of these mechanism in 
> their particular
> > networks.
> >
> > The working group will consider two complementary approaches for
> > handling overload situations:
> > - The first mechanism aims at preventing overload in SIP servers by
> >    adjusting the incoming load to a level that is acceptable for this
> >    server. This mechanism uses implicit and/or explicit feedback to
> >    determine when an overload condition occurs in a SIP server and a
> >    reduction in load is required.
> > - The second mechanism aims at preventing overload in SIP servers by
> >    distributing load control filters to SIP servers that throttle 
calls
> >    based on their destination domain, telephone number prefix or for a
> >    specific user. Such filters can be used, for example, to throttle 
calls
> >    to a hotline during a ticket-giveaway event.
> >
> > The working group will develop the following deliverables:
> >
> >    1. A document describing key design considerations for a SIP 
overload
> >       control mechanism.
> >    2. A specification for an SIP overload control mechanism based on
> >       implicit/explicit feedback.
> >    3. A specification for a SIP load filtering mechanism.
> >
> > Milestones:
> >
> > Sep 2010 Design Considerations to IESG for publication as 
Informational
> > Dec 2010 Specification for a SIP overload control mechanism based 
> on implicit/explicit feedback to IESG for publication as Proposed 
Standard
> > May 2011 Specification for a SIP load filtering mechaism to IESG 
> for publication as Proposed Standard
> >
> >
> > On Apr 1, 2010, at 7:55 PM, Volker Hilt wrote:
> >
> >> All,
> >>
> >> below is an updated charter proposal for a SIP Overload Control 
> WG. It has additional text that specifications developed by the 
> proposed WG need to define scope and limitations (see below).
> >>
> >> Thanks,
> >>
> >> Volker
> >>
> >>
> >>
> >> SIP Overload Control WG Charter
> >> -------------------------------
> >>
> >> As with any network element, a Session Initiation Protocol (SIP) 
server
> >> can suffer from overload when the number of SIP messages it receives
> >> exceeds the number of messages it can process. Overload is said to 
occur
> >> when a SIP server does not have sufficient resources to process all
> >> incoming SIP messages.  These resources can include CPU, memory, 
network
> >> bandwidth, input/output, or disk resources.
> >>
> >> Overload can pose a serious problem for a network of SIP servers. 
During
> >> periods of overload, the throughput of a network of SIP servers can 
be
> >> significantly degraded.  In fact, overload may lead to a situation in
> >> which the throughput drops down to zero or a small fraction of the
> >> original processing capacity.  This is often called congestion 
collapse.
> >>
> >> The objective of a SIP overload control mechanism is to enable SIP
> >> servers to operate close to their capacity limit during times of 
overload.
> >>
> >> The SIP protocol provides a limited mechanism for overload control
> >> through its 503 (Service Unavailable) response code and the 
Retry-After
> >> header.  However, this mechanism cannot fully prevent overload of a 
SIP
> >> server and it cannot prevent congestion collapse.  In fact, its 
on/off
> >> behavior may cause traffic to oscillate and shift between SIP servers
> >> and thereby worsen an overload condition.  A detailed discussion of 
the
> >> SIP overload problem, the problems with the 503 (Service Unavailable)
> >> response code and the Retry-After header and the requirements for a 
SIP
> >> overload control mechanism can be found in RFC5390.
> >>
> >> The objective of the proposed working group is to develop mechanisms 
for
> >> SIP overload control. The problem domain of SIP overload control 
> can be split into i) overload control between a user agent and a SIP
> server and overload control between SIP servers. A specification 
> developed by the proposed working group needs to clearly specify its
> scope. A specification also needs to clearly state any limitations 
> in performance or otherwise the proposed overload control mechanism may 
have.
> >>
> >> Two complementary approaches exist for handling overload situations:
> >> - The first mechanism aims at preventing overload in SIP servers by
> >> adjusting the incoming load to a level that is acceptable for this
> >> server. This mechanism uses implicit and/or explicit feedback to
> >> determine when an overload condition occurs in a SIP server and a
> >> reduction in load is required.
> >> - The second mechanism aims at preventing overload in SIP servers by
> >> distributing load control filters to SIP servers that throttle calls
> >> based on their destination domain, telephone number prefix or for a
> >> specific user. Such filters can be used, for example, to throttle 
calls
> >> to a hotline during a ticket-giveaway event.
> >>
> >> Specifically, the proposed working group will develop the following
> >> deliverables:
> >> 1. A document describing key design considerations for a SIP overload
> >> control mechanism.
> >> 2. A specification for an SIP overload control mechanism based on
> >> implicit/explicit feedback.
> >> 3. A specification for a SIP load filtering mechanism.
> >>
> >>
> >
> 
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload

--=_alternative 00802E6D85257707_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif"><br>
Works for me</font>
<br>
<br><font size=2 face="sans-serif">Janet</font>
<br>
<br><tt><font size=2>sip-overload-bounces@ietf.org wrote on 04/16/2010
04:02:11 PM:<br>
<br>
&gt; [image removed] </font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Re: [sip-overload] Proposed SIP Overload Control Charter</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Volker Hilt </font></tt>
<br><tt><font size=2>&gt; <br>
&gt; to:</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Robert Sparks, DISPATCH, sip-overload@ietf.org, Lars Eggert , <br>
&gt; Gonzalo Camarillo</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; 04/16/2010 04:00 PM</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Sent by:</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; sip-overload-bounces@ietf.org</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; An slight update to the charter Robert has sent out to address Janet's
<br>
&gt; comment.<br>
&gt; <br>
&gt; Volker<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; SIP Overload Control WG Charter<br>
&gt; -------------------------------<br>
&gt; <br>
&gt; As with any network element, a Session Initiation Protocol (SIP) server
<br>
&gt; can suffer from overload when the number of SIP messages it receives
<br>
&gt; exceeds the number of messages it can process. Overload is said to
occur <br>
&gt; when a SIP server does not have sufficient resources to complete the
<br>
&gt; processing of all incoming SIP messages within the required time.
These <br>
&gt; resources can include CPU, memory, network bandwidth, input/output,
or <br>
&gt; disk resources.<br>
&gt; <br>
&gt; Overload can pose a serious problem for a network of SIP servers.
During <br>
&gt; periods of overload, the goodput of a network of SIP servers can be
<br>
&gt; significantly degraded. &nbsp;In fact, overload may lead to a situation
in <br>
&gt; which the goodput drops down to zero or a small fraction of the original
<br>
&gt; processing capacity. &nbsp;This is often called congestion collapse.<br>
&gt; <br>
&gt; The objective of a SIP overload control mechanism is to enable SIP
<br>
&gt; servers to operate close to their capacity limit during times of overload.<br>
&gt; <br>
&gt; The SIP protocol provides a limited mechanism for overload control
<br>
&gt; through its 503 (Service Unavailable) response code and the Retry-After
<br>
&gt; header. &nbsp;However, this mechanism cannot fully prevent overload
of a SIP <br>
&gt; server and it cannot prevent congestion collapse. &nbsp;In fact, its
on/off <br>
&gt; behavior may cause traffic to oscillate and shift between SIP servers
<br>
&gt; and thereby worsen an overload condition. &nbsp;A detailed discussion
of the <br>
&gt; SIP overload problem, the problems with the 503 (Service Unavailable)
<br>
&gt; response code and the Retry-After header and the requirements for
a SIP <br>
&gt; overload control mechanism can be found in RFC5390.<br>
&gt; <br>
&gt; The objective of the working group is to develop mechanisms for SIP
<br>
&gt; overload control. The problem domain of SIP overload control can be
<br>
&gt; split into overload control between a user agent and a SIP server
and <br>
&gt; overload control between SIP servers.<br>
&gt; <br>
&gt; Any specification developed by the working group needs to clearly
<br>
&gt; specify its scope. A specification also needs to clearly state any
<br>
&gt; limitations, in performance or otherwise, the specified overload control
<br>
&gt; mechanism may have. &nbsp;In particular, the working group shall carefully
<br>
&gt; define the deployment considerations for the effective operation of
the <br>
&gt; specified mechanisms and discuss, for example, when a mechanism requires
<br>
&gt; coordinated deployment and operation (if all servers need to deploy
the <br>
&gt; same mechanism, certain configuration values need to be identical
on all <br>
&gt; servers, etc), when a mechanism can become less effective or ineffective
<br>
&gt; under some conditions, or especially if there are cases when a mechanism
<br>
&gt; can reduce goodput compared to no overload protection. The intent
of <br>
&gt; these considerations is to allow potential deployers to make the best
<br>
&gt; use of these mechanism in their particular<br>
&gt; networks.<br>
&gt; <br>
&gt; The working group will consider two complementary approaches for <br>
&gt; handling overload situations:<br>
&gt; - The first mechanism aims at preventing overload in SIP servers by<br>
&gt; &nbsp; &nbsp;adjusting the incoming load to a level that is acceptable
for this<br>
&gt; &nbsp; &nbsp;server. This mechanism uses implicit and/or explicit
feedback to<br>
&gt; &nbsp; &nbsp;determine when an overload condition occurs in a SIP
server and a<br>
&gt; &nbsp; &nbsp;reduction in load is required.<br>
&gt; - The second mechanism aims at preventing overload in SIP servers
by<br>
&gt; &nbsp; &nbsp;distributing load control filters to SIP servers that
throttle calls<br>
&gt; &nbsp; &nbsp;based on their source or destination domain, telephone
number prefix<br>
&gt; &nbsp; &nbsp;or for a specific user. Such filters can be used, for
example, to<br>
&gt; &nbsp; &nbsp;throttle calls to a hotline during a ticket-giveaway
event.<br>
&gt; <br>
&gt; The working group will develop the following deliverables:<br>
&gt; <br>
&gt; &nbsp; &nbsp;1. A document describing key design considerations for
a SIP overload<br>
&gt; &nbsp; &nbsp; &nbsp; control mechanism.<br>
&gt; &nbsp; &nbsp;2. A specification for an SIP overload control mechanism
based on<br>
&gt; &nbsp; &nbsp; &nbsp; implicit/explicit feedback.<br>
&gt; &nbsp; &nbsp;3. A specification for a SIP load filtering mechanism.<br>
&gt; <br>
&gt; Milestones:<br>
&gt; <br>
&gt; Sep 2010 Design Considerations to IESG for publication as Informational<br>
&gt; Dec 2010 Specification for a SIP overload control mechanism based
on <br>
&gt; implicit/explicit feedback to IESG for publication as Proposed Standard<br>
&gt; May 2011 Specification for a SIP load filtering mechaism to IESG for
<br>
&gt; publication as Proposed Standard<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; On 4/16/2010 11:56 AM, Robert Sparks wrote:<br>
&gt; &gt; I have made some tweaks based on the list discussion and <br>
&gt; conversations with IESG members.<br>
&gt; &gt; This is my current working text. Please comment if you disagree
<br>
&gt; with the changes I've made.<br>
&gt; &gt;<br>
&gt; &gt; The changes are in the description of overload in the first <br>
&gt; paragraph, changing the term throughput<br>
&gt; &gt; to goodput, and clarifying the discussion of scope and <br>
&gt; limitations. I've also added some strawman<br>
&gt; &gt; milestones. Please comment on those dates.<br>
&gt; &gt;<br>
&gt; &gt; SIP Overload Control WG Charter<br>
&gt; &gt; -------------------------------<br>
&gt; &gt;<br>
&gt; &gt; As with any network element, a Session Initiation Protocol (SIP)
server<br>
&gt; &gt; can suffer from overload when the number of SIP messages it receives<br>
&gt; &gt; exceeds the number of messages it can process. Overload is said
to occur<br>
&gt; &gt; when a SIP server does not have sufficient resources to complete
the<br>
&gt; &gt; processing of all incoming SIP messages within the required time.<br>
&gt; &gt; These resources can include CPU, memory, network bandwidth, input/output,<br>
&gt; &gt; or disk resources.<br>
&gt; &gt;<br>
&gt; &gt; Overload can pose a serious problem for a network of SIP servers.
During<br>
&gt; &gt; periods of overload, the goodput of a network of SIP servers
can be<br>
&gt; &gt; significantly degraded. &nbsp;In fact, overload may lead to a
situation in<br>
&gt; &gt; which the goodput drops down to zero or a small fraction of the<br>
&gt; &gt; original processing capacity. &nbsp;This is often called congestion
collapse.<br>
&gt; &gt;<br>
&gt; &gt; The objective of a SIP overload control mechanism is to enable
SIP<br>
&gt; &gt; servers to operate close to their capacity limit during times
of overload.<br>
&gt; &gt;<br>
&gt; &gt; The SIP protocol provides a limited mechanism for overload control<br>
&gt; &gt; through its 503 (Service Unavailable) response code and the Retry-After<br>
&gt; &gt; header. &nbsp;However, this mechanism cannot fully prevent overload
of a SIP<br>
&gt; &gt; server and it cannot prevent congestion collapse. &nbsp;In fact,
its on/off<br>
&gt; &gt; behavior may cause traffic to oscillate and shift between SIP
servers<br>
&gt; &gt; and thereby worsen an overload condition. &nbsp;A detailed discussion
of the<br>
&gt; &gt; SIP overload problem, the problems with the 503 (Service Unavailable)<br>
&gt; &gt; response code and the Retry-After header and the requirements
for a SIP<br>
&gt; &gt; overload control mechanism can be found in RFC5390.<br>
&gt; &gt;<br>
&gt; &gt; The objective of the working group is to develop mechanisms for
SIP<br>
&gt; &gt; overload control. The problem domain of SIP overload control
can <br>
&gt; be split into<br>
&gt; &gt; overload control between a user agent and a SIP server and overload
control<br>
&gt; &gt; between SIP servers.<br>
&gt; &gt;<br>
&gt; &gt; Any specification developed by the working group needs to clearly
<br>
&gt; specify its<br>
&gt; &gt; scope. A specification also needs to clearly state any limitations,
in<br>
&gt; &gt; performance or otherwise, the specified overload control mechanism<br>
&gt; may have. &nbsp;In<br>
&gt; &gt; particular, the working group shall carefully define the deployment<br>
&gt; &gt; considerations for the effective operation of the specified mechanisms
and<br>
&gt; &gt; discuss, for example, when a mechanism requires coordinated deployment
and<br>
&gt; &gt; operation (if all servers need to deploy the same mechanism,
certain<br>
&gt; &gt; configuration values need to be identical on all servers, etc),
when a<br>
&gt; &gt; mechanism can become less effective or ineffective under some
conditions, or<br>
&gt; &gt; especially if there are cases when a mechanism can reduce goodput
<br>
&gt; compared to<br>
&gt; &gt; no overload protection. The intent of these considerations is
to allow<br>
&gt; &gt; potential deployers to make the best use of these mechanism in
<br>
&gt; their particular<br>
&gt; &gt; networks.<br>
&gt; &gt;<br>
&gt; &gt; The working group will consider two complementary approaches
for<br>
&gt; &gt; handling overload situations:<br>
&gt; &gt; - The first mechanism aims at preventing overload in SIP servers
by<br>
&gt; &gt; &nbsp; &nbsp;adjusting the incoming load to a level that is acceptable
for this<br>
&gt; &gt; &nbsp; &nbsp;server. This mechanism uses implicit and/or explicit
feedback to<br>
&gt; &gt; &nbsp; &nbsp;determine when an overload condition occurs in a
SIP server and a<br>
&gt; &gt; &nbsp; &nbsp;reduction in load is required.<br>
&gt; &gt; - The second mechanism aims at preventing overload in SIP servers
by<br>
&gt; &gt; &nbsp; &nbsp;distributing load control filters to SIP servers
that throttle calls<br>
&gt; &gt; &nbsp; &nbsp;based on their destination domain, telephone number
prefix or for a<br>
&gt; &gt; &nbsp; &nbsp;specific user. Such filters can be used, for example,
to throttle calls<br>
&gt; &gt; &nbsp; &nbsp;to a hotline during a ticket-giveaway event.<br>
&gt; &gt;<br>
&gt; &gt; The working group will develop the following deliverables:<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp;1. A document describing key design considerations
for a SIP overload<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; control mechanism.<br>
&gt; &gt; &nbsp; &nbsp;2. A specification for an SIP overload control mechanism
based on<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; implicit/explicit feedback.<br>
&gt; &gt; &nbsp; &nbsp;3. A specification for a SIP load filtering mechanism.<br>
&gt; &gt;<br>
&gt; &gt; Milestones:<br>
&gt; &gt;<br>
&gt; &gt; Sep 2010 Design Considerations to IESG for publication as Informational<br>
&gt; &gt; Dec 2010 Specification for a SIP overload control mechanism based
<br>
&gt; on implicit/explicit feedback to IESG for publication as Proposed
Standard<br>
&gt; &gt; May 2011 Specification for a SIP load filtering mechaism to IESG
<br>
&gt; for publication as Proposed Standard<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On Apr 1, 2010, at 7:55 PM, Volker Hilt wrote:<br>
&gt; &gt;<br>
&gt; &gt;&gt; All,<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; below is an updated charter proposal for a SIP Overload Control
<br>
&gt; WG. It has additional text that specifications developed by the <br>
&gt; proposed WG need to define scope and limitations (see below).<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Thanks,<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Volker<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; SIP Overload Control WG Charter<br>
&gt; &gt;&gt; -------------------------------<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; As with any network element, a Session Initiation Protocol
(SIP) server<br>
&gt; &gt;&gt; can suffer from overload when the number of SIP messages
it receives<br>
&gt; &gt;&gt; exceeds the number of messages it can process. Overload is
said to occur<br>
&gt; &gt;&gt; when a SIP server does not have sufficient resources to process
all<br>
&gt; &gt;&gt; incoming SIP messages. &nbsp;These resources can include
CPU, memory, network<br>
&gt; &gt;&gt; bandwidth, input/output, or disk resources.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Overload can pose a serious problem for a network of SIP
servers. During<br>
&gt; &gt;&gt; periods of overload, the throughput of a network of SIP servers
can be<br>
&gt; &gt;&gt; significantly degraded. &nbsp;In fact, overload may lead
to a situation in<br>
&gt; &gt;&gt; which the throughput drops down to zero or a small fraction
of the<br>
&gt; &gt;&gt; original processing capacity. &nbsp;This is often called
congestion collapse.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; The objective of a SIP overload control mechanism is to enable
SIP<br>
&gt; &gt;&gt; servers to operate close to their capacity limit during times
of overload.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; The SIP protocol provides a limited mechanism for overload
control<br>
&gt; &gt;&gt; through its 503 (Service Unavailable) response code and the
Retry-After<br>
&gt; &gt;&gt; header. &nbsp;However, this mechanism cannot fully prevent
overload of a SIP<br>
&gt; &gt;&gt; server and it cannot prevent congestion collapse. &nbsp;In
fact, its on/off<br>
&gt; &gt;&gt; behavior may cause traffic to oscillate and shift between
SIP servers<br>
&gt; &gt;&gt; and thereby worsen an overload condition. &nbsp;A detailed
discussion of the<br>
&gt; &gt;&gt; SIP overload problem, the problems with the 503 (Service
Unavailable)<br>
&gt; &gt;&gt; response code and the Retry-After header and the requirements
for a SIP<br>
&gt; &gt;&gt; overload control mechanism can be found in RFC5390.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; The objective of the proposed working group is to develop
mechanisms for<br>
&gt; &gt;&gt; SIP overload control. The problem domain of SIP overload
control <br>
&gt; can be split into i) overload control between a user agent and a SIP<br>
&gt; server and overload control between SIP servers. A specification <br>
&gt; developed by the proposed working group needs to clearly specify its<br>
&gt; scope. A specification also needs to clearly state any limitations
<br>
&gt; in performance or otherwise the proposed overload control mechanism
may have.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Two complementary approaches exist for handling overload
situations:<br>
&gt; &gt;&gt; - The first mechanism aims at preventing overload in SIP
servers by<br>
&gt; &gt;&gt; adjusting the incoming load to a level that is acceptable
for this<br>
&gt; &gt;&gt; server. This mechanism uses implicit and/or explicit feedback
to<br>
&gt; &gt;&gt; determine when an overload condition occurs in a SIP server
and a<br>
&gt; &gt;&gt; reduction in load is required.<br>
&gt; &gt;&gt; - The second mechanism aims at preventing overload in SIP
servers by<br>
&gt; &gt;&gt; distributing load control filters to SIP servers that throttle
calls<br>
&gt; &gt;&gt; based on their destination domain, telephone number prefix
or for a<br>
&gt; &gt;&gt; specific user. Such filters can be used, for example, to
throttle calls<br>
&gt; &gt;&gt; to a hotline during a ticket-giveaway event.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Specifically, the proposed working group will develop the
following<br>
&gt; &gt;&gt; deliverables:<br>
&gt; &gt;&gt; 1. A document describing key design considerations for a
SIP overload<br>
&gt; &gt;&gt; control mechanism.<br>
&gt; &gt;&gt; 2. A specification for an SIP overload control mechanism
based on<br>
&gt; &gt;&gt; implicit/explicit feedback.<br>
&gt; &gt;&gt; 3. A specification for a SIP load filtering mechanism.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;<br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; sip-overload mailing list<br>
&gt; sip-overload@ietf.org<br>
&gt; </font></tt><a href="https://www.ietf.org/mailman/listinfo/sip-overload"><tt><font size=2>https://www.ietf.org/mailman/listinfo/sip-overload</font></tt></a><tt><font size=2><br>
</font></tt>
--=_alternative 00802E6D85257707_=--

From partr@cisco.com  Mon Apr 19 04:14:59 2010
Return-Path: <partr@cisco.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 55AEF3A6856 for <sip-overload@core3.amsl.com>; Mon, 19 Apr 2010 04:14:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.11
X-Spam-Level: 
X-Spam-Status: No, score=-9.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q+kE2bYtSnxC for <sip-overload@core3.amsl.com>; Mon, 19 Apr 2010 04:14:58 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 7C52E3A69F1 for <sip-overload@ietf.org>; Mon, 19 Apr 2010 04:14:44 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmoFAF/Xy0tAaHte/2dsb2JhbACPfIt5caEcmRiFEASDMA
X-IronPort-AV: E=Sophos;i="4.52,235,1270425600"; d="scan'208";a="517246045"
Received: from hkg-core-1.cisco.com ([64.104.123.94]) by sj-iport-6.cisco.com with ESMTP; 19 Apr 2010 11:14:35 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o3JBEH1i009189 for <sip-overload@ietf.org>; Mon, 19 Apr 2010 11:14:34 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 19 Apr 2010 16:44:14 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Apr 2010 16:44:13 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623901E7AF9B@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New Draft: draft-partha-sip-overload-resource-availability-00 
Thread-Index: Acrfr+uUE8NPPx1uSEqWbfo05qk+4AAABN+w
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: <sip-overload@ietf.org>
X-OriginalArrivalTime: 19 Apr 2010 11:14:14.0615 (UTC) FILETIME=[71DF5E70:01CADFB1]
Cc: "Sanjay Sinha \(sanjsinh\)" <sanjsinh@cisco.com>, "Paul Kyzivat \(pkyzivat\)" <pkyzivat@cisco.com>, "Paul Jones \(paulej\)" <paulej@cisco.com>, "Muthu ArulMozhi Perumal \(mperumal\)" <mperumal@cisco.com>
Subject: [sip-overload] New Draft: draft-partha-sip-overload-resource-availability-00
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 19 Apr 2010 11:14:59 -0000

Hi all,

We have submitted the draft for explicit SIP based resource monitoring
and overload avoidance mechanism based on the resource availability of
the entity. Could you please review the draft and provide your valuable
comments. The draft location is as follows:=20
=20
http://www.ietf.org/id/draft-partha-sip-overload-resource-availability-0
0.txt

Abstract:
Overload occurs in Session Initiation Protocol (SIP) networks when
B2BUA, proxies, and user agents have insufficient resources like CPU,
memory, DSP, or bandwidth to complete the processing of a request.
SIP provides limited support for overload handling through its 503
response code, which tells an upstream element that it is overloaded.
This document defines explicit SIP based resource monitoring and
overload avoidance mechanism based on the resource availability of the
entity.

Thanks
Partha/Sheshadri






From rjsparks@nostrum.com  Wed Apr 21 08:49:11 2010
Return-Path: <rjsparks@nostrum.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 419AC3A6B6F; Wed, 21 Apr 2010 08:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.476
X-Spam-Level: 
X-Spam-Status: No, score=-2.476 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M7kAFBTJsrtT; Wed, 21 Apr 2010 08:49:10 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 8483228C0E2; Wed, 21 Apr 2010 08:29:01 -0700 (PDT)
Received: from [172.16.3.177] (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o3LFSd9s087976 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 21 Apr 2010 10:28:42 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com>
Date: Wed, 21 Apr 2010 10:28:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <6FEFDA2E-C51F-451A-B0A4-3973580468D1@nostrum.com>
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com> <4BB5409E.5080108@alcatel-lucent.com> <0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1078)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: Volker Hilt <volker.hilt@alcatel-lucent.com>, DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 21 Apr 2010 15:49:11 -0000

Please comment on what these dates should actually be=20

RjS

> Milestones:
>=20
> Sep 2010 Design Considerations to IESG for publication as =
Informational
> Dec 2010 Specification for a SIP overload control mechanism based on =
implicit/explicit feedback to IESG for publication as Proposed Standard
> May 2011 Specification for a SIP load filtering mechaism to IESG for =
publication as Proposed Standard


From bruno.chatras@orange-ftgroup.com  Fri Apr 23 01:53:55 2010
Return-Path: <bruno.chatras@orange-ftgroup.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 85F5B3A69C1; Fri, 23 Apr 2010 01:53:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c+IfmrPpJ2zk; Fri, 23 Apr 2010 01:53:54 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id 7B8953A693D; Fri, 23 Apr 2010 01:53:54 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 35CEE6FCC09; Fri, 23 Apr 2010 10:54:13 +0200 (CEST)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id 2BD0A6FCC07; Fri, 23 Apr 2010 10:54:13 +0200 (CEST)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 23 Apr 2010 10:53:43 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 23 Apr 2010 10:53:42 +0200
Message-ID: <9ECCF01B52E7AB408A7EB85352642141015EFC76@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <6FEFDA2E-C51F-451A-B0A4-3973580468D1@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] Proposed SIP Overload Control Charter
Thread-Index: AcrhaivcAWXJruR7Rqq508h/XZIohQBWCz5Q
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com><4BB5409E.5080108@alcatel-lucent.com><0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com> <6FEFDA2E-C51F-451A-B0A4-3973580468D1@nostrum.com>
From: <bruno.chatras@orange-ftgroup.com>
To: <rjsparks@nostrum.com>
X-OriginalArrivalTime: 23 Apr 2010 08:53:43.0723 (UTC) FILETIME=[7A5257B0:01CAE2C2]
Cc: volker.hilt@alcatel-lucent.com, dispatch@ietf.org, sip-overload@ietf.org, Gonzalo.Camarillo@ericsson.com, lars.eggert@nokia.com
Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 23 Apr 2010 08:53:55 -0000

I would prefer to see the SIP load filtering specification released by =
the end of 2010.=20
BC

> -----Message d'origine-----
> De : sip-overload-bounces@ietf.org=20
> [mailto:sip-overload-bounces@ietf.org] De la part de Robert Sparks
> Envoy=E9 : mercredi 21 avril 2010 17:29
> =C0 : Robert Sparks
> Cc : Volker Hilt; DISPATCH; sip-overload@ietf.org; Gonzalo=20
> Camarillo; Lars Eggert
> Objet : Re: [sip-overload] Proposed SIP Overload Control Charter
>=20
> Please comment on what these dates should actually be=20
>=20
> RjS
>=20
> > Milestones:
> >=20
> > Sep 2010 Design Considerations to IESG for publication as=20
> > Informational Dec 2010 Specification for a SIP overload control=20
> > mechanism based on implicit/explicit feedback to IESG for=20
> publication=20
> > as Proposed Standard May 2011 Specification for a SIP load=20
> filtering=20
> > mechaism to IESG for publication as Proposed Standard
>=20
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload
>=20

From en5192@att.com  Mon Apr 26 06:55:27 2010
Return-Path: <en5192@att.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C9AE13A6BAB; Mon, 26 Apr 2010 06:55:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.74
X-Spam-Level: 
X-Spam-Status: No, score=-104.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N5EbOmsIdgfu; Mon, 26 Apr 2010 06:55:27 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by core3.amsl.com (Postfix) with ESMTP id E11833A6A67; Mon, 26 Apr 2010 06:55:26 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: en5192@att.com
X-Msg-Ref: server-5.tower-120.messagelabs.com!1272290113!41237223!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 16081 invoked from network); 26 Apr 2010 13:55:14 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-5.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 26 Apr 2010 13:55:14 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o3QDsvGF003341; Mon, 26 Apr 2010 09:54:57 -0400
Received: from misout7msgusr7b.ugd.att.com (misout7msgusr7b.ugd.att.com [144.155.43.104]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o3QDspcn003217; Mon, 26 Apr 2010 09:54:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 26 Apr 2010 09:53:40 -0400
Message-ID: <5DA01D2CA74FAF40ADF71DB4177D345A055BB760@misout7msgusr7b.ugd.att.com>
In-Reply-To: <9ECCF01B52E7AB408A7EB85352642141015EFC76@ftrdmel0.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] Proposed SIP Overload Control Charter
Thread-Index: AcrhaivcAWXJruR7Rqq508h/XZIohQBWCz5QAJ+6sSA=
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com><4BB5409E.5080108@alcatel-lucent.com><0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com><6FEFDA2E-C51F-451A-B0A4-3973580468D1@nostrum.com> <9ECCF01B52E7AB408A7EB85352642141015EFC76@ftrdmel0.rd.francetelecom.fr>
From: "NOEL, ERIC C (ATTLABS)" <en5192@att.com>
To: <bruno.chatras@orange-ftgroup.com>, <rjsparks@nostrum.com>
Cc: volker.hilt@alcatel-lucent.com, dispatch@ietf.org, sip-overload@ietf.org, Gonzalo.Camarillo@ericsson.com, lars.eggert@nokia.com
Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 26 Apr 2010 13:55:27 -0000

Folks,

Wrt milestones deadlines:

   1. A document describing key design considerations for a SIP overload
      control mechanism =3D=3D> Sep 2010
   2. A specification for an SIP overload control mechanism based on
      implicit/explicit feedback =3D=3D> Dec 2010
   3. A specification for a SIP load filtering mechanism =3D=3D> May =
2011

I have a few comments:

- Is item 1 a cleaned up version of =
draft-ietf-sipping-overload-design-02.pdf?
    =3D=3D> if so I am OK with Sep 2010 date.
- Could item 2 consist of the documentation of one of the SIP overload =
control mechanism studied by the SIP overload design team coordinated by =
Volker?=20
    =3D=3D> Provided work consists of documenting one of the control =
mechanism studied by the SIP overload design team, then I am ok with Dec =
2010.
- With respect to item 3, are there any other related IETF activity =
besides draft-shen-sipping-load-control-event-package that need =
consideration? Is the expectation to validate the proposed load =
filtering mechanism through simulation?
    =3D=3D> Would like feedback on questions prior agreeing on May 2011 =
deadline.

Lastly, what will be the mode of operation to actually work on these =
items? Continue sending comments on the sip-overload distribution list? =
Have regular sub-teams meeting (via conference calls)?=20

Thanks,

Eric

-----Original Message-----
From: sip-overload-bounces@ietf.org =
[mailto:sip-overload-bounces@ietf.org] On Behalf Of =
bruno.chatras@orange-ftgroup.com
Sent: Friday, April 23, 2010 4:54 AM
To: rjsparks@nostrum.com
Cc: volker.hilt@alcatel-lucent.com; dispatch@ietf.org; =
sip-overload@ietf.org; Gonzalo.Camarillo@ericsson.com; =
lars.eggert@nokia.com
Subject: Re: [sip-overload] Proposed SIP Overload Control Charter

I would prefer to see the SIP load filtering specification released by =
the end of 2010.=20
BC

> -----Message d'origine-----
> De : sip-overload-bounces@ietf.org=20
> [mailto:sip-overload-bounces@ietf.org] De la part de Robert Sparks
> Envoy=E9 : mercredi 21 avril 2010 17:29
> =C0 : Robert Sparks
> Cc : Volker Hilt; DISPATCH; sip-overload@ietf.org; Gonzalo=20
> Camarillo; Lars Eggert
> Objet : Re: [sip-overload] Proposed SIP Overload Control Charter
>=20
> Please comment on what these dates should actually be=20
>=20
> RjS
>=20
> > Milestones:
> >=20
> > Sep 2010 Design Considerations to IESG for publication as=20
> > Informational Dec 2010 Specification for a SIP overload control=20
> > mechanism based on implicit/explicit feedback to IESG for=20
> publication=20
> > as Proposed Standard May 2011 Specification for a SIP load=20
> filtering=20
> > mechaism to IESG for publication as Proposed Standard
>=20
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload
>=20
_______________________________________________
sip-overload mailing list
sip-overload@ietf.org
https://www.ietf.org/mailman/listinfo/sip-overload

From volker.hilt@alcatel-lucent.com  Mon Apr 26 13:19:41 2010
Return-Path: <volker.hilt@alcatel-lucent.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB3403A6980; Mon, 26 Apr 2010 13:19:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.033
X-Spam-Level: 
X-Spam-Status: No, score=-2.033 tagged_above=-999 required=5 tests=[AWL=0.567,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xh4xuuygANRB; Mon, 26 Apr 2010 13:19:40 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id ACA713A689D; Mon, 26 Apr 2010 13:19:37 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id o3QKJMYX018113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 26 Apr 2010 15:19:23 -0500 (CDT)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id o3QKJLnC030201; Mon, 26 Apr 2010 15:19:21 -0500
Received: from [135.112.131.79] (135.3.63.241) by USNAVSXCHHUB01.ndc.alcatel-lucent.com (135.3.39.110) with Microsoft SMTP Server (TLS) id 8.2.213.0; Mon, 26 Apr 2010 15:19:21 -0500
Message-ID: <4BD5F5C5.1000705@alcatel-lucent.com>
Date: Mon, 26 Apr 2010 16:21:25 -0400
From: Volker Hilt <volker.hilt@alcatel-lucent.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "NOEL, ERIC C (ATTLABS)" <en5192@att.com>
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com><4BB5409E.5080108@alcatel-lucent.com><0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com><6FEFDA2E-C51F-451A-B0A4-3973580468D1@nostrum.com>	<9ECCF01B52E7AB408A7EB85352642141015EFC76@ftrdmel0.rd.francetelecom.fr> <5DA01D2CA74FAF40ADF71DB4177D345A055BB760@misout7msgusr7b.ugd.att.com>
In-Reply-To: <5DA01D2CA74FAF40ADF71DB4177D345A055BB760@misout7msgusr7b.ugd.att.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: "dispatch@ietf.org" <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, "lars.eggert@nokia.com" <lars.eggert@nokia.com>, "rjsparks@nostrum.com" <rjsparks@nostrum.com>
Subject: Re: [sip-overload] [dispatch] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 26 Apr 2010 20:19:42 -0000

Eric,
>
> Wrt milestones deadlines:
>
>     1. A document describing key design considerations for a SIP overload
>        control mechanism ==>  Sep 2010
>     2. A specification for an SIP overload control mechanism based on
>        implicit/explicit feedback ==>  Dec 2010
>     3. A specification for a SIP load filtering mechanism ==>  May 2011
>
> I have a few comments:
>
> - Is item 1 a cleaned up version of draft-ietf-sipping-overload-design-02.pdf?
>      ==>  if so I am OK with Sep 2010 date.
> - Could item 2 consist of the documentation of one of the SIP overload control mechanism studied by the SIP overload design team coordinated by Volker?
>      ==>  Provided work consists of documenting one of the control mechanism studied by the SIP overload design team, then I am ok with Dec 2010.
> - With respect to item 3, are there any other related IETF activity besides draft-shen-sipping-load-control-event-package that need consideration? Is the expectation to validate the proposed load filtering mechanism through simulation?
>      ==>  Would like feedback on questions prior agreeing on May 2011 deadline.
>
The charter lays out milestones for items the proposed working group 
should produce. It is up to the WG to evaluate the drafts that have been 
proposed and adopt drafts that meet these milestones. The drafts you 
mention are candidates. They may or may not be adopted by the WG.

> Lastly, what will be the mode of operation to actually work on these
> items? Continue sending comments on the sip-overload distribution
> list? Have regular sub-teams meeting (via conference calls)?
>
All discussions will happen on the sip-overload mailing list and all 
comments need to go to this list. We may use conference calls for 
specific topics if needed. If there is a need, calls will be announced 
on the mailing list.

Thanks,

Volker




> -----Original Message-----
> From: sip-overload-bounces@ietf.org [mailto:sip-overload-bounces@ietf.org] On Behalf Of bruno.chatras@orange-ftgroup.com
> Sent: Friday, April 23, 2010 4:54 AM
> To: rjsparks@nostrum.com
> Cc: volker.hilt@alcatel-lucent.com; dispatch@ietf.org; sip-overload@ietf.org; Gonzalo.Camarillo@ericsson.com; lars.eggert@nokia.com
> Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
>
> I would prefer to see the SIP load filtering specification released by the end of 2010.
> BC
>
>> -----Message d'origine-----
>> De : sip-overload-bounces@ietf.org
>> [mailto:sip-overload-bounces@ietf.org] De la part de Robert Sparks
>> Envoyé : mercredi 21 avril 2010 17:29
>> À : Robert Sparks
>> Cc : Volker Hilt; DISPATCH; sip-overload@ietf.org; Gonzalo
>> Camarillo; Lars Eggert
>> Objet : Re: [sip-overload] Proposed SIP Overload Control Charter
>>
>> Please comment on what these dates should actually be
>>
>> RjS
>>
>>> Milestones:
>>>
>>> Sep 2010 Design Considerations to IESG for publication as
>>> Informational Dec 2010 Specification for a SIP overload control
>>> mechanism based on implicit/explicit feedback to IESG for
>> publication
>>> as Proposed Standard May 2011 Specification for a SIP load
>> filtering
>>> mechaism to IESG for publication as Proposed Standard
>>
>> _______________________________________________
>> sip-overload mailing list
>> sip-overload@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-overload
>>
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch


From partr@cisco.com  Tue Apr 27 07:58:51 2010
Return-Path: <partr@cisco.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 60B2D28C235; Tue, 27 Apr 2010 07:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.854
X-Spam-Level: 
X-Spam-Status: No, score=-9.854 tagged_above=-999 required=5 tests=[AWL=0.745,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2wdqe0MJGJx3; Tue, 27 Apr 2010 07:58:50 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id AF9C13A6BBE; Tue, 27 Apr 2010 07:53:43 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnwEAPmW1ktAaHtegWdsb2JhbACcThUBAQsLIiKmY5ofgkyCQgSDOB8
X-IronPort-AV: E=Sophos;i="4.52,280,1270425600"; d="scan'208";a="60173366"
Received: from hkg-core-1.cisco.com ([64.104.123.94]) by ams-iport-1.cisco.com with ESMTP; 27 Apr 2010 14:53:28 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o3RErRjc003699; Tue, 27 Apr 2010 14:53:27 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 27 Apr 2010 20:23:27 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 27 Apr 2010 20:23:26 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623901F36693@XMB-BGL-411.cisco.com>
In-Reply-To: <4BD5F5C5.1000705@alcatel-lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dispatch] [sip-overload] Proposed SIP Overload Control Charter
Thread-Index: AcrlfdskN/qI7PFISx20X/Vf7uzcOwAmyKfw
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com><4BB5409E.5080108@alcatel-lucent.com><0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com><6FEFDA2E-C51F-451A-B0A4-3973580468D1@nostrum.com>	<9ECCF01B52E7AB408A7EB85352642141015EFC76@ftrdmel0.rd.francetelecom.fr><5DA01D2CA74FAF40ADF71DB4177D345A055BB760@misout7msgusr7b.ugd.att.com> <4BD5F5C5.1000705@alcatel-lucent.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Volker Hilt" <volker.hilt@alcatel-lucent.com>, "NOEL, ERIC C (ATTLABS)" <en5192@att.com>
X-OriginalArrivalTime: 27 Apr 2010 14:53:27.0190 (UTC) FILETIME=[64B90B60:01CAE619]
Cc: dispatch@ietf.org, sip-overload@ietf.org, "Paul Kyzivat \(pkyzivat\)" <pkyzivat@cisco.com>, lars.eggert@nokia.com, "Paul Jones \(paulej\)" <paulej@cisco.com>
Subject: Re: [sip-overload] [dispatch] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Apr 2010 14:58:51 -0000

Hi all,

>     2. A specification for an SIP overload control mechanism based on
>        implicit/explicit feedback =3D=3D>  Dec 2010

draft-partha-sip-overload-resource-availability is a draft based on =
explicit feedback mechanism (SUBSCRIBE/NOTIFY).  This draft is an =
enhancement of H.323 Resource Availability Indication mechanism (RAI) =
which is widely deployed in H.323 network for handling overload =
situation.  The draft mechanism is tested in our Lab and it is working =
fine for overloading of different resources like CPU, Memory, DSP, DS0. =
The proposed mechanism works well in case server has capability to =
handle audio & video and audio only call simultaneously. Could you =
please consider this draft for the above requirement.=20

Thanks
Partha
-----Original Message-----
From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On =
Behalf Of Volker Hilt
Sent: Tuesday, April 27, 2010 1:51 AM
To: NOEL, ERIC C (ATTLABS)
Cc: bruno.chatras@orange-ftgroup.com; dispatch@ietf.org; =
sip-overload@ietf.org; lars.eggert@nokia.com
Subject: Re: [dispatch] [sip-overload] Proposed SIP Overload Control =
Charter

Eric,
>
> Wrt milestones deadlines:
>
>     1. A document describing key design considerations for a SIP =
overload
>        control mechanism =3D=3D>  Sep 2010
>     2. A specification for an SIP overload control mechanism based on
>        implicit/explicit feedback =3D=3D>  Dec 2010
>     3. A specification for a SIP load filtering mechanism =3D=3D>  May =

> 2011
>
> I have a few comments:
>
> - Is item 1 a cleaned up version of =
draft-ietf-sipping-overload-design-02.pdf?
>      =3D=3D>  if so I am OK with Sep 2010 date.
> - Could item 2 consist of the documentation of one of the SIP overload =
control mechanism studied by the SIP overload design team coordinated by =
Volker?
>      =3D=3D>  Provided work consists of documenting one of the control =
mechanism studied by the SIP overload design team, then I am ok with Dec =
2010.
> - With respect to item 3, are there any other related IETF activity =
besides draft-shen-sipping-load-control-event-package that need =
consideration? Is the expectation to validate the proposed load =
filtering mechanism through simulation?
>      =3D=3D>  Would like feedback on questions prior agreeing on May =
2011 deadline.
>
The charter lays out milestones for items the proposed working group =
should produce. It is up to the WG to evaluate the drafts that have been =
proposed and adopt drafts that meet these milestones. The drafts you =
mention are candidates. They may or may not be adopted by the WG.

> Lastly, what will be the mode of operation to actually work on these=20
> items? Continue sending comments on the sip-overload distribution=20
> list? Have regular sub-teams meeting (via conference calls)?
>
All discussions will happen on the sip-overload mailing list and all =
comments need to go to this list. We may use conference calls for =
specific topics if needed. If there is a need, calls will be announced =
on the mailing list.

Thanks,

Volker




> -----Original Message-----
> From: sip-overload-bounces@ietf.org=20
> [mailto:sip-overload-bounces@ietf.org] On Behalf Of=20
> bruno.chatras@orange-ftgroup.com
> Sent: Friday, April 23, 2010 4:54 AM
> To: rjsparks@nostrum.com
> Cc: volker.hilt@alcatel-lucent.com; dispatch@ietf.org;=20
> sip-overload@ietf.org; Gonzalo.Camarillo@ericsson.com;=20
> lars.eggert@nokia.com
> Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
>
> I would prefer to see the SIP load filtering specification released by =
the end of 2010.
> BC
>
>> -----Message d'origine-----
>> De : sip-overload-bounces@ietf.org
>> [mailto:sip-overload-bounces@ietf.org] De la part de Robert Sparks=20
>> Envoy=E9 : mercredi 21 avril 2010 17:29 =C0 : Robert Sparks Cc : =
Volker=20
>> Hilt; DISPATCH; sip-overload@ietf.org; Gonzalo Camarillo; Lars Eggert =

>> Objet : Re: [sip-overload] Proposed SIP Overload Control Charter
>>
>> Please comment on what these dates should actually be
>>
>> RjS
>>
>>> Milestones:
>>>
>>> Sep 2010 Design Considerations to IESG for publication as=20
>>> Informational Dec 2010 Specification for a SIP overload control=20
>>> mechanism based on implicit/explicit feedback to IESG for
>> publication
>>> as Proposed Standard May 2011 Specification for a SIP load
>> filtering
>>> mechaism to IESG for publication as Proposed Standard
>>
>> _______________________________________________
>> sip-overload mailing list
>> sip-overload@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-overload
>>
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch

From root@core3.amsl.com  Tue Apr 27 10:30:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: sip-overload@ietf.org
Delivered-To: sip-overload@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 97A3A3A6B58; Tue, 27 Apr 2010 10:30:02 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: ietf-announce@ietf.org
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20100427173002.97A3A3A6B58@core3.amsl.com>
Date: Tue, 27 Apr 2010 10:30:02 -0700 (PDT)
Cc: sip-overload@ietf.org
Subject: [sip-overload] WG Review: SIP Overload Control (soc)
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: iesg@ietf.org
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Apr 2010 17:30:02 -0000

A new IETF working group has been proposed in the Real-time Applications
and Infrastructure Area.  The IESG has not made any determination as yet.
The following draft charter was submitted, and is provided for
informational purposes only. Please send your comments to the IESG mailing
list (iesg@ietf.org) by Tuesday, May 4, 2010.   

SIP Overload Control (soc)
---------------------------
Current Status: Proposed Working Group

Last Modified: 2010-04-22

Chair(s)
TBD

Real-time Applications and Infrastructure Area Directors:
   Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
   Robert Sparks <rjsparks@nostrum.com>

Real-time Applications and Infrastructure Area Advisor:
   Robert Sparks <rjsparks@nostrum.com>

Mailing Lists:
   General Discussion: sip-overload@ietf.org
   To Subscribe: https://www.ietf.org/mailman/listinfo/sip-overload 
   Archive: http://www.ietf.org/mail-archive/web/sip-overload/

Description of Working Group:

As with any network element, a Session Initiation Protocol (SIP) server
can suffer from overload when the number of SIP messages it receives
exceeds the number of messages it can process. Overload is said to occur
when a SIP server does not have sufficient resources to complete the
processing of all incoming SIP messages within the required time.
These resources can include CPU, memory, network bandwidth, input/
output, or disk resources.

Overload can pose a serious problem for a network of SIP servers. During
periods of overload, the goodput (effective application throughput not 
counting the overhead of retransmission and redundant data) of a network 
of SIP servers can be significantly degraded.  In fact, overload may 
lead to a situation in which the goodput drops down to zero or a small 
fraction of the original processing capacity.  This is often called 
congestion collapse. The objective of a SIP overload control mechanism 
is to enable SIP servers to operate close to their capacity limit during 
times of overload.

The SIP protocol provides a limited mechanism for overload control
through its 503 (Service Unavailable) response code and the Retry-After
header.  However, this mechanism cannot fully prevent overload of a SIP
server and it cannot prevent congestion collapse.  In fact, its on/off
behavior may cause traffic to oscillate and shift between SIP servers
and thereby worsen an overload condition.  A detailed discussion of the
SIP overload problem, the problems with the 503 (Service Unavailable)
response code and the Retry-After header and the requirements for a SIP
overload control mechanism can be found in RFC5390.

The objective of the working group is to develop mechanisms for SIP
overload control. The problem domain of SIP overload control can be 
split into overload control between a user agent and a SIP server and 
overload control between SIP servers. 

Any specification developed by the working group needs to clearly 
specify its scope. A specification also needs to clearly state any 
limitations, in performance or otherwise, the specified overload control 
mechanism may have.  In particular, the working group shall carefully 
define the deployment considerations for the effective operation of the 
specified mechanisms and discuss, for example, when a mechanism requires 
coordinated deployment and operation (if all servers need to deploy the 
same mechanism, certain configuration values need to be identical on all 
servers, etc), when a mechanism can become less effective or ineffective 
under some conditions, or especially if there are cases when a mechanism 
can reduce goodput compared to no overload protection. The intent of 
these considerations is to allow potential deployers to make the best 
use of these mechanism in their particular networks.

The working group will consider two complementary approaches for 
handling overload situations:
- The first mechanism aims at preventing overload in SIP servers by
 adjusting the incoming load to a level that is acceptable for this
 server. This mechanism uses implicit and/or explicit feedback to
 determine when an overload condition occurs in a SIP server and a
 reduction in load is required.
- The second mechanism aims at preventing overload in SIP servers by
 distributing load control filters to SIP servers that throttle calls
 based on their source or destination domain, telephone number prefix or 
 for a specific user. Such filters can be used, for example, to throttle 
 calls to a hotline during a ticket-giveaway event.

The working group will develop the following deliverables:

 1. A document describing key design considerations for a SIP overload
    control mechanism.
 2. A specification for an SIP overload control mechanism based on
    implicit/explicit feedback.
 3. A specification for a SIP load filtering mechanism.

Milestones:

Sep 2010 Design Considerations to IESG for publication as Informational
Dec 2010 Specification for a SIP overload control mechanism based on 
         implicit/explicit feedback to IESG for publication as Proposed 
         Standard
May 2011 Specification for a SIP load filtering mechaism to IESG for 
         publication as Proposed Standard

From volker.hilt@alcatel-lucent.com  Tue Apr 27 12:07:31 2010
Return-Path: <volker.hilt@alcatel-lucent.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51AF63A6A4A; Tue, 27 Apr 2010 12:07:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[AWL=0.425,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dXOQu-JNtSee; Tue, 27 Apr 2010 12:07:27 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 3BB1C3A699F; Tue, 27 Apr 2010 12:07:24 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id o3RJ79ow023981 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Apr 2010 14:07:09 -0500 (CDT)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id o3RJ6rbe002557; Tue, 27 Apr 2010 14:07:09 -0500
Received: from [135.222.104.95] (135.3.63.242) by USNAVSXCHHUB02.ndc.alcatel-lucent.com (135.3.39.111) with Microsoft SMTP Server (TLS) id 8.2.213.0; Tue, 27 Apr 2010 14:07:00 -0500
Message-ID: <4BD73716.1050903@alcatel-lucent.com>
Date: Tue, 27 Apr 2010 15:12:22 -0400
From: Volker Hilt <volker.hilt@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "Parthasarathi R (partr)" <partr@cisco.com>
References: <429D5EE4-8790-4D0D-A7A7-CB2DE9E2D70A@nostrum.com><4BB5409E.5080108@alcatel-lucent.com><0F93BDF3-0A60-4E81-B427-3778613EAE45@nostrum.com><6FEFDA2E-C51F-451A-B0A4-3973580468D1@nostrum.com>	<9ECCF01B52E7AB408A7EB85352642141015EFC76@ftrdmel0.rd.francetelecom.fr><5DA01D2CA74FAF40ADF71DB4177D345A055BB760@misout7msgusr7b.ugd.att.com> <4BD5F5C5.1000705@alcatel-lucent.com> <A11921905DA1564D9BCF64A6430A623901F36693@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623901F36693@XMB-BGL-411.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: "dispatch@ietf.org" <dispatch@ietf.org>, "NOEL, ERIC C \(ATTLABS\)" <en5192@att.com>, "Paul Kyzivat \(pkyzivat\)" <pkyzivat@cisco.com>, "lars.eggert@nokia.com" <lars.eggert@nokia.com>, "Paul Jones \(paulej\)" <paulej@cisco.com>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: Re: [sip-overload] [dispatch] Proposed SIP Overload Control Charter
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Apr 2010 19:07:31 -0000

Partha,

please feel encouraged to submit your draft for consideration to the wg 
once it is chartered!

Thanks,

Volker



Parthasarathi R (partr) wrote:
> Hi all,
> 
>>     2. A specification for an SIP overload control mechanism based on
>>        implicit/explicit feedback ==>  Dec 2010
> 
> draft-partha-sip-overload-resource-availability is a draft based on explicit feedback mechanism (SUBSCRIBE/NOTIFY).  This draft is an enhancement of H.323 Resource Availability Indication mechanism (RAI) which is widely deployed in H.323 network for handling overload situation.  The draft mechanism is tested in our Lab and it is working fine for overloading of different resources like CPU, Memory, DSP, DS0. The proposed mechanism works well in case server has capability to handle audio & video and audio only call simultaneously. Could you please consider this draft for the above requirement. 
> 
> Thanks
> Partha
> -----Original Message-----
> From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On Behalf Of Volker Hilt
> Sent: Tuesday, April 27, 2010 1:51 AM
> To: NOEL, ERIC C (ATTLABS)
> Cc: bruno.chatras@orange-ftgroup.com; dispatch@ietf.org; sip-overload@ietf.org; lars.eggert@nokia.com
> Subject: Re: [dispatch] [sip-overload] Proposed SIP Overload Control Charter
> 
> Eric,
>> Wrt milestones deadlines:
>>
>>     1. A document describing key design considerations for a SIP overload
>>        control mechanism ==>  Sep 2010
>>     2. A specification for an SIP overload control mechanism based on
>>        implicit/explicit feedback ==>  Dec 2010
>>     3. A specification for a SIP load filtering mechanism ==>  May 
>> 2011
>>
>> I have a few comments:
>>
>> - Is item 1 a cleaned up version of draft-ietf-sipping-overload-design-02.pdf?
>>      ==>  if so I am OK with Sep 2010 date.
>> - Could item 2 consist of the documentation of one of the SIP overload control mechanism studied by the SIP overload design team coordinated by Volker?
>>      ==>  Provided work consists of documenting one of the control mechanism studied by the SIP overload design team, then I am ok with Dec 2010.
>> - With respect to item 3, are there any other related IETF activity besides draft-shen-sipping-load-control-event-package that need consideration? Is the expectation to validate the proposed load filtering mechanism through simulation?
>>      ==>  Would like feedback on questions prior agreeing on May 2011 deadline.
>>
> The charter lays out milestones for items the proposed working group should produce. It is up to the WG to evaluate the drafts that have been proposed and adopt drafts that meet these milestones. The drafts you mention are candidates. They may or may not be adopted by the WG.
> 
>> Lastly, what will be the mode of operation to actually work on these 
>> items? Continue sending comments on the sip-overload distribution 
>> list? Have regular sub-teams meeting (via conference calls)?
>>
> All discussions will happen on the sip-overload mailing list and all comments need to go to this list. We may use conference calls for specific topics if needed. If there is a need, calls will be announced on the mailing list.
> 
> Thanks,
> 
> Volker
> 
> 
> 
> 
>> -----Original Message-----
>> From: sip-overload-bounces@ietf.org 
>> [mailto:sip-overload-bounces@ietf.org] On Behalf Of 
>> bruno.chatras@orange-ftgroup.com
>> Sent: Friday, April 23, 2010 4:54 AM
>> To: rjsparks@nostrum.com
>> Cc: volker.hilt@alcatel-lucent.com; dispatch@ietf.org; 
>> sip-overload@ietf.org; Gonzalo.Camarillo@ericsson.com; 
>> lars.eggert@nokia.com
>> Subject: Re: [sip-overload] Proposed SIP Overload Control Charter
>>
>> I would prefer to see the SIP load filtering specification released by the end of 2010.
>> BC
>>
>>> -----Message d'origine-----
>>> De : sip-overload-bounces@ietf.org
>>> [mailto:sip-overload-bounces@ietf.org] De la part de Robert Sparks 
>>> Envoyé : mercredi 21 avril 2010 17:29 À : Robert Sparks Cc : Volker 
>>> Hilt; DISPATCH; sip-overload@ietf.org; Gonzalo Camarillo; Lars Eggert 
>>> Objet : Re: [sip-overload] Proposed SIP Overload Control Charter
>>>
>>> Please comment on what these dates should actually be
>>>
>>> RjS
>>>
>>>> Milestones:
>>>>
>>>> Sep 2010 Design Considerations to IESG for publication as 
>>>> Informational Dec 2010 Specification for a SIP overload control 
>>>> mechanism based on implicit/explicit feedback to IESG for
>>> publication
>>>> as Proposed Standard May 2011 Specification for a SIP load
>>> filtering
>>>> mechaism to IESG for publication as Proposed Standard
>>> _______________________________________________
>>> sip-overload mailing list
>>> sip-overload@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sip-overload
>>>
>> _______________________________________________
>> sip-overload mailing list
>> sip-overload@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-overload
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

