Re: [dispatch] SIP Action Referral
Salvatore Loreto <salvatore.loreto@ericsson.com> Wed, 19 January 2011 18:54 UTC
Return-Path: <salvatore.loreto@ericsson.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C8BDE3A7198 for <dispatch@core3.amsl.com>; Wed, 19 Jan 2011 10:54:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.544
X-Spam-Level:
X-Spam-Status: No, score=-106.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 2UXVNAmGKy3x for <dispatch@core3.amsl.com>; Wed, 19 Jan 2011 10:54:48 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id D5AD73A7193 for <dispatch@ietf.org>; Wed, 19 Jan 2011 10:54:47 -0800 (PST)
X-AuditID: c1b4fb3d-b7b89ae0000036a3-76-4d3734171237
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id E9.66.13987.714373D4; Wed, 19 Jan 2011 19:57:27 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.2.234.1; Wed, 19 Jan 2011 19:57:27 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 38B4D25A0 for <dispatch@ietf.org>; Wed, 19 Jan 2011 20:57:27 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id EBB5F5068B for <dispatch@ietf.org>; Wed, 19 Jan 2011 20:57:26 +0200 (EET)
Received: from Salvatore-Loretos-MacBook-Pro.local (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 74DBE50583 for <dispatch@ietf.org>; Wed, 19 Jan 2011 20:57:26 +0200 (EET)
Message-ID: <4D373415.1000402@ericsson.com>
Date: Wed, 19 Jan 2011 19:57:25 +0100
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: dispatch@ietf.org
References: <6369CB70BFD88942B9705AC1E639A33822082B69C6@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <6369CB70BFD88942B9705AC1E639A33822082B69C6@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [dispatch] SIP Action Referral
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jan 2011 18:54:51 -0000
Hi, I tend to agree this draft is very much related to the SPLICE wg. Indeed during the discussion of draft: http://tools.ietf.org/id/draft-loreto-splices-disaggregated-media-00.txt people have foresee REFER as a possible method to solve the use cases showed in the draft. This draft really give a first answer on how REFER can be extended to solve the disaggregated media scenario. Moreover one advantage of the Loosely Coupled UAs scenario you have in Section 3.2 and in the example in Section 3.3 is that in your case the side that want to use a Loosely Coupled UAs scenario does not put any extra requirements on the other side, where in the Disaggregated Framework the other side have to correlate the different dialogs coming from the different Loosely Coupled UAs! That also remove the need to correlate different session in order to let them the different sessions appear as a single conversation to the other side. Finally, I agree with Paul that there is the need to design a sort of distributed call control and decide how the different Loosely Coupled UAs exchange call related information during an on going call, and what are the information that need to be exchanged. I will be happy to help you in move forward this work. cheers /Sal -- Salvatore Loreto www.sloreto.com On 1/14/11 7:41 PM, Shekh-Yusef, Rifaat (Rifaat) wrote: > Hi, > > We have submitted the following SIP Action Referral draft to the IETF and we would like to discuss it during the upcoming DISPATCH meeting in IETF80. > https://datatracker.ietf.org/doc/draft-yusef-dispatch-action-ref/ > A charter proposal will follow by the end of next week. > > We would appreciate any comments or feedback on this draft. > > Thanks, > Rifaat > > > -----Original Message----- > From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] > Sent: Friday, January 14, 2011 8:15 AM > To: Shekh-Yusef, Rifaat (Rifaat) > Cc: fluffy@cisco.com; alan.b.johnston@gmail.com; francois.audet@skype.net > Subject: New Version Notification for draft-yusef-dispatch-action-ref-00 > > > A new version of I-D, draft-yusef-dispatch-action-ref-00.txt has been successfully submitted by Rifaat Shekh-Yusef and posted to the IETF repository. > > Filename: draft-yusef-dispatch-action-ref > Revision: 00 > Title: Action Referral in the Session Initiation Protocol (SIP) > Creation_date: 2011-01-14 > WG ID: Independent Submission > Number_of_pages: 24 > > Abstract: > This specification defines action referral that allows an application > to make a high level request to a User Agent to perform an action, > and let the the User Agent execute the action as it sees fit. Action > referral uses the SIP REFER method with a Refer-To header field > containing a URN, which indicates the requested action. > > This specification also defines the option tag 'action-ref' to allow > the UA to indicate its support for action referral. > > > > The IETF Secretariat. > > > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch >
- [dispatch] SIP Action Referral Shekh-Yusef, Rifaat (Rifaat)
- Re: [dispatch] SIP Action Referral Paul Kyzivat
- Re: [dispatch] SIP Action Referral Shekh-Yusef, Rifaat (Rifaat)
- Re: [dispatch] SIP Action Referral Christer Holmberg
- Re: [dispatch] SIP Action Referral Shekh-Yusef, Rifaat (Rifaat)
- Re: [dispatch] SIP Action Referral Gonzalo Camarillo
- Re: [dispatch] SIP Action Referral Christer Holmberg
- Re: [dispatch] SIP Action Referral Paul Kyzivat
- Re: [dispatch] SIP Action Referral Shekh-Yusef, Rifaat (Rifaat)
- Re: [dispatch] SIP Action Referral Paul Kyzivat
- Re: [dispatch] SIP Action Referral Salvatore Loreto
- Re: [dispatch] SIP Action Referral Salvatore Loreto
- Re: [dispatch] SIP Action Referral Christer Holmberg
- Re: [dispatch] SIP Action Referral Alan Johnston
- Re: [dispatch] SIP Action Referral Gonzalo Camarillo
- Re: [dispatch] SIP Action Referral Paul Kyzivat
- Re: [dispatch] SIP Action Referral Gonzalo Camarillo
- Re: [dispatch] SIP Action Referral Paul Kyzivat
- Re: [dispatch] SIP Action Referral gao.yang2
- Re: [dispatch] SIP Action Referral Shekh-Yusef, Rifaat (Rifaat)
- Re: [dispatch] SIP Action Referral Shekh-Yusef, Rifaat (Rifaat)
- Re: [dispatch] SIP Action Referral Christer Holmberg
- Re: [dispatch] SIP Action Referral Shekh-Yusef, Rifaat (Rifaat)
- Re: [dispatch] SIP Action Referral Christer Holmberg
- Re: [dispatch] SIP Action Referral Shekh-Yusef, Rifaat (Rifaat)
- Re: [dispatch] SIP Action Referral Paul Kyzivat
- Re: [dispatch] SIP Action Referral Shekh-Yusef, Rifaat (Rifaat)
- Re: [dispatch] SIP Action Referral Paul Kyzivat
- Re: [dispatch] SIP Action Referral Mike Hammer (hmmr)
- Re: [dispatch] SIP Action Referral Shekh-Yusef, Rifaat (Rifaat)
- Re: [dispatch] SIP Action Referral Mike Hammer (hmmr)
- Re: [dispatch] SIP Action Referral Paul Kyzivat
- Re: [dispatch] SIP Action Referral Mary Barnes