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

Paul Kyzivat <pkyzivat@cisco.com> Fri, 26 September 2008 14:42 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 CCB1728C0F0; Fri, 26 Sep 2008 07:42:35 -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 012C13A6B33 for <sipping@core3.amsl.com>; Fri, 26 Sep 2008 07:42:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.604
X-Spam-Level:
X-Spam-Status: No, score=-5.604 tagged_above=-999 required=5 tests=[AWL=-0.845, 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 MkVbKhWkcv8Y for <sipping@core3.amsl.com>; Fri, 26 Sep 2008 07:42:32 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id C7B013A6A50 for <sipping@ietf.org>; Fri, 26 Sep 2008 07:42:32 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,314,1220227200"; d="scan'208";a="83274786"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 26 Sep 2008 14:42:24 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m8QEgOjK003283; Fri, 26 Sep 2008 07:42:24 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m8QEgOgw022583; Fri, 26 Sep 2008 14:42:24 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Sep 2008 07:41:52 -0700
Received: from [10.21.64.171] ([10.21.64.171]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Sep 2008 07:41:51 -0700
Message-ID: <48DCF4AF.6010301@cisco.com>
Date: Fri, 26 Sep 2008 10:41:51 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: "Schmidt, Christian 1. (NSN - DE/Munich)" <christian.1.schmidt@nsn.com>
References: <F66D7286825402429571678A16C2F5EE04DAB0EF@zrc2hxm1.corp.nortel.com><48BEB1F8.5050709@ericsson.com> <48D37017.6030300@ericsson.com> <B846208195B11F4EA16E16BE9DC8A9CCF98974@DEMUEXC013.nsn-intra.net> <48D3A98D.9020806@cisco.com> <B846208195B11F4EA16E16BE9DC8A9CC0108AA6F@DEMUEXC013.nsn-intra.net>
In-Reply-To: <B846208195B11F4EA16E16BE9DC8A9CC0108AA6F@DEMUEXC013.nsn-intra.net>
X-OriginalArrivalTime: 26 Sep 2008 14:41:51.0734 (UTC) FILETIME=[036F6160:01C91FE6]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3363; t=1222440144; x=1223304144; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[Sipping]=09FW=3AWGLC=09Review=3A=09dra ft-ietf-sipping-presence-scaling-requirements-01.txt |Sender:=20; bh=7b3L8KLvu/J53cLcgvuJDbRdkBd9zk+ZUv6CSglYe9I=; b=RvWtwtKZ34bsGcaqQp1d9qIblKnIiIraHQbXnDxBMggWRsz79d8abRLcoD 4XNY2DuQX5aPnt0auKncPS/jqxWQu/bcB5ItOfc6Ln2Swtb4ORpIRr1NdIF+ H0r37YSbZ3;
Authentication-Results: sj-dkim-3; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

Christian,

Certainly DoS attacks need to be addressed in practice.
But I question whether they need to be included in the scaling analysis.
Perhaps it would be sufficient to state that the scaling analysis 
assumes the absence of DoS attacks.

Or, I guess, one could assume that in the kind of large scale 
deployments being considered there will *always* be some sort of DoS 
attack, and try to incorporate the cost of coping with that into the 
analysis. But I can't imagine how the statistical characteristics of 
such an attack could be incorporated.

	Paul

Schmidt, Christian 1. (NSN - DE/Munich) wrote:
> 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