
From partr@cisco.com  Mon Feb  1 19:12:31 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 E50AA3A6899 for <sip-overload@core3.amsl.com>; Mon,  1 Feb 2010 19:12:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.202
X-Spam-Level: 
X-Spam-Status: No, score=-9.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, 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 S8nE6UJtWrhN for <sip-overload@core3.amsl.com>; Mon,  1 Feb 2010 19:12:29 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 8627F3A635F for <sip-overload@ietf.org>; Mon,  1 Feb 2010 19:12:29 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqIEAIInZ0urRN+K/2dsb2JhbACaPadCl06ERQSDDIpo
X-IronPort-AV: E=Sophos;i="4.49,387,1262563200";  d="scan'208,217";a="144053246"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-5.cisco.com with ESMTP; 02 Feb 2010 02:57:10 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o122v9f9007967;  Tue, 2 Feb 2010 02:57:09 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, 2 Feb 2010 08:27:08 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAA3B3.6861ECD8"
Date: Tue, 2 Feb 2010 08:27:07 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A6239021FAC@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] Fwd: draft-shen-sipping-avalanche-restart-overload-00
Thread-Index: Acp0JVEF7kcKtgthQRiHuKqW2PJSxgvjRmoZ
References: <e7df28360911230708v50c72a48o7dc9c22a8731146a@mail.gmail.com> <e7df28360912030631i53e600cdwddfc5feecaa6ec65@mail.gmail.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Charles Shen" <charles@cs.columbia.edu>, <sip-overload@ietf.org>
X-OriginalArrivalTime: 02 Feb 2010 02:57:08.0299 (UTC) FILETIME=[689BB9B0:01CAA3B3]
Cc: Arata Koike <koike.arata@lab.ntt.co.jp>, Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [sip-overload] Fwd: draft-shen-sipping-avalanche-restart-overload-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: Tue, 02 Feb 2010 03:12:31 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CAA3B3.6861ECD8
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Charles,
=20
The draft looks good. I have few comments:
=20
1) The proposed mechanism assumes that UA have the capability to store =
the configuration in memory. This may not be appropriate in case of UA =
with zero SIP configuration and configuration is downloaded from config =
server. In case default register restart timer (say 5 or 10 sec) is =
mentioned in UA configuration, this problem may be solved.
=20
2) Sec 4.3 assumes that Register will be the first message by UA. In =
case SIP based configuration mechanism is followed, SUBSCRIBE will be =
send by UA to SIP configuration server to get Registrar address and =
other SIP related configuration and REGISTER message follows next. In =
this scenario, SUBSCRIBE should have restart-timer rather than REGISTER. =

=20
Thanks
Partha


________________________________

From: sip-overload-bounces@ietf.org on behalf of Charles Shen
Sent: Thu 12/3/2009 8:01 PM
To: sip-overload@ietf.org
Cc: Arata Koike; Henning Schulzrinne
Subject: [sip-overload] Fwd: =
draft-shen-sipping-avalanche-restart-overload-00



Hi all, we've submitted the following draft, comments appreciated.

A Mechanism for Session Initiation Protocol (SIP) Avalanche Restart
Overload Control

http://tools.ietf.org/html/draft-shen-sipping-avalanche-restart-overload-=
00

Abstract

  When a large number of clients register with a SIP registrar server
  at approximately the same time, the server may become overloaded.
  Near-simultaneous floods of SIP SUBSCRIBE and PUBLISH requests may
  have similar effects.  Such request avalanches can occur, for
  example, after a power failure and recovery in a metropolitan area.
  This document describes how to avoid such overload situations.  Under
  this mechanism, a server estimates an avalanche restart backoff
  interval during its normal operation and conveys this interval to its
  clients through a new Register-Restart header in registration
  responses.  Once an avalanche restart actually occurs, the clients
  perform backoff based on the previously received Register-Restart
  header value before sending out the first registration attempt.
  Thus, the mechanism spreads all the initial client registration
  requests and prevents them from overloading the registrar server.


Thanks

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



------_=_NextPart_001_01CAA3B3.6861ECD8
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>[sip-overload] Fwd: =
draft-shen-sipping-avalanche-restart-overload-00</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18876"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText57753>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3DArial>Hi =
Charles,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>The draft looks good. I have =
few comments:</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>1) The proposed mechanism =
assumes that UA have the capability to store the configuration in =
memory. This may not be appropriate in case of UA with zero SIP =
configuration and configuration is downloaded from config server. =
</FONT><FONT size=3D2 face=3DArial>In case default register restart =
timer (say 5 or 10 sec) is mentioned in UA configuration, this problem =
may be solved.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>2)&nbsp;Sec 4.3&nbsp;assumes =
that Register will be the first message by UA. In case SIP based =
configuration mechanism is followed, SUBSCRIBE will be send by UA to SIP =
configuration server to get Registrar address and other SIP related =
configuration and REGISTER message follows next. In this scenario, =
SUBSCRIBE should have restart-timer rather than REGISTER.</FONT> </DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>Thanks</DIV>=0A=
<DIV dir=3Dltr>Partha</DIV></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> sip-overload-bounces@ietf.org =
on behalf of Charles Shen<BR><B>Sent:</B> Thu 12/3/2009 8:01 =
PM<BR><B>To:</B> sip-overload@ietf.org<BR><B>Cc:</B> Arata Koike; =
Henning Schulzrinne<BR><B>Subject:</B> [sip-overload] Fwd: =
draft-shen-sipping-avalanche-restart-overload-00<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Hi all, we've submitted the following draft, comments =
appreciated.<BR><BR>A Mechanism for Session Initiation Protocol (SIP) =
Avalanche Restart<BR>Overload Control<BR><BR><A =
href=3D"http://tools.ietf.org/html/draft-shen-sipping-avalanche-restart-o=
verload-00">http://tools.ietf.org/html/draft-shen-sipping-avalanche-resta=
rt-overload-00</A><BR><BR>Abstract<BR><BR>&nbsp; When a large number of =
clients register with a SIP registrar server<BR>&nbsp; at approximately =
the same time, the server may become overloaded.<BR>&nbsp; =
Near-simultaneous floods of SIP SUBSCRIBE and PUBLISH requests =
may<BR>&nbsp; have similar effects. &nbsp;Such request avalanches can =
occur, for<BR>&nbsp; example, after a power failure and recovery in a =
metropolitan area.<BR>&nbsp; This document describes how to avoid such =
overload situations. &nbsp;Under<BR>&nbsp; this mechanism, a server =
estimates an avalanche restart backoff<BR>&nbsp; interval during its =
normal operation and conveys this interval to its<BR>&nbsp; clients =
through a new Register-Restart header in registration<BR>&nbsp; =
responses. &nbsp;Once an avalanche restart actually occurs, the =
clients<BR>&nbsp; perform backoff based on the previously received =
Register-Restart<BR>&nbsp; header value before sending out the first =
registration attempt.<BR>&nbsp; Thus, the mechanism spreads all the =
initial client registration<BR>&nbsp; requests and prevents them from =
overloading the registrar =
server.<BR><BR><BR>Thanks<BR><BR>Charles<BR>_____________________________=
__________________<BR>sip-overload mailing =
list<BR>sip-overload@ietf.org<BR><A =
href=3D"https://www.ietf.org/mailman/listinfo/sip-overload">https://www.i=
etf.org/mailman/listinfo/sip-overload</A><BR></FONT></P></DIV></BODY></HT=
ML>
------_=_NextPart_001_01CAA3B3.6861ECD8--

From charles.newyork@gmail.com  Thu Feb  4 11:49:41 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 08ADF3A6BD9 for <sip-overload@core3.amsl.com>; Thu,  4 Feb 2010 11:49:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.827
X-Spam-Level: 
X-Spam-Status: No, score=-0.827 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MANGLED_LIST=2.3]
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 IYaeoqPO4Gml for <sip-overload@core3.amsl.com>; Thu,  4 Feb 2010 11:49:40 -0800 (PST)
Received: from mail-pz0-f175.google.com (mail-pz0-f175.google.com [209.85.222.175]) by core3.amsl.com (Postfix) with ESMTP id 2A3593A6999 for <sip-overload@ietf.org>; Thu,  4 Feb 2010 11:49:40 -0800 (PST)
Received: by pzk5 with SMTP id 5so171090pzk.29 for <sip-overload@ietf.org>; Thu, 04 Feb 2010 11:50:25 -0800 (PST)
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:message-id:subject:from:to:cc :content-type; bh=jGOPU3fwBJqhNdXplGbno8X+eMsDuZFSaHCgl21Oq2c=; b=GV8My2tRivZqSGkg3JHWti/TSlryguZSJ6RsR+ASBxOqMKhR77RRmZrybFd7br6o5A 82/3wxcGSyBw6mynkWYClUUYGcCzvZRV49BrDIovsIn5FXbra0xuqW51nDjfSd7cpWkl Mb8IdLRLcF+MC2cQJcRSw0E0VUnf349RiNDIY=
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=gv4LvXLOWWYAbcf6yutGO4z/Kf6+wSjfyx3ATQM+pAFOw6g6WD1t6zqayBEZc3n/Gm FhPkx7xyh6Kd71faXsqp5XQylSobbtfG648yTzqGtG90Fp6GiM8IjC3uFEpuxxCYqQNd 1k5uSy3OmZCs0Nz4BGURSXaWCUY4yJTBcjceI=
MIME-Version: 1.0
Sender: charles.newyork@gmail.com
Received: by 10.142.6.32 with SMTP id 32mr1010127wff.6.1265313025155; Thu, 04  Feb 2010 11:50:25 -0800 (PST)
In-Reply-To: <5DA01D2CA74FAF40ADF71DB4177D345A02685104@misout7msgusr7b.ugd.att.com>
References: <AcqD629vEQqape05QWGHquU7KqsfRQ==> <5DA01D2CA74FAF40ADF71DB4177D345A02685104@misout7msgusr7b.ugd.att.com>
Date: Thu, 4 Feb 2010 14:50:25 -0500
X-Google-Sender-Auth: be7205f85d88e047
Message-ID: <e7df28361002041150x8c33b1ai24789ac883988459@mail.gmail.com>
From: Charles Shen <charles@cs.columbia.edu>
To: "NOEL, ERIC C (ATTLABS)" <en5192@att.com>
Content-Type: text/plain; charset=UTF-8
Cc: sip-overload@ietf.org
Subject: Re: [sip-overload] A few comments on draft-shen-sipping-load-control-event-package-03
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: Thu, 04 Feb 2010 19:49:41 -0000

Eric, thanks for your review. Sorry for the late response due to
traveling. please see inline:

On Wed, Dec 23, 2009 at 11:19 AM, NOEL, ERIC C (ATTLABS) <en5192@att.com> wrote:
> Charles,
>
> Do you think it is possible for the specifications in
> draft-shen-sipping-load-control-event-package-03 to actually trigger
> SUBSCRIBE/NOTIFY storms? Or is that already taken care in related RFCs?
>
> For instance, if as suggested in the introduction, User Agents actually
> subscribe to a notifier, in a carrier grade telecommunication network
> this has potential for scaling problems and "large numbers" of NOTIFYs
> could be broadcasted towards the edges. One suggestion would be to add
> text in your RFC to require staggering of SUBSCRIBE/NOTIFYs over "some"
> time period so as to prevent message storms.
>

In the UA -> Notifier direction, there should be natural spacing,
similar to when UAs are registering with their registrar in normal
cases. (in other words, this is not an avalanche restart)

In the Notifier -> UA direction, it seems there shouldn't be scaling
problems since notifications are sent to many different entities. Are
you talking about potential bandwidth issues between the notifier and
the edges? That seems not very likely either ...


> In Section 4.1, similar problem could occur when entities subscribe to a
> notifier "when certain events have occurred". I could imagine a case
> where following an earthquake all User Agents within the region are
> programmed to subscribe to a notifier, resulting in a SUBSCRIBE/NOTIFY
> storm. One suggestion would be to require some randomization over time
> in sending SUBSCRIBEs to notifiers so as to prevent message storms.
>

