
From volkerh@bell-labs.com  Wed Sep  2 20:54:20 2009
Return-Path: <volkerh@bell-labs.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 45DC93A6938 for <sip-overload@core3.amsl.com>; Wed,  2 Sep 2009 20:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=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 zuGEBIk6ytqd for <sip-overload@core3.amsl.com>; Wed,  2 Sep 2009 20:54:19 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 88CDA3A6822 for <sip-overload@ietf.org>; Wed,  2 Sep 2009 20:54:15 -0700 (PDT)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id n832NS35028877 for <sip-overload@ietf.org>; Wed, 2 Sep 2009 21:23:28 -0500 (CDT)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id n832NSRx017826 for <sip-overload@ietf.org>; Wed, 2 Sep 2009 21:23:28 -0500 (CDT)
Received: from [127.0.0.1] (135.3.63.242) by USNAVSXCHHUB01.ndc.alcatel-lucent.com (135.3.39.110) with Microsoft SMTP Server (TLS) id 8.1.375.2; Wed, 2 Sep 2009 21:23:27 -0500
Message-ID: <4A9F288F.1080304@bell-labs.com>
Date: Wed, 2 Sep 2009 22:23:11 -0400
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: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Subject: [sip-overload] no call tomorrow
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-overload>, <mailto:sip-overload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-overload>
List-Post: <mailto:sip-overload@ietf.org>
List-Help: <mailto:sip-overload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-overload>, <mailto:sip-overload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2009 03:54:20 -0000

We don't have an agenda item for tomorrows call. Unless something urgent 
comes up I would propose to cancel the call.

Thanks,

Volker

From volkerh@bell-labs.com  Fri Sep  4 08:44:49 2009
Return-Path: <volkerh@bell-labs.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 24A4128C107 for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 08:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.638
X-Spam-Level: 
X-Spam-Status: No, score=-1.638 tagged_above=-999 required=5 tests=[AWL=-0.528, BAYES_05=-1.11]
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 MoP8nICJkjoX for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 08:44:48 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 698EE3A6A38 for <sip-overload@ietf.org>; Fri,  4 Sep 2009 08:44:45 -0700 (PDT)
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 n84Fic1m017407;  Fri, 4 Sep 2009 10:44:38 -0500 (CDT)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id n84FibZ6008401; Fri, 4 Sep 2009 10:44:38 -0500 (CDT)
Received: from [127.0.0.1] (135.3.63.242) by USNAVSXCHHUB01.ndc.alcatel-lucent.com (135.3.39.110) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 4 Sep 2009 10:44:37 -0500
Message-ID: <4AA135D5.9000600@bell-labs.com>
Date: Fri, 4 Sep 2009 11:44:21 -0400
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: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: [sip-overload] Interest in a SIP Overload WG - URGENT
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, 04 Sep 2009 15:44:49 -0000

All,

the DISPATCH WG is trying to gauge the interest in moving forward with 
the SIP Overload Control work as we had no discussion on the dispatch list.

So please respond to this email if your are
- interested in actively contributing to a standard AND
- have the cycles needed to do so

To avoid spamming please remove "sip-overload@iet.org" from the To of 
your response.

If the interest in this work has ceased and there are not enough people 
willing and able to actively contribute, we will not move forward with it.

Thanks,

Volker

From mdolly@att.com  Fri Sep  4 08:51:44 2009
Return-Path: <mdolly@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 CC1213A6A38 for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 08:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.386
X-Spam-Level: 
X-Spam-Status: No, score=-106.386 tagged_above=-999 required=5 tests=[AWL=0.214, 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 8oKD1WYiv+bl for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 08:51:44 -0700 (PDT)
Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.241.147]) by core3.amsl.com (Postfix) with ESMTP id D900F3A6A17 for <sip-overload@ietf.org>; Fri,  4 Sep 2009 08:51:43 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: mdolly@att.com
X-Msg-Ref: server-2.tower-146.messagelabs.com!1252079489!17482027!1
X-StarScan-Version: 6.1.3; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 25484 invoked from network); 4 Sep 2009 15:51:29 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-2.tower-146.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2009 15:51:29 -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 n84FpQ9j028671 for <sip-overload@ietf.org>; Fri, 4 Sep 2009 11:51:26 -0400
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id n84FpGNO028594 for <sip-overload@ietf.org>; Fri, 4 Sep 2009 11:51:21 -0400
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, 4 Sep 2009 11:50:16 -0400
Message-ID: <14C85D6CCBE92743AF33663BF5D24EBA042BB89F@gaalpa1msgusr7e.ugd.att.com>
In-Reply-To: <4AA135D5.9000600@bell-labs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] Interest in a SIP Overload WG - URGENT
Thread-Index: AcotdrfEUb193S2XSEqfWVZ6a1E2xwAAEHjQ
References: <4AA135D5.9000600@bell-labs.com>
From: "DOLLY, MARTIN C, ATTLABS" <mdolly@att.com>
To: "Volker Hilt" <volkerh@bell-labs.com>, <sip-overload@ietf.org>
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [sip-overload] Interest in a SIP Overload WG - URGENT
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, 04 Sep 2009 15:51:44 -0000

Volker,

This is very important work. The design team are experts from the SP and
vendor communities. Lack of "list" discussion should is not metric here,
and/or other topics.

Regards,

Martin

-----Original Message-----
From: sip-overload-bounces@ietf.org
[mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt
Sent: Friday, September 04, 2009 11:44 AM
To: sip-overload@ietf.org
Cc: Gonzalo Camarillo
Subject: [sip-overload] Interest in a SIP Overload WG - URGENT

All,

the DISPATCH WG is trying to gauge the interest in moving forward with=20
the SIP Overload Control work as we had no discussion on the dispatch
list.

So please respond to this email if your are
- interested in actively contributing to a standard AND
- have the cycles needed to do so

To avoid spamming please remove "sip-overload@iet.org" from the To of=20
your response.

If the interest in this work has ceased and there are not enough people=20
willing and able to actively contribute, we will not move forward with
it.

Thanks,

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

From ecnoel@att.com  Fri Sep  4 09:04:18 2009
Return-Path: <ecnoel@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 BB09E3A6891 for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 09:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.49
X-Spam-Level: 
X-Spam-Status: No, score=-105.49 tagged_above=-999 required=5 tests=[AWL=1.110, 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 UNcOsDsOANXM for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 09:04:18 -0700 (PDT)
Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.242.3]) by core3.amsl.com (Postfix) with ESMTP id B72B33A67AA for <sip-overload@ietf.org>; Fri,  4 Sep 2009 09:04:17 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: ecnoel@att.com
X-Msg-Ref: server-12.tower-121.messagelabs.com!1252079755!25098399!1
X-StarScan-Version: 6.1.3; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 32480 invoked from network); 4 Sep 2009 15:55:55 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-12.tower-121.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2009 15:55:55 -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 n84Ftu63030165 for <sip-overload@ietf.org>; Fri, 4 Sep 2009 11:55:56 -0400
Received: from misout7msgusr7b.ugd.att.com (misout7msgusr7b.ugd.att.com [144.155.43.104]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id n84FtoAS030146 for <sip-overload@ietf.org>; Fri, 4 Sep 2009 11:55:50 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 4 Sep 2009 11:54:45 -0400
Message-ID: <5DA01D2CA74FAF40ADF71DB4177D345A01B1C972@misout7msgusr7b.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] Interest in a SIP Overload WG - URGENT
Thread-Index: AcotdrXgzOOzDSoTRRmju9npl8qN9gAAVAP0
References: <4AA135D5.9000600@bell-labs.com>
From: "NOEL, ERIC C, ATTLABS" <ecnoel@att.com>
To: "Volker Hilt" <volkerh@bell-labs.com>, <sip-overload@ietf.org>
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [sip-overload] Interest in a SIP Overload WG - URGENT
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, 04 Sep 2009 16:04:18 -0000

Volker,

Please count me in (standard contributor with cycles to do so).

Thanks,

Eric=20


-----Original Message-----
From: sip-overload-bounces@ietf.org on behalf of Volker Hilt
Sent: Fri 9/4/2009 11:44 AM
To: sip-overload@ietf.org
Cc: Gonzalo Camarillo
Subject: [sip-overload] Interest in a SIP Overload WG - URGENT
=20
All,

the DISPATCH WG is trying to gauge the interest in moving forward with=20
the SIP Overload Control work as we had no discussion on the dispatch =
list.

So please respond to this email if your are
- interested in actively contributing to a standard AND
- have the cycles needed to do so

To avoid spamming please remove "sip-overload@iet.org" from the To of=20
your response.

