
From aabdelal@sonusnet.com  Mon Jan 11 17:59:20 2010
Return-Path: <aabdelal@sonusnet.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 945C03A6944 for <sip-overload@core3.amsl.com>; Mon, 11 Jan 2010 17:59:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.184
X-Spam-Level: 
X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=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 BXjtRTwuDHBZ for <sip-overload@core3.amsl.com>; Mon, 11 Jan 2010 17:59:17 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by core3.amsl.com (Postfix) with ESMTP id 054813A6942 for <sip-overload@ietf.org>; Mon, 11 Jan 2010 17:59:16 -0800 (PST)
Received: from sonusmail06.sonusnet.com (sonusmail06.sonusnet.com [10.128.32.156]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id o0C1xCxo019028;  Mon, 11 Jan 2010 20:59:12 -0500
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_01CA932A.8C983CFC"
Date: Mon, 11 Jan 2010 20:57:08 -0500
Message-ID: <30CC59382F8B084DA5EEC4F7A26001FB01207665@sonusmail06.sonusnet.com>
In-Reply-To: <OF6F83D839.9DB17719-ON8525769B.005A110A-8525769B.005A5117@csc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: SIP overload control paper
Thread-Index: AcqIo3Xli5K0KG3eR6SONhYx6mO/nAKhkdsg
References: <5DA01D2CA74FAF40ADF71DB4177D345A02685104@misout7msgusr7b.ugd.att.com> <OF6F83D839.9DB17719-ON8525769B.005A110A-8525769B.005A5117@csc.com>
From: "Abdelal, Ahmed" <aabdelal@sonusnet.com>
To: "Volker Hilt" <volkerh@bell-labs.com>
Cc: sip-overload@ietf.org
Subject: [sip-overload] SIP overload control paper
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, 12 Jan 2010 01:59:20 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA932A.8C983CFC
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Volker,

=20

We have just presented a paper titled "Signal-Based Overload Control for
SIP Servers" (co-authored by Ahmed Abdelal & Wassim Matragi) to IEEE
CCNC (http://www.ieee-ccnc.org/).=20

The paper focuses on the signal-based overload control described in
Section 9.4 of IETF draft "Design Considerations for Session Initiation
Protocol (SIP) Overload Control". The paper will soon be available
through IEEE explorer.

=20

Thanks,

Ahmed

=20

=20


------_=_NextPart_001_01CA932A.8C983CFC
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
tt
	{font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>Hi =
Volker,<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>We have just =
presented a
paper titled &quot;Signal-Based Overload Control for SIP Servers&quot;
(co-authored by Ahmed Abdelal &amp; Wassim Matragi) to IEEE CCNC (<a
href=3D"http://www.ieee-ccnc.org/">http://www.ieee-ccnc.org/</a>). =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>The paper focuses =
on the
signal-based overload control described in Section 9.4 of IETF draft
&#8220;Design Considerations for Session Initiation Protocol (SIP) =
Overload
Control&#8221;. The paper will soon be available through IEEE =
explorer.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Ahmed<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01CA932A.8C983CFC--

From volker.hilt@alcatel-lucent.com  Fri Jan 15 05:35:26 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 9316A3A68FF for <sip-overload@core3.amsl.com>; Fri, 15 Jan 2010 05:35:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 HlP0WjOOu9Sd for <sip-overload@core3.amsl.com>; Fri, 15 Jan 2010 05:35:25 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 64C4C3A672F for <sip-overload@ietf.org>; Fri, 15 Jan 2010 05:35:22 -0800 (PST)
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 o0FDZIM4013156 for <sip-overload@ietf.org>; Fri, 15 Jan 2010 07:35:18 -0600 (CST)
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 o0FDZIpn020035 for <sip-overload@ietf.org>; Fri, 15 Jan 2010 07:35:18 -0600 (CST)
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.1.375.2; Fri, 15 Jan 2010 07:35:17 -0600
Message-ID: <4B506F0C.7020602@bell-labs.com>
Date: Fri, 15 Jan 2010 08:35:08 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "sip-overload@ietf.org" <sip-overload@ietf.org>
Content-Type: multipart/mixed; boundary="------------060706000605090700070603"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Subject: [sip-overload] [Fwd: [dispatch] Chartering SIP Overload]
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, 15 Jan 2010 13:36:50 -0000

--------------060706000605090700070603
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

Forwarding this email from DISPATCH (please copy the DISPATCH list on 
responses!).

Any comments?

Volker

--------------060706000605090700070603
Content-Type: message/rfc822; name="[dispatch] Chartering SIP Overload.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
	filename="[dispatch] Chartering SIP Overload.eml"

Received: from ilexp02.ndc.lucent.com (135.3.39.2) by
 USNAVSXCHHUB03.ndc.alcatel-lucent.com (135.3.39.112) with Microsoft SMTP
 Server id 8.1.375.2; Fri, 15 Jan 2010 05:24:05 -0600
Received: from hoemail2.alcatel.com ([172.22.12.28]) by ilexp02.ndc.lucent.com
 with Microsoft SMTPSVC(6.0.3790.3959);	 Fri, 15 Jan 2010 05:24:03 -0600
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32])	by
 hoemail2.alcatel.com (8.13.8/IER-i) with ESMTP id o0FBO23m007191	for
 <volkerh@bell-labs.com>; Fri, 15 Jan 2010 05:24:02 -0600 (CST)
Received: from [127.0.0.1] (localhost [127.0.0.1])	by core3.amsl.com (Postfix)
 with ESMTP id B74163A696A;	Fri, 15 Jan 2010 03:24:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])	by core3.amsl.com (Postfix)
 with ESMTP id 375DA3A6960	for <dispatch@core3.amsl.com>; Fri, 15 Jan 2010
 03:24:03 -0800 (PST)
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 D6o0+my1j3CD for
 <dispatch@core3.amsl.com>;	Fri, 15 Jan 2010 03:24:02 -0800 (PST)
Received: from mailgw5.ericsson.se (mailgw5.ericsson.se [193.180.251.36])	by
 core3.amsl.com (Postfix) with ESMTP id E493D3A68AB	for <dispatch@ietf.org>;
 Fri, 15 Jan 2010 03:24:01 -0800 (PST)
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.124])
	by mailgw5.ericsson.se (Symantec Mail Security) with SMTP id
	2F.38.04178.D40505B4; Fri, 15 Jan 2010 12:23:57 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); 	Fri, 15
 Jan 2010 12:23:06 +0100
Received: from [131.160.37.44] ([131.160.37.44]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); 	Fri, 15
 Jan 2010 12:23:06 +0100
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
To: DISPATCH <dispatch@ietf.org>
Sender: "dispatch-bounces@ietf.org" <dispatch-bounces@ietf.org>
Date: Fri, 15 Jan 2010 05:23:04 -0600
Subject: [dispatch] Chartering SIP Overload
Thread-Topic: [dispatch] Chartering SIP Overload
Thread-Index: AcqV1T8ZVB8XL9p/SJmYKYgPb71WsA==
Message-ID: <4B505018.7020504@ericsson.com>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>,
	<mailto:dispatch-request@ietf.org?subject=subscribe>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>,
	<mailto:dispatch-request@ietf.org?subject=unsubscribe>
Accept-Language: en-US
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-AuthSource: USNAVSXCHHUB03.ndc.alcatel-lucent.com
X-MS-Has-Attach: 
X-Auto-Response-Suppress: All
X-MS-Exchange-Organization-SCL: 0
X-MS-TNEF-Correlator: 
x-originalarrivaltime: 15 Jan 2010 11:23:06.0168 (UTC)
	FILETIME=[1BDF6B80:01CA95D5]
x-scanned-by: MIMEDefang 2.57 on 192.160.6.149
x-brightmail-tracker: AAAAAA==
x-spam-score: -106.123
x-spam-status: No, score=-106.123 tagged_above=-999 required=5
	tests=[AWL=0.126, BAYES_00=-2.599, HELO_EQ_SE=0.35,	RCVD_IN_DNSWL_MED=-4,
 USER_IN_WHITELIST=-100]
x-spam-level: 
user-agent: Thunderbird 2.0.0.23 (Windows/20090812)
errors-to: dispatch-bounces@ietf.org
x-virus-scanned: amavisd-new at amsl.com
x-auditid: c1b4fb24-b7bb6ae000001052-6a-4b50504df3c9
list-post: <mailto:dispatch@ietf.org>
delivered-to: dispatch@core3.amsl.com
list-id: DISPATCH Working Group Mail List <dispatch.ietf.org>
x-spam-flag: NO
list-archive: <http://www.ietf.org/mail-archive/web/dispatch>
x-mailman-version: 2.1.9
x-beenthere: dispatch@ietf.org
x-original-to: dispatch@core3.amsl.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Folks,

as you know, we agreed to charter the SIP overload work a while ago.=20
Below you can find the proposed charter.

We have gotten some comments back from the IESG. There are some concerns=20
about the effects of the proposed solutions in real networks. It seems=20
that those concerns would disappear if we chartered the WG to develop=20
Experimental proposals, at least at the beginning. Those proposals would=20
be able to eventually move to the standards track once we got=20
operational experience with them. Comments?

