Re: [sip-overload] comments on draft-ietf-soc-overload-rate-control-01
"NOEL, ERIC C (ERIC C)" <ecnoel@research.att.com> Thu, 05 April 2012 21:22 UTC
Return-Path: <ecnoel@research.att.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 A767221F866B for <sip-overload@ietfa.amsl.com>; Thu, 5 Apr 2012 14:22: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZqB2RdBSbIKV for <sip-overload@ietfa.amsl.com>; Thu, 5 Apr 2012 14:22:57 -0700 (PDT)
Received: from mail-pink.research.att.com (mail-pink.research.att.com [192.20.225.111]) by ietfa.amsl.com (Postfix) with ESMTP id D00A721F860E for <sip-overload@ietf.org>; Thu, 5 Apr 2012 14:22:56 -0700 (PDT)
Received: from mail-blue.research.att.com (unknown [135.207.178.11]) by mail-pink.research.att.com (Postfix) with ESMTP id 813EB12044A; Thu, 5 Apr 2012 17:22:47 -0400 (EDT)
Received: from njfpsrvexg1.research.att.com (njfpsrvexg1.research.att.com [135.207.177.20]) by mail-blue.research.att.com (Postfix) with ESMTP id 75A4AEF846; Thu, 5 Apr 2012 17:22:30 -0400 (EDT)
Received: from concierge.research.att.com (135.207.179.20) by njfpsrvexg1.research.att.com (135.207.177.20) with Microsoft SMTP Server (TLS) id 8.3.245.1; Thu, 5 Apr 2012 17:20:13 -0400
Received: from njfpsrvexg6.research.att.com ([fe80:0000:0000:0000:a8f7:a94a:213.189.254.11]) by concierge.research.att.com ([135.207.24.83]) with mapi; Thu, 5 Apr 2012 17:22:45 -0400
From: "NOEL, ERIC C (ERIC C)" <ecnoel@research.att.com>
To: 'Volker Hilt' <volker.hilt@bell-labs.com>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Date: Thu, 05 Apr 2012 17:24:11 -0400
Thread-Topic: [sip-overload] comments on draft-ietf-soc-overload-rate-control-01
Thread-Index: Ac0MPmSS86udd2loRVCepKZkBCHFDwHLRsKA
Message-ID: <2F8FB48C17221643AD77FA295756D2A73E64C15B08@njfpsrvexg6.research.att.com>
References: <4F71F78E.80009@bell-labs.com>
In-Reply-To: <4F71F78E.80009@bell-labs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Thu, 05 Apr 2012 21:22:57 -0000
Volker, Apologies for the delayed response. Phil is away and could not provide input to below, and I am about to go away as well. So I am giving you partial responses which I will complete upon my return. Janet also provided some input in below. - Section 3.4.: But when deriving this rate the server may need to take into account the effect of the client prioritization on the load it receives, e.g. CPU utilization will depend upon the characteristics of the requests. How should the server take the client prioritization into account? Does the server need to know the prioritization made by the client? [EN/JG] The server does not know the client(s) prioritization rules, but it could account for it implicitly by relying on a resource measure such as the average CPU load per request due to the particular request stream mix resulting from the client's admission control. Using this measure would allow the server to take into account the client prioritization. - Section 3.5.: What is the adjusted-oc-value? Is this the value received in the oc parameter? How will it be adjusted? [EN/JG] The parameter "adjusted-oc-value" is a typo, should be "oc-value". Will be changed in the next version. How should the values TAU1 and TAU2 be set with respect to the overall TAU? Can you give guidance on how they should be chosen? What will they depend on? [EN/JG] Putting together a small model to produce guidance on parameter selection. It would be very helpful to have a pseudo-code algorithm for rate based controls. This will make the description in this section easier to understand. [EN/JG] Will be added in next version. 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 -----Original Message----- From: sip-overload-bounces@ietf.org [mailto:sip-overload-bounces@ietf.org] On Behalf Of Volker Hilt Sent: Tuesday, March 27, 2012 1:23 PM To: sip-overload@ietf.org Subject: [sip-overload] comments on draft-ietf-soc-overload-rate-control-01 Eric, Phil, here are a few comments on draft-ietf-soc-overload-rate-control-01: - Section 3.4.: But when deriving this rate the server may need to take into account the effect of the client prioritization on the load it receives, e.g. CPU utilization will depend upon the characteristics of the requests. How should the server take the client prioritization into account? Does the server need to know the prioritization made by the client? - Section 3.5.: What is the adjusted-oc-value? Is this the value received in the oc parameter? How will it be adjusted? How should the values TAU1 and TAU2 be set with respect to the overall TAU? Can you give guidance on how they should be chosen? What will they depend on? It would be very helpful to have a pseudo-code algorithm for rate based controls. This will make the description in this section easier to understand. Thanks, Volker _______________________________________________ sip-overload mailing list sip-overload@ietf.org https://www.ietf.org/mailman/listinfo/sip-overload
- [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)