This example will indeed be somewhat like the avalanche restart
problem which is what our another draft
http://tools.ietf.org/html/draft-shen-sipping-avalanche-restart-overload-00
intends to address.

> Then, is it possible for one entity to subscribe to multiple notifiers?
> If so, should not there be provisions against conflicting NOTIFYs from
> different notifiers. For instance, one notifier requests subscriber not
> to send any outbound traffic, while another requests not sending any
> inbound traffic to the same subscriber. Not sure how to deal with such a
> problem without requiring entities to subscribe to no more than one
> notifier.
>

This looks like more an issue of mis-configuration or mis-calculation
(of rules) and seems to be orthogonal to the event package itself?

> In general, as protection against elements or signaling failures, you
> probably want to require NOTIFYs to be sent no earlier than xxx
> days/hours/minutes prior requested action. Similarly, you probably want
> to limit the NOTIFY requested action to be valid for no longer than yyy
> days/hours/minutes.

Mechanism-wise, there is the validity element that allows you to
specify when the action should be valid. I think the detailed timing
(days/hours/minutes) is then subject to the actual operator and
scenarios.

>
> There are a few typos, I assume ispell or equivalent will catch them
> (section 1 1st paragraph "sever", section 6.3.3 "...server depend on the
> type of of an initial...").
>

These should be fixed in the next update.

Thanks!

Charles



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

From charles.newyork@gmail.com  Thu Feb  4 12:32:07 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 03F7728C1DF for <sip-overload@core3.amsl.com>; Thu,  4 Feb 2010 12:32:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.102
X-Spam-Level: 
X-Spam-Status: No, score=-1.102 tagged_above=-999 required=5 tests=[AWL=0.275,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_21=0.6]
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 3bRYxDKIIOrK for <sip-overload@core3.amsl.com>; Thu,  4 Feb 2010 12:32:05 -0800 (PST)
Received: from mail-px0-f186.google.com (mail-px0-f186.google.com [209.85.216.186]) by core3.amsl.com (Postfix) with ESMTP id A7E4A28C1C0 for <sip-overload@ietf.org>; Thu,  4 Feb 2010 12:32:05 -0800 (PST)
Received: by pxi16 with SMTP id 16so411138pxi.29 for <sip-overload@ietf.org>; Thu, 04 Feb 2010 12:32:50 -0800 (PST)
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:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=UES12hn0UHDEbhZZi4WEOwDm9eZ6P9jJr8K30BQo96w=; b=Z622PwUNs/9etEKQodHOFkfEyuTOhyAVwmP6P8l9KEj7iEFZFqfIDy8zVyRdh5t1or 4ZbQKvLs/Q3hX42N+9+TK9D7Plrpr6Dsn+au6YcdSl9WV+u/DXidDUdllLAEbWccc5t4 0rWYcvSMDUoZKzN5V2F07YKv8OKP+J0rC5qBo=
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 :content-transfer-encoding; b=dJbLitBKb1Eqfug/tmPu2i1NQ+E0wY8sWTR8kL4l+tH1avxvKKjTN6qm7JqbAdozz5 I8YDGOXh30uU2KodTq9cE+FMyifCKaExKs//JAQ/nKmPeiM7eCGsy7CzoBMNAcYMvSDg Z+o+PYwcWMPl2ReQ9O8kKqzL9O/dauosVnptI=
MIME-Version: 1.0
Sender: charles.newyork@gmail.com
Received: by 10.142.6.22 with SMTP id 22mr1048076wff.5.1265315570659; Thu, 04  Feb 2010 12:32:50 -0800 (PST)
In-Reply-To: <B71E03B6EDEAA9438A12F0D64BC08C790936EE88@E03MVY2-UKDY.domain1.systemhost.net>
References: <Acp9n0gOqnQpKIR+Q0euCoSv60fduQ==> <B71E03B6EDEAA9438A12F0D64BC08C790936EE88@E03MVY2-UKDY.domain1.systemhost.net>
Date: Thu, 4 Feb 2010 15:32:50 -0500
X-Google-Sender-Auth: c0de9709f68a22e6
Message-ID: <e7df28361002041232x6c108913j931df954b8f610de@mail.gmail.com>
From: Charles Shen <charles@cs.columbia.edu>
To: geoff.hunt@bt.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: sip-overload@ietf.org, Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [sip-overload] Comments on draft-shen-sipping-load-control-event-package-03
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: Thu, 04 Feb 2010 20:32:07 -0000

Hi Geoff: thanks for the review, sorry for the late response. please
see inline.

> On Tue, Dec 15, 2009 at 10:57 AM,  <geoff.hunt@bt.com> wrote:
> Hi Charles, All,
>
> Here are some comments on the draft:
>
> 1) Section 1, para 1, typo "sever"

will correct

>
> 2) Section 4.1 Case 1 text " CPa1 then allocates the received total
> acceptable rate among its neighbors". Whilst CPa1 should not send more
> than the requested rate to EPa1, it is probably not sensible to
> "allocate" the total acceptable rate among its upstream neighbours,
> because this will (almost) guarantee it will send less than the
> requested rate to EPa1, because it is very likely that some sources will
> not offer the rate they are permitted to send. CPa1 might divide up some
> number larger than the total acceptable rate, to guarantee that it is
> able send the requested total acceptable rate to EPa1. Otherwise
> customer service will be worse than necessary (more calls than necessary
> will be rejected) and total network load will be exaggerated by
> unnecessary repeat attempt behaviour.
>
> 3) Section 5.7 para 2 text " then the total rate limit for the specific
> downstream SIP entity in the three NOTIFY messages sent to those three
> upstream neighbors must not exceed =C2=A0100 requests per second." This i=
s a
> similar comment to the comment above about section 4.1. It would be
> better to communicate permitted rates which *do* exceed 100 in total to
> upstream neighbours, and explicitly to limit downstream traffic to 100
> at the local server. Otherwise the network will almost certainly be
> under-utilised, which is damaging to customer service.

The point of possible under-utilization with the simplified example is
recognized. Since it is difficult to give any specific (right) value
of over-commitment either, and the value computation mechanism itself
is considered out-of-scope of the event package, the next update will
clarify this.

> 4) Section 5.8 para 3. typo "previoulsy"

will correct.

>
> 5) Section 6.3.1 para 2 last sentence, text "result is combined using
> logical OR". Just to clarify: does this interpretation allow joint
> control of traffic to a list of destinations (such as a televoting
> destination range) such that control does not have the effect of
> equalising traffic to the individual destinations?

Not sure whether I understand. Could you please elaborate a bit about
the scenario you are referring to?

>
> 6) Section 6.4 para 1, text " takes any one of the three sub-elements
> <rate>, <percent>, and <win>" It's very hard to see how either <percent>
> or <win> could make any sense for a statically-configured filtering type
> of control, given the uncertainty in offered traffic level and in
> downstream server responsiveness.
>

Indeed at this stage it may be the safest to use the <rate> sub-element.

> 7) Section 6.4 para 2, text "The default value is "Drop" . =C2=A0" Will
> "drop" lead to retransmission by upstream elements, in networks using
> unreliable transport? If so this seems undesirable, by increasing load
> on the local device. Also 503 will allow upstream elements to re-try
> elsewhere which seems pointless or damaging in this type of control -
> would it be better to require sending 500?
>

This makes sense. (although sending rejection costs non-negligible
additional cycles too)

> Hope this helps

Yes, thanks!

Charles


>
> Geoff
>
> Geoff Hunt
> BT Design
>
> Tel: 01473 651704
> Email: geoff.hunt@bt.com
> Web: www.bt.com
> This email contains BT information, which may be privileged or
> confidential.
> It is meant only for the individual(s) or entity named above. If you are
> not the intended
> recipient, note that disclosing, copying, distributing or using this
> information
> is prohibited. If you have received this email in error, please let me
> know immediately
> on the email address above. Thank you.
> We monitor our email system, and may record your emails.
> British Telecommunications plc
> Registered office: 81 Newgate Street London EC1A 7AJ
> Registered in England no: 1800000
>
>
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload
>

From charles.newyork@gmail.com  Thu Feb  4 12:43:23 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 0B8673A6E0C for <sip-overload@core3.amsl.com>; Thu,  4 Feb 2010 12:43:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.894
X-Spam-Level: 
X-Spam-Status: No, score=-0.894 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_21=0.6, J_CHICKENPOX_74=0.6]
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 ZzrVUwpYWYgv for <sip-overload@core3.amsl.com>; Thu,  4 Feb 2010 12:43:21 -0800 (PST)
Received: from mail-px0-f186.google.com (mail-px0-f186.google.com [209.85.216.186]) by core3.amsl.com (Postfix) with ESMTP id 28F453A68D1 for <sip-overload@ietf.org>; Thu,  4 Feb 2010 12:43:21 -0800 (PST)
Received: by pxi16 with SMTP id 16so423087pxi.29 for <sip-overload@ietf.org>; Thu, 04 Feb 2010 12:44:06 -0800 (PST)
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:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=81OpkcnYd70C9l7BYe87K8W++C628mBsIYGGAz1SXCc=; b=jaHFYYvocGyAtJf/IazN5I4H8+vcGHZvjCCZFj1Dg2ZGhBvn0VAx1ScbWDwHlykOww gErwTwFUDYa5O57cGRj70BlLu+RQCAbdy8A5yV/rxJ+h1YgmUnfzLb8pInns5HCJPrW5 LhKZzPrWDnVDS/3yWbBqy99f7sIzROB8c1ZHA=
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 :content-transfer-encoding; b=O68VmCZ0eSqXhV1t6E2XFq9JudunZs2Jf3Z3Rn88cgPQb42lxFLEC4GaDX5D5WQBwj btuUbcs9VKgczkzSwIcw/SVJ7s4QgZ786zaCSyePEMrZvAMjJIs8sIUVbcvkqg4eruxE rGjEBJ0ubtyPc7VPuVdLrOhyw1CkrovvGSbDI=
MIME-Version: 1.0
Sender: charles.newyork@gmail.com
Received: by 10.143.25.13 with SMTP id c13mr1038151wfj.112.1265316246054; Thu,  04 Feb 2010 12:44:06 -0800 (PST)
In-Reply-To: <OF30F03E3F.A240DD8B-ON8525769B.0077DA82-8525769B.007B28FF@csc.com>
References: <B71E03B6EDEAA9438A12F0D64BC08C790936EE88@E03MVY2-UKDY.domain1.systemhost.net> <OF30F03E3F.A240DD8B-ON8525769B.0077DA82-8525769B.007B28FF@csc.com>
Date: Thu, 4 Feb 2010 15:44:06 -0500
X-Google-Sender-Auth: 74741128642b0149
Message-ID: <e7df28361002041244u4eb3dfb2m7b45a5892ce5afff@mail.gmail.com>
From: Charles Shen <charles@cs.columbia.edu>
To: Janet P Gunn <jgunn6@csc.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: sip-overload@ietf.org, geoff.hunt@bt.com, Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [sip-overload] Comments on draft-shen-sipping-load-control-event-package-03
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: Thu, 04 Feb 2010 20:43:24 -0000

On Tue, Dec 29, 2009 at 5:24 PM, Janet P Gunn <jgunn6@csc.com> wrote:
>
> I completely agree with point number two. =C2=A0When you are invoking a c=
ontrol
> analogous to "cancel to- call gapping", there is absolutely no assurance
> that the sources of the load to the specific destination will be evenly
> distributed among the neighbors. =C2=A0If you are going to propagate a "c=
ancel
> to-call gapping"load control, the sensible thing would be to give EVERY
> neighbor the full permitted rate. (note that this is a problem with the
> example, and not necessarily with the underlying mechanism)
>
> In case II of section 4.1, I =C2=A0sincerely doubt that CPb2, EPb3 and EP=
b4
> "configure themselves" =C2=A0They will be manually configured under the g=
uidance
> of the same people who have determined that "outgoing calls are more
> important than incoming calls". That is just semantics'. =C2=A0But I am h=
aving
> difficulty following how (or why) this is propagated to other servers bey=
ond
> the direct neighbors. =C2=A0CPb1 and CPa2 can be instructed to reduce the=
 rate at
> which they send calls to CPb2. =C2=A0 But how is CPa1 (or any of the EPax=
) =C2=A0to
> know which calls it needs to suppress?
>

 "configure themselves" may not be a good wording, but the
configuration could be based on a result of an algorithm executed on
the node, or as you suggested, manual configuration. You might have a
tightly controlled intra-domain scenario where you can propagate the
computation upstream, or you might not. As responded to Geoff's
original message, the computation algorithm is orthogonal to the event
package itself, and will be clarified in the next update.

> To follow on the same theme. in section 4.2, I understand how you can lim=
it
> SIP messages based on "callee number" (aka destination URI). =C2=A0but I =
fail to
> see how a "wildcard domain based filter" can identify SIP messages destin=
ed
> for CPb2.
>

wildcard domain based filter assumes that a SIP proxy (e.g., a
corporate proxy) is responsible for a specific domain (e.g, the
corporate domain), and then you use the domain name without specifying
the exact username, to filter all calls to the domain.

> I also agree with comments 3 and 6. =C2=A0There is a good reason why "per=
cent
> blocking" has largely been replaced with "call gapping" (aka rate based)
> load controls in the circuit switched world, and the same logic applies
> here.

yes, rate-based would be the most appropriate comparing with the other opti=
ons.

Thanks

Charles


>
> Janet
>
>
> sip-overload-bounces@ietf.org wrote on 12/15/2009 10:57:19 AM:
>
>> <geoff.hunt@bt.com>
>> Sent by: sip-overload-bounces@ietf.org
>>
>> 12/15/2009 10:57 AM
>>
>> To
>>
>> <charles@cs.columbia.edu>, <sip-overload@ietf.org>
>>
>> cc
>>
>> Subject
>>
>> [sip-overload] Comments on
>> draft-shen-sipping-load-control-event-package-03
>>
>> Hi Charles, All,
>>
>> Here are some comments on the draft:
>>
>> 1) Section 1, para 1, typo "sever"
>>
>> 2) Section 4.1 Case 1 text " CPa1 then allocates the received total
>> acceptable rate among its neighbors". Whilst CPa1 should not send more
>> than the requested rate to EPa1, it is probably not sensible to
>> "allocate" the total acceptable rate among its upstream neighbours,
>> because this will (almost) guarantee it will send less than the
>> requested rate to EPa1, because it is very likely that some sources will
>> not offer the rate they are permitted to send. CPa1 might divide up some
>> number larger than the total acceptable rate, to guarantee that it is
>> able send the requested total acceptable rate to EPa1. Otherwise
>> customer service will be worse than necessary (more calls than necessary
>> will be rejected) and total network load will be exaggerated by
>> unnecessary repeat attempt behaviour.
>>
>> 3) Section 5.7 para 2 text " then the total rate limit for the specific
>> downstream SIP entity in the three NOTIFY messages sent to those three
>> upstream neighbors must not exceed =C2=A0100 requests per second." This =
is a
>> similar comment to the comment above about section 4.1. It would be
>> better to communicate permitted rates which *do* exceed 100 in total to
>> upstream neighbours, and explicitly to limit downstream traffic to 100
>> at the local server. Otherwise the network will almost certainly be
>> under-utilised, which is damaging to customer service.
>>
>> 4) Section 5.8 para 3. typo "previoulsy"
>>
>> 5) Section 6.3.1 para 2 last sentence, text "result is combined using
>> logical OR". Just to clarify: does this interpretation allow joint
>> control of traffic to a list of destinations (such as a televoting
>> destination range) such that control does not have the effect of
>> equalising traffic to the individual destinations?
>>
>> 6) Section 6.4 para 1, text " takes any one of the three sub-elements
>> <rate>, <percent>, and <win>" It's very hard to see how either <percent>
>> or <win> could make any sense for a statically-configured filtering type
>> of control, given the uncertainty in offered traffic level and in
>> downstream server responsiveness.
>>
>> 7) Section 6.4 para 2, text "The default value is "Drop" . =C2=A0" Will
>> "drop" lead to retransmission by upstream elements, in networks using
>> unreliable transport? If so this seems undesirable, by increasing load
>> on the local device. Also 503 will allow upstream elements to re-try
>> elsewhere which seems pointless or damaging in this type of control -
>> would it be better to require sending 500?
>>
>> Hope this helps
>>
>> Geoff
>>
>> Geoff Hunt
>> BT Design
>>
>> Tel: 01473 651704
>> Email: geoff.hunt@bt.com
>> Web: www.bt.com
>> This email contains BT information, which may be privileged or
>> confidential.
>> It is meant only for the individual(s) or entity named above. If you are
>> not the intended
>> recipient, note that disclosing, copying, distributing or using this
>> information
>> is prohibited. If you have received this email in error, please let me
>> know immediately
>> on the email address above. Thank you.
>> We monitor our email system, and may record your emails.
>> British Telecommunications plc
>> Registered office: 81 Newgate Street London EC1A 7AJ
>> Registered in England no: 1800000
>>
>>
>> _______________________________________________
>> sip-overload mailing list
>> sip-overload@ietf.org
>> https://www.ietf.org/mailman/listinfo/sip-overload
>

From charles.newyork@gmail.com  Thu Feb  4 12:55:38 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 8BBCB3A6B4D for <sip-overload@core3.amsl.com>; Thu,  4 Feb 2010 12:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.465
X-Spam-Level: 
X-Spam-Status: No, score=-1.465 tagged_above=-999 required=5 tests=[AWL=0.513,  BAYES_00=-2.599, 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 jHfIVvS90K8S for <sip-overload@core3.amsl.com>; Thu,  4 Feb 2010 12:55:37 -0800 (PST)
Received: from mail-pz0-f175.google.com (mail-pz0-f175.google.com [209.85.222.175]) by core3.amsl.com (Postfix) with ESMTP id B6B8E3A6CE3 for <sip-overload@ietf.org>; Thu,  4 Feb 2010 12:55:37 -0800 (PST)
Received: by pzk5 with SMTP id 5so240398pzk.29 for <sip-overload@ietf.org>; Thu, 04 Feb 2010 12:56:23 -0800 (PST)
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:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=yLP/IaLnb9zu6GjcIJCDtZSYY/fRcyNHOZNt8WzUUBk=; b=kC/0YkZlzx1A/i75BtAwW0X/DuIhJIR0ZaW+VIBVq2wJP0ZjT8UVTvALX1KEKzP8jH nY5+ur5aX2txKqtNapAkT51Hz2P9NSvbBydKcD9pR9Cv9Q4RZ0K/l4EzfjfEwQQFiVOr BmQemjzDw0jASzSOESupUiw7SjS+U5P8mWdiA=
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 :content-transfer-encoding; b=fO2MiWt94gidNJ8LhLhuUA44Cm5wAfXvY0IufHC+r1i4ANvmS5jJRVjc89NouxukEn DPedpIZFzRk/9EO1URQY14mA+86+xjypRHPy1IF6givCnNcSRnmVaf6EWPsCEVKGR7DZ MPnTuJr1HORPOcRp5kfTmkuHSze6067UgN/zs=
MIME-Version: 1.0
Sender: charles.newyork@gmail.com
Received: by 10.142.7.24 with SMTP id 24mr1062239wfg.2.1265316982889; Thu, 04  Feb 2010 12:56:22 -0800 (PST)
In-Reply-To: <A11921905DA1564D9BCF64A6430A6239021FAC@XMB-BGL-411.cisco.com>
References: <e7df28360911230708v50c72a48o7dc9c22a8731146a@mail.gmail.com> <e7df28360912030631i53e600cdwddfc5feecaa6ec65@mail.gmail.com> <A11921905DA1564D9BCF64A6430A6239021FAC@XMB-BGL-411.cisco.com>
Date: Thu, 4 Feb 2010 15:56:22 -0500
X-Google-Sender-Auth: bc7032ee27573d4c
Message-ID: <e7df28361002041256v35f7d4e1we0b61629d71e9174@mail.gmail.com>
From: Charles Shen <charles@cs.columbia.edu>
To: "Parthasarathi R (partr)" <partr@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: sip-overload@ietf.org, Arata Koike <koike.arata@lab.ntt.co.jp>, Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [sip-overload] Fwd: draft-shen-sipping-avalanche-restart-overload-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: Thu, 04 Feb 2010 20:55:38 -0000

Hi Partha: thanks for the comments, please see inline.

On Mon, Feb 1, 2010 at 9:57 PM, Parthasarathi R (partr) <partr@cisco.com> w=
rote:
> Hi Charles,
>
> The draft looks good. I have few comments:
>
> 1) The proposed mechanism assumes that UA have the capability to store th=
e
> configuration in memory. This may not be appropriate in case of UA with z=
ero
> SIP configuration and configuration is downloaded from config server. In
> case default register restart timer (say 5 or 10 sec) is mentioned in UA
> configuration, this problem may be solved.

But shouldn't the UA normally have some flash memory (e.g., storing
the initial server to contact after boot-up)? In that case, couldn't
the timer information be stored in those flash memory as well?

> 2)=C2=A0Sec 4.3=C2=A0assumes that Register will be the first message by U=
A. In case
> SIP based configuration mechanism is followed, SUBSCRIBE will be send by =
UA
> to SIP configuration server to get Registrar address and other SIP relate=
d
> configuration and REGISTER message follows next. In this scenario, SUBSCR=
IBE
> should have restart-timer rather than REGISTER.

This is a very good point. We might then think of revising the name of
the new header from  REGISTER-RESTART to RESTART-TIMER instead to make
it more generic.

Thanks!

Charles

>
> Thanks
> Partha
> ________________________________
> From: sip-overload-bounces@ietf.org on behalf of Charles Shen
> Sent: Thu 12/3/2009 8:01 PM
> To: sip-overload@ietf.org
> Cc: Arata Koike; Henning Schulzrinne
> Subject: [sip-overload] Fwd:
> draft-shen-sipping-avalanche-restart-overload-00
>
> Hi all, we've submitted the following draft, comments appreciated.
>
> A Mechanism for Session Initiation Protocol (SIP) Avalanche Restart
> Overload Control
>
> http://tools.ietf.org/html/draft-shen-sipping-avalanche-restart-overload-=
00
>
> Abstract
>
> =C2=A0 When a large number of clients register with a SIP registrar serve=
r
> =C2=A0 at approximately the same time, the server may become overloaded.
> =C2=A0 Near-simultaneous floods of SIP SUBSCRIBE and PUBLISH requests may
> =C2=A0 have similar effects. =C2=A0Such request avalanches can occur, for
> =C2=A0 example, after a power failure and recovery in a metropolitan area=
.
> =C2=A0 This document describes how to avoid such overload situations. =C2=
=A0Under
> =C2=A0 this mechanism, a server estimates an avalanche restart backoff
> =C2=A0 interval during its normal operation and conveys this interval to =
its
> =C2=A0 clients through a new Register-Restart header in registration
> =C2=A0 responses. =C2=A0Once an avalanche restart actually occurs, the cl=
ients
> =C2=A0 perform backoff based on the previously received Register-Restart
> =C2=A0 header value before sending out the first registration attempt.
> =C2=A0 Thus, the mechanism spreads all the initial client registration
> =C2=A0 requests and prevents them from overloading the registrar server.
>
>
> Thanks
>
> Charles
> _______________________________________________
> 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 geoff.hunt@bt.com  Fri Feb  5 03:07:36 2010
Return-Path: <geoff.hunt@bt.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 A68E93A6D4E for <sip-overload@core3.amsl.com>; Fri,  5 Feb 2010 03:07:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6, J_CHICKENPOX_42=0.6, 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 dz3UueHSoj1a for <sip-overload@core3.amsl.com>; Fri,  5 Feb 2010 03:07:35 -0800 (PST)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by core3.amsl.com (Postfix) with ESMTP id D40EC3A6D53 for <sip-overload@ietf.org>; Fri,  5 Feb 2010 03:07:34 -0800 (PST)
Received: from E03MVY2-UKDY.domain1.systemhost.net ([193.113.30.56]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 5 Feb 2010 11:08:23 +0000
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, 5 Feb 2010 11:08:20 -0000
Message-ID: <B71E03B6EDEAA9438A12F0D64BC08C7909747B09@E03MVY2-UKDY.domain1.systemhost.net>
In-Reply-To: <e7df28361002041232x6c108913j931df954b8f610de@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] Comments on draft-shen-sipping-load-control-event-package-03
Thread-Index: Acql2T1PjkvfV/q5RhiUkp/i8QyppAAbkC2g
References: <Acp9n0gOqnQpKIR+Q0euCoSv60fduQ==> <B71E03B6EDEAA9438A12F0D64BC08C790936EE88@E03MVY2-UKDY.domain1.systemhost.net> <e7df28361002041232x6c108913j931df954b8f610de@mail.gmail.com>
From: <geoff.hunt@bt.com>
To: <charles@cs.columbia.edu>
X-OriginalArrivalTime: 05 Feb 2010 11:08:23.0680 (UTC) FILETIME=[888B3000:01CAA653]
Cc: sip-overload@ietf.org, hgs@cs.columbia.edu
Subject: Re: [sip-overload] Comments on draft-shen-sipping-load-control-event-package-03
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, 05 Feb 2010 11:07:36 -0000

SGkgQ2hhcmxlcywgQWxsLA0KDQpSZXNwb25kaW5nIHRvIENoYXJsZXMnIHJlcXVlc3QgZm9yIGNs
YXJpZmljYXRpb24gb2YgdGhlIHNjZW5hcmlvIGJlaGluZCBteSBjb21tZW50IGFib3V0IHNlY3Rp
b24gNi4zLjEgcGFyYSAyIG9mIHRoZSBkcmFmdC4gDQoNCkluIHRoZSBVSywgc29tZSB0ZWxldmlz
aW9uIGNvbXBhbmllcyBwdXQgb24gInRhbGVudCBjb21wZXRpdGlvbnMiIHJhaXNpbmcgbW9uZXkg
ZnJvbSBsYXJnZSBudW1iZXJzIG9mIHRlbGVwaG9uZSBjYWxscyBtYWRlIGJ5IHRoZSBhdWRpZW5j
ZSB0byBwcmVtaXVtIHJhdGUgbGluZXMsIHRvIHJlZ2lzdGVyIHBvcHVsYXIgdm90ZXMgZm9yIHRo
ZSBjb21wZXRpdG9ycy4gSSBiZWxpZXZlIHlvdSd2ZSBoYWQgc2ltaWxhciBUViBwcm9ncmFtbWVz
IGluIHRoZSBVUywgc3VjaCBhcyAiQW1lcmljYW4gSWRvbCIuIEluIHRoZSBVSywgdGhlc2UgY29t
cGV0aXRpb25zIGdpdmUgcmlzZSB0byBzb21lIG9mIHRoZSBsYXJnZXN0IGNhbGxpbmcgcmF0ZXMg
c2VlbiBvbiB0aGUgVUsgdGVsZXBob25lIG5ldHdvcmssIGFuZCBvbiBTSVAgbmV0d29ya3Mgd2hp
Y2ggaW50ZXJjb25uZWN0IHdpdGggaXQsIGFsdGhvdWdoIHRoZSB2b3RpbmcgcGVyaW9kIGlzIHR5
cGljYWxseSBxdWl0ZSBzaG9ydCAobWF5YmUgYSBmZXcgdGVucyBvZiBtaW51dGVzKS4gU28gY29u
dHJvbCBvZiB0aGlzIHR5cGUgb2YgZXZlbnQgaXMgYSBsaWtlbHkgYXBwbGljYXRpb24gb2YgeW91
ciBwYWNrYWdlLiBJbiB0aGUgVUssIHZvdGVzIGZvciBkaWZmZXJlbnQgY29tcGV0aXRvcnMgYXJl
IHJlZ2lzdGVyZWQgYnkgZGlhbGxpbmcgZGlmZmVyZW50IHRlbGVwaG9uZSBudW1iZXJzLCB1c3Vh
bGx5IGluIGEgY29tcGFjdCByYW5nZSBzdWNoIGFzIGEgMTAtbnVtYmVyIGJsb2NrLiBNb3JlIGdl
bmVyYWxseSB0aGUgdGVsZXBob25lIG51bWJlcnMgd2hpY2ggYXJlIGRlc3RpbmF0aW9ucyBmb3Ig
dGhlIHZvdGUgY291bGQgYmUgYSBzZXQsIGRlZmluZWQgKGZvciBleGFtcGxlKSBieSBhIGxpc3Qu
IFtJIGRvbid0IGtub3cgd2hldGhlciBzaW1pbGFyIFRWIHByb2dyYW1tZXMgaW4gdGhlIFVTIHJl
Z2lzdGVyIHZvdGVzIGluIHRoZSBzYW1lIHdheS5dDQoNClRoZSBzdXJnZSBvZiBjYWxscyB0byB2
b3RpbmcgbnVtYmVycyB0eXBpY2FsbHkgbXVzdCBiZSBjb250cm9sbGVkLCBidXQgYXBwbGljYXRp
b24gb2YgKm11bHRpcGxlKiByYXRlLWJhc2VkIGNvbnRyb2xzIChmb3IgZXhhbXBsZSB3aXRoIGVx
dWFsIHJhdGVzKSB0byAqaW5kaXZpZHVhbCogbnVtYmVycyB3aXRoaW4gdGhlIHZvdGluZyByYW5n
ZSAob25lIGNvbnRyb2wgcGVyIGRlc3RpbmF0aW9uIG51bWJlcikgd291bGQgdGVuZCB0byBzZXQg
dGhlIHBlci1udW1iZXIgcmF0ZXMgb2YgY2FsbHMgcmVjZWl2ZWQgYXQgdGhlIHZvdGUtcmVjb3Jk
aW5nIGVxdWlwbWVudCB0byB0aGUgY29udHJvbGxlZCByYXRlcy4gVGhpcyB3b3VsZCBjbGVhcmx5
IGJlIHVuYWNjZXB0YWJsZSBiZWNhdXNlIHRoZSByYXRpb3Mgb2YgcG9wdWxhciB2b3RlcyBmb3Ig
ZWFjaCBjb21wZXRpdG9yIGFyZSBpbXBvcnRhbnQgZm9yIHRoZSBUViBwcm9ncmFtbWUncyBhcHBs
aWNhdGlvbi4gU28gYSBjb250cm9sIGF0IGEgbmV0d29yayBub2RlLCBpZiBhcHBsaWVkLCBzaG91
bGQgYmUgYSAqc2luZ2xlKiBjb250cm9sIHdoaWNoIHRyZWF0cyBjYWxscyB0byB0aGUgc2V0IG9m
IHZvdGluZyBkZXN0aW5hdGlvbiBudW1iZXJzICpqb2ludGx5Kiwgc3VjaCB0aGF0IHRoZSBwcm9i
YWJpbGl0eSBvZiByZWplY3RpbmcgYSBjYWxsIGF0IHRoZSBjb250cm9sIGlzIGluZGVwZW5kZW50
IG9mIHRoZSBjYWxsJ3MgZGVzdGluYXRpb24gbnVtYmVyIHdpdGhpbiB0aGUgY29udHJvbGxlZCBz
ZXQgb2YgbnVtYmVycyAtIHRodXMgdm90aW5nIHJhdGlvcyBhcmUgcHJlc2VydmVkIGluIHRoZSBz
dHJlYW0gb2YgY2FsbHMgYWRtaXR0ZWQgYnkgdGhlIGNvbnRyb2wuDQoNCkluIG90aGVyIGNpcmN1
bXN0YW5jZXMgdGhlICppbnRlbnRpb24qIG1pZ2h0IGluc3RlYWQgYmUgdG8gYXBwbHkgbXVsdGlw
bGUgcmF0ZS1iYXNlZCBjb250cm9scywgb25lIHRvIGVhY2ggZGVzdGluYXRpb24gaW4gYSBsaXN0
Lg0KDQpNeSBjb21tZW50IHdhcyBpbnRlbmRlZCB0byBhc2sgd2hldGhlciB5b3VyIHN5bnRhY3Rp
Y2FsIHNjaGVtZSBtZWV0cyBib3RoIHRoZXNlIHJlcXVpcmVtZW50cw0KDQooYSkgYSByZXF1aXJl
bWVudCB0byBhcHBseSBhIHNpbmdsZSBqb2ludCBjb250cm9sIHRvIHRyYWZmaWMgdG93YXJkcyBh
IHNldCBvZiBkZXN0aW5hdGlvbiBudW1iZXJzLCBleHByZXNzZWQgZWl0aGVyIGFzIGEgbGlzdCBv
ZiBudW1iZXJzIG9yIGEgbGlzdCBvZiAidXNlckBob3N0IiBhZGRyZXNzZXMsIG9yIGFzIGEgbGVh
ZGluZyBzdWJzdHJpbmcgb2YgYSB0ZWxlcGhvbmUgbnVtYmVyIChmb3IgZXhhbXBsZSwgbGlzdHMg
aW4gMTAtbnVtYmVyIGJsb2NrcykNCg0KYW5kDQoNCihiKSBhIHJlcXVpcmVtZW50IHRvIGFwcGx5
IHNldmVyYWwgaW5kaXZpZHVhbCBjb250cm9scywgZWFjaCBjb250cm9sbGluZyB0cmFmZmljIHRv
d2FyZHMgb25lIG1lbWJlciBvZiBhIHNldCBvZiBudW1iZXJzLCBleHByZXNzZWQgZWl0aGVyIGFz
IGEgbGlzdCBvZiBudW1iZXJzIG9yIGEgbGlzdCBvZiAidXNlckBob3N0IiBhZGRyZXNzZXMsIG9y
IChwb3NzaWJseSBsZXNzIGxpa2VseSBpbiB0aGlzIGNhc2UpIGFzIGEgbGVhZGluZyBzdWJzdHJp
bmcgb2YgYSB0ZWxlcGhvbmUgbnVtYmVyIChmb3IgZXhhbXBsZSwgbGlzdHMgaW4gMTAtbnVtYmVy
IGJsb2NrcykuIFtPZiBjb3Vyc2UgaXQgd291bGQgYmUgYWNjZXB0YWJsZSB0byBtZWV0IHRoaXMg
cmVxdWlyZW1lbnQgd2l0aCBtdWx0aXBsZSA8Y2FsbC1pZGVudGl0eT4gZWxlbWVudHNdDQoNCkJl
c3QgcmVnYXJkcw0KR2VvZmYNCg0KR2VvZmYgSHVudA0KQlQgRGVzaWduDQoNClRlbDogMDE0NzMg
NjUxNzA0DQpFbWFpbDogZ2VvZmYuaHVudEBidC5jb20NCldlYjogd3d3LmJ0LmNvbSANClRoaXMg
ZW1haWwgY29udGFpbnMgQlQgaW5mb3JtYXRpb24sIHdoaWNoIG1heSBiZSBwcml2aWxlZ2VkIG9y
IGNvbmZpZGVudGlhbC4NCkl0IGlzIG1lYW50IG9ubHkgZm9yIHRoZSBpbmRpdmlkdWFsKHMpIG9y
IGVudGl0eSBuYW1lZCBhYm92ZS4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkDQpyZWNpcGll
bnQsIG5vdGUgdGhhdCBkaXNjbG9zaW5nLCBjb3B5aW5nLCBkaXN0cmlidXRpbmcgb3IgdXNpbmcg
dGhpcyBpbmZvcm1hdGlvbg0KaXMgcHJvaGliaXRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhp
cyBlbWFpbCBpbiBlcnJvciwgcGxlYXNlIGxldCBtZSBrbm93IGltbWVkaWF0ZWx5DQpvbiB0aGUg
ZW1haWwgYWRkcmVzcyBhYm92ZS4gVGhhbmsgeW91Lg0KV2UgbW9uaXRvciBvdXIgZW1haWwgc3lz
dGVtLCBhbmQgbWF5IHJlY29yZCB5b3VyIGVtYWlscy4gDQpCcml0aXNoIFRlbGVjb21tdW5pY2F0
aW9ucyBwbGMNClJlZ2lzdGVyZWQgb2ZmaWNlOiA4MSBOZXdnYXRlIFN0cmVldCBMb25kb24gRUMx
QSA3QUoNClJlZ2lzdGVyZWQgaW4gRW5nbGFuZCBubzogMTgwMDAwMCANCg0KPi0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogY2hhcmxlcy5uZXd5b3JrQGdtYWlsLmNvbSBbbWFpbHRv
OmNoYXJsZXMubmV3eW9ya0BnbWFpbC5jb21dIE9uDQo+QmVoYWxmIE9mIENoYXJsZXMgU2hlbg0K
PlNlbnQ6IDA0IEZlYnJ1YXJ5IDIwMTAgMjA6MzMNCj5UbzogSHVudCxSRyxHZW9mZixETFcgUg0K
PkNjOiBzaXAtb3ZlcmxvYWRAaWV0Zi5vcmc7IEhlbm5pbmcgU2NodWx6cmlubmUNCj5TdWJqZWN0
OiBSZTogW3NpcC1vdmVybG9hZF0gQ29tbWVudHMgb24gZHJhZnQtc2hlbi1zaXBwaW5nLWxvYWQt
Y29udHJvbC0NCj5ldmVudC1wYWNrYWdlLTAzDQo+DQo+SGkgR2VvZmY6IHRoYW5rcyBmb3IgdGhl
IHJldmlldywgc29ycnkgZm9yIHRoZSBsYXRlIHJlc3BvbnNlLiBwbGVhc2UNCj5zZWUgaW5saW5l
Lg0KPg0KPj4gT24gVHVlLCBEZWMgMTUsIDIwMDkgYXQgMTA6NTcgQU0sICA8Z2VvZmYuaHVudEBi
dC5jb20+IHdyb3RlOg0KPj4gSGkgQ2hhcmxlcywgQWxsLA0KPj4NCj4+IEhlcmUgYXJlIHNvbWUg
Y29tbWVudHMgb24gdGhlIGRyYWZ0Og0KPj4NCj4+IDEpIFNlY3Rpb24gMSwgcGFyYSAxLCB0eXBv
ICJzZXZlciINCj4NCj53aWxsIGNvcnJlY3QNCj4NCj4+DQo+PiAyKSBTZWN0aW9uIDQuMSBDYXNl
IDEgdGV4dCAiIENQYTEgdGhlbiBhbGxvY2F0ZXMgdGhlIHJlY2VpdmVkIHRvdGFsDQo+PiBhY2Nl
cHRhYmxlIHJhdGUgYW1vbmcgaXRzIG5laWdoYm9ycyIuIFdoaWxzdCBDUGExIHNob3VsZCBub3Qg
c2VuZCBtb3JlDQo+PiB0aGFuIHRoZSByZXF1ZXN0ZWQgcmF0ZSB0byBFUGExLCBpdCBpcyBwcm9i
YWJseSBub3Qgc2Vuc2libGUgdG8NCj4+ICJhbGxvY2F0ZSIgdGhlIHRvdGFsIGFjY2VwdGFibGUg
cmF0ZSBhbW9uZyBpdHMgdXBzdHJlYW0gbmVpZ2hib3VycywNCj4+IGJlY2F1c2UgdGhpcyB3aWxs
IChhbG1vc3QpIGd1YXJhbnRlZSBpdCB3aWxsIHNlbmQgbGVzcyB0aGFuIHRoZQ0KPj4gcmVxdWVz
dGVkIHJhdGUgdG8gRVBhMSwgYmVjYXVzZSBpdCBpcyB2ZXJ5IGxpa2VseSB0aGF0IHNvbWUgc291
cmNlcw0KPndpbGwNCj4+IG5vdCBvZmZlciB0aGUgcmF0ZSB0aGV5IGFyZSBwZXJtaXR0ZWQgdG8g
c2VuZC4gQ1BhMSBtaWdodCBkaXZpZGUgdXANCj5zb21lDQo+PiBudW1iZXIgbGFyZ2VyIHRoYW4g
dGhlIHRvdGFsIGFjY2VwdGFibGUgcmF0ZSwgdG8gZ3VhcmFudGVlIHRoYXQgaXQgaXMNCj4+IGFi
bGUgc2VuZCB0aGUgcmVxdWVzdGVkIHRvdGFsIGFjY2VwdGFibGUgcmF0ZSB0byBFUGExLiBPdGhl
cndpc2UNCj4+IGN1c3RvbWVyIHNlcnZpY2Ugd2lsbCBiZSB3b3JzZSB0aGFuIG5lY2Vzc2FyeSAo
bW9yZSBjYWxscyB0aGFuDQo+bmVjZXNzYXJ5DQo+PiB3aWxsIGJlIHJlamVjdGVkKSBhbmQgdG90
YWwgbmV0d29yayBsb2FkIHdpbGwgYmUgZXhhZ2dlcmF0ZWQgYnkNCj4+IHVubmVjZXNzYXJ5IHJl
cGVhdCBhdHRlbXB0IGJlaGF2aW91ci4NCj4+DQo+PiAzKSBTZWN0aW9uIDUuNyBwYXJhIDIgdGV4
dCAiIHRoZW4gdGhlIHRvdGFsIHJhdGUgbGltaXQgZm9yIHRoZQ0KPnNwZWNpZmljDQo+PiBkb3du
c3RyZWFtIFNJUCBlbnRpdHkgaW4gdGhlIHRocmVlIE5PVElGWSBtZXNzYWdlcyBzZW50IHRvIHRo
b3NlIHRocmVlDQo+PiB1cHN0cmVhbSBuZWlnaGJvcnMgbXVzdCBub3QgZXhjZWVkIMKgMTAwIHJl
cXVlc3RzIHBlciBzZWNvbmQuIiBUaGlzIGlzDQo+YQ0KPj4gc2ltaWxhciBjb21tZW50IHRvIHRo
ZSBjb21tZW50IGFib3ZlIGFib3V0IHNlY3Rpb24gNC4xLiBJdCB3b3VsZCBiZQ0KPj4gYmV0dGVy
IHRvIGNvbW11bmljYXRlIHBlcm1pdHRlZCByYXRlcyB3aGljaCAqZG8qIGV4Y2VlZCAxMDAgaW4g
dG90YWwNCj50bw0KPj4gdXBzdHJlYW0gbmVpZ2hib3VycywgYW5kIGV4cGxpY2l0bHkgdG8gbGlt
aXQgZG93bnN0cmVhbSB0cmFmZmljIHRvIDEwMA0KPj4gYXQgdGhlIGxvY2FsIHNlcnZlci4gT3Ro
ZXJ3aXNlIHRoZSBuZXR3b3JrIHdpbGwgYWxtb3N0IGNlcnRhaW5seSBiZQ0KPj4gdW5kZXItdXRp
bGlzZWQsIHdoaWNoIGlzIGRhbWFnaW5nIHRvIGN1c3RvbWVyIHNlcnZpY2UuDQo+DQo+VGhlIHBv
aW50IG9mIHBvc3NpYmxlIHVuZGVyLXV0aWxpemF0aW9uIHdpdGggdGhlIHNpbXBsaWZpZWQgZXhh
bXBsZSBpcw0KPnJlY29nbml6ZWQuIFNpbmNlIGl0IGlzIGRpZmZpY3VsdCB0byBnaXZlIGFueSBz
cGVjaWZpYyAocmlnaHQpIHZhbHVlDQo+b2Ygb3Zlci1jb21taXRtZW50IGVpdGhlciwgYW5kIHRo
ZSB2YWx1ZSBjb21wdXRhdGlvbiBtZWNoYW5pc20gaXRzZWxmDQo+aXMgY29uc2lkZXJlZCBvdXQt
b2Ytc2NvcGUgb2YgdGhlIGV2ZW50IHBhY2thZ2UsIHRoZSBuZXh0IHVwZGF0ZSB3aWxsDQo+Y2xh
cmlmeSB0aGlzLg0KPg0KPj4gNCkgU2VjdGlvbiA1LjggcGFyYSAzLiB0eXBvICJwcmV2aW91bHN5
Ig0KPg0KPndpbGwgY29ycmVjdC4NCj4NCj4+DQo+PiA1KSBTZWN0aW9uIDYuMy4xIHBhcmEgMiBs
YXN0IHNlbnRlbmNlLCB0ZXh0ICJyZXN1bHQgaXMgY29tYmluZWQgdXNpbmcNCj4+IGxvZ2ljYWwg
T1IiLiBKdXN0IHRvIGNsYXJpZnk6IGRvZXMgdGhpcyBpbnRlcnByZXRhdGlvbiBhbGxvdyBqb2lu
dA0KPj4gY29udHJvbCBvZiB0cmFmZmljIHRvIGEgbGlzdCBvZiBkZXN0aW5hdGlvbnMgKHN1Y2gg
YXMgYSB0ZWxldm90aW5nDQo+PiBkZXN0aW5hdGlvbiByYW5nZSkgc3VjaCB0aGF0IGNvbnRyb2wg
ZG9lcyBub3QgaGF2ZSB0aGUgZWZmZWN0IG9mDQo+PiBlcXVhbGlzaW5nIHRyYWZmaWMgdG8gdGhl
IGluZGl2aWR1YWwgZGVzdGluYXRpb25zPw0KPg0KPk5vdCBzdXJlIHdoZXRoZXIgSSB1bmRlcnN0
YW5kLiBDb3VsZCB5b3UgcGxlYXNlIGVsYWJvcmF0ZSBhIGJpdCBhYm91dA0KPnRoZSBzY2VuYXJp
byB5b3UgYXJlIHJlZmVycmluZyB0bz8NCj4NCj4+DQo+PiA2KSBTZWN0aW9uIDYuNCBwYXJhIDEs
IHRleHQgIiB0YWtlcyBhbnkgb25lIG9mIHRoZSB0aHJlZSBzdWItZWxlbWVudHMNCj4+IDxyYXRl
PiwgPHBlcmNlbnQ+LCBhbmQgPHdpbj4iIEl0J3MgdmVyeSBoYXJkIHRvIHNlZSBob3cgZWl0aGVy
DQo+PHBlcmNlbnQ+DQo+PiBvciA8d2luPiBjb3VsZCBtYWtlIGFueSBzZW5zZSBmb3IgYSBzdGF0
aWNhbGx5LWNvbmZpZ3VyZWQgZmlsdGVyaW5nDQo+dHlwZQ0KPj4gb2YgY29udHJvbCwgZ2l2ZW4g
dGhlIHVuY2VydGFpbnR5IGluIG9mZmVyZWQgdHJhZmZpYyBsZXZlbCBhbmQgaW4NCj4+IGRvd25z
dHJlYW0gc2VydmVyIHJlc3BvbnNpdmVuZXNzLg0KPj4NCj4NCj5JbmRlZWQgYXQgdGhpcyBzdGFn
ZSBpdCBtYXkgYmUgdGhlIHNhZmVzdCB0byB1c2UgdGhlIDxyYXRlPiBzdWItZWxlbWVudC4NCj4N
Cj4+IDcpIFNlY3Rpb24gNi40IHBhcmEgMiwgdGV4dCAiVGhlIGRlZmF1bHQgdmFsdWUgaXMgIkRy
b3AiIC4gwqAiIFdpbGwNCj4+ICJkcm9wIiBsZWFkIHRvIHJldHJhbnNtaXNzaW9uIGJ5IHVwc3Ry
ZWFtIGVsZW1lbnRzLCBpbiBuZXR3b3JrcyB1c2luZw0KPj4gdW5yZWxpYWJsZSB0cmFuc3BvcnQ/
IElmIHNvIHRoaXMgc2VlbXMgdW5kZXNpcmFibGUsIGJ5IGluY3JlYXNpbmcgbG9hZA0KPj4gb24g
dGhlIGxvY2FsIGRldmljZS4gQWxzbyA1MDMgd2lsbCBhbGxvdyB1cHN0cmVhbSBlbGVtZW50cyB0
byByZS10cnkNCj4+IGVsc2V3aGVyZSB3aGljaCBzZWVtcyBwb2ludGxlc3Mgb3IgZGFtYWdpbmcg
aW4gdGhpcyB0eXBlIG9mIGNvbnRyb2wgLQ0KPj4gd291bGQgaXQgYmUgYmV0dGVyIHRvIHJlcXVp
cmUgc2VuZGluZyA1MDA/DQo+Pg0KPg0KPlRoaXMgbWFrZXMgc2Vuc2UuIChhbHRob3VnaCBzZW5k
aW5nIHJlamVjdGlvbiBjb3N0cyBub24tbmVnbGlnaWJsZQ0KPmFkZGl0aW9uYWwgY3ljbGVzIHRv
bykNCj4NCj4+IEhvcGUgdGhpcyBoZWxwcw0KPg0KPlllcywgdGhhbmtzIQ0KPg0KPkNoYXJsZXMN
Cj4NCj4NCj4+DQo+PiBHZW9mZg0KPj4NCj4+IEdlb2ZmIEh1bnQNCj4+IEJUIERlc2lnbg0KPj4N
Cj4+IFRlbDogMDE0NzMgNjUxNzA0DQo+PiBFbWFpbDogZ2VvZmYuaHVudEBidC5jb20NCj4+IFdl
Yjogd3d3LmJ0LmNvbQ0KPj4gVGhpcyBlbWFpbCBjb250YWlucyBCVCBpbmZvcm1hdGlvbiwgd2hp
Y2ggbWF5IGJlIHByaXZpbGVnZWQgb3INCj4+IGNvbmZpZGVudGlhbC4NCj4+IEl0IGlzIG1lYW50
IG9ubHkgZm9yIHRoZSBpbmRpdmlkdWFsKHMpIG9yIGVudGl0eSBuYW1lZCBhYm92ZS4gSWYgeW91
DQo+YXJlDQo+PiBub3QgdGhlIGludGVuZGVkDQo+PiByZWNpcGllbnQsIG5vdGUgdGhhdCBkaXNj
bG9zaW5nLCBjb3B5aW5nLCBkaXN0cmlidXRpbmcgb3IgdXNpbmcgdGhpcw0KPj4gaW5mb3JtYXRp
b24NCj4+IGlzIHByb2hpYml0ZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgZW1haWwgaW4g
ZXJyb3IsIHBsZWFzZSBsZXQgbWUNCj4+IGtub3cgaW1tZWRpYXRlbHkNCj4+IG9uIHRoZSBlbWFp
bCBhZGRyZXNzIGFib3ZlLiBUaGFuayB5b3UuDQo+PiBXZSBtb25pdG9yIG91ciBlbWFpbCBzeXN0
ZW0sIGFuZCBtYXkgcmVjb3JkIHlvdXIgZW1haWxzLg0KPj4gQnJpdGlzaCBUZWxlY29tbXVuaWNh
dGlvbnMgcGxjDQo+PiBSZWdpc3RlcmVkIG9mZmljZTogODEgTmV3Z2F0ZSBTdHJlZXQgTG9uZG9u
IEVDMUEgN0FKDQo+PiBSZWdpc3RlcmVkIGluIEVuZ2xhbmQgbm86IDE4MDAwMDANCj4+DQo+Pg0K
Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+IHNp
cC1vdmVybG9hZCBtYWlsaW5nIGxpc3QNCj4+IHNpcC1vdmVybG9hZEBpZXRmLm9yZw0KPj4gaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXAtb3ZlcmxvYWQNCj4+DQo=

