From ecnoel@att.com Thu Oct 1 08:16:22 2009 Return-Path: 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 F2B043A698C; Thu, 1 Oct 2009 08:16:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.044 X-Spam-Level: X-Spam-Status: No, score=-106.044 tagged_above=-999 required=5 tests=[AWL=0.555, 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 oY9B3KM7YM0J; Thu, 1 Oct 2009 08:16:18 -0700 (PDT) Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id C478B3A6783; Thu, 1 Oct 2009 08:16:18 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: ecnoel@att.com X-Msg-Ref: server-11.tower-161.messagelabs.com!1254410262!3069964!1 X-StarScan-Version: 6.1.3; banners=-,-,- X-Originating-IP: [144.160.20.146] Received: (qmail 6091 invoked from network); 1 Oct 2009 15:17:43 -0000 Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-11.tower-161.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Oct 2009 15:17:43 -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 n91FHgke001762; Thu, 1 Oct 2009 11:17:42 -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 n91FHbs9001723; Thu, 1 Oct 2009 11:17:37 -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: Thu, 1 Oct 2009 11:17:37 -0400 Message-ID: <5DA01D2CA74FAF40ADF71DB4177D345A02684E54@misout7msgusr7b.ugd.att.com> In-Reply-To: <4AA70C29.8020804@bell-labs.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SIP-OVERLOAD confernece call this morning? Thread-Index: Acow8VRa6Kmh5CjLTZaBc20kG+p5JgRuMPrA References: <4A8D551B.7060308@alcatel-lucent.com> <9DE31798099D044DA5F3C0DEAB107C5A03C451E4@misout7msgusr7d.ugd.att.com> <4AA70C29.8020804@bell-labs.com> From: "NOEL, ERIC C, ATTLABS" To: "Volker Hilt" Cc: DISPATCH , SIP-OVERLOAD Subject: [sip-overload] SIP-OVERLOAD confernece call this morning? X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Oct 2009 15:16:23 -0000 Volker, Is there a conference call this morning? I was away during last meeting and may have missed the schedule. Thanks, Eric From volkerh@bell-labs.com Thu Oct 1 18:34:18 2009 Return-Path: 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 B10AD3A6837 for ; Thu, 1 Oct 2009 18:34:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.372 X-Spam-Level: X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[AWL=0.227, 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 qq3H-F-6P1nK for ; Thu, 1 Oct 2009 18:34:17 -0700 (PDT) Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 09E5D3A68B0 for ; Thu, 1 Oct 2009 18:34:16 -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 n921Zhi3014340 for ; Thu, 1 Oct 2009 20:35:43 -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 n921Zh8v011620 for ; Thu, 1 Oct 2009 20:35:43 -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; Thu, 1 Oct 2009 20:35:42 -0500 Message-ID: <4AC558E4.1010200@bell-labs.com> Date: Thu, 1 Oct 2009 21:35:32 -0400 From: Volker Hilt User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: SIP-OVERLOAD References: <4A8D551B.7060308@alcatel-lucent.com> <9DE31798099D044DA5F3C0DEAB107C5A03C451E4@misout7msgusr7d.ugd.att.com> <4AA70C29.8020804@bell-labs.com> <5DA01D2CA74FAF40ADF71DB4177D345A02684E54@misout7msgusr7b.ugd.att.com> In-Reply-To: <5DA01D2CA74FAF40ADF71DB4177D345A02684E54@misout7msgusr7b.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.35 Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Oct 2009 01:34:18 -0000 All, sorry for missing today's conf call. I would suggest that for moving forward it is more effective to use the mailing list for discussions rather than a conference call. We can set up a call any time we need, e.g., if there are new simulation results or a discussion on a specific item is needed. Any thoughts? Thanks, Volker NOEL, ERIC C, ATTLABS wrote: > Volker, > > Is there a conference call this morning? I was away during last meeting > and may have missed the schedule. > > Thanks, > > Eric > _______________________________________________ > sip-overload mailing list > sip-overload@ietf.org > https://www.ietf.org/mailman/listinfo/sip-overload From charles.newyork@gmail.com Thu Oct 1 22:04:18 2009 Return-Path: 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 D8BF53A6924 for ; Thu, 1 Oct 2009 22:04:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.977 X-Spam-Level: X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IW2sMPgZVg-v for ; Thu, 1 Oct 2009 22:04:16 -0700 (PDT) Received: from mail-gx0-f212.google.com (mail-gx0-f212.google.com [209.85.217.212]) by core3.amsl.com (Postfix) with ESMTP id E000F3A690F for ; Thu, 1 Oct 2009 22:04:09 -0700 (PDT) Received: by gxk4 with SMTP id 4so1036818gxk.8 for ; Thu, 01 Oct 2009 22:05: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=M918TbJAFEBkMJPOUIRu4yHxtAhItSMoGyvM7OZJ/04=; b=SqUwPZQAxadLlbkYt849f1FSMnGLEmWhHEslclUJBI+Pz+8nHGWWdRjb9jkqt6BU32 7q8WxOZLRwOQo+4BCRCjim3NkFBB3v17+HNPrfU8/LD/Xt7ELRQpg0g5x7RrUC4aTgW2 7YcVxiIyidAwGCFpDTvZbKlb5tayJB1FuJy/E= 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=cAeUMDzMglYbSor6p7tXBAvGWbBP5uk4ib7GUZ2Mrc5bQCFJ/bbMyB2OrIn3w5JWQj 4FFq1npOnkMlmSpGD0CHvWyJqTtcc58yTCY1EAdGl1hZs4EZuN/6AhpR/0ZukCDcBJpd 6iiqLk6AXl7KYRRJlnNrWVSZrS2cjuVZkBJ44= MIME-Version: 1.0 Sender: charles.newyork@gmail.com Received: by 10.150.100.9 with SMTP id x9mr3701195ybb.203.1254459934315; Thu, 01 Oct 2009 22:05:34 -0700 (PDT) In-Reply-To: <4AC558E4.1010200@bell-labs.com> References: <4A8D551B.7060308@alcatel-lucent.com> <9DE31798099D044DA5F3C0DEAB107C5A03C451E4@misout7msgusr7d.ugd.att.com> <4AA70C29.8020804@bell-labs.com> <5DA01D2CA74FAF40ADF71DB4177D345A02684E54@misout7msgusr7b.ugd.att.com> <4AC558E4.1010200@bell-labs.com> Date: Fri, 2 Oct 2009 01:05:34 -0400 X-Google-Sender-Auth: 9c67d81543f4a817 Message-ID: From: Charles Shen To: Volker Hilt Content-Type: text/plain; charset=UTF-8 Cc: SIP-OVERLOAD Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Oct 2009 05:04:18 -0000 Volker: I think that's a good idea. Thanks Charles On Thu, Oct 1, 2009 at 9:35 PM, Volker Hilt wrote: > All, > > sorry for missing today's conf call. > > I would suggest that for moving forward it is more effective to use the > mailing list for discussions rather than a conference call. We can set up a > call any time we need, e.g., if there are new simulation results or a > discussion on a specific item is needed. Any thoughts? > > Thanks, > > Volker > > > > > > > > > > NOEL, ERIC C, ATTLABS wrote: >> >> Volker, >> >> Is there a conference call this morning? I was away during last meeting >> and may have missed the schedule. >> >> Thanks, >> >> Eric >> _______________________________________________ >> 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 ecnoel@att.com Fri Oct 2 05:42:16 2009 Return-Path: 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 F2CEE28C11D for ; Fri, 2 Oct 2009 05:42:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.229 X-Spam-Level: X-Spam-Status: No, score=-106.229 tagged_above=-999 required=5 tests=[AWL=0.370, 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 YTLQeRpAO7jj for ; Fri, 2 Oct 2009 05:42:08 -0700 (PDT) Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.242.3]) by core3.amsl.com (Postfix) with ESMTP id CA76428C0F9 for ; Fri, 2 Oct 2009 05:42:07 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: ecnoel@att.com X-Msg-Ref: server-2.tower-121.messagelabs.com!1254487414!28223861!1 X-StarScan-Version: 6.1.3; banners=-,-,- X-Originating-IP: [144.160.20.146] Received: (qmail 2843 invoked from network); 2 Oct 2009 12:43:34 -0000 Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-2.tower-121.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Oct 2009 12:43:34 -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 n92ChYKN005777 for ; Fri, 2 Oct 2009 08:43:34 -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 n92ChTX0005737 for ; Fri, 2 Oct 2009 08:43:29 -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, 2 Oct 2009 08:43:29 -0400 Message-ID: <5DA01D2CA74FAF40ADF71DB4177D345A02684E5F@misout7msgusr7b.ugd.att.com> In-Reply-To: <4AC558E4.1010200@bell-labs.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [sip-overload] SIP-OVERLOAD confernece call this morning? Thread-Index: AcpDALKSft5UYVLuQLCEb0TvPRwYZgAXI4DQ References: <4A8D551B.7060308@alcatel-lucent.com> <9DE31798099D044DA5F3C0DEAB107C5A03C451E4@misout7msgusr7d.ugd.att.com> <4AA70C29.8020804@bell-labs.com><5DA01D2CA74FAF40ADF71DB4177D345A02684E54@misout7msgusr7b.ugd.att.com> <4AC558E4.1010200@bell-labs.com> From: "NOEL, ERIC C, ATTLABS" To: "Volker Hilt" , "SIP-OVERLOAD" Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Oct 2009 12:42:17 -0000 Volker, What about having one more conference call to go over actionable work item(s) and then agreed to have a follow-up conference call upon critical mass completion of item(s). Lastly, would be very beneficial (at least to me) to have a web site that contains all the relevant material team members should be familiar with plus work plan/action item document to track our progress(es). =20 What do you think? Thanks, Eric=20 -----Original Message----- From: sip-overload-bounces@ietf.org [mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt Sent: Thursday, October 01, 2009 9:36 PM To: SIP-OVERLOAD Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? All, sorry for missing today's conf call. I would suggest that for moving forward it is more effective to use the=20 mailing list for discussions rather than a conference call. We can set=20 up a call any time we need, e.g., if there are new simulation results or a discussion on a specific item is needed. Any thoughts? Thanks, Volker NOEL, ERIC C, ATTLABS wrote: > Volker, >=20 > Is there a conference call this morning? I was away during last meeting > and may have missed the schedule. >=20 > Thanks, >=20 > Eric > _______________________________________________ > 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 Fri Oct 2 06:33:45 2009 Return-Path: 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 AE70628C0F4 for ; Fri, 2 Oct 2009 06:33:45 -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 eP4F3gEJEsnr for ; Fri, 2 Oct 2009 06:33:44 -0700 (PDT) Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id 73D5B28B797 for ; Fri, 2 Oct 2009 06:33:44 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: crjohnson1@att.com X-Msg-Ref: server-15.tower-161.messagelabs.com!1254490510!26561680!1 X-StarScan-Version: 6.1.3; banners=-,-,- X-Originating-IP: [144.160.20.146] Received: (qmail 22073 invoked from network); 2 Oct 2009 13:35:11 -0000 Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-15.tower-161.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Oct 2009 13:35:11 -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 n92DZARR009959 for ; Fri, 2 Oct 2009 09:35:10 -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 n92DZ73k009929 for ; Fri, 2 Oct 2009 09:35:07 -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, 2 Oct 2009 09:35:05 -0400 Message-ID: <9DE31798099D044DA5F3C0DEAB107C5A03FE4435@misout7msgusr7d.ugd.att.com> In-Reply-To: <4AC558E4.1010200@bell-labs.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [sip-overload] SIP-OVERLOAD confernece call this morning? Thread-Index: AcpDALJbJfYosd+aRYS1CxwSDdSlaQAYtYwg References: <4A8D551B.7060308@alcatel-lucent.com> <9DE31798099D044DA5F3C0DEAB107C5A03C451E4@misout7msgusr7d.ugd.att.com> <4AA70C29.8020804@bell-labs.com><5DA01D2CA74FAF40ADF71DB4177D345A02684E54@misout7msgusr7b.ugd.att.com> <4AC558E4.1010200@bell-labs.com> From: "JOHNSON, CAROLYN R, ATTLABS" To: "Volker Hilt" , "SIP-OVERLOAD" Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Oct 2009 13:33:45 -0000 All, I would prefer we have regular periodic conference calls. From personal experience and observation, it forces all of us to progress the work. Secondly, I get over 50 emails a day on average, and I may easily miss what is happening in this group if we rely on email as our major communication mode. Finally, my schedule is usually full, so scheduling conference calls as needed will likely exclude my participation. I expect I am not the only team member facing these business challenges. I would strongly prefer a scheduled conference call in addition to the emails. I'm OK with making it less frequent than our current 2-week schedule, but really think it is useful to have. How about once per month? Carolyn Carolyn R. Johnson Director Research - Quantitative Analysis AT&T Labs MT D5-3B37 732-420-4182 crjohnson1@att.com =20 -----Original Message----- From: sip-overload-bounces@ietf.org [mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt Sent: Thursday, October 01, 2009 9:36 PM To: SIP-OVERLOAD Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? All, sorry for missing today's conf call. I would suggest that for moving forward it is more effective to use the mailing list for discussions rather than a conference call. We can set up a call any time we need, e.g., if there are new simulation results or a discussion on a specific item is needed. Any thoughts? Thanks, Volker NOEL, ERIC C, ATTLABS wrote: > Volker, >=20 > Is there a conference call this morning? I was away during last=20 > meeting and may have missed the schedule. >=20 > Thanks, >=20 > Eric > _______________________________________________ > 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 nick.m.stewart@bt.com Fri Oct 2 06:46:34 2009 Return-Path: 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 BEFB33A69A2 for ; Fri, 2 Oct 2009 06:46:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.999 X-Spam-Level: X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xdmJA5QceDRs for ; Fri, 2 Oct 2009 06:46:33 -0700 (PDT) Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by core3.amsl.com (Postfix) with ESMTP id 5A6033A6810 for ; Fri, 2 Oct 2009 06:46:33 -0700 (PDT) Received: from E03MVY2-UKDY.domain1.systemhost.net ([193.113.30.58]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 2 Oct 2009 14:48:00 +0100 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, 2 Oct 2009 14:48:00 +0100 Message-ID: <5ACFADE7CFA7BF43A6B64DEED0ED918A08DEEFEF@E03MVY2-UKDY.domain1.systemhost.net> In-Reply-To: <9DE31798099D044DA5F3C0DEAB107C5A03FE4435@misout7msgusr7d.ugd.att.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [sip-overload] SIP-OVERLOAD confernece call this morning? Thread-Index: AcpDALJbJfYosd+aRYS1CxwSDdSlaQAYtYwgAACt+NA= References: <4A8D551B.7060308@alcatel-lucent.com> <9DE31798099D044DA5F3C0DEAB107C5A03C451E4@misout7msgusr7d.ugd.att.com> <4AA70C29.8020804@bell-labs.com><5DA01D2CA74FAF40ADF71DB4177D345A02684E54@misout7msgusr7b.ugd.att.com><4AC558E4.1010200@bell-labs.com> <9DE31798099D044DA5F3C0DEAB107C5A03FE4435@misout7msgusr7d.ugd.att.com> From: To: X-OriginalArrivalTime: 02 Oct 2009 13:48:00.0217 (UTC) FILETIME=[F48E4490:01CA4366] Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Oct 2009 13:46:34 -0000 All, I would like to add my support to Carolyn's case for continuing audios. We are all busy people and it helps to maintain momentum if interested parties meet regularly.=20 Thanks, Nick Nick Stewart BT Innovate & Design Tel: +44 (0)1473 629428 Mob: +44 (0)7962 103572 Email: nick.m.stewart@bt.com Web: www.bt.com This email contains BT information, which may be privileged or confidential. It's meant only for the individual(s) or entity named above. If you're not the intended recipient, note that disclosing, copying, distributing or using this information is prohibited. If you've received this email in error, please let me know immediately on the email address above. Thank you. We monitor our email system, and may record your emails. British Telecommunications plc Registered office: 81 Newgate Street London EC1A 7AJ Registered in England no: 1800000 -----Original Message----- From: sip-overload-bounces@ietf.org [mailto:sip-overload-bounces@ietf.org] On Behalf Of JOHNSON, CAROLYN R, ATTLABS Sent: 02 October 2009 14:35 To: Volker Hilt; SIP-OVERLOAD Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? All, I would prefer we have regular periodic conference calls. From personal experience and observation, it forces all of us to progress the work. Secondly, I get over 50 emails a day on average, and I may easily miss what is happening in this group if we rely on email as our major communication mode. Finally, my schedule is usually full, so scheduling conference calls as needed will likely exclude my participation. I expect I am not the only team member facing these business challenges. I would strongly prefer a scheduled conference call in addition to the emails. I'm OK with making it less frequent than our current 2-week schedule, but really think it is useful to have. How about once per month? Carolyn Carolyn R. Johnson Director Research - Quantitative Analysis AT&T Labs MT D5-3B37 732-420-4182 crjohnson1@att.com =20 -----Original Message----- From: sip-overload-bounces@ietf.org [mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt Sent: Thursday, October 01, 2009 9:36 PM To: SIP-OVERLOAD Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? All, sorry for missing today's conf call. I would suggest that for moving forward it is more effective to use the mailing list for discussions rather than a conference call. We can set up a call any time we need, e.g., if there are new simulation results or a discussion on a specific item is needed. Any thoughts? Thanks, Volker NOEL, ERIC C, ATTLABS wrote: > Volker, >=20 > Is there a conference call this morning? I was away during last=20 > meeting and may have missed the schedule. >=20 > Thanks, >=20 > Eric > _______________________________________________ > 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 _______________________________________________ sip-overload mailing list sip-overload@ietf.org https://www.ietf.org/mailman/listinfo/sip-overload From volkerh@bell-labs.com Fri Oct 2 13:14:35 2009 Return-Path: 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 7F1C23A6881 for ; Fri, 2 Oct 2009 13:14:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.095 X-Spam-Level: X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[AWL=-0.096, BAYES_00=-2.599, J_CHICKENPOX_21=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s9zNsM2YTY3J for ; Fri, 2 Oct 2009 13:14:34 -0700 (PDT) Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 6604B3A67D2 for ; Fri, 2 Oct 2009 13:14:34 -0700 (PDT) Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id n92KFvAp005158; Fri, 2 Oct 2009 15:15:59 -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 n92KFv1k019332; Fri, 2 Oct 2009 15:15:57 -0500 (CDT) Received: from [127.0.0.1] (135.3.63.243) by USNAVSXCHHUB01.ndc.alcatel-lucent.com (135.3.39.110) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 2 Oct 2009 15:15:57 -0500 Message-ID: <4AC65F71.8080307@bell-labs.com> Date: Fri, 2 Oct 2009 16:15:45 -0400 From: Volker Hilt User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: "nick.m.stewart@bt.com" , "JOHNSON, CAROLYN R, ATTLABS" References: <4A8D551B.7060308@alcatel-lucent.com> <9DE31798099D044DA5F3C0DEAB107C5A03C451E4@misout7msgusr7d.ugd.att.com> <4AA70C29.8020804@bell-labs.com><5DA01D2CA74FAF40ADF71DB4177D345A02684E54@misout7msgusr7b.ugd.att.com><4AC558E4.1010200@bell-labs.com> <9DE31798099D044DA5F3C0DEAB107C5A03FE4435@misout7msgusr7d.ugd.att.com> <5ACFADE7CFA7BF43A6B64DEED0ED918A08DEEFEF@E03MVY2-UKDY.domain1.systemhost.net> In-Reply-To: <5ACFADE7CFA7BF43A6B64DEED0ED918A08DEEFEF@E03MVY2-UKDY.domain1.systemhost.net> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33 Cc: "sip-overload@ietf.org" Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Oct 2009 20:14:35 -0000 Let's use our next scheduled slot on Oct 15 at 11:00am ET to discuss. All technical discussions need to happen on the sip-overload mailing list and not on a call! This will enable everyone to catch up on discussions and contribute. Thanks, Volker nick.m.stewart@bt.com wrote: > All, > > I would like to add my support to Carolyn's case for continuing audios. > We are all busy people and it helps to maintain momentum if interested > parties meet regularly. > > Thanks, > > Nick > > Nick Stewart > BT Innovate & Design > > Tel: +44 (0)1473 629428 > Mob: +44 (0)7962 103572 > Email: nick.m.stewart@bt.com > Web: www.bt.com > This email contains BT information, which may be privileged or > confidential. It's meant only for the individual(s) or entity named > above. If you're not the intended recipient, note that disclosing, > copying, distributing or using this information is prohibited. If you've > received this email in error, please let me know immediately on the > email address above. Thank you. > We monitor our email system, and may record your emails. > British Telecommunications plc > Registered office: 81 Newgate Street London EC1A 7AJ > Registered in England no: 1800000 > > > > -----Original Message----- > From: sip-overload-bounces@ietf.org > [mailto:sip-overload-bounces@ietf.org] On Behalf Of JOHNSON, CAROLYN R, > ATTLABS > Sent: 02 October 2009 14:35 > To: Volker Hilt; SIP-OVERLOAD > Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? > > All, > I would prefer we have regular periodic conference calls. From personal > experience and observation, it forces all of us to progress the work. > Secondly, I get over 50 emails a day on average, and I may easily miss > what is happening in this group if we rely on email as our major > communication mode. Finally, my schedule is usually full, so scheduling > conference calls as needed will likely exclude my participation. I > expect I am not the only team member facing these business challenges. > I would strongly prefer a scheduled conference call in addition to the > emails. I'm OK with making it less frequent than our current 2-week > schedule, but really think it is useful to have. How about once per > month? > > > Carolyn > Carolyn R. Johnson > Director Research - Quantitative Analysis > AT&T Labs > MT D5-3B37 > 732-420-4182 > crjohnson1@att.com > > > -----Original Message----- > From: sip-overload-bounces@ietf.org > [mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt > Sent: Thursday, October 01, 2009 9:36 PM > To: SIP-OVERLOAD > Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? > > All, > > sorry for missing today's conf call. > > I would suggest that for moving forward it is more effective to use the > mailing list for discussions rather than a conference call. We can set > up a call any time we need, e.g., if there are new simulation results or > a discussion on a specific item is needed. Any thoughts? > > Thanks, > > Volker > > > > > > > > > > NOEL, ERIC C, ATTLABS wrote: >> Volker, >> >> Is there a conference call this morning? I was away during last >> meeting and may have missed the schedule. >> >> Thanks, >> >> Eric >> _______________________________________________ >> 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 > _______________________________________________ > sip-overload mailing list > sip-overload@ietf.org > https://www.ietf.org/mailman/listinfo/sip-overload > _______________________________________________ > sip-overload mailing list > sip-overload@ietf.org > https://www.ietf.org/mailman/listinfo/sip-overload From partr@cisco.com Sun Oct 4 22:45:07 2009 Return-Path: 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 7AB703A6954 for ; Sun, 4 Oct 2009 22:45:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.399 X-Spam-Level: X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_17=0.6, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bh83OAb+P-Af for ; Sun, 4 Oct 2009 22:45:06 -0700 (PDT) Received: from syd-iport-2.cisco.com (syd-iport-2.cisco.com [64.104.193.197]) by core3.amsl.com (Postfix) with ESMTP id 950AB3A68E7 for ; Sun, 4 Oct 2009 22:45:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=4697; q=dns/txt; s=sydiport02001; t=1254721602; x=1255931202; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20"Parthasarathi=20R=20(partr)"=20|Subject:=20RE:=20[sip-overload]=20SIP-OVERLOAD=20confer nece=20call=20this=20morning?|Date:=20Mon,=205=20Oct=2020 09=2011:16:07=20+0530|Message-ID:=20|To:=20"Volker =20Hilt"=20,=20,=0D=0A=20=20=20=20=20=20=20=20"JOHNSON,=20CAROLYN=20 R,ATTLABS"=20|Cc:=20|MIME-Version:=201.0|Content-Transfer-Encoding:=20q uoted-printable|In-Reply-To:=20<4AC65F71.8080307@bell-lab s.com>|References:=20<4A8D551B.7060308@alcatel-lucent.com >=09<9DE31798099D044DA5F3C0DEAB107C5A03C451E4@misout7msgu sr7d.ugd.att.com>=09<4AA70C29.8020804@bell-labs.com><5DA0 1D2CA74FAF40ADF71DB4177D345A02684E54@misout7msgusr7b.ugd. att.com><4AC558E4.1010200@bell-labs.com>=09<9DE31798099D0 44DA5F3C0DEAB107C5A03FE4435@misout7msgusr7d.ugd.att.com>< 5ACFADE7CFA7BF43A6B64DEED0ED918A08DEEFEF@E03MVY2-UKDY.dom ain1.systemhost.net>=20<4AC65F71.8080307@bell-labs.com>; bh=DJrVorECCY6njj29LpXbLkFY+CTy+4+IsHC7fTxx4IU=; b=BhMAcB1zj7KYTi8Nojz/Z1DqMXhMk8gqB02wvIGEZXwgmO5jNkBsDc3Q 6D6Tjbs7sWc6kzH5yCOU6irjhsGP9CSgbPIJmzeXqxtULnL6vk7CbdcEl RqnpztddL4+p4eN2HFg+tEzRkh9QM9pFKAz4hIag+WOQ3NeY0cStNMOmi o=; Authentication-Results: syd-iport-2.cisco.com; dkim=pass (signature verified [TEST]) header.i=partr@cisco.com X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAKolyUoKS+eh/2dsb2JhbAC5OohhATIJjQ8GAoJIgWCCLA X-IronPort-AV: E=Sophos;i="4.44,505,1249257600"; d="scan'208";a="58760703" Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by syd-iport-2.cisco.com with ESMTP; 05 Oct 2009 05:46:21 +0000 Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n955kIKX020369; Mon, 5 Oct 2009 13:46:18 +0800 Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n955iaRe020642; Mon, 5 Oct 2009 05:46:18 GMT Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 5 Oct 2009 11:16:09 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 5 Oct 2009 11:16:07 +0530 Message-ID: In-Reply-To: <4AC65F71.8080307@bell-labs.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [sip-overload] SIP-OVERLOAD confernece call this morning? Thread-Index: AcpDnS6/SqrgoCISTSS6SFPV1gBs8AB3kDxw References: <4A8D551B.7060308@alcatel-lucent.com> <9DE31798099D044DA5F3C0DEAB107C5A03C451E4@misout7msgusr7d.ugd.att.com> <4AA70C29.8020804@bell-labs.com><5DA01D2CA74FAF40ADF71DB4177D345A02684E54@misout7msgusr7b.ugd.att.com><4AC558E4.1010200@bell-labs.com> <9DE31798099D044DA5F3C0DEAB107C5A03FE4435@misout7msgusr7d.ugd.att.com><5ACFADE7CFA7BF43A6B64DEED0ED918A08DEEFEF@E03MVY2-UKDY.domain1.systemhost.net> <4AC65F71.8080307@bell-labs.com> From: "Parthasarathi R (partr)" To: "Volker Hilt" , , "JOHNSON, CAROLYN R,ATTLABS" X-OriginalArrivalTime: 05 Oct 2009 05:46:09.0152 (UTC) FILETIME=[23751800:01CA457F] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4697; t=1254721578; x=1255585578; c=relaxed/simple; s=hkgdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=partr@cisco.com; z=From:=20=22Parthasarathi=20R=20(partr)=22=20 |Subject:=20RE=3A=20[sip-overload]=20SIP-OVERLOAD=20confern ece=20call=20this=20morning? |Sender:=20; bh=DJrVorECCY6njj29LpXbLkFY+CTy+4+IsHC7fTxx4IU=; b=U78UXquvsfMw55ntTkrqfrhHM5caGGTFfayP6ZWJcZRLs9qGtCXTcTb8G5 WuWZkVscElT7e+teUPeShsB+zDWsSHHo5RA5tfDFL+vDcotmImc7hAbmqthZ j6ZAGxgfg7kzR88+H7OXIbU9pcBFvPpq3vJhOfEq5aX/nlXUCRnsc=; Cc: sip-overload@ietf.org Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Oct 2009 05:45:07 -0000 Hi all, I joined in this mailing list recently. Could you please send the conference details.=20 Thanks Partha =20 -----Original Message----- From: sip-overload-bounces@ietf.org [mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt Sent: Saturday, October 03, 2009 1:46 AM To: nick.m.stewart@bt.com; JOHNSON, CAROLYN R,ATTLABS Cc: sip-overload@ietf.org Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? Let's use our next scheduled slot on Oct 15 at 11:00am ET to discuss. All technical discussions need to happen on the sip-overload mailing list and not on a call! This will enable everyone to catch up on discussions and contribute. Thanks, Volker nick.m.stewart@bt.com wrote: > All, >=20 > I would like to add my support to Carolyn's case for continuing audios. > We are all busy people and it helps to maintain momentum if interested > parties meet regularly. >=20 > Thanks, >=20 > Nick >=20 > Nick Stewart > BT Innovate & Design >=20 > Tel: +44 (0)1473 629428 > Mob: +44 (0)7962 103572 > Email: nick.m.stewart@bt.com > Web: www.bt.com > This email contains BT information, which may be privileged or=20 > confidential. It's meant only for the individual(s) or entity named=20 > above. If you're not the intended recipient, note that disclosing,=20 > copying, distributing or using this information is prohibited. If=20 > you've received this email in error, please let me know immediately on > the email address above. Thank you. > We monitor our email system, and may record your emails. > British Telecommunications plc > Registered office: 81 Newgate Street London EC1A 7AJ Registered in=20 > England no: 1800000 >=20 >=20 >=20 > -----Original Message----- > From: sip-overload-bounces@ietf.org > [mailto:sip-overload-bounces@ietf.org] On Behalf Of JOHNSON, CAROLYN=20 > R, ATTLABS > Sent: 02 October 2009 14:35 > To: Volker Hilt; SIP-OVERLOAD > Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? >=20 > All, > I would prefer we have regular periodic conference calls. From=20 > personal experience and observation, it forces all of us to progress the work. > Secondly, I get over 50 emails a day on average, and I may easily miss > what is happening in this group if we rely on email as our major=20 > communication mode. Finally, my schedule is usually full, so=20 > scheduling conference calls as needed will likely exclude my=20 > participation. I expect I am not the only team member facing these business challenges. > I would strongly prefer a scheduled conference call in addition to the > emails. I'm OK with making it less frequent than our current 2-week=20 > schedule, but really think it is useful to have. How about once per=20 > month? >=20 >=20 > Carolyn > Carolyn R. Johnson > Director Research - Quantitative Analysis AT&T Labs MT D5-3B37 > 732-420-4182 > crjohnson1@att.com > =20 >=20 > -----Original Message----- > From: sip-overload-bounces@ietf.org > [mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt > Sent: Thursday, October 01, 2009 9:36 PM > To: SIP-OVERLOAD > Subject: Re: [sip-overload] SIP-OVERLOAD confernece call this morning? >=20 > All, >=20 > sorry for missing today's conf call. >=20 > I would suggest that for moving forward it is more effective to use=20 > the mailing list for discussions rather than a conference call. We can > set up a call any time we need, e.g., if there are new simulation=20 > results or a discussion on a specific item is needed. Any thoughts? >=20 > Thanks, >=20 > Volker >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 > NOEL, ERIC C, ATTLABS wrote: >> Volker, >> >> Is there a conference call this morning? I was away during last=20 >> meeting and may have missed the schedule. >> >> Thanks, >> >> Eric >> _______________________________________________ >> sip-overload mailing list >> sip-overload@ietf.org >> https://www.ietf.org/mailman/listinfo/sip-overload >=20 >=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 > _______________________________________________ > sip-overload mailing list > sip-overload@ietf.org > https://www.ietf.org/mailman/listinfo/sip-overload _______________________________________________ sip-overload mailing list sip-overload@ietf.org https://www.ietf.org/mailman/listinfo/sip-overload From partr@cisco.com Sun Oct 4 22:46:56 2009 Return-Path: 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 D0DF53A6993 for ; Sun, 4 Oct 2009 22:46:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.999 X-Spam-Level: X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[AWL=0.599, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kREqxS1RS+X5 for ; Sun, 4 Oct 2009 22:46:56 -0700 (PDT) Received: from syd-iport-2.cisco.com (syd-iport-2.cisco.com [64.104.193.197]) by core3.amsl.com (Postfix) with ESMTP id A2B2F3A6954 for ; Sun, 4 Oct 2009 22:46:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=2447; q=dns/txt; s=sydiport02001; t=1254721712; x=1255931312; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20"Parthasarathi=20R=20(partr)"=20|Subject:=20SIP=20Routing=20based=20on=20Hardware=20reso urce=20availability|Date:=20Mon,=205=20Oct=202009=2011:18 :24=20+0530|Message-ID:=20|To:=20|MIME-Version:=201.0; bh=YVO6jxPMuAHW0OQORDwV9o/uzB2dmYrUyKedtye0DNM=; b=Lg6/sEXBjC6Hi5qJcl1P6ZL9ZHrls4ZWi5QMslzfX8srfrudOJKL7H9r SulbBy+iG3GLdUw1MwkAtvN6+bUkBUGyrMe/gEfUL+A6gRK6hwioH6R3P 00P7Bk2HjP7d6IrAs3yqXiQQUook4i1sF25DnJMwBWKh4KhKRpqoKTSDa 8=; Authentication-Results: syd-iport-2.cisco.com; dkim=pass (partially verified [2386 bytes] [TEST]) header.i=partr@cisco.com X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AksFAKolyUoKS+ej/2dsb2JhbACCJi+2ZYhhAY1KBoQqgiw X-IronPort-AV: E=Sophos;i="4.44,505,1249257600"; d="scan'208,217";a="58760828" Received: from hkg-dkim-2.cisco.com ([10.75.231.163]) by syd-iport-2.cisco.com with ESMTP; 05 Oct 2009 05:48:29 +0000 Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n955mRHs014770 for ; Mon, 5 Oct 2009 13:48:27 +0800 Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n955eAtF019546 for ; Mon, 5 Oct 2009 05:48:26 GMT Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 5 Oct 2009 11:18:26 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA457F.74E16FC3" Date: Mon, 5 Oct 2009 11:18:24 +0530 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SIP Routing based on Hardware resource availability Thread-Index: AcpFf3RBqQ2FmSYuScGhJwN0q/xvQA== From: "Parthasarathi R (partr)" To: X-OriginalArrivalTime: 05 Oct 2009 05:48:26.0048 (UTC) FILETIME=[750DC400:01CA457F] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2386; t=1254721707; x=1255585707; c=relaxed/simple; s=hkgdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=partr@cisco.com; z=From:=20=22Parthasarathi=20R=20(partr)=22=20 |Subject:=20SIP=20Routing=20based=20on=20Hardware=20resourc e=20availability |Sender:=20; bh=2k56Kh9G6Jy6WCsaP0MC6vzCN+T0hcdEC92uGlsGnys=; b=Uj6q66LqiaxEpALMcOJJwaZQZhDKuRlpbzzhG/sQ4rBzBu3PN6ofNwsFbH 0frrmSmECi9aHSHS4AZ3fYhjqohtDuAJ4rViypLpzBTQoEyfvyD9aD/qS/yC f14lKc8cnAH3lW4dmDYQRzeUSc5tMG6xOG6U8zYYwLi8TyqT4Ihgs=; Subject: [sip-overload] SIP Routing based on Hardware resource availability X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Oct 2009 05:46:56 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CA457F.74E16FC3 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I'm working in SIP Overloading solution based on the individual hardware resource availability like DSP, DSO, CPU, Memory etc and the calling number. SIP overload distributing entity will route the call based on the calling number and hardware resource availability. The advantage of routing based on individual hardware availability is that maximum resource utilization. I noticed that draft-shen-sipping-load-control-event-package is based on SIP URI only. The other drafts are based on the system level resource availability (overloaded or not) only. Could Please let me know any similar draft is already available in this WG. Thanks Partha=20 ------_=_NextPart_001_01CA457F.74E16FC3 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi,

I'm working in SIP Overloading solution = based on the=20 individual hardware resource availability like DSP, DSO, CPU, Memory etc = and the=20 calling number. SIP overload distributing entity will route the call = based on=20 the calling number and hardware resource availability. The advantage of = routing=20 based on individual hardware availability is that maximum resource = utilization.=20 I noticed that draft-shen-sipping-load-control-event-package is based on = SIP URI=20 only. The other drafts are based on the system level resource = availability=20 (overloaded or not) only. Could Please let me know any similar draft is = already=20 available in this WG.

Thanks

Partha 

------_=_NextPart_001_01CA457F.74E16FC3-- From volkerh@bell-labs.com Mon Oct 5 07:45:51 2009 Return-Path: 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 54E603A688D for ; Mon, 5 Oct 2009 07:45:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.386 X-Spam-Level: X-Spam-Status: No, score=-2.386 tagged_above=-999 required=5 tests=[AWL=0.213, 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 3wglXYEPum0U for ; Mon, 5 Oct 2009 07:45:50 -0700 (PDT) Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 9B0923A67A1 for ; Mon, 5 Oct 2009 07:45:50 -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 n95ElN9Y025658; Mon, 5 Oct 2009 09:47:23 -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 n95ElH8M022620; Mon, 5 Oct 2009 09:47:22 -0500 (CDT) Received: from [135.112.131.41] (135.3.63.242) by USNAVSXCHHUB02.ndc.alcatel-lucent.com (135.3.39.111) with Microsoft SMTP Server (TLS) id 8.1.375.2; Mon, 5 Oct 2009 09:47:19 -0500 Message-ID: <4ACA06F5.3070702@bell-labs.com> Date: Mon, 5 Oct 2009 10:47:17 -0400 From: Volker Hilt User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: "Parthasarathi R (partr)" References: In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35 Cc: "sip-overload@ietf.org" Subject: Re: [sip-overload] SIP Routing based on Hardware resource availability X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Oct 2009 14:45:51 -0000 Partha, I think you are looking at the correct set of drafts. Volker Parthasarathi R (partr) wrote: > Hi, > > I'm working in SIP Overloading solution based on the individual hardware > resource availability like DSP, DSO, CPU, Memory etc and the calling > number. SIP overload distributing entity will route the call based on > the calling number and hardware resource availability. The advantage of > routing based on individual hardware availability is that maximum > resource utilization. I noticed that > draft-shen-sipping-load-control-event-package is based on SIP URI only. > The other drafts are based on the system level resource availability > (overloaded or not) only. Could Please let me know any similar draft is > already available in this WG. > > Thanks > > Partha > From partr@cisco.com Mon Oct 5 18:38:47 2009 Return-Path: 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 5BC2D3A6890 for ; Mon, 5 Oct 2009 18:38:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.1 X-Spam-Level: X-Spam-Status: No, score=-4.1 tagged_above=-999 required=5 tests=[AWL=1.102, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, 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 DhIEodsV3xde for ; Mon, 5 Oct 2009 18:38:46 -0700 (PDT) Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 3A59C3A67C2 for ; Mon, 5 Oct 2009 18:38:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=4696; q=dns/txt; s=sjiport03001; t=1254793222; x=1256002822; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20"Parthasarathi=20R=20(partr)"=20|Subject:=20RE:=20[sip-overload]=20SIP=20Routing=20based =20on=20Hardware=20resource=20availability|Date:=20Tue, =206=20Oct=202009=2007:10:19=20+0530|Message-ID:=20 |To:=20"Volker=20Hilt"=20|Cc:=20,=0D=0A=20=20=20=20=20=20=20=20"Shes hadri=20Shalya=20(svshesha)"=20 |MIME-Version:=201.0|References:=20=20<4ACA06F5.3070 702@bell-labs.com>; bh=PHOUuFvTbCycMKW1I7Bx8TYUZ53Se95rMcSPBVqreaE=; b=Ghw5SHFaSxQa8c8FNG6s5mfv8xrwTPjaXLmkcxY7nv0rkT9UHUZPhM0m /ldgpNimzuFyHJybMX9WxV/oNFegN+l0nrAQrhngHzBqfOr51xuyS6jMA vIISTHHL93q+gjYhNZfP9YiY2/+bwSLRERR56i4f43JRpzbEqNluBSk2D U=; Authentication-Results: sj-iport-3.cisco.com; dkim=pass (partially verified [4637 bytes] [TEST]) header.i=partr@cisco.com X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgEFAFg8ykqrR7O6/2dsb2JhbACCJi6XAaFpiGEBjlwGhCqCLA X-IronPort-AV: E=Sophos;i="4.44,509,1249257600"; d="scan'208,217";a="194481729" Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-3.cisco.com with ESMTP; 06 Oct 2009 01:40:22 +0000 Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n961eLvS016506; Mon, 5 Oct 2009 18:40:21 -0700 Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n961eK2C018185; Tue, 6 Oct 2009 01:40:21 GMT Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 6 Oct 2009 07:10:20 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA4625.F69FA6C1" Date: Tue, 6 Oct 2009 07:10:19 +0530 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [sip-overload] SIP Routing based on Hardware resource availability Thread-Index: AcpFysqg3Ne9dZHOQxCNKRZFSMSAgAAV7amB References: <4ACA06F5.3070702@bell-labs.com> From: "Parthasarathi R (partr)" To: "Volker Hilt" X-OriginalArrivalTime: 06 Oct 2009 01:40:20.0473 (UTC) FILETIME=[F6F90690:01CA4625] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4637; t=1254793221; x=1255657221; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=partr@cisco.com; z=From:=20=22Parthasarathi=20R=20(partr)=22=20 |Subject:=20RE=3A=20[sip-overload]=20SIP=20Routing=20based= 20on=20Hardware=20resource=20availability |Sender:=20; bh=jXcMTPxdeN208XE13ocKAUiLl7Px3n8UZdmoQCMowTI=; b=pWlJQ6EIXSMhJvClvYMMK9ZD/h2CEkSetvBv/DGVaaFJvscZvul+EEjt0J y9ERXYXJ7CaGP2r5+EQW0yisuqMAkaKuaYIhUImZGhHTC//ooUOF3nWeQhZn RlEtiSypFP; Cc: "Sheshadri Shalya \(svshesha\)" , sip-overload@ietf.org Subject: Re: [sip-overload] SIP Routing based on Hardware resource availability X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2009 01:38:47 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CA4625.F69FA6C1 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Volker/All, =20 Thanks for the information Volker. I will come up with the draft which = provides the mechanism for Resource availability based SIP routing. = Please let me know incase any concern in including this requirement in = this WG. =20 Thanks Partha ________________________________ From: Volker Hilt [mailto:volkerh@bell-labs.com] Sent: Mon 10/5/2009 8:17 PM To: Parthasarathi R (partr) Cc: sip-overload@ietf.org Subject: Re: [sip-overload] SIP Routing based on Hardware resource = availability Partha, I think you are looking at the correct set of drafts. Volker Parthasarathi R (partr) wrote: > Hi, > > I'm working in SIP Overloading solution based on the individual = hardware > resource availability like DSP, DSO, CPU, Memory etc and the calling > number. SIP overload distributing entity will route the call based on > the calling number and hardware resource availability. The advantage = of > routing based on individual hardware availability is that maximum > resource utilization. I noticed that > draft-shen-sipping-load-control-event-package is based on SIP URI = only. > The other drafts are based on the system level resource availability > (overloaded or not) only. Could Please let me know any similar draft = is > already available in this WG. > > Thanks > > Partha > ------_=_NextPart_001_01CA4625.F69FA6C1 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: [sip-overload] SIP Routing based on = Hardware resource availability=0A= =0A= =0A= =0A=
=0A=
=0A=

Hi = Volker/All,

=0A=

 

=0A=

Thanks for the information = Volker. I will come up with the draft which provides the = mechanism for Resource availability based SIP routing. Please let = me know incase any concern in including this requirement in this = WG.

=0A=

 

=0A=

Thanks

=0A=

Partha

=0A=
=0A= From: Volker Hilt = [mailto:volkerh@bell-labs.com]
Sent: Mon 10/5/2009 8:17 = PM
To: Parthasarathi R (partr)
Cc: = sip-overload@ietf.org
Subject: Re: [sip-overload] SIP Routing = based on Hardware resource availability

=0A=
=0A=

Partha,

I think you are looking at the correct = set of drafts.

Volker


Parthasarathi R (partr) = wrote:
> Hi,
>
> I'm working in SIP Overloading = solution based on the individual hardware
> resource availability = like DSP, DSO, CPU, Memory etc and the calling
> number. SIP = overload distributing entity will route the call based on
> the = calling number and hardware resource availability. The advantage = of
> routing based on individual hardware availability is that = maximum
> resource utilization. I noticed that
> = draft-shen-sipping-load-control-event-package is based on SIP URI = only.
> The other drafts are based on the system level resource = availability
> (overloaded or not) only. Could Please let me know = any similar draft is
> already available in this = WG.
>
> Thanks
>
> = Partha
>

------_=_NextPart_001_01CA4625.F69FA6C1-- From volkerh@bell-labs.com Mon Oct 26 08:20:45 2009 Return-Path: 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 2BD1C3A67E7 for ; Mon, 26 Oct 2009 08:20:44 -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 HR4HYy7CfkhD for ; Mon, 26 Oct 2009 08:20:44 -0700 (PDT) Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id E50CB3A6A03 for ; Mon, 26 Oct 2009 08:20:42 -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 n9QFKtcf020223 for ; Mon, 26 Oct 2009 10:20:55 -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 n9QFKmJv013528 for ; Mon, 26 Oct 2009 10:20:55 -0500 (CDT) Received: from [135.112.131.41] (135.3.63.242) by USNAVSXCHHUB01.ndc.alcatel-lucent.com (135.3.39.110) with Microsoft SMTP Server (TLS) id 8.1.375.2; Mon, 26 Oct 2009 10:20:52 -0500 Message-ID: <4AE5BE5C.1050803@alcatel-lucent.com> Date: Mon, 26 Oct 2009 11:21:00 -0400 From: Volker Hilt User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: "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 Subject: [sip-overload] [Fwd: I-D Action:draft-hilt-sipping-overload-07.txt] X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Oct 2009 15:20:45 -0000 I've submitted a new version of the overload control draft (see below). Thanks, Volker ---------------- New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Session Initiation Protocol (SIP) Overload Control Author(s) : V. Hilt, H. Schulzrinne Filename : draft-hilt-sipping-overload-07.txt Pages : 14 Date : 2009-10-25 Overload occurs in Session Initiation Protocol (SIP) networks when SIP servers have insufficient resources to handle all SIP messages they receive. Even though the SIP protocol provides a limited overload control mechanism through its 503 (Service Unavailable) response code, SIP servers are still vulnerable to overload. This document defines an overload control mechanism for SIP. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-hilt-sipping-overload-07.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. From en5192@att.com Tue Oct 27 06:13:50 2009 Return-Path: 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 AC1D43A6859 for ; Tue, 27 Oct 2009 06:13:50 -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 pyqXPaIjWIHU for ; Tue, 27 Oct 2009 06:13:49 -0700 (PDT) Received: from mail167.messagelabs.com (mail167.messagelabs.com [216.82.253.179]) by core3.amsl.com (Postfix) with ESMTP id A24DA3A6782 for ; Tue, 27 Oct 2009 06:13:49 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: en5192@att.com X-Msg-Ref: server-7.tower-167.messagelabs.com!1256649242!18922942!1 X-StarScan-Version: 6.1.3; banners=-,-,- X-Originating-IP: [144.160.20.146] Received: (qmail 19700 invoked from network); 27 Oct 2009 13:14:02 -0000 Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-7.tower-167.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Oct 2009 13:14:02 -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 n9RDE1VE003976 for ; Tue, 27 Oct 2009 09:14:01 -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 n9RDDwt0003963 for ; Tue, 27 Oct 2009 09:13:58 -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, 27 Oct 2009 09:13:58 -0400 Message-ID: <5DA01D2CA74FAF40ADF71DB4177D345A02684F69@misout7msgusr7b.ugd.att.com> In-Reply-To: <4AE5BE5C.1050803@alcatel-lucent.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [sip-overload] [Fwd: I-D Action:draft-hilt-sipping-overload-07.txt] Thread-Index: AcpWT/eM1EJai1QXQ7uuDoCcVni76gAtSwjw References: <4AE5BE5C.1050803@alcatel-lucent.com> From: "NOEL, ERIC C (ATTLABS)" To: "Volker Hilt" , X-Mailman-Approved-At: Tue, 27 Oct 2009 07:23:15 -0700 Subject: Re: [sip-overload] [Fwd: I-D Action:draft-hilt-sipping-overload-07.txt] X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Oct 2009 14:21:55 -0000 Volker, Based, on our conference call 2 weeks ago, I understand the sip-overload group immediate role would be to provide comments (over the sip-overload mailing list) on both =20 http://www.ietf.org/internet-drafts/draft-hilt-sipping-overload-07.txt And=20 http://tools.ietf.org/html/draft-shen-sipping-load-control-event-package -02 And that going forward we would interact through the sip-overload mailing list.=20 Our (sip overload design team) bi-weekly conference calls are in effect stopped and will only occur on a as needed basis (i.e. presentation form team member....). Lastly, I presented a paper titled "Novel Overload Controls for SIP Networks" (Eric Noel & Carolyn Johnson co-authored) to ITC21 (http://www.i-teletraffic.org/itc21/technical-program/). For copyright reasons, I cannot broadcast an e-version of that paper. Eventually it will be available through IEEE explorer. Thanks, Eric =20 =20 -----Original Message----- From: sip-overload-bounces@ietf.org [mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt Sent: Monday, October 26, 2009 11:21 AM To: sip-overload@ietf.org Subject: [sip-overload] [Fwd: I-D Action:draft-hilt-sipping-overload-07.txt] I've submitted a new version of the overload control draft (see below). Thanks, Volker ---------------- New Internet-Draft is available from the on-line Internet-Drafts=20 directories. Title : Session Initiation Protocol (SIP) Overload Control Author(s) : V. Hilt, H. Schulzrinne Filename : draft-hilt-sipping-overload-07.txt Pages : 14 Date : 2009-10-25 Overload occurs in Session Initiation Protocol (SIP) networks when SIP servers have insufficient resources to handle all SIP messages they receive. Even though the SIP protocol provides a limited overload control mechanism through its 503 (Service Unavailable) response code, SIP servers are still vulnerable to overload. This document defines an overload control mechanism for SIP. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-hilt-sipping-overload-07.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ sip-overload mailing list sip-overload@ietf.org https://www.ietf.org/mailman/listinfo/sip-overload From volkerh@bell-labs.com Tue Oct 27 07:36:13 2009 Return-Path: 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 0CF4F3A6979 for ; Tue, 27 Oct 2009 07:36:13 -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 8vxQoE4IQoMd for ; Tue, 27 Oct 2009 07:36:09 -0700 (PDT) Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 3CDEC3A688B for ; Tue, 27 Oct 2009 07:36:08 -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 n9REaMqO020477 for ; Tue, 27 Oct 2009 09:36:22 -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 n9REaMY1022309 for ; Tue, 27 Oct 2009 09:36:22 -0500 (CDT) Received: from [127.0.0.1] (135.3.63.243) by USNAVSXCHHUB01.ndc.alcatel-lucent.com (135.3.39.110) with Microsoft SMTP Server (TLS) id 8.1.375.2; Tue, 27 Oct 2009 09:36:22 -0500 Message-ID: <4AE7055E.9060208@alcatel-lucent.com> Date: Tue, 27 Oct 2009 10:36:14 -0400 From: Volker Hilt User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: "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 Subject: [sip-overload] Expert Review for Overload Control Drafts X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Oct 2009 14:36:13 -0000 All, We are looking for experts who can do a review for the following two drafts: http://www.ietf.org/internet-drafts/draft-hilt-sipping-overload-07.txt http://tools.ietf.org/html/draft-shen-sipping-load-control-event-package-03.txt Please send me a quick note if you are interested and available to do a review for one of these drafts (or both of them). Please post the review on this mailing list. We had many people expressing interest in contributing to a SIP overload control solution. This is a great chance to do so! Thanks, Volker From victor.pascual.avila@gmail.com Tue Oct 27 07:41:22 2009 Return-Path: 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 3EAFC28C217 for ; Tue, 27 Oct 2009 07:41:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.542 X-Spam-Level: X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 YXC2UQ3hntym for ; Tue, 27 Oct 2009 07:41:19 -0700 (PDT) Received: from mail-ew0-f208.google.com (mail-ew0-f208.google.com [209.85.219.208]) by core3.amsl.com (Postfix) with ESMTP id CCCF828C0EB for ; Tue, 27 Oct 2009 07:41:18 -0700 (PDT) Received: by ewy4 with SMTP id 4so218582ewy.37 for ; Tue, 27 Oct 2009 07:41:29 -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=Hn3x4OiYFMYOlPwVGW3xfJ7ZJwtUkIw61Vr/fvQWj+g=; b=mKrx2edY33NAVQzWx4YaYqZjIa4MeqUqmi9jYuVyr0Bjdk6KpjBTY8BAKIBaYiJLiO RyZs0GAJxT6yoOuEGLEehWMk3UxTSniwAv7q5UOLMyL/LxSDizt7G//iiptZCocXnHDT KMdN42OlDhghOd53gkFPGj8QNbsp4b/iVECx4= 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=uhcVOSnCAq7hISSih373pQrCiJTzAMm0TkOPKdh3eNaCvrBoqugaQe9EaibTy7jtI5 kqARmRujDcHNgCYq2ouPJRNm/aoxQwMlXz4eFjyKfTOEPSWzHbayM4gjxcdKdnJikP0X e07+4CRm7v7Rpbq2iTOn+jSgKCrshTwrbWyzc= MIME-Version: 1.0 Received: by 10.216.90.18 with SMTP id d18mr2825496wef.225.1256654489299; Tue, 27 Oct 2009 07:41:29 -0700 (PDT) In-Reply-To: <5DA01D2CA74FAF40ADF71DB4177D345A02684F69@misout7msgusr7b.ugd.att.com> References: <4AE5BE5C.1050803@alcatel-lucent.com> <5DA01D2CA74FAF40ADF71DB4177D345A02684F69@misout7msgusr7b.ugd.att.com> Date: Tue, 27 Oct 2009 15:41:29 +0100 Message-ID: <618e24240910270741i6176eae7n83c5ef983ee31402@mail.gmail.com> From: Victor Pascual Avila To: "NOEL, ERIC C (ATTLABS)" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: sip-overload@ietf.org Subject: Re: [sip-overload] [Fwd: I-D Action:draft-hilt-sipping-overload-07.txt] X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Oct 2009 14:41:23 -0000 Hi, On Tue, Oct 27, 2009 at 2:13 PM, NOEL, ERIC C (ATTLABS) wr= ote: > http://tools.ietf.org/html/draft-shen-sipping-load-control-event-package Is the goal to define a SIP event package enabling notification according to various XML schema (please see [1]) or rather mandating the support of a particular schema? [1] Draft ETSI ES 283 039-2 V3.0.0 (2009-06), Section 6 Thanks, --=20 Victor Pascual =C3=81vila From en5192@att.com Wed Oct 28 06:50:45 2009 Return-Path: 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 46D753A69E7 for ; Wed, 28 Oct 2009 06:50:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.565 X-Spam-Level: X-Spam-Status: No, score=-106.565 tagged_above=-999 required=5 tests=[AWL=0.034, 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 yJgyTa0GzxYG for ; Wed, 28 Oct 2009 06:50:44 -0700 (PDT) Received: from mail167.messagelabs.com (mail167.messagelabs.com [216.82.253.179]) by core3.amsl.com (Postfix) with ESMTP id 06E193A69D7 for ; Wed, 28 Oct 2009 06:50:43 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: en5192@att.com X-Msg-Ref: server-3.tower-167.messagelabs.com!1256737857!12828964!1 X-StarScan-Version: 6.1.3; banners=-,-,- X-Originating-IP: [144.160.20.146] Received: (qmail 1764 invoked from network); 28 Oct 2009 13:50:58 -0000 Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-3.tower-167.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 28 Oct 2009 13:50:58 -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 n9SDov3T022322 for ; Wed, 28 Oct 2009 09:50:57 -0400 Received: from misout7msgusr7b.ugd.att.com (misout7msgusr7b.ugd.att.com [144.155.43.104]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id n9SDoqit022280 for ; Wed, 28 Oct 2009 09:50:52 -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: Wed, 28 Oct 2009 09:50:52 -0400 Message-ID: <5DA01D2CA74FAF40ADF71DB4177D345A02684F83@misout7msgusr7b.ugd.att.com> In-Reply-To: <4AE7055E.9060208@alcatel-lucent.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [sip-overload] Expert Review for Overload Control Drafts Thread-Index: AcpXEuI94mIDNVh1Txm4o6iWXQRrvgAwlomQ References: <4AE7055E.9060208@alcatel-lucent.com> From: "NOEL, ERIC C (ATTLABS)" To: "Volker Hilt" , X-Mailman-Approved-At: Wed, 28 Oct 2009 17:55:44 -0700 Subject: Re: [sip-overload] Expert Review for Overload Control Drafts X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Oct 2009 13:50:45 -0000 Volker, I do not consider myself as an expert, but I will be reviewing both drafts based on my experience in SIP based overload control algorithms and associated simulation model implementation. Thanks, Eric=20 -----Original Message----- From: sip-overload-bounces@ietf.org [mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt Sent: Tuesday, October 27, 2009 10:36 AM To: sip-overload@ietf.org Subject: [sip-overload] Expert Review for Overload Control Drafts All, We are looking for experts who can do a review for the following two drafts: http://www.ietf.org/internet-drafts/draft-hilt-sipping-overload-07.txt http://tools.ietf.org/html/draft-shen-sipping-load-control-event-package -03.txt Please send me a quick note if you are interested and available to do a=20 review for one of these drafts (or both of them). Please post the review on this mailing list. We had many people expressing interest in contributing to a SIP overload control solution. This is a great chance to do so! Thanks, Volker _______________________________________________ sip-overload mailing list sip-overload@ietf.org https://www.ietf.org/mailman/listinfo/sip-overload From youssef.chadli@orange-ftgroup.com Thu Oct 29 08:45:30 2009 Return-Path: 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 3DF0D3A698F for ; Thu, 29 Oct 2009 08:45:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nw3e6EnHxzIf for ; Thu, 29 Oct 2009 08:45:29 -0700 (PDT) Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 13CA03A697C for ; Thu, 29 Oct 2009 08:45:28 -0700 (PDT) Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959); Thu, 29 Oct 2009 16:45:41 +0100 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: Thu, 29 Oct 2009 16:45:42 +0100 Message-ID: <9ECCF01B52E7AB408A7EB85352642141ACA0BF@ftrdmel0.rd.francetelecom.fr> In-Reply-To: <4AE7055E.9060208@alcatel-lucent.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [sip-overload] Expert Review for Overload Control Drafts Thread-Index: AcpXEuIw8s6jQWWRTQ+jE3M0AFGH/ABm9hcA References: <4AE7055E.9060208@alcatel-lucent.com> From: To: , X-OriginalArrivalTime: 29 Oct 2009 15:45:41.0476 (UTC) FILETIME=[DE8C2240:01CA58AE] Subject: Re: [sip-overload] Expert Review for Overload Control Drafts X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2009 15:45:30 -0000 Hi,=20 I will be happy to review these drafts. Best regards Youssef=20 -----Message d'origine----- De : sip-overload-bounces@ietf.org = [mailto:sip-overload-bounces@ietf.org] De la part de Volker Hilt Envoy=E9 : mardi 27 octobre 2009 15:36 =C0 : sip-overload@ietf.org Objet : [sip-overload] Expert Review for Overload Control Drafts All, We are looking for experts who can do a review for the following two = drafts: http://www.ietf.org/internet-drafts/draft-hilt-sipping-overload-07.txt http://tools.ietf.org/html/draft-shen-sipping-load-control-event-package-= 03.txt Please send me a quick note if you are interested and available to do a = review for one of these drafts (or both of them). Please post the review = on this mailing list. We had many people expressing interest in contributing to a SIP overload = control solution. This is a great chance to do so! Thanks, Volker _______________________________________________ sip-overload mailing list sip-overload@ietf.org https://www.ietf.org/mailman/listinfo/sip-overload From partr@cisco.com Thu Oct 29 23:30:23 2009 Return-Path: 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 9E52C3A6A2C for ; Thu, 29 Oct 2009 23:30:23 -0700 (PDT) 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 krHK64a3MgPn for ; Thu, 29 Oct 2009 23:30:22 -0700 (PDT) Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 9564B3A63D3 for ; Thu, 29 Oct 2009 23:30:22 -0700 (PDT) Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAHsl6kpAaHte/2dsb2JhbADHPZgXhD0EglY X-IronPort-AV: E=Sophos;i="4.44,651,1249257600"; d="scan'208";a="263776420" Received: from hkg-core-1.cisco.com ([64.104.123.94]) by sj-iport-1.cisco.com with ESMTP; 30 Oct 2009 06:30:22 +0000 Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n9U6UKKU003284; Fri, 30 Oct 2009 06:30:21 GMT Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 30 Oct 2009 12:00:21 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 30 Oct 2009 12:00:20 +0530 Message-ID: In-Reply-To: <4AE7055E.9060208@alcatel-lucent.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [sip-overload] Expert Review for Overload Control Drafts Thread-Index: AcpXEu5jACpgmkqpQtefL0jaVB0zVACFzmdA References: <4AE7055E.9060208@alcatel-lucent.com> From: "Parthasarathi R (partr)" To: "Volker Hilt" , X-OriginalArrivalTime: 30 Oct 2009 06:30:21.0219 (UTC) FILETIME=[748A2730:01CA592A] Subject: Re: [sip-overload] Expert Review for Overload Control Drafts X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2009 06:30:23 -0000 Hi Volker, I'll provide the review comments based on my SIP overload understanding. Thanks Partha=20 -----Original Message----- From: sip-overload-bounces@ietf.org [mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt Sent: Tuesday, October 27, 2009 8:06 PM To: sip-overload@ietf.org Subject: [sip-overload] Expert Review for Overload Control Drafts All, We are looking for experts who can do a review for the following two drafts: http://www.ietf.org/internet-drafts/draft-hilt-sipping-overload-07.txt http://tools.ietf.org/html/draft-shen-sipping-load-control-event-package -03.txt Please send me a quick note if you are interested and available to do a review for one of these drafts (or both of them). Please post the review on this mailing list. We had many people expressing interest in contributing to a SIP overload control solution. This is a great chance to do so! Thanks, Volker _______________________________________________ sip-overload mailing list sip-overload@ietf.org https://www.ietf.org/mailman/listinfo/sip-overload