[sip-overload] Bar BOF request for SIP Load balancing & (media) overload handling

"Parthasarathi R (partr)" <partr@cisco.com> Thu, 17 March 2011 00:43 UTC

Return-Path: <partr@cisco.com>
X-Original-To: sip-overload@core3.amsl.com
Delivered-To: sip-overload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DFE563A6906; Wed, 16 Mar 2011 17:43:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.292
X-Spam-Level:
X-Spam-Status: No, score=-9.292 tagged_above=-999 required=5 tests=[AWL=-0.090, 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 qvkuqOSQsEW0; Wed, 16 Mar 2011 17:43:13 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 6BF2D3A68DE; Wed, 16 Mar 2011 17:43:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=3432; q=dns/txt; s=iport; t=1300322681; x=1301532281; h=mime-version:subject:date:message-id:from:to:cc; bh=q7Z1Mw4k7VXsAbRQJK5n80hCRWnpjLoGvTJDBJ3UT40=; b=Qj1MV8TR7M0V0LQwRDaBLcNxjlSbHtQ4HM5i+vrKeNAZJxJhb93P6ZRu Dq315jTYatZwvu1WmLMr0Qhn7FBBb8oJ9BtGSulKjmnQvuHg5Q7mTF49j Bi/GLiVu6GhNcinzAhp+gSwBYViCHi/xl+7q0YUpPGxO0veLSweMs1o22 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq8EAGr2gE2Q/khMgWdsb2JhbACkfFMUAQEWJiWmHpxegnuCaASFLYsE
X-IronPort-AV: E=Sophos; i="4.63,196,1299456000"; d="scan'208,217"; a="79530412"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 17 Mar 2011 00:44:39 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2H0icJt008871; Thu, 17 Mar 2011 00:44:39 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); Thu, 17 Mar 2011 06:14:38 +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_01CBE43C.7E7458A2"
Date: Thu, 17 Mar 2011 06:14:38 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390293A6AF@XMB-BGL-411.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Bar BOF request for SIP Load balancing & (media) overload handling
Thread-Index: AcvkNQDWIeXRlo1yRRq3Yg+LUWi3ZA==
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: dworley@avaya.com, "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "Mike Hammer (hmmr)" <hmmr@cisco.com>, HKaplan@acmepacket.com, keith.drage@alcatel-lucent.com, john.elwell@siemens-enterprise.com, mary.ietf.barnes@gmail.com, "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>, paulej@packetizer.com, rjsparks@nostrum.com, spromano@unina.it, Thierry.Bessis@alcatel-lucent.com, vkg@bell-labs.com, vpascual@acmepacket.com
X-OriginalArrivalTime: 17 Mar 2011 00:44:38.0848 (UTC) FILETIME=[7EE7C400:01CBE43C]
X-Mailman-Approved-At: Thu, 17 Mar 2011 06:19:12 -0700
Cc: dispatch@ietf.org, sip-overload@ietf.org
Subject: [sip-overload] Bar BOF request for SIP Load balancing & (media) overload handling
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-overload>, <mailto:sip-overload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-overload>
List-Post: <mailto:sip-overload@ietf.org>
List-Help: <mailto:sip-overload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-overload>, <mailto:sip-overload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2011 00:43:15 -0000

Hi all,
 
There is lot of discussion about SIP load balancing and overload handling in Dispatch alias. I wish to have discussion about SIP Load balancing & (media) overload handling at IETF-80 Prague. I guess that Bar BOF is the idle way to start the discussion about this topic to common understanding and identify the way to move forward. Please suggest me in case any other mechanism exists in IETF.
 
I have included the folks who has shown the interest in this topic as part of SIP Load balancing & overload handling, dispatch WG chairs, CCed to Dispatch and SoC WG alias. AFAIK, the couple of drafts are related to this problem:
 
draft-bessis-dispatch-adaptive-load-balancing-00
draft-partha-dispatch-sip-media-overload-control-00.txt
draft-jones-sip-overload-sce-00
draft-partha-dispatch-resource-availability-00 
draft-sparks-sipping-load-00
 
Please let me about others interest and opinion to have Bar BOF for SIP Load balancing & overload handling during IETF-80.
 
Thanks
Partha