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

Paul Kyzivat <pkyzivat@cisco.com> Sat, 16 April 2011 00:23 UTC

Return-Path: <pkyzivat@cisco.com>
X-Original-To: splices@ietfc.amsl.com
Delivered-To: splices@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 702A9E0680 for <splices@ietfc.amsl.com>; Fri, 15 Apr 2011 17:23:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.436
X-Spam-Level:
X-Spam-Status: No, score=-110.436 tagged_above=-999 required=5 tests=[AWL=0.163, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vinN9MbkAORl for <splices@ietfc.amsl.com>; Fri, 15 Apr 2011 17:23:20 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfc.amsl.com (Postfix) with ESMTP id B7C22E066C for <splices@ietf.org>; Fri, 15 Apr 2011 17:23:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=1040; q=dns/txt; s=iport; t=1302913400; x=1304123000; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=Aj8DWpQ0Q04+DceuTNCbyI9SZiIoUtmbMs1rODLsJYQ=; b=Fl+oafJ19jrgnefNerX7g33ukoiN1hO/9EAlvBC/WWxpTju9oWCJOv53 0loLG5s3EJ2r/egXlQgkb2Nbi4bMmh8uVdVE53E7d0I7LwHIH4cQH9yt0 zH4Hnj8u3kKvuNNyO3tA+fLeYo90PVL85OdTaHKtG5wCPg0ZOSnYqV7DG A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiIIAE7gqE2rRDoG/2dsb2JhbACYTY1Ad6dVnRWFbgSNeoN0
X-IronPort-AV: E=Sophos;i="4.64,222,1301875200"; d="scan'208";a="295660650"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-3.cisco.com with ESMTP; 16 Apr 2011 00:23:20 +0000
Received: from [161.44.174.125] (dhcp-161-44-174-125.cisco.com [161.44.174.125]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p3G0NJkV022407 for <splices@ietf.org>; Sat, 16 Apr 2011 00:23:20 GMT
Message-ID: <4DA8E177.7070908@cisco.com>
Date: Fri, 15 Apr 2011 20:23:19 -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>
In-Reply-To: <4DA88832.2090202@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: Sat, 16 Apr 2011 00:23:21 -0000

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.

	Thanks,
	Paul