If the interest in this work has ceased and there are not enough people=20
willing and able to actively contribute, we will not move forward with =
it.

Thanks,

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


From mary.barnes@nortel.com  Fri Sep  4 09:07:03 2009
Return-Path: <mary.barnes@nortel.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 90B1A3A6939 for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 09:07:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.551
X-Spam-Level: 
X-Spam-Status: No, score=-6.551 tagged_above=-999 required=5 tests=[AWL=0.048,  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 93uQFa-PoSV0 for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 09:07:02 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id 790A73A6403 for <sip-overload@ietf.org>; Fri,  4 Sep 2009 09:07:02 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n84G6Au19323; Fri, 4 Sep 2009 16:06:10 GMT
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, 4 Sep 2009 11:08:13 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF1FCA8826@zrc2hxm0.corp.nortel.com>
In-Reply-To: <14C85D6CCBE92743AF33663BF5D24EBA042BB89F@gaalpa1msgusr7e.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] Interest in a SIP Overload WG - URGENT
Thread-Index: AcotdrfEUb193S2XSEqfWVZ6a1E2xwAAEHjQAAA9NEA=
References: <4AA135D5.9000600@bell-labs.com> <14C85D6CCBE92743AF33663BF5D24EBA042BB89F@gaalpa1msgusr7e.ugd.att.com>
From: "Mary Barnes" <mary.barnes@nortel.com>
To: "DOLLY, MARTIN C, ATTLABS" <mdolly@att.com>, "Volker Hilt" <volkerh@bell-labs.com>, <sip-overload@ietf.org>
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [sip-overload] Interest in a SIP Overload WG - URGENT
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, 04 Sep 2009 16:07:03 -0000

Part of what we need to discern here is whether folks are willing to
contribute cycles to solving this problem. By that I mean reviewing
documents in detail, serving as document editors, actively driving issue
resolution on the mailing list, updating documents more often than just
prior to the f2f meetings, etc. =20

I recognize the significant effort by the overload design team that went
into the overload design  document in the SIPPING WG.  So, we need to
assess that the level of commitment to completing the solution work
remains high.  And, the primary guage for making that assessment is the
level of discussion on the mailing list (both this overload list and the
DISPATCH WG list in terms of agreement on the charter/milestones) -
without that, we cannot get the necessary community support or feedback
for the work.=20

Thanks,
Mary.=20

-----Original Message-----
From: DOLLY, MARTIN C, ATTLABS [mailto:mdolly@att.com]=20
Sent: Friday, September 04, 2009 10:50 AM
To: Volker Hilt; sip-overload@ietf.org
Cc: Gonzalo Camarillo; Barnes, Mary (RICH2:AR00)
Subject: RE: [sip-overload] Interest in a SIP Overload WG - URGENT

Volker,

This is very important work. The design team are experts from the SP and
vendor communities. Lack of "list" discussion should is not metric here,
and/or other topics.

Regards,

Martin

-----Original Message-----
From: sip-overload-bounces@ietf.org
[mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt
Sent: Friday, September 04, 2009 11:44 AM
To: sip-overload@ietf.org
Cc: Gonzalo Camarillo
Subject: [sip-overload] Interest in a SIP Overload WG - URGENT

All,

the DISPATCH WG is trying to gauge the interest in moving forward with
the SIP Overload Control work as we had no discussion on the dispatch
list.

So please respond to this email if your are
- interested in actively contributing to a standard AND
- have the cycles needed to do so

To avoid spamming please remove "sip-overload@iet.org" from the To of
your response.

If the interest in this work has ceased and there are not enough people
willing and able to actively contribute, we will not move forward with
it.

Thanks,

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

From D.Malas@cablelabs.com  Fri Sep  4 09:34:23 2009
Return-Path: <D.Malas@cablelabs.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 A769F3A6A4F for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 09:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 D5jvXozm9Sph for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 09:34:22 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id CE9573A6911 for <sip-overload@ietf.org>; Fri,  4 Sep 2009 09:34:22 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with SMTP id n84GXZAF032192; Fri, 4 Sep 2009 10:33:36 -0600
Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com); Fri, 4 Sep 2009 10:33:36 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com)
Received: from 10.4.10.173 ([10.4.10.173]) by srvxchg3.cablelabs.com ([10.5.0.25]) with Microsoft Exchange Server HTTP-DAV ;  Fri,  4 Sep 2009 16:33:36 +0000
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Fri, 04 Sep 2009 10:33:36 -0600
From: Daryl Malas <d.malas@cablelabs.com>
To: Volker Hilt <volkerh@bell-labs.com>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Message-ID: <C6C69D80.4992%d.malas@cablelabs.com>
Thread-Topic: [sip-overload] Re: Interest in a SIP Overload WG - URGENT
Thread-Index: AcotfXMteeqE2mH/ckyh5DElEQ88OA==
In-Reply-To: <4AA135D5.9000600@bell-labs.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Approved: ondar
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: [sip-overload]  Re: Interest in a SIP Overload WG - URGENT
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, 04 Sep 2009 16:34:23 -0000

All,

The problem is not interest in this issue.  The problem is the interest was
there 3 years ago when this problem was introduced.  The other issue is
related working groups tend to be more interested in developing more
features rather than dealing with the operational issues that exist for
service providers.  Since, this is the case, service providers simply ask
their proxy, session border controller, and media gateway vendors to solve
it in an adhoc, proprietary manner in the interim.  Once we finally get
through 2 years of design work and many theoretical discussions the service
provider community thumbs their proverbial nose at the IETF and says we have
it taken care of...thanks, but no thanks (don't believe me...see ICE, NAT,
LNP, History-Info....).  Also, the vendor community says we don't care,
because they've already implemented their proprietary solutions, meeting the
needs of their customers.  Why would they want to invest more time on a
problem they've already "solved"?

With these things in mind, I think the design group did a great job, more
than thorough.  The work they have done should not be left on the shelf to
gain dust for years to come.  Instead, I think a solution should be driven
forward for the community to consider when they realize their proprietary
solutions don't scale for some unknown reason...it will happen.

I desperately wish I had the cycles to invest the time commitment to this
work, but I am knee deep in tasks on the "home front".  My comments are to
encourage the work to continue and discourage throwing it away due to
silence on the mailing list.  The alternative is to "shelf" the work and
address it again when those "scaling" issues come back...maybe they
won't...we can only speculate.

My two cents...

--Daryl


On 9/4/09 9:44 AM, "Volker Hilt" <volkerh@bell-labs.com> wrote:

> All,
> 
> the DISPATCH WG is trying to gauge the interest in moving forward with
> the SIP Overload Control work as we had no discussion on the dispatch list.
> 
> So please respond to this email if your are
> - interested in actively contributing to a standard AND
> - have the cycles needed to do so
> 
> To avoid spamming please remove "sip-overload@iet.org" from the To of
> your response.
> 
> If the interest in this work has ceased and there are not enough people
> willing and able to actively contribute, we will not move forward with it.
> 
> Thanks,
> 
> Volker
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload


-----------------
Daryl Malas
CableLabs
(o) +1 303 661 3302
(f) +1 303 661 9199
mailto:d.malas@cablelabs.com



From TIMOTHY.L.MORAN@saic.com  Fri Sep  4 09:44:57 2009
Return-Path: <TIMOTHY.L.MORAN@saic.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 5D1373A6A77 for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 09:44:57 -0700 (PDT)
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 AelIdtw5DK9N for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 09:44:56 -0700 (PDT)
Received: from mclmx2.mail.saic.com (mclmx2.mail.saic.com [149.8.64.32]) by core3.amsl.com (Postfix) with ESMTP id 74AA33A6A73 for <sip-overload@ietf.org>; Fri,  4 Sep 2009 09:44:56 -0700 (PDT)
Received: from 0015-its-sbg01.saic.com ([149.8.64.21] [149.8.64.21]) by mclmx2.mail.saic.com with ESMTP id BT-MMP-9355612; Fri, 4 Sep 2009 12:45:02 -0400
X-AuditID: 9508401a-b7ceeae00000220a-7a-4aa1440eb61c
Received: from 0015-its-exbh03.us.saic.com (mcl-sixl-nat.saic.com [149.8.64.21]) by  (Symantec Brightmail Gateway) with SMTP id 4D.CC.08714.E0441AA4; Fri,  4 Sep 2009 12:45:02 -0400 (EDT)
Received: from 0015-ITS-EXBH01.us.saic.com ([10.43.229.18]) by 0015-its-exbh03.us.saic.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 4 Sep 2009 12:45:02 -0400
Received: from 0256-its-exmp02.us.saic.com ([10.40.16.18]) by 0015-ITS-EXBH01.us.saic.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 4 Sep 2009 12:45:02 -0400
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, 4 Sep 2009 12:45:01 -0400
Message-Id: <DF6DD917A6E6D34C9619D66816FF0C4F018BD08F@0256-its-exmp02.us.saic.com>
In-Reply-To: <4AA135D5.9000600@bell-labs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] Interest in a SIP Overload WG - URGENT
Thread-Index: AcotdsEgmKidEkjyQjOgZUjU0MwfmAAB7mQg
References: <4AA135D5.9000600@bell-labs.com>
From: "Moran, Timothy L." <TIMOTHY.L.MORAN@saic.com>
To: "Volker Hilt" <volkerh@bell-labs.com>, <sip-overload@ietf.org>
X-OriginalArrivalTime: 04 Sep 2009 16:45:02.0400 (UTC) FILETIME=[0C4DC400:01CA2D7F]
X-Brightmail-Tracker: AAAAAA==
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [sip-overload] Interest in a SIP Overload WG - URGENT
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, 04 Sep 2009 16:44:57 -0000

Volker,

Very important work for those of us supporting the NCS NS/EP NGN
Priority Services program.  Where do you need help -specifically? =20

Br,
Tim M.

-----Original Message-----
From: sip-overload-bounces@ietf.org
[mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt
Sent: Friday, September 04, 2009 11:44 AM
To: sip-overload@ietf.org
Cc: Gonzalo Camarillo
Subject: [sip-overload] Interest in a SIP Overload WG - URGENT

All,

the DISPATCH WG is trying to gauge the interest in moving forward with=20
the SIP Overload Control work as we had no discussion on the dispatch
list.

So please respond to this email if your are
- interested in actively contributing to a standard AND
- have the cycles needed to do so

To avoid spamming please remove "sip-overload@iet.org" from the To of=20
your response.

If the interest in this work has ceased and there are not enough people=20
willing and able to actively contribute, we will not move forward with
it.

Thanks,

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

From charles.newyork@gmail.com  Fri Sep  4 09:48:16 2009
Return-Path: <charles.newyork@gmail.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB6603A6A7C for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 09:48:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 bQ7jrdldqpL9 for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 09:48:16 -0700 (PDT)
Received: from mail-yw0-f203.google.com (mail-yw0-f203.google.com [209.85.211.203]) by core3.amsl.com (Postfix) with ESMTP id EEC493A6A7A for <sip-overload@ietf.org>; Fri,  4 Sep 2009 09:48:15 -0700 (PDT)
Received: by ywh41 with SMTP id 41so143070ywh.31 for <sip-overload@ietf.org>; Fri, 04 Sep 2009 09:48:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=USTPGj5onPL4DwelKfRzKOBfMt7S20lBp6N608WGmw0=; b=MGNXiSSMFLxeYBKQ54VWH/CbBi817F4QXZQrqOhEtamHH3uNtpVbjoeGw4xnmu2mPa noUGlkWv2CZzWHnN3oy4OZPUh85A6A62/UiHDg/apsWdHGdr8bZeEOtUmqY8WCqH721E RGmbVnByUyFY/7H94irBQTlhaLgte1qffkmtg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=jl9yazR0QqtaQEcaueD91pFVS+0M6zdiOYk9jkFdF5ERjsW0PuMCbbW5PfXij+i/6c Pd6LdpKEwmK2jx7rWaSHb5rljsle0Bfwie9b5xKrN7Vv0aSMdzCrn4M1Rd9KFp0QUxgX hOuPfhB0VHmX5sbL+7h/V05WH+Vd4Yfpm2iyg=
MIME-Version: 1.0
Sender: charles.newyork@gmail.com
Received: by 10.151.86.5 with SMTP id o5mr17163413ybl.179.1252082909924; Fri,  04 Sep 2009 09:48:29 -0700 (PDT)
In-Reply-To: <4AA135D5.9000600@bell-labs.com>
References: <4AA135D5.9000600@bell-labs.com>
Date: Fri, 4 Sep 2009 12:48:24 -0400
X-Google-Sender-Auth: be72fbe086a24796
Message-ID: <e7df28360909040948i64982395ue95e25582bd8b49e@mail.gmail.com>
From: Charles Shen <charles@cs.columbia.edu>
To: Volker Hilt <volkerh@bell-labs.com>
Content-Type: multipart/alternative; boundary=000e0cd359aa13e5a00472c3454a
Cc: "sip-overload@ietf.org" <sip-overload@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [sip-overload] Interest in a SIP Overload WG - URGENT
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, 04 Sep 2009 16:48:16 -0000

--000e0cd359aa13e5a00472c3454a
Content-Type: text/plain; charset=UTF-8

Volker: absolutely count me in.

Thanks

Charles



On Fri, Sep 4, 2009 at 11:44 AM, Volker Hilt <volkerh@bell-labs.com> wrote:

> All,
>
> the DISPATCH WG is trying to gauge the interest in moving forward with the
> SIP Overload Control work as we had no discussion on the dispatch list.
>
> So please respond to this email if your are
> - interested in actively contributing to a standard AND
> - have the cycles needed to do so
>
> To avoid spamming please remove "sip-overload@iet.org" from the To of your
> response.
>
> If the interest in this work has ceased and there are not enough people
> willing and able to actively contribute, we will not move forward with it.
>
> Thanks,
>
> Volker
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload
>

--000e0cd359aa13e5a00472c3454a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Volker: absolutely count me in.<br clear=3D"all"><br>Thanks<br><br>Charles<=
br><br>
<br><br><div class=3D"gmail_quote">On Fri, Sep 4, 2009 at 11:44 AM, Volker =
Hilt <span dir=3D"ltr">&lt;<a href=3D"mailto:volkerh@bell-labs.com">volkerh=
@bell-labs.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8e=
x; padding-left: 1ex;">
All,<br>
<br>
the DISPATCH WG is trying to gauge the interest in moving forward with the =
SIP Overload Control work as we had no discussion on the dispatch list.<br>
<br>
So please respond to this email if your are<br>
- interested in actively contributing to a standard AND<br>
- have the cycles needed to do so<br>
<br>
To avoid spamming please remove &quot;<a href=3D"mailto:sip-overload@iet.or=
g" target=3D"_blank">sip-overload@iet.org</a>&quot; from the To of your res=
ponse.<br>
<br>
If the interest in this work has ceased and there are not enough people wil=
ling and able to actively contribute, we will not move forward with it.<br>
<br>
Thanks,<br>
<br>
Volker<br>
_______________________________________________<br>
sip-overload mailing list<br>
<a href=3D"mailto:sip-overload@ietf.org" target=3D"_blank">sip-overload@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sip-overload" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/sip-overload</a><br>
</blockquote></div><br>

--000e0cd359aa13e5a00472c3454a--

From volkerh@bell-labs.com  Fri Sep  4 09:51:15 2009
Return-Path: <volkerh@bell-labs.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 477483A68CD for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 09:51:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.307
X-Spam-Level: 
X-Spam-Status: No, score=-2.307 tagged_above=-999 required=5 tests=[AWL=0.292,  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 Mtyo1qNewGVA for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 09:51:09 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id CD2623A68B2 for <sip-overload@ietf.org>; Fri,  4 Sep 2009 09:51:09 -0700 (PDT)
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 n84GowuC006683;  Fri, 4 Sep 2009 11:50:58 -0500 (CDT)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id n84GowUW020537; Fri, 4 Sep 2009 11:50:58 -0500 (CDT)
Received: from [127.0.0.1] (135.3.63.242) by USNAVSXCHHUB01.ndc.alcatel-lucent.com (135.3.39.110) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 4 Sep 2009 11:50:58 -0500
Message-ID: <4AA14561.10207@bell-labs.com>
Date: Fri, 4 Sep 2009 12:50:41 -0400
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "Moran, Timothy L." <TIMOTHY.L.MORAN@saic.com>
References: <4AA135D5.9000600@bell-labs.com> <DF6DD917A6E6D34C9619D66816FF0C4F018BD08F@0256-its-exmp02.us.saic.com>
In-Reply-To: <DF6DD917A6E6D34C9619D66816FF0C4F018BD08F@0256-its-exmp02.us.saic.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.39
Cc: "sip-overload@ietf.org" <sip-overload@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [sip-overload] Interest in a SIP Overload WG - URGENT
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, 04 Sep 2009 16:51:15 -0000

Timothy,

Mary had listed a few of the tasks ahead in her mail. Essentially we 
need help with reviewing the current drafts, identifying issues that 
need to be resolved and driving these issues forward on the mailing 
list, editing and updating the drafts, etc.

Thanks,

Volker



Moran, Timothy L. wrote:
> Volker,
> 
> Very important work for those of us supporting the NCS NS/EP NGN
> Priority Services program.  Where do you need help -specifically?  
> 
> Br,
> Tim M.
> 
> -----Original Message-----
> From: sip-overload-bounces@ietf.org
> [mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt
> Sent: Friday, September 04, 2009 11:44 AM
> To: sip-overload@ietf.org
> Cc: Gonzalo Camarillo
> Subject: [sip-overload] Interest in a SIP Overload WG - URGENT
> 
> All,
> 
> the DISPATCH WG is trying to gauge the interest in moving forward with 
> the SIP Overload Control work as we had no discussion on the dispatch
> list.
> 
> So please respond to this email if your are
> - interested in actively contributing to a standard AND
> - have the cycles needed to do so
> 
> To avoid spamming please remove "sip-overload@iet.org" from the To of 
> your response.
> 
> If the interest in this work has ceased and there are not enough people 
> willing and able to actively contribute, we will not move forward with
> it.
> 
> Thanks,
> 
> Volker
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload


From aabdelal@sonusnet.com  Fri Sep  4 09:52:09 2009
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 B58DB3A6A7D for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 09:52:09 -0700 (PDT)
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 KPKc1istvlQi for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 09:52:09 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by core3.amsl.com (Postfix) with ESMTP id DD3BB3A6965 for <sip-overload@ietf.org>; Fri,  4 Sep 2009 09:52:08 -0700 (PDT)
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 n84Gpf6e026964;  Fri, 4 Sep 2009 12:51:41 -0400
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, 4 Sep 2009 12:50:47 -0400
Message-ID: <30CC59382F8B084DA5EEC4F7A26001FB010355BD@sonusmail06.sonusnet.com>
In-Reply-To: <4AA135D5.9000600@bell-labs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] Interest in a SIP Overload WG - URGENT
Thread-Index: AcotdpED/lYW7DW/QbalEfH8nbsPuQACTo1Q
References: <4AA135D5.9000600@bell-labs.com>
From: "Abdelal, Ahmed" <aabdelal@sonusnet.com>
To: "Volker Hilt" <volkerh@bell-labs.com>
Cc: sip-overload@ietf.org, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [sip-overload] Interest in a SIP Overload WG - URGENT
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, 04 Sep 2009 16:52:09 -0000

Hi Volker,

Please count me in for this effort.

Thanks,
Ahmed=20


-----Original Message-----
From: sip-overload-bounces@ietf.org
[mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt
Sent: Friday, September 04, 2009 11:44 AM
To: sip-overload@ietf.org
Cc: Gonzalo Camarillo
Subject: [sip-overload] Interest in a SIP Overload WG - URGENT

All,

the DISPATCH WG is trying to gauge the interest in moving forward with=20
the SIP Overload Control work as we had no discussion on the dispatch
list.

So please respond to this email if your are
- interested in actively contributing to a standard AND
- have the cycles needed to do so

To avoid spamming please remove "sip-overload@iet.org" from the To of=20
your response.

If the interest in this work has ceased and there are not enough people=20
willing and able to actively contribute, we will not move forward with
it.

Thanks,

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

From victor.pascual.avila@gmail.com  Fri Sep  4 10:25:08 2009
Return-Path: <victor.pascual.avila@gmail.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 33CC13A67FE for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 10:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.461
X-Spam-Level: 
X-Spam-Status: No, score=-2.461 tagged_above=-999 required=5 tests=[AWL=0.138,  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 y+NSFolLQYiU for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 10:25:07 -0700 (PDT)
Received: from mail-ew0-f207.google.com (mail-ew0-f207.google.com [209.85.219.207]) by core3.amsl.com (Postfix) with ESMTP id 2912E3A67A1 for <sip-overload@ietf.org>; Fri,  4 Sep 2009 10:25:07 -0700 (PDT)
Received: by ewy3 with SMTP id 3so1071145ewy.42 for <sip-overload@ietf.org>; Fri, 04 Sep 2009 10:23:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=lZ++ON5U7Q3uFY1OZdijDTcm4Q2fjaDuLFu7UXM3EvI=; b=lReP9zj2UCuo7WpJIiBc2kLeETVjI54f1fJt0BLTnrmSaTMVSSOmLDC01lJEdc0DqU XFcAlHD87LDvE6lXoHS/Hpb+0Hym4r8017hdKg0Wuw94SPLtVIbClOl/2Pa4RnBFYbsB mormITBkobNnBGxftX7sd8UXDozByiPLoP9qw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=MmyIPNP7fhUjFMjbcxRgaGQLc912SayudUMQDVanHJ3v2hEtbafVKl/PsuCbQYjLeZ R4MuGdAtiAI0mIIfYWcIUmrG0iTAO+mh+Hb15Gcw07m3kzvFs9InrGyvlv+ULM4dfKcn qOJwRKbEsSka/Z4pfQJhgWA7tYftImMh7AuMQ=
MIME-Version: 1.0
Received: by 10.216.91.82 with SMTP id g60mr2200997wef.74.1252084701413; Fri,  04 Sep 2009 10:18:21 -0700 (PDT)
In-Reply-To: <e7df28360909040948i64982395ue95e25582bd8b49e@mail.gmail.com>
References: <4AA135D5.9000600@bell-labs.com> <e7df28360909040948i64982395ue95e25582bd8b49e@mail.gmail.com>
Date: Fri, 4 Sep 2009 19:18:21 +0200
Message-ID: <618e24240909041018w76af7674ofc5e9d8e95e38d6c@mail.gmail.com>
From: Victor Pascual Avila <victor.pascual.avila@gmail.com>
To: Charles Shen <charles@cs.columbia.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Volker Hilt <volkerh@bell-labs.com>, "sip-overload@ietf.org" <sip-overload@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [sip-overload] Interest in a SIP Overload WG - URGENT
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, 04 Sep 2009 17:25:08 -0000

+1

On Fri, Sep 4, 2009 at 6:48 PM, Charles Shen<charles@cs.columbia.edu> wrote=
:
> Volker: absolutely count me in.
>
> Thanks
>
> Charles
>
>
>
> On Fri, Sep 4, 2009 at 11:44 AM, Volker Hilt <volkerh@bell-labs.com> wrot=
e:
>>
>> All,
>>
>> the DISPATCH WG is trying to gauge the interest in moving forward with t=
he
>> SIP Overload Control work as we had no discussion on the dispatch list.
>>
>> So please respond to this email if your are
>> - interested in actively contributing to a standard AND
>> - have the cycles needed to do so
>>
>> To avoid spamming please remove "sip-overload@iet.org" from the To of yo=
ur
>> response.
>>
>> If the interest in this work has ceased and there are not enough people
>> willing and able to actively contribute, we will not move forward with i=
t.
>>
>> Thanks,
>>
>> Volker
>> _______________________________________________
>> 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
>
>



--=20
Victor Pascual =C3=81vila

From jgunn6@csc.com  Fri Sep  4 11:31:50 2009
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 65D0F3A6819; Fri,  4 Sep 2009 11:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.404
X-Spam-Level: 
X-Spam-Status: No, score=-6.404 tagged_above=-999 required=5 tests=[AWL=0.194,  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 sfIrD16vBtWV; Fri,  4 Sep 2009 11:31:47 -0700 (PDT)
Received: from mail168.messagelabs.com (mail168.messagelabs.com [216.82.253.195]) by core3.amsl.com (Postfix) with ESMTP id B673A3A6824; Fri,  4 Sep 2009 11:31:43 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-13.tower-168.messagelabs.com!1252089049!12510679!1
X-StarScan-Version: 6.1.3; banners=-,-,-
X-Originating-IP: [20.137.2.87]
Received: (qmail 1215 invoked from network); 4 Sep 2009 18:30:50 -0000
Received: from amer-mta101.csc.com (HELO amer-mta101.csc.com) (20.137.2.87) by server-13.tower-168.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2009 18:30:50 -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 n84IUjLZ010317; Fri, 4 Sep 2009 14:30:45 -0400
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1FCA8826@zrc2hxm0.corp.nortel.com>
To: "Mary Barnes" <mary.barnes@nortel.com>, Richard F Kaczmarek <rkaczmarek@csc.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes 652HF83 November 04, 2004
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF45707F57.5EA9BE8F-ON85257627.0064B14D-85257627.0065AF9E@csc.com>
Date: Fri, 4 Sep 2009 14:30:48 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.0.1 HF996|December 23, 2008) at 09/04/2009 02:32:25 PM, Serialize complete at 09/04/2009 02:32:25 PM
Content-Type: multipart/alternative; boundary="=_alternative 0065AE6B85257627_="
X-Mailman-Approved-At: Fri, 04 Sep 2009 12:17:18 -0700
Cc: sip-overload-bounces@ietf.org, sip-overload@ietf.org, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Max Puckett <fpuckett@csc.com>, Volker Hilt <volkerh@bell-labs.com>, Dennis Q Berg <dberg3@csc.com>
Subject: Re: [sip-overload] Interest in a SIP Overload WG - URGENT
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, 04 Sep 2009 18:31:50 -0000

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

Mary,

This is VERY important to us.

I will make sure we have the cycles for review, edit, update, and 
resolving issues.

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.



"Mary Barnes" <mary.barnes@nortel.com> 
Sent by: sip-overload-bounces@ietf.org
09/04/2009 12:08 PM

To
"DOLLY, MARTIN C, ATTLABS" <mdolly@att.com>, "Volker Hilt" 
<volkerh@bell-labs.com>, <sip-overload@ietf.org>
cc
Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject
Re: [sip-overload] Interest in a SIP Overload WG - URGENT






Part of what we need to discern here is whether folks are willing to
contribute cycles to solving this problem. By that I mean reviewing
documents in detail, serving as document editors, actively driving issue
resolution on the mailing list, updating documents more often than just
prior to the f2f meetings, etc. 

I recognize the significant effort by the overload design team that went
into the overload design  document in the SIPPING WG.  So, we need to
assess that the level of commitment to completing the solution work
remains high.  And, the primary guage for making that assessment is the
level of discussion on the mailing list (both this overload list and the
DISPATCH WG list in terms of agreement on the charter/milestones) -
without that, we cannot get the necessary community support or feedback
for the work. 

Thanks,
Mary. 

-----Original Message-----
From: DOLLY, MARTIN C, ATTLABS [mailto:mdolly@att.com] 
Sent: Friday, September 04, 2009 10:50 AM
To: Volker Hilt; sip-overload@ietf.org
Cc: Gonzalo Camarillo; Barnes, Mary (RICH2:AR00)
Subject: RE: [sip-overload] Interest in a SIP Overload WG - URGENT

Volker,

This is very important work. The design team are experts from the SP and
vendor communities. Lack of "list" discussion should is not metric here,
and/or other topics.

Regards,

Martin

-----Original Message-----
From: sip-overload-bounces@ietf.org
[mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt
Sent: Friday, September 04, 2009 11:44 AM
To: sip-overload@ietf.org
Cc: Gonzalo Camarillo
Subject: [sip-overload] Interest in a SIP Overload WG - URGENT

All,

the DISPATCH WG is trying to gauge the interest in moving forward with
the SIP Overload Control work as we had no discussion on the dispatch
list.

So please respond to this email if your are
- interested in actively contributing to a standard AND
- have the cycles needed to do so

To avoid spamming please remove "sip-overload@iet.org" from the To of
your response.

If the interest in this work has ceased and there are not enough people
willing and able to actively contribute, we will not move forward with
it.

Thanks,

Volker
_______________________________________________
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


--=_alternative 0065AE6B85257627_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Mary,</font>
<br>
<br><font size=2 face="sans-serif">This is VERY important to us.</font>
<br>
<br><font size=2 face="sans-serif">I will make sure we have the cycles
for review, edit, update, and resolving issues.</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 width=40%><font size=1 face="sans-serif"><b>&quot;Mary Barnes&quot;
&lt;mary.barnes@nortel.com&gt;</b> </font>
<br><font size=1 face="sans-serif">Sent by: sip-overload-bounces@ietf.org</font>
<p><font size=1 face="sans-serif">09/04/2009 12:08 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">&quot;DOLLY, MARTIN C, ATTLABS&quot;
&lt;mdolly@att.com&gt;, &quot;Volker Hilt&quot; &lt;volkerh@bell-labs.com&gt;,
&lt;sip-overload@ietf.org&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">Gonzalo Camarillo &lt;Gonzalo.Camarillo@ericsson.com&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [sip-overload] Interest in a SIP
Overload WG - URGENT</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Part of what we need to discern here is whether folks
are willing to<br>
contribute cycles to solving this problem. By that I mean reviewing<br>
documents in detail, serving as document editors, actively driving issue<br>
resolution on the mailing list, updating documents more often than just<br>
prior to the f2f meetings, etc. &nbsp;<br>
<br>
I recognize the significant effort by the overload design team that went<br>
into the overload design &nbsp;document in the SIPPING WG. &nbsp;So, we
need to<br>
assess that the level of commitment to completing the solution work<br>
remains high. &nbsp;And, the primary guage for making that assessment is
the<br>
level of discussion on the mailing list (both this overload list and the<br>
DISPATCH WG list in terms of agreement on the charter/milestones) -<br>
without that, we cannot get the necessary community support or feedback<br>
for the work. <br>
<br>
Thanks,<br>
Mary. <br>
<br>
-----Original Message-----<br>
From: DOLLY, MARTIN C, ATTLABS [mailto:mdolly@att.com] <br>
Sent: Friday, September 04, 2009 10:50 AM<br>
To: Volker Hilt; sip-overload@ietf.org<br>
Cc: Gonzalo Camarillo; Barnes, Mary (RICH2:AR00)<br>
Subject: RE: [sip-overload] Interest in a SIP Overload WG - URGENT<br>
<br>
Volker,<br>
<br>
This is very important work. The design team are experts from the SP and<br>
vendor communities. Lack of &quot;list&quot; discussion should is not metric
here,<br>
and/or other topics.<br>
<br>
Regards,<br>
<br>
Martin<br>
<br>
-----Original Message-----<br>
From: sip-overload-bounces@ietf.org<br>
[mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt<br>
Sent: Friday, September 04, 2009 11:44 AM<br>
To: sip-overload@ietf.org<br>
Cc: Gonzalo Camarillo<br>
Subject: [sip-overload] Interest in a SIP Overload WG - URGENT<br>
<br>
All,<br>
<br>
the DISPATCH WG is trying to gauge the interest in moving forward with<br>
the SIP Overload Control work as we had no discussion on the dispatch<br>
list.<br>
<br>
So please respond to this email if your are<br>
- interested in actively contributing to a standard AND<br>
- have the cycles needed to do so<br>
<br>
To avoid spamming please remove &quot;sip-overload@iet.org&quot; from the
To of<br>
your response.<br>
<br>
If the interest in this work has ceased and there are not enough people<br>
willing and able to actively contribute, we will not move forward with<br>
it.<br>
<br>
Thanks,<br>
<br>
Volker<br>
_______________________________________________<br>
sip-overload mailing list<br>
sip-overload@ietf.org<br>
https://www.ietf.org/mailman/listinfo/sip-overload<br>
_______________________________________________<br>
sip-overload mailing list<br>
sip-overload@ietf.org<br>
https://www.ietf.org/mailman/listinfo/sip-overload<br>
</tt></font>
<br>
--=_alternative 0065AE6B85257627_=--

From salvatore.loreto@ericsson.com  Fri Sep  4 12:24:37 2009
Return-Path: <salvatore.loreto@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 163C93A6825 for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 12:24:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.486
X-Spam-Level: 
X-Spam-Status: No, score=-3.486 tagged_above=-999 required=5 tests=[AWL=-1.237, BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 7nQlb5Cs3PFq for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 12:24:36 -0700 (PDT)
Received: from mailgw5.ericsson.se (mailgw5.ericsson.se [193.180.251.36]) by core3.amsl.com (Postfix) with ESMTP id 133183A681B for <sip-overload@ietf.org>; Fri,  4 Sep 2009 12:24:35 -0700 (PDT)
X-AuditID: c1b4fb24-b7c01ae00000498b-9d-4aa14f559b34
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw5.ericsson.se (Symantec Brightmail Gateway) with SMTP id 6C.36.18827.55F41AA4; Fri,  4 Sep 2009 19:33:09 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 4 Sep 2009 19:33:09 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 4 Sep 2009 19:33:09 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 2087924BC; Fri,  4 Sep 2009 20:33:09 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id BFCC221A17; Fri,  4 Sep 2009 20:33:08 +0300 (EEST)
Received: from localhost.localdomain (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 63ECB219CB; Fri,  4 Sep 2009 20:33:08 +0300 (EEST)
Message-ID: <4AA14F54.80209@ericsson.com>
Date: Fri, 04 Sep 2009 20:33:08 +0300
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090825)
MIME-Version: 1.0
To: Volker Hilt <volkerh@bell-labs.com>
References: <4AA135D5.9000600@bell-labs.com>	<DF6DD917A6E6D34C9619D66816FF0C4F018BD08F@0256-its-exmp02.us.saic.com> <4AA14561.10207@bell-labs.com>
In-Reply-To: <4AA14561.10207@bell-labs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 04 Sep 2009 17:33:09.0292 (UTC) FILETIME=[C50686C0:01CA2D85]
X-Brightmail-Tracker: AAAAAA==
Cc: "sip-overload@ietf.org" <sip-overload@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "Moran, Timothy L." <TIMOTHY.L.MORAN@saic.com>
Subject: Re: [sip-overload] Interest in a SIP Overload WG - URGENT
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, 04 Sep 2009 19:24:37 -0000

I am interested to help and contribute

Sal

Volker Hilt wrote:
> Timothy,
>
> Mary had listed a few of the tasks ahead in her mail. Essentially we 
> need help with reviewing the current drafts, identifying issues that 
> need to be resolved and driving these issues forward on the mailing 
> list, editing and updating the drafts, etc.
>
> Thanks,
>
> Volker
>
>
>
> Moran, Timothy L. wrote:
>> Volker,
>>
>> Very important work for those of us supporting the NCS NS/EP NGN
>> Priority Services program.  Where do you need help -specifically? 
>> Br,
>> Tim M.
>>
>> -----Original Message-----
>> From: sip-overload-bounces@ietf.org
>> [mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt
>> Sent: Friday, September 04, 2009 11:44 AM
>> To: sip-overload@ietf.org
>> Cc: Gonzalo Camarillo
>> Subject: [sip-overload] Interest in a SIP Overload WG - URGENT
>>
>> All,
>>
>> the DISPATCH WG is trying to gauge the interest in moving forward 
>> with the SIP Overload Control work as we had no discussion on the 
>> dispatch
>> list.
>>
>> So please respond to this email if your are
>> - interested in actively contributing to a standard AND
>> - have the cycles needed to do so
>>
>> To avoid spamming please remove "sip-overload@iet.org" from the To of 
>> your response.
>>
>> If the interest in this work has ceased and there are not enough 
>> people willing and able to actively contribute, we will not move 
>> forward with
>> it.
>>
>> Thanks,
>>
>> Volker
>> _______________________________________________
>> 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 mdolly@att.com  Fri Sep  4 12:48:07 2009
Return-Path: <mdolly@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 9D6AA3A6831 for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 12:48:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.409
X-Spam-Level: 
X-Spam-Status: No, score=-106.409 tagged_above=-999 required=5 tests=[AWL=0.190, 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 K0HGWSlAh38I for <sip-overload@core3.amsl.com>; Fri,  4 Sep 2009 12:48:06 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by core3.amsl.com (Postfix) with SMTP id A83D13A6826 for <sip-overload@ietf.org>; Fri,  4 Sep 2009 12:48:06 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: mdolly@att.com
X-Msg-Ref: server-10.tower-120.messagelabs.com!1252093539!20003528!1
X-StarScan-Version: 6.1.3; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 30748 invoked from network); 4 Sep 2009 19:45:40 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-10.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2009 19:45:40 -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 n84JjeNx002660 for <sip-overload@ietf.org>; Fri, 4 Sep 2009 15:45:40 -0400
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id n84JjQl4002577 for <sip-overload@ietf.org>; Fri, 4 Sep 2009 15:45:32 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Fri, 4 Sep 2009 15:42:43 -0400
Message-ID: <14C85D6CCBE92743AF33663BF5D24EBA02BD4A37@gaalpa1msgusr7e.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] Re: Interest in a SIP Overload WG - URGENT
Thread-Index: AcotfXMteeqE2mH/ckyh5DElEQ88OAAGmuy4
From: "DOLLY, MARTIN C, ATTLABS" <mdolly@att.com>
To: <D.Malas@cablelabs.com>, <volkerh@bell-labs.com>, <sip-overload@ietf.org>
Cc: Gonzalo.Camarillo@ericsson.com
Subject: Re: [sip-overload] Interest in a SIP Overload WG - URGENT
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, 04 Sep 2009 19:48:07 -0000

SW4gMiBhbmQgcmFpc2UgeW91IDIgb24gdGhhdCByYW50LiBUaHVtYnMgdXANCg0KLS0tLS0gT3Jp
Z2luYWwgTWVzc2FnZSAtLS0tLQ0KRnJvbTogc2lwLW92ZXJsb2FkLWJvdW5jZXNAaWV0Zi5vcmcg
PHNpcC1vdmVybG9hZC1ib3VuY2VzQGlldGYub3JnPg0KVG86IFZvbGtlciBIaWx0IDx2b2xrZXJo
QGJlbGwtbGFicy5jb20+OyBzaXAtb3ZlcmxvYWRAaWV0Zi5vcmcgPHNpcC1vdmVybG9hZEBpZXRm
Lm9yZz4NCkNjOiBHb256YWxvIENhbWFyaWxsbyA8R29uemFsby5DYW1hcmlsbG9AZXJpY3Nzb24u
Y29tPg0KU2VudDogRnJpIFNlcCAwNCAxMjozMzozNiAyMDA5DQpTdWJqZWN0OiBbc2lwLW92ZXJs
b2FkXSAgUmU6IEludGVyZXN0IGluIGEgU0lQIE92ZXJsb2FkIFdHIC0gVVJHRU5UDQoNCkFsbCwN
Cg0KVGhlIHByb2JsZW0gaXMgbm90IGludGVyZXN0IGluIHRoaXMgaXNzdWUuICBUaGUgcHJvYmxl
bSBpcyB0aGUgaW50ZXJlc3Qgd2FzDQp0aGVyZSAzIHllYXJzIGFnbyB3aGVuIHRoaXMgcHJvYmxl
bSB3YXMgaW50cm9kdWNlZC4gIFRoZSBvdGhlciBpc3N1ZSBpcw0KcmVsYXRlZCB3b3JraW5nIGdy
b3VwcyB0ZW5kIHRvIGJlIG1vcmUgaW50ZXJlc3RlZCBpbiBkZXZlbG9waW5nIG1vcmUNCmZlYXR1
cmVzIHJhdGhlciB0aGFuIGRlYWxpbmcgd2l0aCB0aGUgb3BlcmF0aW9uYWwgaXNzdWVzIHRoYXQg
ZXhpc3QgZm9yDQpzZXJ2aWNlIHByb3ZpZGVycy4gIFNpbmNlLCB0aGlzIGlzIHRoZSBjYXNlLCBz
ZXJ2aWNlIHByb3ZpZGVycyBzaW1wbHkgYXNrDQp0aGVpciBwcm94eSwgc2Vzc2lvbiBib3JkZXIg
Y29udHJvbGxlciwgYW5kIG1lZGlhIGdhdGV3YXkgdmVuZG9ycyB0byBzb2x2ZQ0KaXQgaW4gYW4g
YWRob2MsIHByb3ByaWV0YXJ5IG1hbm5lciBpbiB0aGUgaW50ZXJpbS4gIE9uY2Ugd2UgZmluYWxs
eSBnZXQNCnRocm91Z2ggMiB5ZWFycyBvZiBkZXNpZ24gd29yayBhbmQgbWFueSB0aGVvcmV0aWNh
bCBkaXNjdXNzaW9ucyB0aGUgc2VydmljZQ0KcHJvdmlkZXIgY29tbXVuaXR5IHRodW1icyB0aGVp
ciBwcm92ZXJiaWFsIG5vc2UgYXQgdGhlIElFVEYgYW5kIHNheXMgd2UgaGF2ZQ0KaXQgdGFrZW4g
Y2FyZSBvZi4uLnRoYW5rcywgYnV0IG5vIHRoYW5rcyAoZG9uJ3QgYmVsaWV2ZSBtZS4uLnNlZSBJ
Q0UsIE5BVCwNCkxOUCwgSGlzdG9yeS1JbmZvLi4uLikuICBBbHNvLCB0aGUgdmVuZG9yIGNvbW11
bml0eSBzYXlzIHdlIGRvbid0IGNhcmUsDQpiZWNhdXNlIHRoZXkndmUgYWxyZWFkeSBpbXBsZW1l
bnRlZCB0aGVpciBwcm9wcmlldGFyeSBzb2x1dGlvbnMsIG1lZXRpbmcgdGhlDQpuZWVkcyBvZiB0
aGVpciBjdXN0b21lcnMuICBXaHkgd291bGQgdGhleSB3YW50IHRvIGludmVzdCBtb3JlIHRpbWUg
b24gYQ0KcHJvYmxlbSB0aGV5J3ZlIGFscmVhZHkgInNvbHZlZCI/DQoNCldpdGggdGhlc2UgdGhp
bmdzIGluIG1pbmQsIEkgdGhpbmsgdGhlIGRlc2lnbiBncm91cCBkaWQgYSBncmVhdCBqb2IsIG1v
cmUNCnRoYW4gdGhvcm91Z2guICBUaGUgd29yayB0aGV5IGhhdmUgZG9uZSBzaG91bGQgbm90IGJl
IGxlZnQgb24gdGhlIHNoZWxmIHRvDQpnYWluIGR1c3QgZm9yIHllYXJzIHRvIGNvbWUuICBJbnN0
ZWFkLCBJIHRoaW5rIGEgc29sdXRpb24gc2hvdWxkIGJlIGRyaXZlbg0KZm9yd2FyZCBmb3IgdGhl
IGNvbW11bml0eSB0byBjb25zaWRlciB3aGVuIHRoZXkgcmVhbGl6ZSB0aGVpciBwcm9wcmlldGFy
eQ0Kc29sdXRpb25zIGRvbid0IHNjYWxlIGZvciBzb21lIHVua25vd24gcmVhc29uLi4uaXQgd2ls
bCBoYXBwZW4uDQoNCkkgZGVzcGVyYXRlbHkgd2lzaCBJIGhhZCB0aGUgY3ljbGVzIHRvIGludmVz
dCB0aGUgdGltZSBjb21taXRtZW50IHRvIHRoaXMNCndvcmssIGJ1dCBJIGFtIGtuZWUgZGVlcCBp
biB0YXNrcyBvbiB0aGUgImhvbWUgZnJvbnQiLiAgTXkgY29tbWVudHMgYXJlIHRvDQplbmNvdXJh
Z2UgdGhlIHdvcmsgdG8gY29udGludWUgYW5kIGRpc2NvdXJhZ2UgdGhyb3dpbmcgaXQgYXdheSBk
dWUgdG8NCnNpbGVuY2Ugb24gdGhlIG1haWxpbmcgbGlzdC4gIFRoZSBhbHRlcm5hdGl2ZSBpcyB0
byAic2hlbGYiIHRoZSB3b3JrIGFuZA0KYWRkcmVzcyBpdCBhZ2FpbiB3aGVuIHRob3NlICJzY2Fs
aW5nIiBpc3N1ZXMgY29tZSBiYWNrLi4ubWF5YmUgdGhleQ0Kd29uJ3QuLi53ZSBjYW4gb25seSBz
cGVjdWxhdGUuDQoNCk15IHR3byBjZW50cy4uLg0KDQotLURhcnlsDQoNCg0KT24gOS80LzA5IDk6
NDQgQU0sICJWb2xrZXIgSGlsdCIgPHZvbGtlcmhAYmVsbC1sYWJzLmNvbT4gd3JvdGU6DQoNCj4g
QWxsLA0KPiANCj4gdGhlIERJU1BBVENIIFdHIGlzIHRyeWluZyB0byBnYXVnZSB0aGUgaW50ZXJl
c3QgaW4gbW92aW5nIGZvcndhcmQgd2l0aA0KPiB0aGUgU0lQIE92ZXJsb2FkIENvbnRyb2wgd29y
ayBhcyB3ZSBoYWQgbm8gZGlzY3Vzc2lvbiBvbiB0aGUgZGlzcGF0Y2ggbGlzdC4NCj4gDQo+IFNv
IHBsZWFzZSByZXNwb25kIHRvIHRoaXMgZW1haWwgaWYgeW91ciBhcmUNCj4gLSBpbnRlcmVzdGVk
IGluIGFjdGl2ZWx5IGNvbnRyaWJ1dGluZyB0byBhIHN0YW5kYXJkIEFORA0KPiAtIGhhdmUgdGhl
IGN5Y2xlcyBuZWVkZWQgdG8gZG8gc28NCj4gDQo+IFRvIGF2b2lkIHNwYW1taW5nIHBsZWFzZSBy
ZW1vdmUgInNpcC1vdmVybG9hZEBpZXQub3JnIiBmcm9tIHRoZSBUbyBvZg0KPiB5b3VyIHJlc3Bv
bnNlLg0KPiANCj4gSWYgdGhlIGludGVyZXN0IGluIHRoaXMgd29yayBoYXMgY2Vhc2VkIGFuZCB0
aGVyZSBhcmUgbm90IGVub3VnaCBwZW9wbGUNCj4gd2lsbGluZyBhbmQgYWJsZSB0byBhY3RpdmVs
eSBjb250cmlidXRlLCB3ZSB3aWxsIG5vdCBtb3ZlIGZvcndhcmQgd2l0aCBpdC4NCj4gDQo+IFRo
YW5rcywNCj4gDQo+IFZvbGtlcg0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0KPiBzaXAtb3ZlcmxvYWQgbWFpbGluZyBsaXN0DQo+IHNpcC1vdmVybG9h
ZEBpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcC1v
dmVybG9hZA0KDQoNCi0tLS0tLS0tLS0tLS0tLS0tDQpEYXJ5bCBNYWxhcw0KQ2FibGVMYWJzDQoo
bykgKzEgMzAzIDY2MSAzMzAyDQooZikgKzEgMzAzIDY2MSA5MTk5DQptYWlsdG86ZC5tYWxhc0Bj
YWJsZWxhYnMuY29tDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCnNpcC1vdmVybG9hZCBtYWlsaW5nIGxpc3QNCnNpcC1vdmVybG9hZEBpZXRmLm9y
Zw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXAtb3ZlcmxvYWQNCg==

From youssef.chadli@orange-ftgroup.com  Mon Sep  7 07:16:22 2009
Return-Path: <youssef.chadli@orange-ftgroup.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5EF753A6949 for <sip-overload@core3.amsl.com>; Mon,  7 Sep 2009 07:16:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 U1d11bgC5hwa for <sip-overload@core3.amsl.com>; Mon,  7 Sep 2009 07:16:21 -0700 (PDT)
Received: from R-MAIL1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id 2BF5D3A6A18 for <sip-overload@ietf.org>; Mon,  7 Sep 2009 07:16:20 -0700 (PDT)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 7 Sep 2009 14:12:38 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 7 Sep 2009 14:12:36 +0200
Message-ID: <9ECCF01B52E7AB408A7EB85352642141706168@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <9ECCF01B52E7AB408A7EB8535264214114B31C@ftrdmel0.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE : RE: [sip-overload] Interest in a SIP Overload WG - URGENT
Thread-Index: AcovklyfjxPoyq8FTri09c3CMcb3LwAIAXAg
References: <9ECCF01B52E7AB408A7EB8535264214114B31C@ftrdmel0.rd.francetelecom.fr>
From: <youssef.chadli@orange-ftgroup.com>
To: <mdolly@att.com>, <volkerh@bell-labs.com>, <sip-overload@ietf.org>
X-OriginalArrivalTime: 07 Sep 2009 12:12:38.0907 (UTC) FILETIME=[7E0FE4B0:01CA2FB4]
Cc: Gonzalo.Camarillo@ericsson.com
Subject: [sip-overload] RE : RE:  Interest in a SIP Overload WG - URGENT
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, 07 Sep 2009 14:16:22 -0000

=20
Hi,

I'm interested in actively contributing to this work providing that the =
solution enables negotiation of the format to be used to convey overload =
control information and therefore does not mandate a specific format.

Best regards,

Youssef

-----Message d'origine-----
De : sip-overload-bounces@ietf.org =
[mailto:sip-overload-bounces@ietf.org] De la part de DOLLY, MARTIN C, =
ATTLABS Envoy=E9 : vendredi 4 septembre 2009 17:50 =C0 : Volker Hilt; =
sip-overload@ietf.org Cc : Gonzalo Camarillo Objet : Re: [sip-overload] =
Interest in a SIP Overload WG - URGENT

Volker,

This is very important work. The design team are experts from the SP and =
vendor communities. Lack of "list" discussion should is not metric here, =
and/or other topics.

Regards,

Martin

-----Original Message-----
From: sip-overload-bounces@ietf.org
[mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt
Sent: Friday, September 04, 2009 11:44 AM
To: sip-overload@ietf.org
Cc: Gonzalo Camarillo
Subject: [sip-overload] Interest in a SIP Overload WG - URGENT

All,

the DISPATCH WG is trying to gauge the interest in moving forward with =
the SIP Overload Control work as we had no discussion on the dispatch =
list.

So please respond to this email if your are
- interested in actively contributing to a standard AND
- have the cycles needed to do so

To avoid spamming please remove "sip-overload@iet.org" from the To of =
your response.

If the interest in this work has ceased and there are not enough people =
willing and able to actively contribute, we will not move forward with =
it.

Thanks,

Volker
_______________________________________________
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 crjohnson1@att.com  Tue Sep  8 18:23:58 2009
Return-Path: <crjohnson1@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 F3D3B3A689A; Tue,  8 Sep 2009 18:23:57 -0700 (PDT)
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 hxyXV0f43bXr; Tue,  8 Sep 2009 18:23:56 -0700 (PDT)
Received: from mail167.messagelabs.com (mail167.messagelabs.com [216.82.253.179]) by core3.amsl.com (Postfix) with ESMTP id BA5303A682B; Tue,  8 Sep 2009 18:23:50 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: crjohnson1@att.com
X-Msg-Ref: server-8.tower-167.messagelabs.com!1252459460!15129568!1
X-StarScan-Version: 6.1.3; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 13757 invoked from network); 9 Sep 2009 01:24:21 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-8.tower-167.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Sep 2009 01:24:21 -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 n891OLL7010837; Tue, 8 Sep 2009 21:24:21 -0400
Received: from misout7msgusr7d.ugd.att.com (misout7msgusr7d.ugd.att.com [144.155.43.106]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id n891OFoQ010824; Tue, 8 Sep 2009 21:24:15 -0400
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: Tue, 8 Sep 2009 21:24:13 -0400
Message-ID: <9DE31798099D044DA5F3C0DEAB107C5A03C451E4@misout7msgusr7d.ugd.att.com>
In-Reply-To: <4A8D551B.7060308@alcatel-lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [sip-overload] Revised Charter Proposal for SIP Overload
Thread-Index: AcohnYQuAg4halqwT069AAL/gB8D5QABWWIg
References: <4A8D551B.7060308@alcatel-lucent.com>
From: "JOHNSON, CAROLYN R, ATTLABS" <crjohnson1@att.com>
To: "Volker Hilt" <volkerh@alcatel-lucent.com>, "DISPATCH" <dispatch@ietf.org>, "SIP-OVERLOAD" <sip-overload@ietf.org>, "NOEL, ERIC C, ATTLABS" <ecnoel@att.com>
Subject: Re: [sip-overload] Revised Charter Proposal for 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: Wed, 09 Sep 2009 01:23:58 -0000

Volker,
Sorry for the delay, this got stuck in my drafts folder while I was out
on vacation.

One comment on the last dashed item:
- 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.

I suggest replacing "telephone number" with "destination routing" so as
not to limit to applications that use telephone prefixes. I believe it
will be more general without losing the applicability to telephone IDs.

The charter is clearly laid out.=20
Regards,

Carolyn
=20

-----Original Message-----
From: sip-overload-bounces@ietf.org
[mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt
Sent: Thursday, August 20, 2009 9:52 AM
To: DISPATCH; SIP-OVERLOAD
Subject: [sip-overload] Revised Charter Proposal for SIP Overload

All,

below is an revised SIP Overload Control charter proposal. I have
received a few comments that are reflected in the new proposal.

All comments, thoughts, feedback is very welcome!

Thanks,

Volker



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

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

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

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

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

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

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



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

From volkerh@bell-labs.com  Tue Sep  8 19:00:04 2009
Return-Path: <volkerh@bell-labs.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 7F13B28C1E3; Tue,  8 Sep 2009 19:00:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.343
X-Spam-Level: 
X-Spam-Status: No, score=-2.343 tagged_above=-999 required=5 tests=[AWL=0.256,  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 Idkc3sHd42HG; Tue,  8 Sep 2009 19:00:02 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 6808728C1DE; Tue,  8 Sep 2009 19:00:01 -0700 (PDT)
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 n8920UZx000280;  Tue, 8 Sep 2009 21:00:30 -0500 (CDT)
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 n8920UvP021112; Tue, 8 Sep 2009 21:00:30 -0500 (CDT)
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; Tue, 8 Sep 2009 21:00:30 -0500
Message-ID: <4AA70C29.8020804@bell-labs.com>
Date: Tue, 8 Sep 2009 22:00:09 -0400
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "JOHNSON, CAROLYN R, ATTLABS" <crjohnson1@att.com>
References: <4A8D551B.7060308@alcatel-lucent.com> <9DE31798099D044DA5F3C0DEAB107C5A03C451E4@misout7msgusr7d.ugd.att.com>
In-Reply-To: <9DE31798099D044DA5F3C0DEAB107C5A03C451E4@misout7msgusr7d.ugd.att.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.39
Cc: "NOEL, ERIC C, ATTLABS" <ecnoel@att.com>, DISPATCH <dispatch@ietf.org>, SIP-OVERLOAD <sip-overload@ietf.org>
Subject: Re: [sip-overload] Revised Charter Proposal for 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: Wed, 09 Sep 2009 02:00:05 -0000

Carolyn,

thanks for your feedback! I'll update the charter proposal to address 
the comment.

Thanks,

Volker

JOHNSON, CAROLYN R, ATTLABS wrote:
> Volker,
> Sorry for the delay, this got stuck in my drafts folder while I was out
> on vacation.
> 
> One comment on the last dashed item:
> - 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.
> 
> I suggest replacing "telephone number" with "destination routing" so as
> not to limit to applications that use telephone prefixes. I believe it
> will be more general without losing the applicability to telephone IDs.
> 
> The charter is clearly laid out. 
> Regards,
> 
> Carolyn
>  
> 
> -----Original Message-----
> From: sip-overload-bounces@ietf.org
> [mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt
> Sent: Thursday, August 20, 2009 9:52 AM
> To: DISPATCH; SIP-OVERLOAD
> Subject: [sip-overload] Revised Charter Proposal for SIP Overload
> 
> All,
> 
> below is an revised SIP Overload Control charter proposal. I have
> received a few comments that are reflected in the new proposal.
> 
> All comments, thoughts, feedback is very welcome!
> 
> Thanks,
> 
> Volker
> 
> 
> 
> SIP Overload Control WG Charter
> -------------------------------
> 
> As with any network element, a Session Initiation Protocol (SIP) server
> can suffer from overload when the number of SIP messages it receives
> exceeds the number of messages it can process. Overload is said to occur
> when a SIP server does not have sufficient resources to process all
> incoming SIP messages.  These resources can include CPU, memory, network
> bandwidth, input/output, or disk resources.
> 
> Overload can pose a serious problem for a network of SIP servers. During
> periods of overload, the throughput of a network of SIP servers can be
> significantly degraded.  In fact, overload may lead to a situation in
> which the throughput drops down to zero or a small fraction of the
> original processing capacity.  This is often called congestion collapse.
> 
> The objective of a SIP overload control mechanism is to enable SIP
> servers to operate close to their capacity limit during times of
> overload.
> 
> The SIP protocol provides a limited mechanism for overload control
> through its 503 (Service Unavailable) response code and the Retry-After
> header.  However, this mechanism cannot fully prevent overload of a SIP
> server and it cannot prevent congestion collapse.  In fact, its on/off
> behavior may cause traffic to oscillate and shift between SIP servers
> and thereby worsen an overload condition.  A detailed discussion of the
> SIP overload problem, the problems with the 503 (Service Unavailable)
> response code and the Retry-After header and the requirements for a SIP
> overload control mechanism can be found in RFC5390.
> 
> The objective of the proposed working group is to develop mechanisms for
> SIP overload control. Two complementary approaches exist for handling
> overload situations:
> - The first mechanism aims at preventing overload in SIP servers by
> adjusting the incoming load to a level that is acceptable for this
> server. This mechanism uses implicit and/or explicit feedback to
> determine when an overload condition occurs in a SIP server and a
> reduction in load is required.
> - The second mechanism aims at preventing overload in SIP servers by
> distributing load control filters to SIP servers that throttle calls
> based on their destination domain, telephone number prefix or for a
> specific user. Such filters can be used, for example, to throttle calls
> to a hotline during a ticket-giveaway event.
> 
> Specifically, the proposed working group will develop the following
> deliverables:
> 1. A document describing key design considerations for a SIP overload
> control mechanism.
> 2. A specification for an SIP overload control mechanism based on
> implicit/explicit feedback.
> 3. A specification for a SIP load filtering mechanism.
> 
> 
> 
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload

