Re: [sip-overload] comments on draft-ietf-soc-overload-rate-control-01
Janet P Gunn <jgunn6@csc.com> Mon, 07 May 2012 15:06 UTC
Return-Path: <jgunn6@csc.com>
X-Original-To: sip-overload@ietfa.amsl.com
Delivered-To: sip-overload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D340F21F85CE for <sip-overload@ietfa.amsl.com>; Mon, 7 May 2012 08:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.492
X-Spam-Level:
X-Spam-Status: No, score=-6.492 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EnvOoJHwz4AH for <sip-overload@ietfa.amsl.com>; Mon, 7 May 2012 08:06:10 -0700 (PDT)
Received: from mail85.messagelabs.com (mail85.messagelabs.com [216.82.241.211]) by ietfa.amsl.com (Postfix) with ESMTP id ECD1A21F85CF for <sip-overload@ietf.org>; Mon, 7 May 2012 08:06:09 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-10.tower-85.messagelabs.com!1336403167!31514062!1
X-Originating-IP: [20.137.2.88]
X-StarScan-Version: 6.5.7; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29932 invoked from network); 7 May 2012 15:06:07 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-10.tower-85.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 May 2012 15:06:07 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q47F62PT011021 for <sip-overload@ietf.org>; Mon, 7 May 2012 11:06:06 -0400
In-Reply-To: <2F8FB48C17221643AD77FA295756D2A73E64C15BD9@njfpsrvexg6.research.att.com>
References: <4F71F78E.80009@bell-labs.com> <2F8FB48C17221643AD77FA295756D2A73E64C15B08@njfpsrvexg6.research.att.com> <4F7F509B.3080608@bell-labs.com> <OF35AA9EC7.22C467FD-ON852579F1.006DC582-852579F1.006E0D4A@csc.com> <2F8FB48C17221643AD77FA295756D2A73E64C15BD9@njfpsrvexg6.research.att.com>
To: "NOEL, ERIC C (ERIC C)" <ecnoel@att.com>
MIME-Version: 1.0
X-KeepSent: 41C4006D:EC209FFA-852579F7:00524F89; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP3 July 11, 2011
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF41C4006D.EC209FFA-ON852579F7.00524F89-852579F7.0052F498@csc.com>
Date: Mon, 07 May 2012 11:06:00 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 05/07/2012 11:02:46 AM, Serialize complete at 05/07/2012 11:02:46 AM
Content-Type: multipart/alternative; boundary="=_alternative 0052F453852579F7_="
Cc: "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: Re: [sip-overload] comments on draft-ietf-soc-overload-rate-control-01
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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 May 2012 15:06:10 -0000
From: "NOEL, ERIC C (ERIC C)" <ecnoel@research.att.com> To: Janet P Gunn/USA/CSC@CSC, "sip-overload@ietf.org" <sip-overload@ietf.org> Date: 05/07/2012 10:01 AM Subject: RE: [sip-overload] comments on draft-ietf-soc-overload-rate-control-01 Janet, Thanks for your comments. Please see below our response. Thanks, Eric Noel AT&T Labs, Inc. Rethink Possible Network Design and Performance Analysis 200 South Laurel Avenue, D5-3D19 Middletown, NJ 07748 P: 732.420.4174 ecnoel@att.com These are largely editorial comments. ... Sec 3.4 ... 4th para Note that the target SIP request rate is a max rate that may not be attained by the arrival rate at the client, and the server cannot assume that it will. To Note that the target SIP request rate is an upper bound on the rate the client may send requests to the server. In many cases, the client will send messages at a lower rate. > Suggested writing is different than original paragraph meaning. Originally that paragraph stated the server should not assume the arrival rate at client will exceed the server target rate. Your suggested change does away with the observation on the arrival rate at client and focuses on the arrival rate presented by the client to the server. Was that the intent? [JPG] I guess I am confused. Why would the server care what the arrival rate at the client is? Why would the server assume that the arrival rate at the client ( which may be distributed among many different servers) would, or would not, be bigger that the server target rate? Janet
- [sip-overload] comments on draft-ietf-soc-overloa… Volker Hilt
- Re: [sip-overload] comments on draft-ietf-soc-ove… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] comments on draft-ietf-soc-ove… Volker Hilt
- [sip-overload] comments on draft-ietf-soc-overloa… Janet P Gunn
- Re: [sip-overload] comments on draft-ietf-soc-ove… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] comments on draft-ietf-soc-ove… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] comments on draft-ietf-soc-ove… Janet P Gunn
- Re: [sip-overload] comments on draft-ietf-soc-ove… NOEL, ERIC C (ERIC C)