Thanks,

Gonzalo



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. 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.


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

--------------060706000605090700070603--

From volker.hilt@alcatel-lucent.com  Fri Jan 15 06:47: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 BD0B428C0E2; Fri, 15 Jan 2010 06:47:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 RJoGTJesUg08; Fri, 15 Jan 2010 06:47:05 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 8FEF728C0D6; Fri, 15 Jan 2010 06:47:05 -0800 (PST)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id o0FEkxli029764;  Fri, 15 Jan 2010 08:46:59 -0600 (CST)
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 o0FEkxUh013241; Fri, 15 Jan 2010 08:46:59 -0600 (CST)
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.1.375.2; Fri, 15 Jan 2010 08:46:58 -0600
Message-ID: <4B507FD9.4010407@bell-labs.com>
Date: Fri, 15 Jan 2010 09:46:49 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
References: <4B505018.7020504@ericsson.com>
In-Reply-To: <4B505018.7020504@ericsson.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.37
Cc: DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 15 Jan 2010 14:47:06 -0000

Gonzalo,

it would be great to understand what the specific concerns are.

We had a design team working on simulations on SIP overload control for 
a substantial period of time. The group has produced many results and 
has published these results at scientific conferences and status reports 
to the IETF. Some of the drafts have been implemented and tested in 
prototypes or products by multiple vendors. What else is needed?

I'm worried that we are taking yet another detour which will further 
delay the process.

Volker





Gonzalo Camarillo wrote:
> Folks,
> 
> as you know, we agreed to charter the SIP overload work a while ago. 
> Below you can find the proposed charter.
> 
> We have gotten some comments back from the IESG. There are some concerns 
> about the effects of the proposed solutions in real networks. It seems 
> that those concerns would disappear if we chartered the WG to develop 
> Experimental proposals, at least at the beginning. Those proposals would 
> be able to eventually move to the standards track once we got 
> operational experience with them. Comments?
> 
> Thanks,
> 
> Gonzalo
> 
> 
> 
> 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. 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.
> 
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch


From gonzalo.camarillo@ericsson.com  Fri Jan 15 07:02:08 2010
Return-Path: <gonzalo.camarillo@ericsson.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 B459628C0D9; Fri, 15 Jan 2010 07:02:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.1
X-Spam-Level: 
X-Spam-Status: No, score=-106.1 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 fVqExx9tkm1S; Fri, 15 Jan 2010 07:02:08 -0800 (PST)
Received: from mailgw5.ericsson.se (mailgw5.ericsson.se [193.180.251.36]) by core3.amsl.com (Postfix) with ESMTP id 3BB5828C0D6; Fri, 15 Jan 2010 07:02:07 -0800 (PST)
X-AuditID: c1b4fb24-b7bb6ae000001052-f5-4b50836a7125
Received: from esealmw127.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw5.ericsson.se (Symantec Mail Security) with SMTP id 31.59.04178.A63805B4; Fri, 15 Jan 2010 16:02:03 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 15 Jan 2010 16:02:02 +0100
Received: from [131.160.37.44] ([131.160.37.44]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 15 Jan 2010 16:02:02 +0100
Message-ID: <4B50836A.4020607@ericsson.com>
Date: Fri, 15 Jan 2010 17:02:02 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Volker Hilt <volkerh@bell-labs.com>
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com>
In-Reply-To: <4B507FD9.4010407@bell-labs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Jan 2010 15:02:02.0613 (UTC) FILETIME=[B1CDDA50:01CA95F3]
X-Brightmail-Tracker: AAAAAA==
X-Mailman-Approved-At: Fri, 15 Jan 2010 07:03:51 -0800
Cc: DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 15 Jan 2010 15:02:08 -0000

Hi,

> I'm worried that we are taking yet another detour which will further 
> delay the process.

this would not delay the process in any way. If something, it could 
speed it up, because the requirements to review Experimental RFCs are 
lower than to review standards track RFCs... at the end of the day, I do 
not expect this to influence the time it takes to publish the specs 
because I am sure the group will make sure the quality of the specs as 
high as for a standards-track RFC.

Cheers,

Gonzalo


From volker.hilt@alcatel-lucent.com  Fri Jan 15 07:08:19 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 7F2D73A67FB; Fri, 15 Jan 2010 07:08:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 uqoCoyllPmDw; Fri, 15 Jan 2010 07:08:18 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id AD3ED3A690B; Fri, 15 Jan 2010 07:08:18 -0800 (PST)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id o0FF8D11025893;  Fri, 15 Jan 2010 09:08:13 -0600 (CST)
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 o0FF8DaX012133; Fri, 15 Jan 2010 09:08:13 -0600 (CST)
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.1.375.2; Fri, 15 Jan 2010 09:08:12 -0600
Message-ID: <4B5084D3.5020606@bell-labs.com>
Date: Fri, 15 Jan 2010 10:08:03 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com> <4B50836A.4020607@ericsson.com>
In-Reply-To: <4B50836A.4020607@ericsson.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.37
Cc: DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 15 Jan 2010 15:08:19 -0000

Gonzalo,
> 
>> I'm worried that we are taking yet another detour which will further 
>> delay the process.
> 
> this would not delay the process in any way. If something, it could 
> speed it up, because the requirements to review Experimental RFCs are 
> lower than to review standards track RFCs... at the end of the day, I do 
> not expect this to influence the time it takes to publish the specs 
> because I am sure the group will make sure the quality of the specs as 
> high as for a standards-track RFC.
> 
I'd like to understand the concerns that lead to the proposal of putting 
this work through the experimental track.

What are we missing that prevents us from creating a standards track 
document?

Volker




From jgunn6@csc.com  Fri Jan 15 07:19:04 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 7C8223A6A5D; Fri, 15 Jan 2010 07:19:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[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 6fPGb74Arat6; Fri, 15 Jan 2010 07:19:03 -0800 (PST)
Received: from mail145.messagelabs.com (mail145.messagelabs.com [216.82.242.163]) by core3.amsl.com (Postfix) with ESMTP id 7A6093A6A87; Fri, 15 Jan 2010 07:18:59 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-15.tower-145.messagelabs.com!1263568734!15868952!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [20.137.2.88]
Received: (qmail 21546 invoked from network); 15 Jan 2010 15:18:55 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-15.tower-145.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Jan 2010 15:18:55 -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 o0FFIfKP014477; Fri, 15 Jan 2010 10:18:41 -0500
In-Reply-To: <4B507FD9.4010407@bell-labs.com>
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com>
To: Volker Hilt <volkerh@bell-labs.com>
MIME-Version: 1.0
X-KeepSent: 73848687:E2EFB750-852576AC:0053E618; 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: <OF73848687.E2EFB750-ON852576AC.0053E618-852576AC.0054203B@csc.com>
Date: Fri, 15 Jan 2010 10:18:52 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.0.1 HF996|December 23, 2008) at 01/15/2010 10:20:04 AM, Serialize complete at 01/15/2010 10:20:04 AM
Content-Type: multipart/alternative; boundary="=_alternative 00541FF7852576AC_="
Cc: sip-overload-bounces@ietf.org, DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 15 Jan 2010 15:19:04 -0000

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

Is the concern "real networks" vs "simulated networks"?

Or is the concern "the (open) Internet" vs "(closed, walled-garden) 
carrier networks"?

Janet

This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to 
any order or other contract unless pursuant to explicit written agreement 
or government initiative expressly permitting the use of e-mail for such 
purpose.



From:
Volker Hilt <volkerh@bell-labs.com>
To:
Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Cc:
DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" 
<sip-overload@ietf.org>
Date:
01/15/2010 09:47 AM
Subject:
Re: [sip-overload] [dispatch] Chartering SIP Overload



Gonzalo,

it would be great to understand what the specific concerns are.

We had a design team working on simulations on SIP overload control for 
a substantial period of time. The group has produced many results and 
has published these results at scientific conferences and status reports 
to the IETF. Some of the drafts have been implemented and tested in 
prototypes or products by multiple vendors. What else is needed?

I'm worried that we are taking yet another detour which will further 
delay the process.

Volker





Gonzalo Camarillo wrote:
> Folks,
> 
> as you know, we agreed to charter the SIP overload work a while ago. 
> Below you can find the proposed charter.
> 
> We have gotten some comments back from the IESG. There are some concerns 

> about the effects of the proposed solutions in real networks. It seems 
> that those concerns would disappear if we chartered the WG to develop 
> Experimental proposals, at least at the beginning. Those proposals would 

> be able to eventually move to the standards track once we got 
> operational experience with them. Comments?
> 
> Thanks,
> 
> Gonzalo
> 
> 
> 
> 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. 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.
> 
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

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



--=_alternative 00541FF7852576AC_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Is the concern &quot;real networks&quot;
vs &quot;simulated networks&quot;?</font>
<br>
<br><font size=2 face="sans-serif">Or is the concern &quot;the (open) Internet&quot;
vs &quot;(closed, walled-garden) carrier networks&quot;?</font>
<br>
<br><font size=2 face="sans-serif">Janet<br>
<br>
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. <br>
NOTE: Regardless of content, this e-mail shall not operate to bind CSC
to any order or other contract unless pursuant to explicit written agreement
or government initiative expressly permitting the use of e-mail for such
purpose.</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">Volker Hilt &lt;volkerh@bell-labs.com&gt;</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">Gonzalo Camarillo &lt;Gonzalo.Camarillo@ericsson.com&gt;</font>
<tr>
<td valign=top><font size=1 color=#5f5f5f face="sans-serif">Cc:</font>
<td><font size=1 face="sans-serif">DISPATCH &lt;dispatch@ietf.org&gt;,
&quot;sip-overload@ietf.org&quot; &lt;sip-overload@ietf.org&gt;</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">01/15/2010 09:47 AM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">Re: [sip-overload] [dispatch] Chartering
SIP Overload</font></table>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Gonzalo,<br>
<br>
it would be great to understand what the specific concerns are.<br>
<br>
We had a design team working on simulations on SIP overload control for
<br>
a substantial period of time. The group has produced many results and <br>
has published these results at scientific conferences and status reports
<br>
to the IETF. Some of the drafts have been implemented and tested in <br>
prototypes or products by multiple vendors. What else is needed?<br>
<br>
I'm worried that we are taking yet another detour which will further <br>
delay the process.<br>
<br>
Volker<br>
<br>
<br>
<br>
<br>
<br>
Gonzalo Camarillo wrote:<br>
&gt; Folks,<br>
&gt; <br>
&gt; as you know, we agreed to charter the SIP overload work a while ago.
<br>
&gt; Below you can find the proposed charter.<br>
&gt; <br>
&gt; We have gotten some comments back from the IESG. There are some concerns
<br>
&gt; about the effects of the proposed solutions in real networks. It seems
<br>
&gt; that those concerns would disappear if we chartered the WG to develop
<br>
&gt; Experimental proposals, at least at the beginning. Those proposals
would <br>
&gt; be able to eventually move to the standards track once we got <br>
&gt; operational experience with them. Comments?<br>
&gt; <br>
&gt; Thanks,<br>
&gt; <br>
&gt; Gonzalo<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 process all<br>
&gt; incoming SIP messages. &nbsp;These resources can include CPU, memory,
network<br>
&gt; bandwidth, input/output, 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 throughput 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 throughput 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 proposed working group is to develop mechanisms
for<br>
&gt; SIP overload control. Two complementary approaches exist for handling<br>
&gt; 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.<br>
&gt; <br>
&gt; Specifically, the proposed working group will develop the following<br>
&gt; deliverables:<br>
&gt; 1. A document describing key design considerations for a SIP overload<br>
&gt; control mechanism.<br>
&gt; 2. A specification for an SIP overload control mechanism based on<br>
&gt; implicit/explicit feedback.<br>
&gt; 3. A specification for a SIP load filtering mechanism.<br>
&gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; dispatch mailing list<br>
&gt; dispatch@ietf.org<br>
&gt; </font></tt><a href=https://www.ietf.org/mailman/listinfo/dispatch><tt><font size=2>https://www.ietf.org/mailman/listinfo/dispatch</font></tt></a><tt><font size=2><br>
<br>
_______________________________________________<br>
sip-overload mailing list<br>
sip-overload@ietf.org<br>
</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>
<br>
<br>
--=_alternative 00541FF7852576AC_=--

From hgs@cs.columbia.edu  Fri Jan 15 07:38:36 2010
Return-Path: <hgs@cs.columbia.edu>
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 B990B3A6AE0; Fri, 15 Jan 2010 07:38:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Igi+gPGJIMER; Fri, 15 Jan 2010 07:38:36 -0800 (PST)
Received: from tarap.cc.columbia.edu (tarap.cc.columbia.edu [128.59.29.7]) by core3.amsl.com (Postfix) with ESMTP id C800C3A6829; Fri, 15 Jan 2010 07:38:35 -0800 (PST)
Received: from ice.cs.columbia.edu (ice.cs.columbia.edu [128.59.18.177]) (user=hgs10 mech=PLAIN bits=0) by tarap.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id o0FFcOTj000182 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 15 Jan 2010 10:38:25 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <0D5387FA-749B-4EF4-9C44-53668CBAB9E0@nostrum.com>
Date: Fri, 15 Jan 2010 10:38:24 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <199BC2E4-B4E7-4447-95B8-BA67CE7061F8@cs.columbia.edu>
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com> <4B50836A.4020607@ericsson.com> <4B5084D3.5020606@bell-labs.com> <0D5387FA-749B-4EF4-9C44-53668CBAB9E0@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1077)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.7
Cc: Volker Hilt <volkerh@bell-labs.com>, DISPATCH <dispatch@ietf.org>, sip-overload@ietf.org, Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 15 Jan 2010 15:38:36 -0000

At least according to our measurements and simulations, that is not the =
case. The throughput stays at ~100% until infinity.

Henning

On Jan 15, 2010, at 10:34 AM, Robert Sparks wrote:

> (Copying Lars - please preserve him on the CC for this thread).
>=20
> The big concern, as I understand it, is that the state of what the =
team's explored so far
> reduces the degradation of throughput as load increases, but still =
eventually collapses.
> Is that accurate? (I might have missed something the team's done that =
manages to converge
> to a stable point.)
>=20
> RjS
>=20
>=20
> On Jan 15, 2010, at 9:08 AM, Volker Hilt wrote:
>=20
>> Gonzalo,
>>>> I'm worried that we are taking yet another detour which will =
further delay the process.
>>> this would not delay the process in any way. If something, it could =
speed it up, because the requirements to review Experimental RFCs are =
lower than to review standards track RFCs... at the end of the day, I do =
not expect this to influence the time it takes to publish the specs =
because I am sure the group will make sure the quality of the specs as =
high as for a standards-track RFC.
>> I'd like to understand the concerns that lead to the proposal of =
putting this work through the experimental track.
>>=20
>> What are we missing that prevents us from creating a standards track =
document?
>>=20
>> Volker
>>=20
>>=20
>>=20
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>=20
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>=20