From partr@cisco.com  Sun Feb  7 20:01:16 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 702BD3A6FEF for <sip-overload@core3.amsl.com>; Sun,  7 Feb 2010 20:01:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.202
X-Spam-Level: 
X-Spam-Status: No, score=-9.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, 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 k45J7isDTaXl for <sip-overload@core3.amsl.com>; Sun,  7 Feb 2010 20:01:14 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id DCC613A67FF for <sip-overload@ietf.org>; Sun,  7 Feb 2010 20:01:14 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwEAA0cb0tAaHte/2dsb2JhbACaMKU1lkuEVASDEIsL
X-IronPort-AV: E=Sophos;i="4.49,425,1262563200"; d="scan'208,217";a="84865990"
Received: from hkg-core-1.cisco.com ([64.104.123.94]) by sj-iport-4.cisco.com with ESMTP; 08 Feb 2010 04:02:10 +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 o18429Qf011875; Mon, 8 Feb 2010 04:02:10 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, 8 Feb 2010 09:32:09 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAA873.7BFE3D4E"
Date: Mon, 8 Feb 2010 09:32:08 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A6239021FB7@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] Fwd: draft-shen-sipping-avalanche-restart-overload-00
Thread-Index: Acql3IWxW8H4wU7PSBKwknjzj1oxoQClYvD+
References: <e7df28360911230708v50c72a48o7dc9c22a8731146a@mail.gmail.com><e7df28360912030631i53e600cdwddfc5feecaa6ec65@mail.gmail.com><A11921905DA1564D9BCF64A6430A6239021FAC@XMB-BGL-411.cisco.com> <e7df28361002041256v35f7d4e1we0b61629d71e9174@mail.gmail.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Charles Shen" <charles@cs.columbia.edu>
X-OriginalArrivalTime: 08 Feb 2010 04:02:09.0316 (UTC) FILETIME=[7C462E40:01CAA873]
Cc: sip-overload@ietf.org, Arata Koike <koike.arata@lab.ntt.co.jp>, Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [sip-overload] Fwd: draft-shen-sipping-avalanche-restart-overload-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, 08 Feb 2010 04:01:16 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CAA873.7BFE3D4E
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Shen,
=20
In case of zero configuration entity (SIP UA), DHCP discovery mechanism =
is used to discover the configuration server. The configuration server =
may use SIP or non-SIP mechanism. In these deployment, Entity will not =
have any configuration information within itself. I mentioned this =
caveat as most of these entities will not have mechanism to upload the =
configuration to configuration server which means that these entities =
only download the configuration from config server. I may be looking =
from one of the deployment scenario, Let others comments whether this =
deployment has to be considered.
=20
Thanks
Partha

