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

"Sheshadri Shalya (svshesha)" <svshesha@cisco.com> Fri, 03 September 2010 09:21 UTC

Return-Path: <svshesha@cisco.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 0AD073A6819; Fri, 3 Sep 2010 02:21:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 UkfKklm6oF-v; Fri, 3 Sep 2010 02:21:23 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id BC76A3A684A; Fri, 3 Sep 2010 02:20:28 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAChagExAaMHG/2dsb2JhbAChDHGhEZwYhTsEhD+IWA
X-IronPort-AV: E=Sophos;i="4.56,312,1280707200"; d="scan'208";a="180940480"
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-4.cisco.com with ESMTP; 03 Sep 2010 09:20:54 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o839Ki7u008017; Fri, 3 Sep 2010 09:20:53 GMT
Received: from xmb-bgl-41d.cisco.com ([72.163.129.219]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 3 Sep 2010 14:50:52 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 3 Sep 2010 14:50:50 +0530
Message-ID: <28FC823DF72A5F49B694914951A0A83201FFB6F2@XMB-BGL-41D.cisco.com>
In-Reply-To: <fae18c96126f.126ffae18c96@huawei.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sip-overload] [dispatch] SIP Resource availabilityEvent package
Thread-Index: ActJ1hBGEEczs/j0T/6JX9pC5rduLwBbprkw
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> <fae18c96126f.126ffae18c96@huawei.com>
From: "Sheshadri Shalya (svshesha)" <svshesha@cisco.com>
To: "RahulSrivastava 71616" <rahuls@huawei.com>, "Parthasarathi R (partr)" <partr@cisco.com>
X-OriginalArrivalTime: 03 Sep 2010 09:20:52.0032 (UTC) FILETIME=[4DCF5400:01CB4B49]
X-Mailman-Approved-At: Fri, 03 Sep 2010 08:09:40 -0700
Cc: sip-overload@ietf.org, mediactrl@ietf.org
Subject: Re: [MEDIACTRL] [sip-overload] [dispatch] SIP Resource availabilityEvent 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: Fri, 03 Sep 2010 09:21:28 -0000

Rahul,
Thanks for your comments/suggestions. See responses inline:

Thanks,
Shesh

-----Original Message-----
From: sip-overload-bounces@ietf.org
[mailto:sip-overload-bounces@ietf.org] On Behalf Of RahulSrivastava
71616
Sent: Wednesday, September 01, 2010 6:32 PM
To: Parthasarathi R (partr)
Cc: sip-overload@ietf.org; mediactrl@ietf.org
Subject: Re: [sip-overload] [dispatch] SIP Resource availabilityEvent
package


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.
<svshesha>
In Section 6, we have indicated the use cases. We can add topology
diagram to make those use cases clear. The topologies could be 

  1. SIP server -------- Resource monitor 
  2. SIP server -----Proxy ------Resource monitor
   
</svshesha>

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. 
<svshesha>
This CPU is total system CPU. Based on the system architecture,
additional sub-types could be added as required.
</svshesha>

    
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.

<svshesha>
This draft does not mandate the resource monitor on different CPUs. This
again depends on the system architecture. 
</svshesha>

4.  "ICMP message received during dialog creation from the Notifying
      entity" ----> Is it ICMP error?

<svshesha>
It is for ICMP error. We will update the text to be more specific.
</svshesha>
    
     Hence is this mandatory for SIP Servers to know ping status of
SIPServers?

<svshesha>
I am not clear on the question here. In case if you are asking to know
whether SIP server is alive or not, then, it is covered as part of
SUB/NOT mechanism mentioned in the draft.
</svshesha>

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?
<svshesha>
The intention here is to have single to few resource monitoring entity
with multiple devices reporting to these resource monitors. In case, the
resource monitoring entity is monitoring multiple devices, even in that
case, as there is only one SUBSCRIPTION per device, it is not going to
be heavy.
</svshesha>

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
> 	
> 
> 
_______________________________________________
sip-overload mailing list
sip-overload@ietf.org
https://www.ietf.org/mailman/listinfo/sip-overload