From rjsparks@nostrum.com  Fri Jan 15 07:34:25 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 A30093A6A33; Fri, 15 Jan 2010 07:34:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, 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 Cy7CmezjycnE; Fri, 15 Jan 2010 07:34:24 -0800 (PST)
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 68CBD3A6856; Fri, 15 Jan 2010 07:34:24 -0800 (PST)
Received: from [192.168.2.2] (pool-173-71-49-137.dllstx.fios.verizon.net [173.71.49.137]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o0FFYCNt026772 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 15 Jan 2010 09:34:13 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-Id: <0D5387FA-749B-4EF4-9C44-53668CBAB9E0@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: Volker Hilt <volkerh@bell-labs.com>
In-Reply-To: <4B5084D3.5020606@bell-labs.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 15 Jan 2010 09:34:12 -0600
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com> <4B50836A.4020607@ericsson.com> <4B5084D3.5020606@bell-labs.com>
X-Mailer: Apple Mail (2.936)
Received-SPF: pass (nostrum.com: 173.71.49.137 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Fri, 15 Jan 2010 07:41:20 -0800
Cc: DISPATCH <dispatch@ietf.org>, sip-overload@ietf.org, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 15 Jan 2010 15:34:25 -0000

(Copying Lars - please preserve him on the CC for this thread).

The big concern, as I understand it, is that the state of what the  
team's explored so far
reduces the degradation of throughput as load increases, but still  
eventually collapses.
Is that accurate? (I might have missed something the team's done that  
manages to converge
to a stable point.)

RjS


On Jan 15, 2010, at 9:08 AM, Volker Hilt wrote:

> Gonzalo,
>>> I'm worried that we are taking yet another detour which will  
>>> further delay the process.
>> this would not delay the process in any way. If something, it could  
>> speed it up, because the requirements to review Experimental RFCs  
>> are lower than to review standards track RFCs... at the end of the  
>> day, I do not expect this to influence the time it takes to publish  
>> the specs because I am sure the group will make sure the quality of  
>> the specs as high as for a standards-track RFC.
> I'd like to understand the concerns that lead to the proposal of  
> putting this work through the experimental track.
>
> What are we missing that prevents us from creating a standards track  
> document?
>
> Volker
>
>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch


From volker.hilt@alcatel-lucent.com  Fri Jan 15 07:58:01 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 A81A03A6AFE; Fri, 15 Jan 2010 07:58:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 rbAoYdAC9Ccd; Fri, 15 Jan 2010 07:58:00 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id C0AD23A6AE1; Fri, 15 Jan 2010 07:57:59 -0800 (PST)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id o0FFvmTS022774;  Fri, 15 Jan 2010 09:57:48 -0600 (CST)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id o0FFvkVB019031; Fri, 15 Jan 2010 09:57:47 -0600 (CST)
Received: from [127.0.0.1] (135.3.63.242) by USNAVSXCHHUB02.ndc.alcatel-lucent.com (135.3.39.111) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 15 Jan 2010 09:57:47 -0600
Message-ID: <4B509071.8090904@bell-labs.com>
Date: Fri, 15 Jan 2010 10:57:37 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com> <4B50836A.4020607@ericsson.com> <4B5084D3.5020606@bell-labs.com> <0D5387FA-749B-4EF4-9C44-53668CBAB9E0@nostrum.com> <199BC2E4-B4E7-4447-95B8-BA67CE7061F8@cs.columbia.edu>
In-Reply-To: <199BC2E4-B4E7-4447-95B8-BA67CE7061F8@cs.columbia.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Lars Eggert <lars.eggert@nokia.com>, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 15 Jan 2010 15:58:01 -0000

Yes, we have the same results - the throughput stays at the capacity
limit and remains stable.

Volker




Henning Schulzrinne wrote:
> At least according to our measurements and simulations, that is not the case. The throughput stays at ~100% until infinity.
> 
> Henning
> 
> On Jan 15, 2010, at 10:34 AM, Robert Sparks wrote:
> 
>> (Copying Lars - please preserve him on the CC for this thread).
>>
>> The big concern, as I understand it, is that the state of what the team's explored so far
>> reduces the degradation of throughput as load increases, but still eventually collapses.
>> Is that accurate? (I might have missed something the team's done that manages to converge
>> to a stable point.)
>>
>> RjS
>>
>>
>> On Jan 15, 2010, at 9:08 AM, Volker Hilt wrote:
>>
>>> Gonzalo,
>>>>> I'm worried that we are taking yet another detour which will further delay the process.
>>>> this would not delay the process in any way. If something, it could speed it up, because the requirements to review Experimental RFCs are lower than to review standards track RFCs... at the end of the day, I do not expect this to influence the time it takes to publish the specs because I am sure the group will make sure the quality of the specs as high as for a standards-track RFC.
>>> I'd like to understand the concerns that lead to the proposal of putting this work through the experimental track.
>>>
>>> What are we missing that prevents us from creating a standards track document?
>>>
>>> Volker
>>>
>>>
>>>
>>> _______________________________________________
>>> 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 en5192@att.com  Fri Jan 15 07:59:19 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 DE4E93A6AFD; Fri, 15 Jan 2010 07:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[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 LtFEK8NG4JYA; Fri, 15 Jan 2010 07:59:19 -0800 (PST)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by core3.amsl.com (Postfix) with ESMTP id 017723A6AE1; Fri, 15 Jan 2010 07:59:18 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: en5192@att.com
X-Msg-Ref: server-9.tower-120.messagelabs.com!1263571154!51028866!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 31218 invoked from network); 15 Jan 2010 15:59:15 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-9.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Jan 2010 15:59:15 -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 o0FFx9e8000694; Fri, 15 Jan 2010 10:59:10 -0500
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 o0FFx7fr000687; Fri, 15 Jan 2010 10:59:07 -0500
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: Fri, 15 Jan 2010 10:56:44 -0500
Message-ID: <5DA01D2CA74FAF40ADF71DB4177D345A04841C08@misout7msgusr7b.ugd.att.com>
In-Reply-To: <4B509071.8090904@bell-labs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] [dispatch] Chartering SIP Overload
Thread-Index: AcqV+4lvdMnDQtMPS26qpIxgo/BZ8AAAE3GA
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com><4B50836A.4020607@ericsson.com> <4B5084D3.5020606@bell-labs.com><0D5387FA-749B-4EF4-9C44-53668CBAB9E0@nostrum.com><199BC2E4-B4E7-4447-95B8-BA67CE7061F8@cs.columbia.edu> <4B509071.8090904@bell-labs.com>
From: "NOEL, ERIC C (ATTLABS)" <en5192@att.com>
To: "Volker Hilt" <volkerh@bell-labs.com>, "Henning Schulzrinne" <hgs@cs.columbia.edu>
Cc: DISPATCH <dispatch@ietf.org>, sip-overload@ietf.org, Lars Eggert <lars.eggert@nokia.com>, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 15 Jan 2010 15:59:20 -0000

Same here at AT&T.

Eric

-----Original Message-----
From: sip-overload-bounces@ietf.org
[mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt
Sent: Friday, January 15, 2010 10:58 AM
To: Henning Schulzrinne
Cc: DISPATCH; sip-overload@ietf.org; Lars Eggert; Robert Sparks
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload

Yes, we have the same results - the throughput stays at the capacity
limit and remains stable.

Volker




Henning Schulzrinne wrote:
> At least according to our measurements and simulations, that is not
the case. The throughput stays at ~100% until infinity.
>=20
> Henning
>=20
> On Jan 15, 2010, at 10:34 AM, Robert Sparks wrote:
>=20
>> (Copying Lars - please preserve him on the CC for this thread).
>>
>> The big concern, as I understand it, is that the state of what the
team's explored so far
>> reduces the degradation of throughput as load increases, but still
eventually collapses.
>> Is that accurate? (I might have missed something the team's done that
manages to converge
>> to a stable point.)
>>
>> RjS
>>
>>
>> On Jan 15, 2010, at 9:08 AM, Volker Hilt wrote:
>>
>>> Gonzalo,
>>>>> I'm worried that we are taking yet another detour which will
further delay the process.
>>>> this would not delay the process in any way. If something, it could
speed it up, because the requirements to review Experimental RFCs are
lower than to review standards track RFCs... at the end of the day, I do
not expect this to influence the time it takes to publish the specs
because I am sure the group will make sure the quality of the specs as
high as for a standards-track RFC.
>>> I'd like to understand the concerns that lead to the proposal of
putting this work through the experimental track.
>>>
>>> What are we missing that prevents us from creating a standards track
document?
>>>
>>> Volker
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>=20


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

From jgunn6@csc.com  Fri Jan 15 08:09:38 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 92E0F3A6945; Fri, 15 Jan 2010 08:09:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[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 wPvUBFFFQwXx; Fri, 15 Jan 2010 08:09:35 -0800 (PST)
Received: from mail86.messagelabs.com (mail86.messagelabs.com [216.82.242.179]) by core3.amsl.com (Postfix) with ESMTP id CBE113A6966; Fri, 15 Jan 2010 08:09:34 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-5.tower-86.messagelabs.com!1263571769!11810786!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [20.137.2.87]
Received: (qmail 19429 invoked from network); 15 Jan 2010 16:09:30 -0000
Received: from amer-mta101.csc.com (HELO amer-mta101.csc.com) (20.137.2.87) by server-5.tower-86.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Jan 2010 16:09:30 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta101.csc.com (Switch-3.3.3mp/Switch-3.3.3mp) with ESMTP id o0FG9IcB025993; Fri, 15 Jan 2010 11:09:26 -0500
In-Reply-To: <0D5387FA-749B-4EF4-9C44-53668CBAB9E0@nostrum.com>
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com>	<4B50836A.4020607@ericsson.com> <4B5084D3.5020606@bell-labs.com> <0D5387FA-749B-4EF4-9C44-53668CBAB9E0@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
MIME-Version: 1.0
X-KeepSent: 9BE099C4:F5D46763-852576AC:0058AA28; 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: <OF9BE099C4.F5D46763-ON852576AC.0058AA28-852576AC.0058C020@csc.com>
Date: Fri, 15 Jan 2010 11:09:22 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.0.1 HF996|December 23, 2008) at 01/15/2010 11:10:37 AM, Serialize complete at 01/15/2010 11:10:37 AM
Content-Type: multipart/alternative; boundary="=_alternative 0058BFD7852576AC_="
Cc: sip-overload-bounces@ietf.org, DISPATCH <dispatch@ietf.org>, sip-overload@ietf.org, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Lars Eggert <lars.eggert@nokia.com>, Volker Hilt <volkerh@bell-labs.com>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 15 Jan 2010 16:09:38 -0000

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

That was a concern with the very first work done by the SIP overload 
group.  But all the results presented recently have avoided that problem.

Janet

sip-overload-bounces@ietf.org wrote on 01/15/2010 10:34:12 AM:

> [image removed] 
> 
> Re: [sip-overload] [dispatch] Chartering SIP Overload
> 
> Robert Sparks 
> 
> to:
> 
> Volker Hilt
> 
> 01/15/2010 10:41 AM
> 
> Sent by:
> 
> sip-overload-bounces@ietf.org
> 
> Cc:
> 
> DISPATCH, sip-overload, Gonzalo Camarillo, Lars Eggert
> 
> (Copying Lars - please preserve him on the CC for this thread).
> 
> The big concern, as I understand it, is that the state of what the 
> team's explored so far
> reduces the degradation of throughput as load increases, but still 
> eventually collapses.
> Is that accurate? (I might have missed something the team's done that 
> manages to converge
> to a stable point.)
> 
> RjS
> 
> 
> On Jan 15, 2010, at 9:08 AM, Volker Hilt wrote:
> 
> > Gonzalo,
> >>> I'm worried that we are taking yet another detour which will 
> >>> further delay the process.
> >> this would not delay the process in any way. If something, it could 
> >> speed it up, because the requirements to review Experimental RFCs 
> >> are lower than to review standards track RFCs... at the end of the 
> >> day, I do not expect this to influence the time it takes to publish 
> >> the specs because I am sure the group will make sure the quality of 
> >> the specs as high as for a standards-track RFC.
> > I'd like to understand the concerns that lead to the proposal of 
> > putting this work through the experimental track.
> >
> > What are we missing that prevents us from creating a standards track 
> > document?
> >
> > Volker
> >
> >
> >
> > _______________________________________________
> > dispatch mailing list
> > dispatch@ietf.org
> > https://www.ietf.org/mailman/listinfo/dispatch
> 
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload

--=_alternative 0058BFD7852576AC_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif"><br>
<br>
That was a concern with the very first work done by the SIP overload group.
&nbsp;But all the results presented recently have avoided that problem.</font>
<br>
<br><font size=2 face="sans-serif">Janet</font>
<br>
<br><tt><font size=2>sip-overload-bounces@ietf.org wrote on 01/15/2010
10:34:12 AM:<br>
<br>
&gt; [image removed] </font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Re: [sip-overload] [dispatch] Chartering SIP Overload</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; 01/15/2010 10:41 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, sip-overload, Gonzalo Camarillo, Lars Eggert</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; (Copying Lars - please preserve him on the CC for this thread).<br>
&gt; <br>
&gt; The big concern, as I understand it, is that the state of what the
&nbsp;<br>
&gt; team's explored so far<br>
&gt; reduces the degradation of throughput as load increases, but still
&nbsp;<br>
&gt; eventually collapses.<br>
&gt; Is that accurate? (I might have missed something the team's done that
&nbsp;<br>
&gt; manages to converge<br>
&gt; to a stable point.)<br>
&gt; <br>
&gt; RjS<br>
&gt; <br>
&gt; <br>
&gt; On Jan 15, 2010, at 9:08 AM, Volker Hilt wrote:<br>
&gt; <br>
&gt; &gt; Gonzalo,<br>
&gt; &gt;&gt;&gt; I'm worried that we are taking yet another detour which
will &nbsp;<br>
&gt; &gt;&gt;&gt; further delay the process.<br>
&gt; &gt;&gt; this would not delay the process in any way. If something,
it could &nbsp;<br>
&gt; &gt;&gt; speed it up, because the requirements to review Experimental
RFCs &nbsp;<br>
&gt; &gt;&gt; are lower than to review standards track RFCs... at the end
of the &nbsp;<br>
&gt; &gt;&gt; day, I do not expect this to influence the time it takes
to publish &nbsp;<br>
&gt; &gt;&gt; the specs because I am sure the group will make sure the
quality of &nbsp;<br>
&gt; &gt;&gt; the specs as high as for a standards-track RFC.<br>
&gt; &gt; I'd like to understand the concerns that lead to the proposal
of &nbsp;<br>
&gt; &gt; putting this work through the experimental track.<br>
&gt; &gt;<br>
&gt; &gt; What are we missing that prevents us from creating a standards
track &nbsp;<br>
&gt; &gt; document?<br>
&gt; &gt;<br>
&gt; &gt; Volker<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; dispatch mailing list<br>
&gt; &gt; dispatch@ietf.org<br>
&gt; &gt; </font></tt><a href=https://www.ietf.org/mailman/listinfo/dispatch><tt><font size=2>https://www.ietf.org/mailman/listinfo/dispatch</font></tt></a><tt><font size=2><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 0058BFD7852576AC_=--

From aabdelal@sonusnet.com  Fri Jan 15 14:06:53 2010
Return-Path: <aabdelal@sonusnet.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 3FF743A6857; Fri, 15 Jan 2010 14:06:53 -0800 (PST)
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.208,  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 LOrPbsptdkue; Fri, 15 Jan 2010 14:06:52 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by core3.amsl.com (Postfix) with ESMTP id 0F1B23A67FC; Fri, 15 Jan 2010 14:06:51 -0800 (PST)
Received: from sonusmail06.sonusnet.com (sonusmail06.sonusnet.com [10.128.32.156]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id o0FM6alS016599;  Fri, 15 Jan 2010 17:06:36 -0500
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: Fri, 15 Jan 2010 17:04:26 -0500
Message-ID: <30CC59382F8B084DA5EEC4F7A26001FB0120776D@sonusmail06.sonusnet.com>
In-Reply-To: <5DA01D2CA74FAF40ADF71DB4177D345A04841C08@misout7msgusr7b.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: [sip-overload] [dispatch] Chartering SIP Overload
Thread-Index: AcqV+4lvdMnDQtMPS26qpIxgo/BZ8AAAE3GAAAw7RfA=
References: <4B509071.8090904@bell-labs.com> <5DA01D2CA74FAF40ADF71DB4177D345A04841C08@misout7msgusr7b.ugd.att.com>
From: "Abdelal, Ahmed" <aabdelal@sonusnet.com>
To: "NOEL, ERIC C (ATTLABS)" <en5192@att.com>, "Volker Hilt" <volkerh@bell-labs.com>, "Henning Schulzrinne" <hgs@cs.columbia.edu>
Cc: DISPATCH <dispatch@ietf.org>, sip-overload@ietf.org, Lars Eggert <lars.eggert@nokia.com>, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 15 Jan 2010 22:06:53 -0000

We (Sonus) have implemented the SIP overload control and extensively
tested it. The results show that it mainatins the goodput under
different overload levels.

--Ahmed

-----Original Message-----
From: sip-overload-bounces@ietf.org
[mailto:sip-overload-bounces@ietf.org] On Behalf Of NOEL, ERIC C
(ATTLABS)
Sent: Friday, January 15, 2010 10:57 AM
To: Volker Hilt; Henning Schulzrinne
Cc: DISPATCH; sip-overload@ietf.org; Lars Eggert; Robert Sparks
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload

Same here at AT&T.

Eric

-----Original Message-----
From: sip-overload-bounces@ietf.org
[mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt
Sent: Friday, January 15, 2010 10:58 AM
To: Henning Schulzrinne
Cc: DISPATCH; sip-overload@ietf.org; Lars Eggert; Robert Sparks
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload

Yes, we have the same results - the throughput stays at the capacity
limit and remains stable.

Volker




Henning Schulzrinne wrote:
> At least according to our measurements and simulations, that is not
the case. The throughput stays at ~100% until infinity.
>=20
> Henning
>=20
> On Jan 15, 2010, at 10:34 AM, Robert Sparks wrote:
>=20
>> (Copying Lars - please preserve him on the CC for this thread).
>>
>> The big concern, as I understand it, is that the state of what the
team's explored so far
>> reduces the degradation of throughput as load increases, but still
eventually collapses.
>> Is that accurate? (I might have missed something the team's done that
manages to converge
>> to a stable point.)
>>
>> RjS
>>
>>
>> On Jan 15, 2010, at 9:08 AM, Volker Hilt wrote:
>>
>>> Gonzalo,
>>>>> I'm worried that we are taking yet another detour which will
further delay the process.
>>>> this would not delay the process in any way. If something, it could
speed it up, because the requirements to review Experimental RFCs are
lower than to review standards track RFCs... at the end of the day, I do
not expect this to influence the time it takes to publish the specs
because I am sure the group will make sure the quality of the specs as
high as for a standards-track RFC.
>>> I'd like to understand the concerns that lead to the proposal of
putting this work through the experimental track.
>>>
>>> What are we missing that prevents us from creating a standards track
document?
>>>
>>> Volker
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>=20


_______________________________________________
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 drage@alcatel-lucent.com  Mon Jan 18 06:05:14 2010
Return-Path: <drage@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 E8BEF3A672F; Mon, 18 Jan 2010 06:05:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.196
X-Spam-Level: 
X-Spam-Status: No, score=-5.196 tagged_above=-999 required=5 tests=[AWL=1.053,  BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 Gn9nhz6fXwMe; Mon, 18 Jan 2010 06:05:14 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id CFEF03A6778; Mon, 18 Jan 2010 06:05:13 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail3.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id o0IDo9MX017016 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 18 Jan 2010 15:05:05 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Mon, 18 Jan 2010 15:04:34 +0100
From: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "Hilt, Volker (Volker)" <volker.hilt@alcatel-lucent.com>
Date: Mon, 18 Jan 2010 15:04:32 +0100
Thread-Topic: [dispatch] Chartering SIP Overload
Thread-Index: AcqV89AA79g/BrwHQAi3XXLOVzs8XgCUyaaQ
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE209E4F988@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com> <4B50836A.4020607@ericsson.com>
In-Reply-To: <4B50836A.4020607@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.83
Cc: DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 18 Jan 2010 14:05:15 -0000

I am worried that we are raising the bar on standards track documents.

I am certainly aware that some of the mechanisms described in the documents=
 have been prototyped and have been shown to work. With that, the documenta=
tion merits standards track deliverables.

regards

Keith=20

> -----Original Message-----
> From: dispatch-bounces@ietf.org=20
> [mailto:dispatch-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
> Sent: Friday, January 15, 2010 3:02 PM
> To: Hilt, Volker (Volker)
> Cc: DISPATCH; sip-overload@ietf.org
> Subject: Re: [dispatch] Chartering SIP Overload
>=20
> Hi,
>=20
> > I'm worried that we are taking yet another detour which=20
> will further=20
> > delay the process.
>=20
> this would not delay the process in any way. If something, it=20
> could speed it up, because the requirements to review=20
> Experimental RFCs are lower than to review standards track=20
> RFCs... at the end of the day, I do not expect this to=20
> influence the time it takes to publish the specs because I am=20
> sure the group will make sure the quality of the specs as=20
> high as for a standards-track RFC.
>=20
> Cheers,
>=20
> Gonzalo
>=20
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
> =

From hgs@cs.columbia.edu  Mon Jan 18 10:25:24 2010
Return-Path: <hgs@cs.columbia.edu>
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 BD21B3A69C9; Mon, 18 Jan 2010 10:25:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 gJvXIwYKfh3S; Mon, 18 Jan 2010 10:25:24 -0800 (PST)
Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8]) by core3.amsl.com (Postfix) with ESMTP id D74AE3A6947; Mon, 18 Jan 2010 10:25:23 -0800 (PST)
Received: from new-host.home (pool-173-54-225-147.nwrknj.fios.verizon.net [173.54.225.147]) (user=hgs10 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id o0IIPHca021724 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 18 Jan 2010 13:25:17 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <465AE87E-B62B-4EC0-A68F-1F5ABD6F5D88@softarmor.com>
Date: Mon, 18 Jan 2010 13:25:17 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E40C0DE-34E3-4F12-A1DE-F3C03CE4103A@cs.columbia.edu>
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com> <4B50836A.4020607@ericsson.com> <EDC0A1AE77C57744B664A310A0B23AE209E4F988@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <465AE87E-B62B-4EC0-A68F-1F5ABD6F5D88@softarmor.com>
To: Dean Willis <dean.willis@softarmor.com>
X-Mailer: Apple Mail (2.1077)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.8
Cc: "Hilt, Volker \(Volker\)" <volker.hilt@alcatel-lucent.com>, DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 18 Jan 2010 18:25:24 -0000

In addition, if multiple, independent simulations, published in =
peer-reviewed conferences, are no longer sufficient for standards-track =
designation, I'm at a bit of a loss to figure out what more any =
algorithm-containing protocol spec should do to avoid the "experimental" =
label. We constantly complain that we can't move specs up the maturity =
ladder; now, we can't even get *on* the ladder...

Henning

On Jan 18, 2010, at 1:08 PM, Dean Willis wrote:

>=20
> On Jan 18, 2010, at 8:04 AM, DRAGE, Keith (Keith) wrote:
>=20
>> I am worried that we are raising the bar on standards track =
documents.
>>=20
>> I am certainly aware that some of the mechanisms described in the =
documents have been prototyped and have been shown to work. With that, =
the documentation merits standards track deliverables.
>=20
> Judging from the number of "We have implemented this" responses, it =
might almost be ready to go from Proposed to Draft Standard.
>=20
> --
> Dean
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>=20


From spencer@wonderhamster.org  Mon Jan 18 10:57:12 2010
Return-Path: <spencer@wonderhamster.org>
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 313593A68FD; Mon, 18 Jan 2010 10:57:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[AWL=0.048,  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 aAkutHLq9YVd; Mon, 18 Jan 2010 10:57:11 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 4B84A3A67FB; Mon, 18 Jan 2010 10:57:11 -0800 (PST)
Received: from S73602b (w173.z064002096.dfw-tx.dsl.cnc.net [64.2.96.173]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0Lnghj-1O3XEu1TkF-00hsAi; Mon, 18 Jan 2010 13:57:03 -0500
Message-ID: <3E7B24A71C33413CAE1B6F3D02EBD251@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Dean Willis" <dean.willis@softarmor.com>, "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com><4B50836A.4020607@ericsson.com><EDC0A1AE77C57744B664A310A0B23AE209E4F988@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <465AE87E-B62B-4EC0-A68F-1F5ABD6F5D88@softarmor.com>
Date: Mon, 18 Jan 2010 12:56:32 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1/GJthCw7kcTYRQJilo0/pE3Lx8J9QJljHyzNt TUPl+RnEN2VxnuHLZVaYj+i7goyPd3LXzaYySQ/8H4f0EKcZlM vjAUfyKqG1qGhZwHDlQQcKNvwar/0HM8/pD+dyqRHA=
Cc: "Hilt, Volker \(Volker\)" <volker.hilt@alcatel-lucent.com>, DISPATCH <dispatch@ietf.org>, sip-overload@ietf.org, Lars Eggert <lars.eggert@nokia.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 18 Jan 2010 18:57:12 -0000

Just following up here...

I sent a private e-mail to Robert, Lars and Magnus that might better have 
gone to the mailing list ...

My point was that

- I understand why TSV detours congestion avoidance drafts through 
Experimental, because we already have congestion avoidance mechanisms that 
actually work, so we should be cautious about dorking with them, but

- our standards-track SIP overload mechanisms have already been observed to 
fail on multiple live networks (I've heard this from two tier-one 
operators), so

- it seems appropriate to use a less restrictive strategy here - we 
shouldn't encourage people to ignore our maturity levels completely, and we 
shouldn't use our maturity levels to encourage people to continue deploying 
standards-track mechanisms that have already been observed to fail, and are 
not self-correcting when they fail, on production networks.

That fails the "first, do no harm" test. IMO, of course.

Spencer, whose first working group was a TSV-classic working group (PILC 
with Aaron Falk), and whose first RFC credit was on TCP congestion avoidance 
behavior ("TCP over Satellite", edited by Mark Allman)


>
> On Jan 18, 2010, at 8:04 AM, DRAGE, Keith (Keith) wrote:
>
>> I am worried that we are raising the bar on standards track documents.
>>
>> I am certainly aware that some of the mechanisms described in the 
>> documents have been prototyped and have been shown to work. With  that, 
>> the documentation merits standards track deliverables.
>
> Judging from the number of "We have implemented this" responses, it  might 
> almost be ready to go from Proposed to Draft Standard.
>
> --
> Dean
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch 


From jmpolk@cisco.com  Mon Jan 18 11:23:48 2010
Return-Path: <jmpolk@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 7AA5F3A67DA for <sip-overload@core3.amsl.com>; Mon, 18 Jan 2010 11:23:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.699
X-Spam-Level: 
X-Spam-Status: No, score=-10.699 tagged_above=-999 required=5 tests=[AWL=-0.100, 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 0uaUaPRvWNeP for <sip-overload@core3.amsl.com>; Mon, 18 Jan 2010 11:23:47 -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 921EE3A6858 for <sip-overload@ietf.org>; Mon, 18 Jan 2010 11:23:47 -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: AqAFAFxEVEurR7Hu/2dsb2JhbACHBIhosUqUGIQzBA
X-IronPort-AV: E=Sophos;i="4.49,298,1262563200"; d="scan'208";a="468820966"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-6.cisco.com with ESMTP; 18 Jan 2010 19:23:44 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o0IJNiMq017035; Mon, 18 Jan 2010 19:23:44 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 18 Jan 2010 11:23:44 -0800
Received: from jmpolk-wxp01.cisco.com ([10.89.8.235]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 18 Jan 2010 11:23:43 -0800
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 18 Jan 2010 13:23:41 -0600
To: sip-overload@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <XFE-SJC-2119KuERIqV000019c9@xfe-sjc-211.amer.cisco.com>
X-OriginalArrivalTime: 18 Jan 2010 19:23:43.0780 (UTC) FILETIME=[BFAB0E40:01CA9873]
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Lars Eggert <lars.eggert@nokia.com>
Subject: [sip-overload] Fwd: Re: [dispatch] Chartering SIP Overload
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, 18 Jan 2010 19:23:48 -0000

It appears that multiple threads on different lists are talking about 
the same subject. I just sent this to another list, that this list 
ought to see IMO

James

>Date: Mon, 18 Jan 2010 13:21:01 -0600
>To: "Bernard Aboba" <bernard_aboba@hotmail.com>, <dispatch@ietf.org>
>From: "James M. Polk" <jmpolk@cisco.com>
>Subject: Re: [dispatch] Chartering SIP Overload
>Cc: Lars Eggert <lars.eggert@nokia.com>, Magnus Westerlund 
><magnus.westerlund@ericsson.com>
>
>At 01:08 PM 1/18/2010, Bernard Aboba wrote:
>>Content-Type: multipart/alternative;
>>         boundary="----=_NextPart_000_0676_01CA982E.930534F0"
>>Content-Language: en-us
>>
>>Henning said:
>>
>>"In addition, if multiple, independent simulations, published in 
>>peer-reviewed conferences, are no longer sufficient for 
>>standards-track designation, I'm at a bit of a loss to figure out 
>>what more any algorithm-containing protocol spec should do to avoid 
>>the "experimental" label. We constantly complain that we can't move 
>>specs up the maturity ladder; now, we can't even get *on* the ladder..."
>>
>>[BA] Experimental RFCs can subsequently be placed on the standards 
>>track, based on implementation evidence.  This is routinely done in 
>>the Transport Area, for example.
>>
>>IMHO, the major difference between "Experimental" and "Proposed" in 
>>this particular case would be whether the algorithm is considered 
>>safe for mass deployment on the Internet.   If we have enough 
>>information from existing implementations to know that there is no 
>>potential for congestive collapse or other catastrophic failures, 
>>then the document should be allowed to be published as a Proposed 
>>Standard.  Rather than writing this into the charter, the WG and 
>>IESG could be allowed to make the determination based on the 
>>evidence presented within the WG.  The process for making this 
>>judgment is relatively well established (at least within the Transport Area).
>
>Bernard
>
>Transport is focus on congestion, sure, but it is focused on 
>congestion when a protocol can't do anything about the congestion 
>(i.e., something has to be done because the protocol can't react 
>appropriately on its own to address or solve congestion -- for 
>something like HTTP or FTP, not about TCP vs UDP).
>
>Overload effort is what can be done in SIP to help alleviate the TCP 
>vs UDP issues at a SIP entity.  I'd argue that isn't so much about 
>TCP or SCTP or DCCP or UDP -- would you?
>
>As far as the protocol is concerned, a SIP server (whether it is 
>experiencing congestion or not) is a destination entity, not a 
>transit entity like a classic router. That makes this scenario wrt 
>Overload special, if not unique compared to other transport protocols.
>
>I don't believe it ought to be treated or thought of in the same 
>light as other transport solutions to congestion.
>
>>_______________________________________________
>>dispatch mailing list
>>dispatch@ietf.org
>>https://www.ietf.org/mailman/listinfo/dispatch


From dean.willis@softarmor.com  Mon Jan 18 10:09:07 2010
Return-Path: <dean.willis@softarmor.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 CE3B33A68E6; Mon, 18 Jan 2010 10:09:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 gh1yK9LXIfhD; Mon, 18 Jan 2010 10:09:07 -0800 (PST)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 142183A6877; Mon, 18 Jan 2010 10:09:07 -0800 (PST)
Received: from [10.188.233.210] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may be forged)) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id o0II8q0U022892 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 18 Jan 2010 12:08:55 -0600
Message-Id: <465AE87E-B62B-4EC0-A68F-1F5ABD6F5D88@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE209E4F988@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 18 Jan 2010 12:08:47 -0600
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com> <4B50836A.4020607@ericsson.com> <EDC0A1AE77C57744B664A310A0B23AE209E4F988@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
X-Mailer: Apple Mail (2.936)
X-Mailman-Approved-At: Mon, 18 Jan 2010 11:26:13 -0800
Cc: "Hilt, Volker \(Volker\)" <volker.hilt@alcatel-lucent.com>, DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 18 Jan 2010 18:09:07 -0000

On Jan 18, 2010, at 8:04 AM, DRAGE, Keith (Keith) wrote:

> I am worried that we are raising the bar on standards track documents.
>
> I am certainly aware that some of the mechanisms described in the  
> documents have been prototyped and have been shown to work. With  
> that, the documentation merits standards track deliverables.

Judging from the number of "We have implemented this" responses, it  
might almost be ready to go from Proposed to Draft Standard.

--
Dean

From lars.eggert@nokia.com  Mon Jan 18 11:18:10 2010
Return-Path: <lars.eggert@nokia.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 50F0D3A659C; Mon, 18 Jan 2010 11:18:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.566
X-Spam-Level: 
X-Spam-Status: No, score=-6.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, 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 FfATJBaUZVo9; Mon, 18 Jan 2010 11:18:09 -0800 (PST)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 61EB73A67DA; Mon, 18 Jan 2010 11:18:09 -0800 (PST)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx09.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o0IJHx9f032675; Mon, 18 Jan 2010 13:18:00 -0600
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 18 Jan 2010 21:17:59 +0200
Received: from mgw-sa01.ext.nokia.com ([147.243.1.47]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 18 Jan 2010 21:17:59 +0200
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-sa01.ext.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o0IJHulO007966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Jan 2010 21:17:57 +0200
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.95.3 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: multipart/signed; boundary=Apple-Mail-5--80254844; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <3E7B24A71C33413CAE1B6F3D02EBD251@china.huawei.com>
Date: Mon, 18 Jan 2010 21:17:50 +0200
Message-Id: <4F5CCE81-E5E6-4550-A737-A33E78F77F36@nokia.com>
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com><4B50836A.4020607@ericsson.com><EDC0A1AE77C57744B664A310A0B23AE209E4F988@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <465AE87E-B62B-4EC0-A68F-1F5ABD6F5D88@softarmor.com> <3E7B24A71C33413CAE1B6F3D02EBD251@china.huawei.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
X-Mailer: Apple Mail (2.1077)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (mail.fit.nokia.com [0.0.0.0]); Mon, 18 Jan 2010 21:17:50 +0200 (EET)
X-OriginalArrivalTime: 18 Jan 2010 19:17:59.0082 (UTC) FILETIME=[F23650A0:01CA9872]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Mon, 18 Jan 2010 11:26:13 -0800
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Dean Willis <dean.willis@softarmor.com>, "Hilt, Volker \(Volker\)" <volker.hilt@alcatel-lucent.com>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 18 Jan 2010 19:18:10 -0000

--Apple-Mail-5--80254844
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

could someone send me a pointer to the latest experimental or simulation =
results for the various proposed mechanisms? I want to make sure I've =
seen the latest data.

I'm not on this list, so apologies if I have missed this.

On 2010-1-18, at 20:56, Spencer Dawkins wrote:
> - it seems appropriate to use a less restrictive strategy here - we=20
> shouldn't encourage people to ignore our maturity levels completely, =
and we=20
> shouldn't use our maturity levels to encourage people to continue =
deploying=20
> standards-track mechanisms that have already been observed to fail, =
and are=20
> not self-correcting when they fail, on production networks.

I fully agree that the proposed mechanisms (that I've seen) are better =
than what we currently have (which is almost nothing.) I'm by no means =
opposed to doing this work. It's also extremely encouraging that these =
mechanisms are actively being developed, analyzed, deployed and =
monitored.

My main concern in a nutshell is: Do we have have one mechanism of which =
we are confident that it (1) operates very well in many deployment =
scenarios, (2) degrades gracefully (i.e., doesn't oscillate, etc.) in =
cases where it doesn't work very well and (3) is never worse than what =
we currently have?

If we do, then PS is appropriate. If we don't, then IMO publishing PS =
sends the wrong signal to deployers.

I've personally not seen enough data to convince me of (1) and (2) - but =
maybe I've missed some work, hence the request at the beginning of the =
email.

Lars=

--Apple-Mail-5--80254844
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGbDCCAyUw
ggKOoAMCAQICEAdjk36sXKbnVn15S0/qUp0wDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDYxNTExMjYxNFoXDTEwMDYxNTExMjYx
NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA7mR8A+Pn0/FsUkMX6Pyjw+FL3IFcJk8GaKV5VJ40TMI0Wh8oq20cqA9X
uqnVDW9WztKwH+o+msJenLwWpprbpJm4TImYGbnUJxYyN8gb81aiX1Bw2xCpJ5z3H2+8DsReJLuY
Rdl4bVvaIxLIL4odmfsRwzPyNkOK8LRtfl6OPcaDOlFWzbikULfIVGGu7BqK4lxQSpYwwpZkOMOB
6nnBSfUOtBEmqO+qZG/nL/JxWFV5vxQgg4XHbsMMTxFf6+ji18BD09BUIfDLTuJoCzFmQhrM9vLT
VuRhHWSL20LoafGjXv6mPt3i9IGJHpVb2dMQUgOgRyWHTKiUJVU/rUTdWwIDAQABo14wXDAqBgUr
ZQEEAQQhMB8CAQAwGjAYAgEEBBNMMnVNeWZmQk5VYk5KSmNkWjJzMCAGA1UdEQQZMBeBFWxhcnMu
ZWdnZXJ0QG5va2lhLmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBADUx+67n98wt
I1vydB90HeSZP4Y64VCxxb0NxGGFvfc2+JdVKeHJ/xT+l+ygYKsWNwJJprkPi4WZ5G0crkq4VK1H
5drEJIztpSPVfWI05vPidaaGuuuCR+6MvJMtOTEYEvc/6eovBnkrzRf9x5x5EyuJXAWTeuBADg80
QI3vQ1tZMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTAT
BgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUg
Q29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIG
A1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25h
bC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjEL
MAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNV
BAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUA
A4GNADCBiQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAK
MNcCY1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7
n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAw
QwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJl
ZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRl
TGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9M
Ibj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowg
T2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCAxAwggMMAgEBMHYw
YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAq
BgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAHY5N+rFym51Z9eUtP
6lKdMAkGBSsOAwIaBQCgggFvMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkF
MQ8XDTEwMDExODE5MTc1MFowIwYJKoZIhvcNAQkEMRYEFI4o3iwd4iHiUO9uPjknCFFWD3GiMIGF
BgkrBgEEAYI3EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGlu
ZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBD
QQIQB2OTfqxcpudWfXlLT+pSnTCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUw
IwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVy
c29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQB2OTfqxcpudWfXlLT+pSnTANBgkqhkiG9w0BAQEF
AASCAQDMGTwvu61UTLBpttaSX5OWww2bUyoKr3VaGBqMgHSeTohb5YLq4GMVl5vzB0DGG81T/zlu
VbfFJGXgiCEi9SxXfIVfVdTpt1tL3cElM3khNB+O4FLkwfRRUqu0I1GOtrC+dt8epxHFoKu4664S
FzHeyAPyv9ceBl6fLLGJ9qCvJxKV8l3fD86UhUaDFz2OwAWPKKP95pKZma7irr0yhJOmgLohJomJ
IGB8L45YcGF2vvrwDpJFA1l6k4tuXQ0hJXhVXwyl9KqqIp9OvhJ8k+LqiICmNRvWAWSe7TI9rVtN
rvUua8vM35gjryLvcADmSLuVsn+GRmvwES/fbLHO3PYNAAAAAAAA

--Apple-Mail-5--80254844--

From volker.hilt@alcatel-lucent.com  Mon Jan 18 12:08:09 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 5F2C53A67E1; Mon, 18 Jan 2010 12:08:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  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 Z4FWXauneHGX; Mon, 18 Jan 2010 12:08:08 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 62D0D3A67ED; Mon, 18 Jan 2010 12:08:08 -0800 (PST)
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 o0IK82xo029521;  Mon, 18 Jan 2010 14:08:02 -0600 (CST)
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 o0IK82rH018886; Mon, 18 Jan 2010 14:08:02 -0600 (CST)
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.1.375.2; Mon, 18 Jan 2010 14:08:01 -0600
Message-ID: <4B54BF3B.3020802@alcatel-lucent.com>
Date: Mon, 18 Jan 2010 15:06:19 -0500
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.5) Gecko/20091204 Thunderbird/3.0
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com><4B50836A.4020607@ericsson.com><EDC0A1AE77C57744B664A310A0B23AE209E4F988@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <465AE87E-B62B-4EC0-A68F-1F5ABD6F5D88@softarmor.com> <3E7B24A71C33413CAE1B6F3D02EBD251@china.huawei.com> <4F5CCE81-E5E6-4550-A737-A33E78F77F36@nokia.com>
In-Reply-To: <4F5CCE81-E5E6-4550-A737-A33E78F77F36@nokia.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: Mon, 18 Jan 2010 12:09:04 -0800
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 18 Jan 2010 20:08:09 -0000

Lars,

here is a list of papers on SIP overload that are referenced in 
http://tools.ietf.org/html/draft-ietf-sipping-overload-design-02:
- Hilt, V. and I. Widjaja, "Controlling Overload in Networks of SIP 
Servers", IEEE International Conference on Network Protocols (ICNP'08), 
Orlando, Florida, October 2008.
- Noel, E. and C. Johnson, "Initial Simulation Results That Analyze SIP 
Based VoIP Networks Under Overload", International Teletraffic Congress 
(ITC'07), Ottawa, Canada, June 2007.
- Shen, C., Schulzrinne, H., and E. Nahum, "Session Initiation Protocol 
(SIP) Server Overload Control: Design and Evaluation, Principles", 
Systems and Applications of IP Telecommunications (IPTComm'08), 
Heidelberg, Germany, July 2008.

More papers are referenced in these papers.

In addition, there were presentations at IETF meetings including
- IETF 74 SIPPING 
(http://www.ietf.org/proceedings/74/slides/sipping-11/sipping-11.htm),
- IETF 73 SIPPING 
(http://www.ietf.org/proceedings/73/slides/sipping-8/sipping-8.htm),
- IETF 71 TSVAREA 
(http://www.ietf.org/proceedings/71/slides/tsvarea-3/tsvarea-3.htm)

Volker




On 1/18/2010 2:17 PM, Lars Eggert wrote:
> Hi,
>
> could someone send me a pointer to the latest experimental or
> simulation results for the various proposed mechanisms? I want to
> make sure I've seen the latest data.
>
> I'm not on this list, so apologies if I have missed this.
>
> On 2010-1-18, at 20:56, Spencer Dawkins wrote:
>> - it seems appropriate to use a less restrictive strategy here -
>> we shouldn't encourage people to ignore our maturity levels
>> completely, and we shouldn't use our maturity levels to encourage
>> people to continue deploying standards-track mechanisms that have
>> already been observed to fail, and are not self-correcting when
>> they fail, on production networks.
>
> I fully agree that the proposed mechanisms (that I've seen) are
> better than what we currently have (which is almost nothing.) I'm by
> no means opposed to doing this work. It's also extremely encouraging
> that these mechanisms are actively being developed, analyzed,
> deployed and monitored.
>
> My main concern in a nutshell is: Do we have have one mechanism of
> which we are confident that it (1) operates very well in many
> deployment scenarios, (2) degrades gracefully (i.e., doesn't
> oscillate, etc.) in cases where it doesn't work very well and (3) is
> never worse than what we currently have?
>
> If we do, then PS is appropriate. If we don't, then IMO publishing PS
> sends the wrong signal to deployers.
>
> I've personally not seen enough data to convince me of (1) and (2) -
> but maybe I've missed some work, hence the request at the beginning
> of the email.
>
> Lars


From hgs@cs.columbia.edu  Mon Jan 18 14:43:13 2010
Return-Path: <hgs@cs.columbia.edu>
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 59EE23A67F4; Mon, 18 Jan 2010 14:43:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 hCxINmobn4GJ; Mon, 18 Jan 2010 14:43:12 -0800 (PST)
Received: from serrano.cc.columbia.edu (serrano.cc.columbia.edu [128.59.29.6]) by core3.amsl.com (Postfix) with ESMTP id 407813A67D1; Mon, 18 Jan 2010 14:43:12 -0800 (PST)
Received: from upstairs.home (pool-173-54-225-147.nwrknj.fios.verizon.net [173.54.225.147]) (user=hgs10 mech=PLAIN bits=0) by serrano.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id o0IMh4In014825 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 18 Jan 2010 17:43:04 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <4F5CCE81-E5E6-4550-A737-A33E78F77F36@nokia.com>
Date: Mon, 18 Jan 2010 17:43:04 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC50A533-9D71-4E23-8972-1BD02936CB0B@cs.columbia.edu>
References: <4B505018.7020504@ericsson.com> <4B507FD9.4010407@bell-labs.com><4B50836A.4020607@ericsson.com><EDC0A1AE77C57744B664A310A0B23AE209E4F988@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <465AE87E-B62B-4EC0-A68F-1F5ABD6F5D88@softarmor.com> <3E7B24A71C33413CAE1B6F3D02EBD251@china.huawei.com> <4F5CCE81-E5E6-4550-A737-A33E78F77F36@nokia.com>
To: Lars Eggert <lars.eggert@nokia.com>
X-Mailer: Apple Mail (2.1077)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.6
Cc: "Hilt, Volker \(Volker\)" <volker.hilt@alcatel-lucent.com>, DISPATCH <dispatch@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: Re: [sip-overload] [dispatch] Chartering SIP Overload
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, 18 Jan 2010 22:43:13 -0000

>=20
> I fully agree that the proposed mechanisms (that I've seen) are better =
than what we currently have (which is almost nothing.) I'm by no means =
opposed to doing this work. It's also extremely encouraging that these =
mechanisms are actively being developed, analyzed, deployed and =
monitored.
>=20
> My main concern in a nutshell is: Do we have have one mechanism of =
which we are confident that it (1) operates very well in many deployment =
scenarios, (2) degrades gracefully (i.e., doesn't oscillate, etc.) in =
cases where it doesn't work very well and (3) is never worse than what =
we currently have?

I don't see how you can prove a negative, even if we simulate (or =
implement) for another ten years. There's always the theoretical =
possibility that some constellation of the moon and the operating system =
will cause undesirable behavior. Thus, your bar is provably impossible =
to meet.

That said, I think the proponents of various congestion control =
mechanisms can indeed do a better job describing the inherent limitation =
of some of the algorithms. In particular, the issue is with cases of a =
very large number of upstream proxies (say, hundreds to thousands). Just =
as with flow control, you can design for inherent safety, but there's a =
limit of how many active connections you can allow. In a UDP-based =
system where all the world's proxies can theoretically conspire to send =
a SIP INVITE to the "victim" at 5 pm EST today, no SIP congestion =
control can help since the "victim" can't know that universe of senders. =
But TCP (or SCTP) has exactly the same problem, at connection setup. =
This is one instance of the SIP avalanche problem discussed separately, =
but which hasn't received as much attention.

Thus, I think the problem is more usefully scoped, we might make more =
progress and limit what needs to be evaluated.

>=20
> If we do, then PS is appropriate. If we don't, then IMO publishing PS =
sends the wrong signal to deployers.
>=20
> I've personally not seen enough data to convince me of (1) and (2) - =
but maybe I've missed some work, hence the request at the beginning of =
the email.

It would be more productive, I think, if there was a concrete set of =
benchmarks or test cases. In general, not reflecting your particular =
remarks, I find the typical review remark of "the authors of paper X =
should do more measurements" rather unhelpful.

In response to another email: The analogy to congestion control is only =
helpful to a limited extent, in my view. The system (and algorithms) are =
much closer to TCP flow control, since you don't have the third party =
effects ("cross traffic") and the primary limitation is avoiding buffer =
overflow (or, rather, SIP timer triggering, which amounts to roughly the =
same thing).


Henning


>=20
> Lars_______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