________________________________

From: charles.newyork@gmail.com on behalf of Charles Shen
Sent: Fri 2/5/2010 2:26 AM
To: Parthasarathi R (partr)
Cc: sip-overload@ietf.org; Arata Koike; Henning Schulzrinne
Subject: Re: [sip-overload] Fwd: =
draft-shen-sipping-avalanche-restart-overload-00



Hi Partha: thanks for the comments, please see inline.

On Mon, Feb 1, 2010 at 9:57 PM, Parthasarathi R (partr) =
<partr@cisco.com> wrote:
> Hi Charles,
>
> The draft looks good. I have few comments:
>
> 1) The proposed mechanism assumes that UA have the capability to store =
the
> configuration in memory. This may not be appropriate in case of UA =
with zero
> SIP configuration and configuration is downloaded from config server. =
In
> case default register restart timer (say 5 or 10 sec) is mentioned in =
UA
> configuration, this problem may be solved.

But shouldn't the UA normally have some flash memory (e.g., storing
the initial server to contact after boot-up)? In that case, couldn't
the timer information be stored in those flash memory as well?

> 2) Sec 4.3 assumes that Register will be the first message by UA. In =
case
> SIP based configuration mechanism is followed, SUBSCRIBE will be send =
by UA
> to SIP configuration server to get Registrar address and other SIP =
related
> configuration and REGISTER message follows next. In this scenario, =
SUBSCRIBE
> should have restart-timer rather than REGISTER.

This is a very good point. We might then think of revising the name of
the new header from  REGISTER-RESTART to RESTART-TIMER instead to make
it more generic.

Thanks!

Charles

>
> Thanks
> Partha
> ________________________________
> From: sip-overload-bounces@ietf.org on behalf of Charles Shen
> Sent: Thu 12/3/2009 8:01 PM
> To: sip-overload@ietf.org
> Cc: Arata Koike; Henning Schulzrinne
> Subject: [sip-overload] Fwd:
> draft-shen-sipping-avalanche-restart-overload-00
>
> Hi all, we've submitted the following draft, comments appreciated.
>
> A Mechanism for Session Initiation Protocol (SIP) Avalanche Restart
> Overload Control
>
> =
http://tools.ietf.org/html/draft-shen-sipping-avalanche-restart-overload-=
00
>
> Abstract
>
>   When a large number of clients register with a SIP registrar server
>   at approximately the same time, the server may become overloaded.
>   Near-simultaneous floods of SIP SUBSCRIBE and PUBLISH requests may
>   have similar effects.  Such request avalanches can occur, for
>   example, after a power failure and recovery in a metropolitan area.
>   This document describes how to avoid such overload situations.  =
Under
>   this mechanism, a server estimates an avalanche restart backoff
>   interval during its normal operation and conveys this interval to =
its
>   clients through a new Register-Restart header in registration
>   responses.  Once an avalanche restart actually occurs, the clients
>   perform backoff based on the previously received Register-Restart
>   header value before sending out the first registration attempt.
>   Thus, the mechanism spreads all the initial client registration
>   requests and prevents them from overloading the registrar server.
>
>
> Thanks
>
> Charles
> _______________________________________________
> 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
>
>



