[splices] Fwd: Progressing the INVOKE-related work

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Mon, 25 July 2011 21:41 UTC

Return-Path: <gonzalo.camarillo@ericsson.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 8614511E80BA for <splices@ietfa.amsl.com>; Mon, 25 Jul 2011 14:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.606
X-Spam-Level:
X-Spam-Status: No, score=-106.606 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 tmLtFpNGJi19 for <splices@ietfa.amsl.com>; Mon, 25 Jul 2011 14:41:20 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id C576921F8BD3 for <splices@ietf.org>; Mon, 25 Jul 2011 14:41:19 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-9f-4e2de2fe4076
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id DB.57.20773.EF2ED2E4; Mon, 25 Jul 2011 23:41:19 +0200 (CEST)
Received: from [131.160.126.141] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.137.0; Mon, 25 Jul 2011 23:41:18 +0200
Message-ID: <4E2DE2FC.1050900@ericsson.com>
Date: Mon, 25 Jul 2011 17:41:16 -0400
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: splices@ietf.org
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Subject: [splices] Fwd: Progressing the INVOKE-related work
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: Mon, 25 Jul 2011 21:41:20 -0000

FYI.

-------- Original Message --------
Subject: Progressing the INVOKE-related work
Date: Mon, 25 Jul 2011 17:35:38 -0400
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>;
To: rai@ietf.org

Folks,

as you know, the following draft has lately been discussed in the
SPLICES and RAI area mailing lists:

https://datatracker.ietf.org/doc/draft-yusef-splices-invoke/

>From all the discussions, there seems to be interest in working on a
call/device control mechanism. In order to do that, we need to clearly
define the scope of such an effort (i.e., which types of primitives
would be in scope and which ones wouldn't).

In addition to defining the scope, there are open issues related to how
to model the mechanism (i.e., using SIP directly vs. using SIP to
establish a control channel). They will need to be resolved at some
point as well.

As some people have pointed out, the charter of SPLICES excludes working
on such a mechanism. Therefore, the next step is to have DISPATCH work
on a charter proposal for this effort. Nevertheless, we want to take
advantage of the current momentum behind this effort. So, this topic
will be discussed in SPLICES, as planned, during the IETF.

Cheers,

Gonzalo