Re: [splices] SPLICES IETF-80 meeting minutes and start of ML discussion

Paul Kyzivat <pkyzivat@cisco.com> Wed, 27 April 2011 22:43 UTC

Return-Path: <pkyzivat@cisco.com>
X-Original-To: splices@ietfa.amsl.com
Delivered-To: splices@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 958E0E07AE for <splices@ietfa.amsl.com>; Wed, 27 Apr 2011 15:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.176
X-Spam-Level:
X-Spam-Status: No, score=-110.176 tagged_above=-999 required=5 tests=[AWL=-0.177, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id psN99pYQVotZ for <splices@ietfa.amsl.com>; Wed, 27 Apr 2011 15:43:35 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by ietfa.amsl.com (Postfix) with ESMTP id C207BE07A9 for <splices@ietf.org>; Wed, 27 Apr 2011 15:43:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=2682; q=dns/txt; s=iport; t=1303944215; x=1305153815; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=9ym827+Y5wrAKa4m0oSP0zj+GNsI0/djyZ0pqevaFvE=; b=PX8RwGOv2Mae1wqJ547HXyqSTweC8mN18/OdmiNcWlYl8/PUdjaKuQer mXprjoPabb9alIWzCajwE4791g+UKuCwR3DbumAlx/g/lrds4eVTiv7YY anR5j1k9VBDFvZlu44mE0vcND2PKqt8XgY0GE4SiGXfXEsHZD2+GhtYXE E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArkHAOSauE2tJXG9/2dsb2JhbACYUY0ud6d8nHiFdgSOUYQSijY
X-IronPort-AV: E=Sophos;i="4.64,276,1301875200"; d="scan'208";a="437726962"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by sj-iport-1.cisco.com with ESMTP; 27 Apr 2011 22:43:35 +0000
Received: from [161.44.174.124] (dhcp-161-44-174-124.cisco.com [161.44.174.124]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id p3RMhYQs011357 for <splices@ietf.org>; Wed, 27 Apr 2011 22:43:35 GMT
Message-ID: <4DB89C16.6080001@cisco.com>
Date: Wed, 27 Apr 2011 18:43:34 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: splices@ietf.org
References: <4DA762EF.60007@unina.it> <4DA88832.2090202@ericsson.com> <4DA8E177.7070908@cisco.com> <4DB86443.8040008@ericsson.com>
In-Reply-To: <4DB86443.8040008@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [splices] SPLICES IETF-80 meeting minutes and start of ML discussion
X-BeenThere: splices@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Loosely-coupled SIP Devices \(splices\) working group discussion list" <splices.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/splices>, <mailto:splices-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/splices>
List-Post: <mailto:splices@ietf.org>
List-Help: <mailto:splices-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/splices>, <mailto:splices-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2011 22:43:36 -0000

inline

On 4/27/2011 2:45 PM, Salvatore Loreto wrote:
> On 4/16/11 2:23 AM, Paul Kyzivat wrote:
>> Sal,
>>
>> On 4/15/2011 2:02 PM, Salvatore Loreto wrote:
>> ...
>>> I am interested in scenarios where both ends may be impacted by the
>>> implementation
>>> of the new mechanism to be developed;
>>> of course in the case an impact is required, I do think the design
>>> should consider a fall back for the case the other
>>> peer does not implement it (e.g. a legacy UA)
>> ...
>>> work of a loosely-coupled coordination scenario,
>>> where no single device needs to remain in the session for its entire
>>> duration
>>> and no single device needs to act as master...
>>> is still something that I personally find interesting to be investigated
>> I still don't *get* it.
>>
>> Can you lay out a scenario/use case/example of what you have in mind?
>> - describe to moving parts
>> - what interactions they have to make the case work
>> - what capabilities each has/expects of others
>> - if parts of the coordination depend on special behavior of
>> *people* rather than automata, explain that too.
>>
>> Nothing complicated - just very high level.
>
> what I have in mind is a scenario where
> a user can make or answer a Call Using Two or more separate devices;
> the devices can happen to be in the same network or in different area
> networks,
> however I don't want any of the devices to be a single point of failure
> for the call:
> that means that any device, involved in the side of the call
> (the one is using different devices to handle the call), can go out of
> coverage, can restart etc.etc.
> without having any impact on the call as such.

Well, maybe a little more detail that that :-)

The above seems to be of the "and then magic happens" school.

I presume you have in mind that the *other* party manages two separate 
dialogs and coordinates them.

But who has the intelligence to establish the multi-device call?
- know that more than two devices should be used
- know how to reach the additional device
- know enough about the existing call to splice it in

	Thanks,
	Paul

P.S. I think a variant of the 3pcc approach we are discussing in another 
thread could potentially be used in your scenario too, if the main point 
is to manage where the failure point is.

For instance, if Alice and Bob are talking, and Alice wants to add in a 
local display device, it could send a REFER to the display device, 
asking it to send and INVITE/Join to Bob. This is not so straightforward 
- there are many details to work out. But I find it no less plausible 
than any other yet-to-be-devised scheme.