[sip-ops] SIP Resource availability Event package

"Parthasarathi R (partr)" <partr@cisco.com> Mon, 30 August 2010 16:51 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 B7B4D3A6837; Mon, 30 Aug 2010 09:51:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.287
X-Spam-Level:
X-Spam-Status: No, score=-9.287 tagged_above=-999 required=5 tests=[AWL=-0.085, 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 iewwSj5unsHd; Mon, 30 Aug 2010 09:51:02 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 076363A6841; Mon, 30 Aug 2010 09:50:36 -0700 (PDT)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkgIAOV9e0yrR7H+/2dsb2JhbACTJoUYAYc3S3GhXJs7hTcEhDmIRA
X-IronPort-AV: E=Sophos; i="4.56,293,1280707200"; d="scan'208,217"; a="275346263"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-2.cisco.com with ESMTP; 30 Aug 2010 16:51:07 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o7UGp58k010748; Mon, 30 Aug 2010 16:51:06 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 30 Aug 2010 22:21:04 +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_01CB4863.88D4CDFE"
Date: Mon, 30 Aug 2010 22:21:04 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A4B3@XMB-BGL-411.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: SIP Resource availability Event package
Thread-Index: ActITqjnejR+Z0DIROGgppf59yc2GgAE/EYL
References: <20100830142058.6A0EA3A69B8@core3.amsl.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: <dispatch@ietf.org>
X-OriginalArrivalTime: 30 Aug 2010 16:51:04.0732 (UTC) FILETIME=[88FB3DC0:01CB4863]
Cc: sip-ops@ietf.org, "Sheshadri Shalya \(svshesha\)" <svshesha@cisco.com>, sip-overload@ietf.org, "Paul Kyzivat \(pkyzivat\)" <pkyzivat@cisco.com>, mediactrl@ietf.org
Subject: [sip-ops] 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: Mon, 30 Aug 2010 16:51:03 -0000

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.