------_=_NextPart_001_01CAA873.7BFE3D4E
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Re: [sip-overload] Fwd: =
draft-shen-sipping-avalanche-restart-overload-00</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18876"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText32281>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3DArial>Hi =
Shen,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>In case of zero configuration =
entity (SIP UA), DHCP discovery mechanism&nbsp;is used to discover the =
configuration server. The configuration server may&nbsp;use SIP or =
non-SIP mechanism. In these deployment, Entity will not have any =
configuration information within itself. I mentioned this caveat as most =
of these entities will not have mechanism to upload the configuration to =
configuration server which means that these entities only download the =
configuration from config server. I may be looking from one of the =
deployment scenario, Let others comments whether this deployment has to =
be considered.</FONT></DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Thanks</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Partha</FONT><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> charles.newyork@gmail.com on =
behalf of Charles Shen<BR><B>Sent:</B> Fri 2/5/2010 2:26 =
AM<BR><B>To:</B> Parthasarathi R (partr)<BR><B>Cc:</B> =
sip-overload@ietf.org; Arata Koike; Henning =
Schulzrinne<BR><B>Subject:</B> Re: [sip-overload] Fwd: =
draft-shen-sipping-avalanche-restart-overload-00<BR></FONT><BR></DIV></DI=
V>=0A=
<DIV>=0A=
<P><FONT size=3D2>Hi Partha: thanks for the comments, please see =
inline.<BR><BR>On Mon, Feb 1, 2010 at 9:57 PM, Parthasarathi R (partr) =
&lt;partr@cisco.com&gt; wrote:<BR>&gt; Hi Charles,<BR>&gt;<BR>&gt; The =
draft looks good. I have few comments:<BR>&gt;<BR>&gt; 1) The proposed =
mechanism assumes that UA have the capability to store the<BR>&gt; =
configuration in memory. This may not be appropriate in case of UA with =
zero<BR>&gt; SIP configuration and configuration is downloaded from =
config server. In<BR>&gt; case default register restart timer (say 5 or =
10 sec) is mentioned in UA<BR>&gt; configuration, this problem may be =
solved.<BR><BR>But shouldn't the UA normally have some flash memory =
(e.g., storing<BR>the initial server to contact after boot-up)? In that =
case, couldn't<BR>the timer information be stored in those flash memory =
as well?<BR><BR>&gt; 2)&nbsp;Sec 4.3&nbsp;assumes that Register will be =
the first message by UA. In case<BR>&gt; SIP based configuration =
mechanism is followed, SUBSCRIBE will be send by UA<BR>&gt; to SIP =
configuration server to get Registrar address and other SIP =
related<BR>&gt; configuration and REGISTER message follows next. In this =
scenario, SUBSCRIBE<BR>&gt; should have restart-timer rather than =
REGISTER.<BR><BR>This is a very good point. We might then think of =
revising the name of<BR>the new header from&nbsp; REGISTER-RESTART to =
RESTART-TIMER instead to make<BR>it more =
generic.<BR><BR>Thanks!<BR><BR>Charles<BR><BR>&gt;<BR>&gt; =
Thanks<BR>&gt; Partha<BR>&gt; ________________________________<BR>&gt; =
From: sip-overload-bounces@ietf.org on behalf of Charles Shen<BR>&gt; =
Sent: Thu 12/3/2009 8:01 PM<BR>&gt; To: sip-overload@ietf.org<BR>&gt; =
Cc: Arata Koike; Henning Schulzrinne<BR>&gt; Subject: [sip-overload] =
Fwd:<BR>&gt; =
draft-shen-sipping-avalanche-restart-overload-00<BR>&gt;<BR>&gt; Hi all, =
we've submitted the following draft, comments =
appreciated.<BR>&gt;<BR>&gt; A Mechanism for Session Initiation Protocol =
(SIP) Avalanche Restart<BR>&gt; Overload Control<BR>&gt;<BR>&gt; <A =
href=3D"http://tools.ietf.org/html/draft-shen-sipping-avalanche-restart-o=
verload-00">http://tools.ietf.org/html/draft-shen-sipping-avalanche-resta=
rt-overload-00</A><BR>&gt;<BR>&gt; Abstract<BR>&gt;<BR>&gt; &nbsp; When =
a large number of clients register with a SIP registrar server<BR>&gt; =
&nbsp; at approximately the same time, the server may become =
overloaded.<BR>&gt; &nbsp; Near-simultaneous floods of SIP SUBSCRIBE and =
PUBLISH requests may<BR>&gt; &nbsp; have similar effects. &nbsp;Such =
request avalanches can occur, for<BR>&gt; &nbsp; example, after a power =
failure and recovery in a metropolitan area.<BR>&gt; &nbsp; This =
document describes how to avoid such overload situations. =
&nbsp;Under<BR>&gt; &nbsp; this mechanism, a server estimates an =
avalanche restart backoff<BR>&gt; &nbsp; interval during its normal =
operation and conveys this interval to its<BR>&gt; &nbsp; clients =
through a new Register-Restart header in registration<BR>&gt; &nbsp; =
responses. &nbsp;Once an avalanche restart actually occurs, the =
clients<BR>&gt; &nbsp; perform backoff based on the previously received =
Register-Restart<BR>&gt; &nbsp; header value before sending out the =
first registration attempt.<BR>&gt; &nbsp; Thus, the mechanism spreads =
all the initial client registration<BR>&gt; &nbsp; requests and prevents =
them from overloading the registrar server.<BR>&gt;<BR>&gt;<BR>&gt; =
Thanks<BR>&gt;<BR>&gt; Charles<BR>&gt; =
_______________________________________________<BR>&gt; sip-overload =
mailing list<BR>&gt; sip-overload@ietf.org<BR>&gt; <A =
href=3D"https://www.ietf.org/mailman/listinfo/sip-overload">https://www.i=
etf.org/mailman/listinfo/sip-overload</A><BR>&gt;<BR>&gt; =
_______________________________________________<BR>&gt; sip-overload =
mailing list<BR>&gt; sip-overload@ietf.org<BR>&gt; <A =
href=3D"https://www.ietf.org/mailman/listinfo/sip-overload">https://www.i=
etf.org/mailman/listinfo/sip-overload</A><BR>&gt;<BR>&gt;<BR></FONT></P><=
/DIV></BODY></HTML>
------_=_NextPart_001_01CAA873.7BFE3D4E--

From charles.newyork@gmail.com  Tue Feb  9 18:36:21 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 1147B28C1B8 for <sip-overload@core3.amsl.com>; Tue,  9 Feb 2010 18:36:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.035
X-Spam-Level: 
X-Spam-Status: No, score=-1.035 tagged_above=-999 required=5 tests=[AWL=-0.258, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_21=0.6, J_CHICKENPOX_42=0.6]
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 DaUUzELx6IOF for <sip-overload@core3.amsl.com>; Tue,  9 Feb 2010 18:36:19 -0800 (PST)
Received: from mail-pz0-f190.google.com (mail-pz0-f190.google.com [209.85.222.190]) by core3.amsl.com (Postfix) with ESMTP id BC3983A74F6 for <sip-overload@ietf.org>; Tue,  9 Feb 2010 18:36:19 -0800 (PST)
Received: by pzk28 with SMTP id 28so1059757pzk.31 for <sip-overload@ietf.org>; Tue, 09 Feb 2010 18:37:25 -0800 (PST)
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:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=LBXXbNfFFZ2eKDeW6IcRaeP+tarjNswYAb8LrPq0POc=; b=JeZuNgs4ItvgHTbAGI54g4Rt4LZPBywYsAVcWsThIb0r5556BgR9Z5okfm3E6wxAdl dPrLAO5tM+bcOpmSnieqyPfZVqB+C5lHZ+WbmnJBL/I19UrJ/Y07LuJrm3TTzJwtpDD9 FsPujgly9ebGKjoyevj8SYyTAxNreJaiEaNtU=
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 :content-transfer-encoding; b=SwIP3Tm6a19PGDVFGgTVkA2e9dTOas9uS+Vt9DLi3NMrUliMPqb7Ks1w3Hp+p/xKeH /wbgDDh84VSROOHMArBQkiBDRB6AJ7fsTUmvXPj4u3+MXmR8vH3wBzJraja0i8K9mD2W v2e23xR/IMBXClgXSUj/lkIe0etVp/pJr9JhQ=
MIME-Version: 1.0
Sender: charles.newyork@gmail.com
Received: by 10.142.120.26 with SMTP id s26mr3278877wfc.157.1265769445236;  Tue, 09 Feb 2010 18:37:25 -0800 (PST)
In-Reply-To: <B71E03B6EDEAA9438A12F0D64BC08C7909747B09@E03MVY2-UKDY.domain1.systemhost.net>
References: <B71E03B6EDEAA9438A12F0D64BC08C790936EE88@E03MVY2-UKDY.domain1.systemhost.net> <e7df28361002041232x6c108913j931df954b8f610de@mail.gmail.com> <B71E03B6EDEAA9438A12F0D64BC08C7909747B09@E03MVY2-UKDY.domain1.systemhost.net>
Date: Tue, 9 Feb 2010 21:37:25 -0500
X-Google-Sender-Auth: bcb5928f68b55fdb
Message-ID: <e7df28361002091837n148835f6y99789e37b186db9@mail.gmail.com>
From: Charles Shen <charles@cs.columbia.edu>
To: geoff.hunt@bt.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: sip-overload@ietf.org, hgs@cs.columbia.edu
Subject: Re: [sip-overload] Comments on draft-shen-sipping-load-control-event-package-03
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, 10 Feb 2010 02:36:21 -0000

Hi Geoff, thanks for the detailed and interesting description. Please see i=
nline

On Fri, Feb 5, 2010 at 6:08 AM,  <geoff.hunt@bt.com> wrote:
> Hi Charles, All,
>
> Responding to Charles' request for clarification of the scenario behind m=
y comment about section 6.3.1 para 2 of the draft.
>
> In the UK, some television companies put on "talent competitions" raising=
 money from large numbers of telephone calls made by the audience to premiu=
m rate lines, to register popular votes for the competitors. I believe you'=
ve had similar TV programmes in the US, such as "American Idol". In the UK,=
 these competitions give rise to some of the largest calling rates seen on =
the UK telephone network, and on SIP networks which interconnect with it, a=
lthough the voting period is typically quite short (maybe a few tens of min=
utes). So control of this type of event is a likely application of your pac=
kage. In the UK, votes for different competitors are registered by dialling=
 different telephone numbers, usually in a compact range such as a 10-numbe=
r block. More generally the telephone numbers which are destinations for th=
e vote could be a set, defined (for example) by a list. [I don't know wheth=
er similar TV programmes in the US register votes in the same way.]
>
> The surge of calls to voting numbers typically must be controlled, but ap=
plication of *multiple* rate-based controls (for example with equal rates) =
to *individual* numbers within the voting range (one control per destinatio=
n number) would tend to set the per-number rates of calls received at the v=
ote-recording equipment to the controlled rates. This would clearly be unac=
ceptable because the ratios of popular votes for each competitor are import=
ant for the TV programme's application. So a control at a network node, if =
applied, should be a *single* control which treats calls to the set of voti=
ng destination numbers *jointly*, such that the probability of rejecting a =
call at the control is independent of the call's destination number within =
the controlled set of numbers - thus voting ratios are preserved in the str=
eam of calls admitted by the control.
>
> In other circumstances the *intention* might instead be to apply multiple=
 rate-based controls, one to each destination in a list.
>
> My comment was intended to ask whether your syntactical scheme meets both=
 these requirements
>
> (a) a requirement to apply a single joint control to traffic towards a se=
t of destination numbers, expressed either as a list of numbers or a list o=
f "user@host" addresses, or as a leading substring of a telephone number (f=
or example, lists in 10-number blocks)
>

I think this is achieved by using a single <call-identity> and <to>
element, with multiple <one>  sub-elements containing the individual
destination numbers or "user@host" addresses, or with a <many>
sub-element containing the leading string (prefix) of a telephone
number. Since the individual destinations are interpreted as logical
"OR", the associated <action> will be applied to the whole pool of the
numbers in the <call-identity> element, and I think that satisfies
this requirement (a).


> and
>
> (b) a requirement to apply several individual controls, each controlling =
traffic towards one member of a set of numbers, expressed either as a list =
of numbers or a list of "user@host" addresses, or (possibly less likely in =
this case) as a leading substring of a telephone number (for example, lists=
 in 10-number blocks). [Of course it would be acceptable to meet this requi=
rement with multiple <call-identity> elements]

Yes, as you mentioned, the simplest method to satisfy requirement (b)
is to use multiple <call-identity>  elements, each associated with its
action (which may or may not be the same for all the numbers in the
<call-identity> element)

Thanks

Charles

