[Dmsp] Fw: [Inquiry #84447] AutoReply: Request for Distributed Multimodal Synchronization Protocol (DMSP) BOF in Dallas

Chris Cross <xcross@us.ibm.com> Tue, 07 February 2006 16:02 UTC

Received: from localhost.cnri.reston.va.us ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6VIB-0007aG-8s; Tue, 07 Feb 2006 11:02:11 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6VIA-0007Mh-5q for dmsp@megatron.ietf.org; Tue, 07 Feb 2006 11:02:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06523 for <dmsp@ietf.org>; Tue, 7 Feb 2006 10:59:57 -0500 (EST)
Received: from e35.co.us.ibm.com ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6VU4-000557-Jg for dmsp@ietf.org; Tue, 07 Feb 2006 11:14:30 -0500
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com []) by e35.co.us.ibm.com (8.12.11/8.12.11) with ESMTP id k17G1TB9019943 for <dmsp@ietf.org>; Tue, 7 Feb 2006 11:01:29 -0500
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com []) by d03relay04.boulder.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id k17G3t5b168648 for <dmsp@ietf.org>; Tue, 7 Feb 2006 09:03:55 -0700
Received: from d03av01.boulder.ibm.com (loopback []) by d03av01.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id k17G1Sbj027638 for <dmsp@ietf.org>; Tue, 7 Feb 2006 09:01:28 -0700
Received: from d03nm119.boulder.ibm.com (d03nm119.boulder.ibm.com []) by d03av01.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id k17G1ScS027620 for <dmsp@ietf.org>; Tue, 7 Feb 2006 09:01:28 -0700
To: dmsp@ietf.org
X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005
Message-ID: <OF0234FE95.82A7255F-ON8525710E.0057FE0F-8525710E.005803AB@us.ibm.com>
From: Chris Cross <xcross@us.ibm.com>
Date: Tue, 7 Feb 2006 11:01:21 -0500
X-MIMETrack: Serialize by Router on D03NM119/03/M/IBM(Release 6.53HF654 | July 22, 2005) at 02/07/2006 09:03:30
MIME-Version: 1.0
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 3cb75504e283d08ef0543f38ba481a75
Subject: [Dmsp] Fw: [Inquiry #84447] AutoReply: Request for Distributed Multimodal Synchronization Protocol (DMSP) BOF in Dallas
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="===============1176212764=="
Sender: dmsp-bounces@ietf.org
Errors-To: dmsp-bounces@ietf.org

----- Forwarded by Chris Cross/West Palm Beach/IBM on 02/07/2006 11:01 AM
             "IETF Agenda via                                              
             <agenda@ietf.org>                                          To 
             Sent by: Apache           Chris Cross/West Palm               
             <apache@ticket.ie         Beach/IBM@IBMUS                     
             tf.org>                                                    cc 
             01/30/2006 12:58          [Inquiry #84447] AutoReply: Request 
             PM                        for Distributed Multimodal          
                                       Synchronization Protocol (DMSP) BOF 
                                       in Dallas                           
             Please respond to                                             


This message has been automatically generated in response to the
creation of a ticket regarding:
             "Request for Distributed Multimodal Synchronization Protocol
(DMSP) BOF in Dallas",
a summary of which appears below.

There is no need to reply to this message right now.  Your ticket has been
assigned an ID of [Inquiry #84447] in the queue: IETF-Agenda.

Please include the string:

         [Inquiry #84447]

in the subject line of all future correspondence about this issue. To do
you may reply to this message.

                        Thank you,


I am requesting a BOF at the Dallas meeting in the RAI Area. Below are the

    BOF Name: Distributed Multimodal Synchronization Protocol [DMSP]

    BOF Chair:  Nathaniel Borenstein <nborenst@us.ibm.com>

    AREA: Real-time Applications and Infrastructure Area

    CONFLICTS: SPEECHSC is in the same community, more or less. Please do
not schedule during the SPEECHSC meeting.

    Expected Attendance: 10

    Special requests (i.e. multicast, specific day of the week): None

    Number of slots: 1

    Length of slot: 2 hours


Chair:  Nathaniel Borenstein, IBM

Area Directors:  Allison Mankin <mankin@psg.com>

I.  Note Well, Blue Sheets, Introductions

II.  DMSP Overview and Discussion  -- Chris Cross, IBM, and J. Engelsma,
      (Initial I-D at

III.  Goals for a Possible WG
      (we hope to circulate a draft charter before the meeting)

IV.  Next Steps
      -- Revise I-D?
      -- New mailing list?
      -- Create WG?

    The goal of this BoF is to understand the need and discuss the creation
    a working group to create a protocol for the synchronization of
    in a distributed multimodal system.

   The advancement of wireless networking, mobile computing, and voice
   processing technologies have created a mobile computing environment
   where access to network based content and services is possible from
   mobile devices.  While the compact form factor of these devices is an
   essential and desirable characteristic from the mobility perspective,
   it unfortunately gives rise to a "user interface bottleneck".  That
   is, the small displays and limited keypads are significant barriers
   to usability.  The aim of multimodal user interfaces is to enhance
   the usability of mobile devices.

   The term "multimodal interface" in the context of this specification
   refers to augmenting the existing graphical user interface (GUI) of
   mobile devices with a voice user interface (VUI).  In this way, the
   strengths of one modality offset the weaknesses of the other.  For
   example, use speech to enter data that would be tedious to enter on a
   small keypad.  Similarly, use tactile input to disambiguate or
   confirm speech recognition results, or in lieu of speech recognition
   in a noisy environment.  Speech output also improves the
   accessibility of mobile applications for visually impaired users and
   is a means for addressing growing safety concerns by providing hands-
   free operation.  A visual display helps the user better retain and
   interpret information presented audibly via speech prompts.

   The  DMSP internet draft elaborates on a broad architectural framework
that combines
   the existing web and VoiceXML (Voice Extensible Markup Language)
   ecosystems and the industry standards upon which they are based.  The
   scope of the specification is limited to one particular
   architectural configuration within this framework: the coordination
   of a GUI browser or application running on a mobile device with a
   VoiceXML browser running in the network.  The Distributed Multimodal
   Synchronization Protocol (DMSP) accomplishes this. The ID is located at
Dmsp mailing list