Re: [Sipping] FW:WGLC Review: draft-ietf-sipping-presence-scaling-requirements-01.txt

"Schmidt, Christian 1. (NSN - DE/Munich)" <christian.1.schmidt@nsn.com> Fri, 26 September 2008 12:58 UTC

Return-Path: <sipping-bounces@ietf.org>
X-Original-To: sipping-archive@optimus.ietf.org
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 43F843A6A8A; Fri, 26 Sep 2008 05:58:27 -0700 (PDT)
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 705953A6A8A for <sipping@core3.amsl.com>; Fri, 26 Sep 2008 05:58:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.759
X-Spam-Level:
X-Spam-Status: No, score=-4.759 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_24=0.6, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24]
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 XxeHS09jN8Jr for <sipping@core3.amsl.com>; Fri, 26 Sep 2008 05:58:25 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [217.115.75.233]) by core3.amsl.com (Postfix) with ESMTP id 426063A6A58 for <sipping@ietf.org>; Fri, 26 Sep 2008 05:58:25 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id m8QCw3Au003692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 26 Sep 2008 14:58:03 +0200
Received: from demuexc022.nsn-intra.net (webmail.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id m8QCw3ZF011612; Fri, 26 Sep 2008 14:58:03 +0200
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 26 Sep 2008 14:58:03 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 26 Sep 2008 14:58:02 +0200
Message-ID: <B846208195B11F4EA16E16BE9DC8A9CC0108AA6F@DEMUEXC013.nsn-intra.net>
In-Reply-To: <48D3A98D.9020806@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sipping] FW:WGLC Review: draft-ietf-sipping-presence-scaling-requirements-01.txt
Thread-Index: AckaW/Ns0dO7qVGBT/yjbSvesYsoygFd6sKw
References: <F66D7286825402429571678A16C2F5EE04DAB0EF@zrc2hxm1.corp.nortel.com><48BEB1F8.5050709@ericsson.com> <48D37017.6030300@ericsson.com> <B846208195B11F4EA16E16BE9DC8A9CCF98974@DEMUEXC013.nsn-intra.net> <48D3A98D.9020806@cisco.com>
From: "Schmidt, Christian 1. (NSN - DE/Munich)" <christian.1.schmidt@nsn.com>
To: ext Paul Kyzivat <pkyzivat@cisco.com>
X-OriginalArrivalTime: 26 Sep 2008 12:58:03.0894 (UTC) FILETIME=[835A6960:01C91FD7]
X-purgate: clean
X-purgate: This mail is considered clean
X-purgate-type: clean
X-purgate-Ad: Checked for Spam by eleven - eXpurgate www.eXpurgate.net
X-purgate-ID: 151667::080926145803-21F35BB0-8CF42406/0-0/0-15
X-purgate-size: 2613/0
Cc: draft-ietf-sipping-presence-scaling-requirements@tools.ietf.org, sipping@ietf.org, ext Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Mary Barnes <mary.barnes@nortel.com>
Subject: Re: [Sipping] FW:WGLC Review: draft-ietf-sipping-presence-scaling-requirements-01.txt
X-BeenThere: sipping@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@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

Hi Paul,

Sorry for the late reply, but the harddisk of my notebook has refused
further service this week.

I like your new version of REQ-007, it covers the point I raises.

A related question: What about Denial of Service attacks? Should we
provide requirements, to restrict the risk of DoS attacks? For example
to restrict the number of watchers per presentity or to restrict the
number of changes in presence status per time-unit?

Regards
Christian 



 

-----Original Message-----
From: ext Paul Kyzivat [mailto:pkyzivat@cisco.com] 
Sent: Freitag, 19. September 2008 15:31
To: Schmidt, Christian 1. (NSN - DE/Munich)
Cc: ext Gonzalo Camarillo; sipping@ietf.org;
draft-ietf-sipping-presence-scaling-requirements@tools.ietf.org; Mary
Barnes
Subject: Re: [Sipping] FW:WGLC Review:
draft-ietf-sipping-presence-scaling-requirements-01.txt



Schmidt, Christian 1. (NSN - DE/Munich) wrote:
> Hi,
> 
> A short comment / queston, concerning a scalility requirement:
> 
>    o  REQ-007: Presence systems (intra or inter-domain) SHOULD scale
in
>       linear proportion to the number of watchers and presentities in
>       the system.
> 
> This requirement takes not into account the relationsship between
presentities
> And watchers. Meaning for example in adding few presentities with a
huge amount of watchers,
> This linear proportion can not be achieved. Therefore I think, this
has to
> Be taken into account in this requirement.

>    o  REQ-007: Presence systems (intra or inter-domain) SHOULD scale
in
>       linear proportion to the number of watchers and presentities in
>       the system. Precondition ist that the number of watchers of a
presentity and the
>       number of precentities a watcher can monitor is restricted.

How about:

    o  REQ-007: Presence systems (intra or inter-domain) SHOULD scale in
       linear proportion to the number of watchers and presentities in
       the system, so long as the average number of watchers per
       presentity has a fixed bound.

Namely, its not necessary to bound any particular user's behavior so 
long as the average is fixed rather than proportional to the number of 
presentities.

Over the short term that is likely to be true by accident. Over longer 
periods of time, as the system becomes ubiquitous, the average number is

likely to rise but maybe not in proportion to the number of users in the

system.

This behavior could probably be constrained if there was a cost to the 
end user associated with having a buddy.

	Thanks,
	Paul
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP