[Dmsp] draft charter revision 3

Chris Cross <xcross@us.ibm.com> Wed, 08 February 2006 15:00 UTC

Received: from localhost.cnri.reston.va.us ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6qo8-0002Fu-Lq; Wed, 08 Feb 2006 10:00:36 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6qo6-0002CH-OT for dmsp@megatron.ietf.org; Wed, 08 Feb 2006 10:00:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29246 for <dmsp@ietf.org>; Wed, 8 Feb 2006 09:58:21 -0500 (EST)
Received: from e31.co.us.ibm.com ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6r0C-0007mj-IF for dmsp@ietf.org; Wed, 08 Feb 2006 10:13:06 -0500
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com []) by e31.co.us.ibm.com (8.12.11/8.12.11) with ESMTP id k18Exonj008903 for <dmsp@ietf.org>; Wed, 8 Feb 2006 09:59:50 -0500
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com []) by d03relay04.boulder.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id k18F2HiN056452 for <dmsp@ietf.org>; Wed, 8 Feb 2006 08:02:17 -0700
Received: from d03av04.boulder.ibm.com (loopback []) by d03av04.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id k18Exnrw002552 for <dmsp@ietf.org>; Wed, 8 Feb 2006 07:59:49 -0700
Received: from d03nm119.boulder.ibm.com (d03nm119.boulder.ibm.com []) by d03av04.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id k18ExnFP002543 for <dmsp@ietf.org>; Wed, 8 Feb 2006 07:59:49 -0700
To: dmsp@ietf.org
X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005
Message-ID: <OF0443C39F.DCA1D554-ON8525710F.0051D3C8-8525710F.00523EA1@us.ibm.com>
From: Chris Cross <xcross@us.ibm.com>
Date: Wed, 8 Feb 2006 09:58:19 -0500
X-MIMETrack: Serialize by Router on D03NM119/03/M/IBM(Release 6.53HF654 | July 22, 2005) at 02/08/2006 08:01:53
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Subject: [Dmsp] draft charter revision 3
X-BeenThere: dmsp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Multimodal Synchronization Protocol <dmsp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dmsp>, <mailto:dmsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/dmsp>
List-Post: <mailto:dmsp@ietf.org>
List-Help: <mailto:dmsp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dmsp>, <mailto:dmsp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1900080419=="
Sender: dmsp-bounces@ietf.org
Errors-To: dmsp-bounces@ietf.org

I've only added an enumeration of our goals at the bottom.

----------WG Charter – revision 3--------------

The convergence of wireless communications with information technology and
the miniaturization of computing platforms have resulted in advanced mobile
devices that offer high resolution displays, application programs with
graphical user interfaces, and access to the internet through full function
web browsers.

Mobile phones now support most of the functionality of a laptop computer.
However the miniaturization that has made the technology possible and
commercially successful also puts constraints on the user interface. Tiny
displays and keypads significantly reduce the usability of application

Multimodal user interfaces, UIs that offer multiple modes of interaction,
have been developed that greatly improve the usability of mobile devices.
In particular multimodal UIs that combine speech and graphical interaction
are proving themselves in the marketplace.

However, not all mobile devices provide the computing resources to perform
speech recognition and synthesis locally on the device. For these devices
it is necessary to distribute the speech modality to a server in the

The Distributed Multimodal Working Group will develop the protocols
necessary to control, coordinate, and synchronize distributed modalities in
a distributed Multimodal system. There are several protocols and standards
necessary to implement such a system including DSR and AMR speech
compression, session control, and media streaming. However, the DM WG will
focus exclusively on the synchronization of modalities being rendered
across a network, in particular Graphical User Interface and Voice Servers.

The DM WG will develop an RFC for a Distributed Multimodal Synchronization
Protocol that defines the logical message set to effect synchronization
between modalities and enough background on the expected multimodal system
architecture (or reference architecture defined elsewhere in W3C or OMA) to
present a clear understanding of the protocol. It will investigate existing
protocols for the transport of the logical synchronization messages and
develop an RFC detailing the message format for commercial alternatives,
including, possibly, HTTP and SIP.

While not being limited to these, for simplicity of the scope the protocol
will assume RTP for carriage of media, SIP and SDP for session control, and
DSR and AMR for speech compression. The working group will not consider the
authoring of applications as it will be assumed that this will be done with
existing W3C markup standards such as XHTML and VoiceXML and commercial
programming languages like Java and C/C++.

It is expected that we will coordinate our work in the IETF with the W3C
Multimodal Interaction Work Group.

The following are our goals for the Working Group.

Date        Milestone
TBD         Submit Internet Draft Describing DMSP (standards track)
TBD         Submit Drafts to IESG for publication
Nov 2006    Submit DMSP specification to IESG


Chris Cross
Multimodal Browser Architect
IBM Boca Raton
voice 561.862.2102  t/l 975.2102
mobile 561.317.0700
fax 501.641.6727
Dmsp mailing list