>
> Best regards
> Geoff
>
> Geoff Hunt
> BT Design
>
> Tel: 01473 651704
> Email: geoff.hunt@bt.com
> Web: www.bt.com
> This email contains BT information, which may be privileged or confidenti=
al.
> It is meant only for the individual(s) or entity named above. If you are =
not the intended
> recipient, note that disclosing, copying, distributing or using this info=
rmation
> is prohibited. If you have received this email in error, please let me kn=
ow immediately
> on the email address above. Thank you.
> We monitor our email system, and may record your emails.
> British Telecommunications plc
> Registered office: 81 Newgate Street London EC1A 7AJ
> Registered in England no: 1800000
>
>>-----Original Message-----
>>From: charles.newyork@gmail.com [mailto:charles.newyork@gmail.com] On
>>Behalf Of Charles Shen
>>Sent: 04 February 2010 20:33
>>To: Hunt,RG,Geoff,DLW R
>>Cc: sip-overload@ietf.org; Henning Schulzrinne
>>Subject: Re: [sip-overload] Comments on draft-shen-sipping-load-control-
>>event-package-03
>>
>>Hi Geoff: thanks for the review, sorry for the late response. please
>>see inline.
>>
>>> On Tue, Dec 15, 2009 at 10:57 AM, =C2=A0<geoff.hunt@bt.com> wrote:
>>> Hi Charles, All,
>>>
>>> Here are some comments on the draft:
>>>
>>> 1) Section 1, para 1, typo "sever"
>>
>>will correct
>>
>>>
>>> 2) Section 4.1 Case 1 text " CPa1 then allocates the received total
>>> acceptable rate among its neighbors". Whilst CPa1 should not send more
>>> than the requested rate to EPa1, it is probably not sensible to
>>> "allocate" the total acceptable rate among its upstream neighbours,
>>> because this will (almost) guarantee it will send less than the
>>> requested rate to EPa1, because it is very likely that some sources
>>will
>>> not offer the rate they are permitted to send. CPa1 might divide up
>>some
>>> number larger than the total acceptable rate, to guarantee that it is
>>> able send the requested total acceptable rate to EPa1. Otherwise
>>> customer service will be worse than necessary (more calls than
>>necessary
>>> will be rejected) and total network load will be exaggerated by
>>> unnecessary repeat attempt behaviour.
>>>
>>> 3) Section 5.7 para 2 text " then the total rate limit for the
>>specific
>>> downstream SIP entity in the three NOTIFY messages sent to those three
>>> upstream neighbors must not exceed =C2=A0100 requests per second." This=
 is
>>a
>>> similar comment to the comment above about section 4.1. It would be
>>> better to communicate permitted rates which *do* exceed 100 in total
>>to
>>> upstream neighbours, and explicitly to limit downstream traffic to 100
>>> at the local server. Otherwise the network will almost certainly be
>>> under-utilised, which is damaging to customer service.
>>
>>The point of possible under-utilization with the simplified example is
>>recognized. Since it is difficult to give any specific (right) value
>>of over-commitment either, and the value computation mechanism itself
>>is considered out-of-scope of the event package, the next update will
>>clarify this.
>>
>>> 4) Section 5.8 para 3. typo "previoulsy"
>>
>>will correct.
>>
>>>
>>> 5) Section 6.3.1 para 2 last sentence, text "result is combined using
>>> logical OR". Just to clarify: does this interpretation allow joint
>>> control of traffic to a list of destinations (such as a televoting
>>> destination range) such that control does not have the effect of
>>> equalising traffic to the individual destinations?
>>
>>Not sure whether I understand. Could you please elaborate a bit about
>>the scenario you are referring to?
>>
>>>
>>> 6) Section 6.4 para 1, text " takes any one of the three sub-elements
>>> <rate>, <percent>, and <win>" It's very hard to see how either
>><percent>
>>> or <win> could make any sense for a statically-configured filtering
>>type
>>> of control, given the uncertainty in offered traffic level and in
>>> downstream server responsiveness.
>>>
>>
>>Indeed at this stage it may be the safest to use the <rate> sub-element.
>>
>>> 7) Section 6.4 para 2, text "The default value is "Drop" . =C2=A0" Will
>>> "drop" lead to retransmission by upstream elements, in networks using
>>> unreliable transport? If so this seems undesirable, by increasing load
>>> on the local device. Also 503 will allow upstream elements to re-try
>>> elsewhere which seems pointless or damaging in this type of control -
>>> would it be better to require sending 500?
>>>
>>
>>This makes sense. (although sending rejection costs non-negligible
>>additional cycles too)
>>
>>> Hope this helps
>>
>>Yes, thanks!
>>
>>Charles
>>
>>
>>>
>>> Geoff
>>>
>>> Geoff Hunt
>>> BT Design
>>>
>>> Tel: 01473 651704
>>> Email: geoff.hunt@bt.com
>>> Web: www.bt.com
>>> This email contains BT information, which may be privileged or
>>> confidential.
>>> It is meant only for the individual(s) or entity named above. If you
>>are
>>> not the intended
>>> recipient, note that disclosing, copying, distributing or using this
>>> information
>>> is prohibited. If you have received this email in error, please let me
>>> know immediately
>>> on the email address above. Thank you.
>>> We monitor our email system, and may record your emails.
>>> British Telecommunications plc
>>> Registered office: 81 Newgate Street London EC1A 7AJ
>>> Registered in England no: 1800000
>>>
>>>
>>> _______________________________________________
>>> 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 partr@cisco.com  Sat Feb 20 00:23:12 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 CF3963A80E3 for <sip-overload@core3.amsl.com>; Sat, 20 Feb 2010 00:23:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.202
X-Spam-Level: 
X-Spam-Status: No, score=-9.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, 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 I4EcMi1o9B+u for <sip-overload@core3.amsl.com>; Sat, 20 Feb 2010 00:23:11 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id D24B43A80DE for <sip-overload@ietf.org>; Sat, 20 Feb 2010 00:23:11 -0800 (PST)
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: Av8EAO4qf0urRN+J/2dsb2JhbACBQphrXnOjfpdzhGgEgxM
X-IronPort-AV: E=Sophos;i="4.49,507,1262563200";  d="scan'208,217";a="485841296"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-6.cisco.com with ESMTP; 20 Feb 2010 08:25:01 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o1K8P0mx009865;  Sat, 20 Feb 2010 08:25:01 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);  Sat, 20 Feb 2010 13:54:59 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAB206.30C8E0F6"
Date: Sat, 20 Feb 2010 13:54:59 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A6239021FC7@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] Expert Review for Overload Control Drafts
Thread-Index: AcpXEu5jACpgmkqpQtefL0jaVB0zVBa710e3
References: <4AE7055E.9060208@alcatel-lucent.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Volker Hilt" <volkerh@alcatel-lucent.com>, <sip-overload@ietf.org>
X-OriginalArrivalTime: 20 Feb 2010 08:24:59.0649 (UTC) FILETIME=[31150710:01CAB206]
Subject: Re: [sip-overload] Expert Review for Overload Control Drafts
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: Sat, 20 Feb 2010 08:23:12 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CAB206.30C8E0F6
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Volker,

=20

The draft looks good for SIP server handling the signaling only or =
single type of dialogs like audio dialogs only. The computing "oc" =
parameter looks like tricky accepts in case of handling multiple types =
of dialogs like audio dialog, video dialog and telepresence dialog with =
media. For example, the server is capable of handling all types of calls =
at the same time and individual capacities are as follows: 1000 audio =
dialog, 100 video dialog and 10 telepresence dialog and the server shall =
receive dialogs from 5 neighboring servers.  How to compute "oc" value? =
it is not clear whether oc value represents audio or video or =
telepresence dialogs. Say the least capacity (audio) is considered for =
"oc", the system will be overloaded often. Thinks will be more =
complicated in case SUBSCRIBE & INVITE based dialogs co-exists. Please =
clarify how to overcome compute "oc" value for these deployments.

=20

In case server decides to pass "oc" and "oc_validity" parameters only =
for trusted parties, the untrusted parties dialogs will have advantage =
over trusted parties even though they support this draft. Is it implicit =
that trusted parties should have some policy mechanism and others should =
have another policy mechanism?

=20
Thanks
Partha

________________________________

From: sip-overload-bounces@ietf.org on behalf of Volker Hilt
Sent: Tue 10/27/2009 8:06 PM
To: sip-overload@ietf.org
Subject: [sip-overload] Expert Review for Overload Control Drafts



All,

We are looking for experts who can do a review for the following two =
drafts:

http://www.ietf.org/internet-drafts/draft-hilt-sipping-overload-07.txt

http://tools.ietf.org/html/draft-shen-sipping-load-control-event-package-=
03.txt

Please send me a quick note if you are interested and available to do a
review for one of these drafts (or both of them). Please post the
review on this mailing list.

We had many people expressing interest in contributing to a SIP overload
control solution. This is a great chance to do so!

Thanks,

Volker

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



------_=_NextPart_001_01CAB206.30C8E0F6
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>[sip-overload] Expert Review for Overload =
Control Drafts</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18876"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText30122>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3DArial>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT size=3D3><FONT =
face=3D"Times New Roman">Hi Volker,</FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT size=3D3 =
face=3D"Times New Roman"></FONT>&nbsp;</P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT size=3D3><FONT =
face=3D"Times New Roman">The draft looks good for SIP server handling =
the signaling only or single type of dialogs like audio dialogs only. =
The computing "oc" parameter looks like tricky accepts in case of =
handling multiple types of dialogs like audio dialog, video dialog and =
telepresence dialog with media. For example, the server is capable of =
handling all types of calls at the same time and individual capacities =
are as follows: 1000 audio dialog, 100 video dialog and 10 telepresence =
dialog and the server shall receive dialogs from 5 neighboring =
servers.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>How to compute =
"oc" value? it is not clear whether oc value represents audio or video =
or telepresence dialogs. Say the least capacity (audio) is considered =
for "oc", the system will be overloaded often. Thinks will be more =
complicated in case SUBSCRIBE &amp; INVITE based dialogs co-exists. =
Please clarify how to overcome compute "oc" value for these =
deployments.<?xml:namespace prefix =3D o ns =3D =
"urn:schemas-microsoft-com:office:office" /><o:p></o:p></FONT></FONT></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><o:p><FONT size=3D3 =
face=3D"Times New Roman">&nbsp;</FONT></o:p></P>=0A=
<P style=3D"MARGIN: 0in 0in 0pt" class=3DMsoNormal><FONT size=3D3 =
face=3D"Times New Roman">In case server decides to pass "oc" and =
"oc_validity" parameters only for trusted parties, the untrusted parties =
dialogs will have advantage over trusted parties even though they =
support this draft. Is it implicit that trusted parties should have some =
policy mechanism and others should have another policy =
mechanism?</FONT></P></FONT></DIV></DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>Thanks</DIV>=0A=
<DIV dir=3Dltr>Partha<BR></DIV>=0A=
<DIV dir=3Dltr>=0A=
<HR tabIndex=3D-1>=0A=
</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DTahoma><B>From:</B> =
sip-overload-bounces@ietf.org on behalf of Volker Hilt<BR><B>Sent:</B> =
Tue 10/27/2009 8:06 PM<BR><B>To:</B> =
sip-overload@ietf.org<BR><B>Subject:</B> [sip-overload] Expert Review =
for Overload Control Drafts<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>All,<BR><BR>We are looking for experts who can do a =
review for the following two drafts:<BR><BR><A =
href=3D"http://www.ietf.org/internet-drafts/draft-hilt-sipping-overload-0=
7.txt">http://www.ietf.org/internet-drafts/draft-hilt-sipping-overload-07=
.txt</A><BR><BR><A =
href=3D"http://tools.ietf.org/html/draft-shen-sipping-load-control-event-=
package-03.txt">http://tools.ietf.org/html/draft-shen-sipping-load-contro=
l-event-package-03.txt</A><BR><BR>Please send me a quick note if you are =
interested and available to do a<BR>review for one of these drafts (or =
both of them). Please post the<BR>review on this mailing list.<BR><BR>We =
had many people expressing interest in contributing to a SIP =
overload<BR>control solution. This is a great chance to do =
so!<BR><BR>Thanks,<BR><BR>Volker<BR><BR>_________________________________=
______________<BR>sip-overload mailing =
list<BR>sip-overload@ietf.org<BR><A =
href=3D"https://www.ietf.org/mailman/listinfo/sip-overload">https://www.i=
etf.org/mailman/listinfo/sip-overload</A><BR></FONT></P></DIV></BODY></HT=
ML>
------_=_NextPart_001_01CAB206.30C8E0F6--
