IETF Logo Mail Archive

[dispatch] Charter Proposal - Remote Call/Device Control WG

"Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com> Tue, 20 September 2011 18:34 UTC

Return-Path: <rifatyu@avaya.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2521D1F0C69 for <dispatch@ietfa.amsl.com>; Tue, 20 Sep 2011 11:34:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.551
X-Spam-Level:
X-Spam-Status: No, score=-3.551 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sKikSQ8V+bqo for <dispatch@ietfa.amsl.com>; Tue, 20 Sep 2011 11:34:27 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 407D41F0C68 for <dispatch@ietf.org>; Tue, 20 Sep 2011 11:34:26 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EANjbeE7GmAcF/2dsb2JhbABCgk2kK2l4gVoSG14BFWsmAQQbGpsThAwCm02GHWAEmQiMDg
X-IronPort-AV: E=Sophos; i="4.68,412,1312171200"; d="scan'208,217"; a="268830282"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 20 Sep 2011 14:36:50 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 20 Sep 2011 14:36:09 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Tue, 20 Sep 2011 14:36:44 -0400
From: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
To: "dispatch@ietf.org" <dispatch@ietf.org>
Date: Tue, 20 Sep 2011 14:36:43 -0400
Thread-Topic: [dispatch] Charter Proposal - Remote Call/Device Control WG
Thread-Index: Acx3xD58K/QCxy77RU+NJxPPpra6SQ==
Message-ID: <6369CB70BFD88942B9705AC1E639A33822D1B91606@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_6369CB70BFD88942B9705AC1E639A33822D1B91606DCUS1MBEX4glo_"
MIME-Version: 1.0
Subject: [dispatch] Charter Proposal - Remote Call/Device Control WG
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 20 Sep 2011 18:34:28 -0000

Hi,



The following is a charter proposal for a Remote Call/Device Control WG.

We would appreciate it if you review it and provide us with your feedback.



Thanks,

Rifaat



-------



Remote Call/Device Control WG



The Session Initiation Protocol (SIP) [RFC3261] provides users with the ability to initiate, manage, and terminate multimedia sessions.

A SIP application is a program running on a SIP network element that provides some value-added function to a user.

Many deployments have SIP applications in the SIP signaling path that get involved in the setup and management of these multimedia sessions.

Third-Party Application might also be interested in interacting with User Agents and the setup of multimedia sessions.

Some of these applications need a mechanism to remotely invoke some actions or/and monitor the invocation of actions on a SIP User Agent.

SIP allows for the invocation of actions on a remote User Agent using the REFER method.

The actions that can be invoked by the REFER method are limited, and there is a need for more actions by some SIP applications.

The purpose of this WG is to evaluate the various available mechanisms or proposed mechanism and recommend one or more of them,

or define a new mechanism if none of the available are good enough to address this need.



The work group will need to address the following:

* Clearly answer the following questions:

   a. What is "call control"?

   b. What is "device control"?

* Will the new mechanism address "call control", "device control" or both?

* Will the new mechanism be a SIP or a non-SIP based mechanism?

* If a non-SIP mechanism is used, how to deal with the fact that some of these

  actions already covered by the SIP REFER method and widely used in the industry

* Define a model for the actions

* Define a scope for the actions

* Define a set of initial actions that can be later extended, if needed.

* Others?

v2.23.0 | Report a Bug | By Email