[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Sipping] New Version draft-niemi-sipping-event-throttle-07
Hi there,
I have just submitted a new version of the throttle draft.
This version include the mailing list discussion we have had during the
last two months.
It specify now other the throttle mechanism other two mechanism: forge
and average.
These mechanisms are defined as an extension to the SIP events framework
defining the following three "Event" header field parameters that allow
a subscriber
to set a Minimum, a Maximum and an Average rate of event notifications
generated by the notifier:
Throttle: specifies a minimum notification tiFrom sipping-bounces at ietf.org Wed Oct 22 06:58:28 2008
Return-Path: <sipping-bounces at ietf.org>
X-Original-To: sipping-web-archive at optimus.ietf.org
Delivered-To: ietfarch-sipping-web-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id DF05F28C13A;
Wed, 22 Oct 2008 06:58:28 -0700 (PDT)
X-Original-To: sipping at core3.amsl.com
Delivered-To: sipping at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 92BF528C15B
for <sipping at core3.amsl.com>; Wed, 22 Oct 2008 06:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.306
X-Spam-Level:
X-Spam-Status: No, score=-6.306 tagged_above=-999 required=5
tests=[AWL=-0.057, BAYES_00=-2.599, HELO_EQ_SE=0.35,
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 hxC14EbPHq0l for <sipping at core3.amsl.com>;
Wed, 22 Oct 2008 06:58:26 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
by core3.amsl.com (Postfix) with ESMTP id 7EC1E28C13A
for <sipping at ietf.org>; Wed, 22 Oct 2008 06:58:26 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
8742422046
for <sipping at ietf.org>; Wed, 22 Oct 2008 15:57:30 +0200 (CEST)
X-AuditID: c1b4fb3e-aa77dbb00000537b-07-48ff314a35ad
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
6FBB520658
for <sipping at ietf.org>; Wed, 22 Oct 2008 15:57:30 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);
Wed, 22 Oct 2008 15:57:29 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);
Wed, 22 Oct 2008 15:57:29 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
[131.160.33.3])
by mail.lmf.ericsson.se (Postfix) with ESMTP id 025902507
for <sipping at ietf.org>; Wed, 22 Oct 2008 16:57:30 +0300 (EEST)
Received: from n75.nomadiclab.com (localhost [IPv6:::1])
by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id E0D134DC85
for <sipping at ietf.org>; Wed, 22 Oct 2008 16:57:29 +0300 (EEST)
Message-ID: <48FF3149.9010004 at ericsson.com>
Date: Wed, 22 Oct 2008 16:57:29 +0300
From: Salvatore Loreto <salvatore.loreto at ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080914)
MIME-Version: 1.0
To: sipping <sipping at ietf.org>
X-OriginalArrivalTime: 22 Oct 2008 13:57:29.0708 (UTC)
FILETIME=[1F7BF2C0:01C9344E]
X-Brightmail-Tracker: AAAAAA==
Subject: [Sipping] New Version draft-niemi-sipping-event-throttle-07
X-BeenThere: sipping at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>,
<mailto:sipping-request at ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sipping>
List-Post: <mailto:sipping at ietf.org>
List-Help: <mailto:sipping-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>,
<mailto:sipping-request at ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sipping-bounces at ietf.org
Errors-To: sipping-bounces at ietf.org
Hi there,
I have just submitted a new version of the throttle draft.
This version include the mailing list discussion we have had during the
last two months.
It specify now other the throttle mechanism other two mechanism: forge
and average.
These mechanisms are defined as an extension to the SIP events framework
defining the following three "Event" header field parameters that allow
a subscriber
to set a Minimum, a Maximum and an Average rate of event notifications
generated by the notifier:
Throttle: specifies a minimum notificme period between two
notifications, in seconds.
Force: specifies a maximum notification time period between two
notifications, in seconds. Whenever the time since the most
recent notification exceeds the value in the "force" parameter,
then the current state would be sent in its entirety (just like
after a subscription refresh).
Average: specifies an average cadence at which notifications are
desired, in seconds. It works similar to the "force" parameter,
except that it will reduce the frequency at which notifications
are sent if several have already been sent recently.
best regards
Sal
-------- Original Message --------
Subject: New Version Notification for
draft-niemi-sipping-event-throttle-07
Date: Wed, 22 Oct 2008 06:48:04 -0700 (PDT)
From: IETF I-D Submission Tool <idsubmission at ietf.org>
To: Salvatore.Loreto at ericsson.com
CC:
aki.niemi at nokia.com,krisztian.kiss at nokia.com,salvatore.loreto at ericsson.com
A new version of I-D, draft-niemi-sipping-event-throttle-07.txt has been successfuly submitted by Salvatore Loreto and posted to the IETF repository.
Filename: draft-niemi-sipping-event-throttle
Revision: 07
Title: Session Initiation Protocol (SIP) Event Notification Extension for Notification Throttling
Creation_date: 2008-10-22
WG ID: Independent Submission
Number_of_pages: 22
Abstract:
This memo specifies the throttle, forge and average mechanisms for
adjusting the rate of Session Initiation Protocol (SIP) event
notifications. These mechanisms can be applied in subscriptions to
all SIP event packages, but in particular the throttle mechanism is
especially designed to be used in combination with a subscription to
a Resource List Server (RLS).
The IETF Secretariat.
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP
ation time period between two
notifications, in seconds.
Force: specifies a maximum notification time period between two
notifications, in seconds. Whenever the time since the most
recent notification exceeds the value in the "force" parameter,
then the current state would be sent in its entirety (just like
after a subscription refresh).
Average: specifies an average cadence at which notifications are
desired, in seconds. It works similar to the "force" parameter,
except that it will reduce the frequency at which notifications
are sent if several have already been sent recently.
best regards
Sal
-------- Original Message --------
Subject: New Version Notification for
draft-niemi-sipping-event-throttle-07
Date: Wed, 22 Oct 2008 06:48:04 -0700 (PDT)
From: IETF I-D Submission Tool <idsubmission at ietf.org>
To: Salvatore.Loreto at ericsson.com
CC:
aki.niemi at nokia.com,krisztian.kiss at nokia.com,salvatore.loreto at ericsson.com
A new version of I-D, draft-niemi-sipping-event-throttle-07.txt has been successfuly submitted by Salvatore Loreto and posted to the IETF repository.
Filename: draft-niemi-sipping-event-throttle
Revision: 07
Title: Session Initiation Protocol (SIP) Event Notification Extension for Notification Throttling
Creation_date: 2008-10-22
WG ID: Independent Submission
Number_of_pages: 22
Abstract:
This memo specifies the throttle, forge and average mechanisms for
adjusting the rate of Session Initiation Protocol (SIP) event
notifications. These mechanisms can be applied in subscriptions to
all SIP event packages, but in particular the throttle mechanism is
especially designed to be used in combination with a subscription to
a Resource List Server (RLS).
The IETF Secretariat.
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP