Re: [MEDIACTRL] [sip-overload] [dispatch] SIP Resource availability Event package

RahulSrivastava 71616 <rahuls@huawei.com> Wed, 01 September 2010 13:02 UTC

Return-Path: <rahuls@huawei.com>
X-Original-To: mediactrl@core3.amsl.com
Delivered-To: mediactrl@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB6B23A6A4F; Wed, 1 Sep 2010 06:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.189
X-Spam-Level:
X-Spam-Status: No, score=-1.189 tagged_above=-999 required=5 tests=[AWL=-0.694, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 AkO3ZIaG2VTj; Wed, 1 Sep 2010 06:02:02 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 1A79A3A6A4E; Wed, 1 Sep 2010 06:02:01 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L82000XXK7WAA@szxga03-in.huawei.com>; Wed, 01 Sep 2010 21:02:20 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L8200BMCK7WLS@szxga03-in.huawei.com>; Wed, 01 Sep 2010 21:02:20 +0800 (CST)
Received: from [172.24.1.33] (Forwarded-For: 10.18.1.33, [172.24.1.119]) by szxmc04-in.huawei.com (mshttpd); Wed, 01 Sep 2010 18:02:20 +0500
Date: Wed, 01 Sep 2010 18:02:20 +0500
From: RahulSrivastava 71616 <rahuls@huawei.com>
In-reply-to: <A11921905DA1564D9BCF64A6430A62390293A4BA@XMB-BGL-411.cisco.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>
Message-id: <fae18c96126f.126ffae18c96@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug 8 2006)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
Priority: normal
References: <20100830142058.6A0EA3A69B8@core3.amsl.com> <A11921905DA1564D9BCF64A6430A62390293A4B3@XMB-BGL-411.cisco.com> <5D9746F9-9D36-4482-8B61-94AED338EDE2@gmail.com> <A11921905DA1564D9BCF64A6430A62390293A4BA@XMB-BGL-411.cisco.com>
Cc: sip-overload@ietf.org, mediactrl@ietf.org
Subject: Re: [MEDIACTRL] [sip-overload] [dispatch] SIP Resource availability Event package
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Control WG Discussion List <mediactrl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mediactrl>
List-Post: <mailto:mediactrl@ietf.org>
List-Help: <mailto:mediactrl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Sep 2010 13:02:03 -0000

I have some queries/suggestions on this draft:

1. Can we have a figure for network topology where this device is being targetted and which 
   entity performs which function? This will make document very clear.
   

2.  value="cpu|memory|ds0|dsp|storage|([a-z][a-z0-9])*"/>
    This CPU is total system CPU or process CPU? 
    If its per process CPU and SIPServer is multi process (with single entry point) does it add the values 
    or how much it should be indicated. 
    

3.  does this draft mandates resource monitor works on different CPUs? 
    If not some then does it need to substract its own CPU while applying overload alogorithm.

4.  "ICMP message received during dialog creation from the Notifying
      entity" ----> Is it ICMP error?
    
     Hence is this mandatory for SIP Servers to know ping status of SIPServers?

5.  If SIPServer has more than one incoming pxys and each of the pxys subscribe for this events. This SUBSCRIPTION
    becomes heavy. Do we need to see those areas or this is ok?


Regards,
Rahul
******************************************************************************************
 This email and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained here in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it!
 *****************************************************************************************

----- Original Message -----
From: "Parthasarathi R (partr)" <partr@cisco.com>
Date: Wednesday, September 1, 2010 9:06 am
Subject: Re: [sip-overload] [dispatch] SIP Resource availability Event	package
To: Michael Miller <mlm.michael.miller@gmail.com>
Cc: sip-ops@ietf.org, dispatch@ietf.org, sip-overload@ietf.org, mediactrl@ietf.org

> Michael,
> 
> Thanks for the comment. In the draft, Almost-out-of-resource 
> element for the particular resource has to be used whenever the 
> resource is reaching the critical condition (threshold) and it is 
> explained in sec 5.4.1. Almost-out-of-resource indication provides 
> the alert to the administrator about overuse of the specific 
> resource in a particular device. I'll add the text in the resource 
> availability indication mechanism for providing more clarity.
> 
> Thanks
> Partha
> 
> ________________________________
> 
> From: Michael Miller [mailto:mlm.michael.miller@gmail.com]
> Sent: Wed 9/1/2010 3:05 AM
> To: Parthasarathi R (partr)
> Cc: <dispatch@ietf.org>rg>; sip-ops@ietf.org; sip-overload@ietf.org; 
> mediactrl@ietf.orgSubject: Re: [dispatch] SIP Resource 
> availability Event package
> 
> 
> This draft looks pretty good. Should there be language that saids 
> management servers are alerted of critical conditions or is that 
> outside of this draft?
> 
> Michael L. Miller
> Sent from my Mobile Device
> 
> On Aug 30, 2010, at 12:51 PM, "Parthasarathi R (partr)" 
> <partr@cisco.com> wrote:
> 
> 
> 
> 	
> 	Resource availability information from SIP devices improves the 
> manageability of SIP devices by providing a framework for multiple 
> applications like Resource utilization monitoring, overload 
> handling in SIP based media servers. 
> 
> 	This draft was discussed in IETF-78 SoC WG and considered as 
> outside the scope of SOC as it focus on SIP overload based on non-
> critical resources like DS0, DSP. By looking at the mediactrl WG 
> charter and working documents, I doubt that this draft will falls 
> under current media-ctrl work. As this draft helps in SIP based 
> devices manageability, I looked for SIP manageability related WG 
> but Sip-ops mailing alias only exists and there is no WG 
> associated with it. So, I'm putting this document in dispatch WG 
> for further proceedings. 
> 
> 	Abstract is as follows:
> 
> 	"Collecting Resource availability information in Session 
> Initiation Protocol (SIP) devices in real time helps in better 
> manageability of resources in the SIP network. Resource 
> availability monitoring in SIP devices helps administrator to take 
> informed decision and corrective measures to tackle under or over 
> resource utilization in the network. Resource availability 
> information can also be used for SIP overload control in SIP based 
> Media servers by passing resource demand vector between devices. 
> This document defines resource availability XML document and the 
> mechanisms that can be used to exchange the document between SIP 
> entities."
> 	
> 
> 	The draft is available at http://datatracker.ietf.org/doc/draft-
> partha-dispatch-resource-availability/ 
> <http://datatracker.ietf.org/doc/draft-partha-dispatch-resource-
> availability/> . Could you please provide your valuable comments.
> 
> 	Thanks
> 
> 	Partha
> 
> 	
> 	
> 
> ________________________________
> 
> 	From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> 	Sent: Mon 8/30/2010 7:50 PM
> 	To: Parthasarathi R (partr)
> 	Cc: Sheshadri Shalya (svshesha)
> 	Subject: New Version Notification for draft-partha-dispatch-
> resource-availability-00 
> 	
> 	
> 
> 	
> 
> 
> 	A new version of I-D, draft-partha-dispatch-resource-availability-
> 00.txt has been successfully submitted by Parthasarathi R and 
> posted to the IETF repository.
> 	
> 	Filename:        draft-partha-dispatch-resource-availability
> 	Revision:        00
> 	Title:           Session Initiation Protocol (SIP) Resource 
> availability Event package
> 	Creation_date:   2010-08-30
> 	WG ID:           Independent Submission
> 	Number_of_pages: 17
> 	
> 	Abstract:
> 	Collecting Resource availability information in Session Initiation
> 	Protocol (SIP) devices in real time helps in better managebility of
> 	resources in the SIP network.  Resource availability monitoring in
> 	SIP devices helps administrator to take informed decision and
> 	corrective measures to tackle under or over resource utilization in
> 	the network.  Resource availability information can also be used for
> 	SIP overload control in SIP based Media servers by passing resource
> 	demand vector between devices.  This document defines resource
> 	availability XML document and the mechanisms that can be used to
> 	exchange the document between SIP entities.
>                                                                   
>                      
> 	
> 	
> 	The IETF Secretariat.
> 	
> 	
> 	
> 
> 	_______________________________________________
> 	dispatch mailing list
> 	dispatch@ietf.org
> 	https://www.ietf.org/mailman/listinfo/dispatch
> 	
> 
>