Re: [sip-overload] comments on draft-ietf-soc-overload-rate-control-01

["NOEL, ERIC C (ERIC C)" <[e-mail]>]

Janet,

Thanks for your follow-up comment.

==================
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?
===================

Another interpretation of the contentious paragraph is that because the client Leaky Bucket will not throttle offered load below the target SIP request rate, the server does not need to make any immediate adjustments for such situations. This is in contrast with percent blocking where blocking is applied by clients whether or not the offered load presented to clients is below the server overload limit.

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
[e-mail]<mailto:[e-mail]>

From: Janet P Gunn [mailto:[e-mail]]
Sent: Monday, May 07, 2012 11:06 AM
To: NOEL, ERIC C (ERIC C)
Cc: [e-mail]
Subject: RE: [sip-overload] comments on draft-ietf-soc-overload-rate-control-01






From:        "NOEL, ERIC C (ERIC C)" <[e-mail]<mailto:[e-mail]>>
To:        Janet P Gunn/USA/CSC@CSC, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
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
[e-mail]<mailto:[e-mail]>


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