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

"Parthasarathi R (partr)" <partr@cisco.com> Wed, 01 September 2010 03:34 UTC

Return-Path: <partr@cisco.com>
X-Original-To: sip-ops@core3.amsl.com
Delivered-To: sip-ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 742CD3A68E2; Tue, 31 Aug 2010 20:34:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.189
X-Spam-Level:
X-Spam-Status: No, score=-9.189 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, 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 AEBxODF1bRt9; Tue, 31 Aug 2010 20:34:55 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 531A03A68D0; Tue, 31 Aug 2010 20:34:55 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgGAIdmfUxAaMHG/2dsb2JhbACPYINhhRoBhzdKcaMpnBiFNwSEO4hR
X-IronPort-AV: E=Sophos; i="4.56,301,1280707200"; d="scan'208,217"; a="581580691"
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-6.cisco.com with ESMTP; 01 Sep 2010 03:35:24 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o813ZN3r000827; Wed, 1 Sep 2010 03:35:23 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 1 Sep 2010 09:05:22 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB4986.B51BFFC5"
Date: Wed, 1 Sep 2010 09:05:22 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A4BA@XMB-BGL-411.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dispatch] SIP Resource availability Event package
Thread-Index: ActJVHS+ebQI6RTDRGi7fyArDuPY7QAMOJfF
References: <20100830142058.6A0EA3A69B8@core3.amsl.com> <A11921905DA1564D9BCF64A6430A62390293A4B3@XMB-BGL-411.cisco.com> <5D9746F9-9D36-4482-8B61-94AED338EDE2@gmail.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Michael Miller" <mlm.michael.miller@gmail.com>
X-OriginalArrivalTime: 01 Sep 2010 03:35:22.0830 (UTC) FILETIME=[B56A9EE0:01CB4986]
Cc: sip-ops@ietf.org, dispatch@ietf.org, sip-overload@ietf.org, mediactrl@ietf.org
Subject: Re: [sip-ops] [dispatch] SIP Resource availability Event package
X-BeenThere: sip-ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Operations <sip-ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-ops>, <mailto:sip-ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-ops>
List-Post: <mailto:sip-ops@ietf.org>
List-Help: <mailto:sip-ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-ops>, <mailto:sip-ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Sep 2010 03:34:58 -0000

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>;; sip-ops@ietf.org; sip-overload@ietf.org; mediactrl@ietf.org
Subject: 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