Re: [sipcore] AD review: draft-ietf-sipcore-event-rate-control-04

<krisztian.kiss@nokia.com> Thu, 30 September 2010 07:17 UTC

Return-Path: <krisztian.kiss@nokia.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4B163A6DD6 for <sipcore@core3.amsl.com>; Thu, 30 Sep 2010 00:17:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.338
X-Spam-Level:
X-Spam-Status: No, score=-6.338 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XLbwrwOdI8H9 for <sipcore@core3.amsl.com>; Thu, 30 Sep 2010 00:17:27 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id DC40F3A6E1D for <sipcore@ietf.org>; Thu, 30 Sep 2010 00:16:38 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx06.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o8U7H7hn008534; Thu, 30 Sep 2010 10:17:17 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 30 Sep 2010 10:17:12 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 30 Sep 2010 10:17:04 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-04.mgdnok.nokia.com ([65.54.30.8]) with mapi; Thu, 30 Sep 2010 09:17:03 +0200
From: krisztian.kiss@nokia.com
To: jgunn6@csc.com
Date: Thu, 30 Sep 2010 09:17:03 +0200
Thread-Topic: [sipcore] AD review: draft-ietf-sipcore-event-rate-control-04
Thread-Index: Acss4ccjInMBAbxhSB2mA5wlVsCQEwzRZWhg
Message-ID: <A80667440D58A1469E651BA443BED3C15483986DE7@NOK-EUMSG-01.mgdnok.nokia.com>
References: <99619466-573D-4CEA-ACCD-3A3D262EB2B0@nostrum.com> <A80667440D58A1469E651BA443BED3C1547F4EDE9D@NOK-EUMSG-01.mgdnok.nokia.com> <OFAA614B95.28939D2C-ON85257762.006BA0F9-85257765.006C073D@csc.com> <OF83203587.D64E8A92-ON85257769.0076B37E-85257769.00770588@LocalDomain> <OF94ACB9BB.9CFE31F2-ON8525776C.005B6D79-8525776C.005BD2D2@csc.com>
In-Reply-To: <OF94ACB9BB.9CFE31F2-ON8525776C.005B6D79-8525776C.005BD2D2@csc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A80667440D58A1469E651BA443BED3C15483986DE7NOKEUMSG01mgd_"
MIME-Version: 1.0
X-OriginalArrivalTime: 30 Sep 2010 07:17:04.0368 (UTC) FILETIME=[7BBAFF00:01CB606F]
X-Nokia-AV: Clean
Cc: sipcore@ietf.org
Subject: Re: [sipcore] AD review: draft-ietf-sipcore-event-rate-control-04
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Sep 2010 07:17:31 -0000

Hi,

Please find in-line with [KK]:

From: ext Janet P Gunn [mailto:jgunn6@csc.com]
Sent: 2010. július 26. 09:43
To: Janet P Gunn
Cc: Kiss Krisztian (Nokia-CIC/MtView); sipcore@ietf.org; sipcore-bounces@ietf.org
Subject: Re: [sipcore] AD review: draft-ietf-sipcore-event-rate-control-04


Just want to address one technical issue that seems to have been missed..


Who/what sets the value of "period" for the adaptive/average mechanism?

[KK] As a continuation of my previous reply, the "period" is chosen by the notifier.

What is the range and granularity of the values for "period"?

[KK] I think that's an implementation decision.

Is it set separately for every subscription?

[KK]. It could be set separately per subscription (as it is also dependent on the "average-interval" and that can change per subscription) but it doesn't necessarily have to be...

Can the subscriber change it?

No, it's not visible to the subscriber.

Or does the notifier have a single value of "period" that it uses for all subscriptions, forever?

That's also an option, as long as "the value of the "period" parameter must be greater than the value of the "average-interval" parameter" is true.

Cheers,
Krisztian


Janet

This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.