top priority is to write the charte= r for the WG,

Hello,

You're receiving this email because of your interest and/or involvement=
 in

the Distributed Multimodal Synchronization Protocol (DMSP):

http://www.ietf.org/internet-drafts/draft-engelsma-dmsp-00=
.txt

We will advance this work within the IETF during early 2006, and in the=

interim are establishing a more formal mechanism to proactively collect=

everybody's feedback and progress the specification further. We will be=

establishing a mailing list shortly and will begin having one hour bi-w=
eekly

conference calls on November 30:

Time: Alternating Wednesdays, beginning November 30, 2005.  10:00a=
m Eastern.

US/Canada: +1-877-283-2663 

Italy: 800781687      

Japan: 00531160347

Norway: 8057408

UK: 08006920816

Other: +1.416.621.1671

Passcode: 0986279

On the initial November 30 call we will have a general discussion of th=
e

protocol's background and identify and discuss the objectives for this<=
br>
activity moving forward.  We look forward to your participation.

Regards,

-jre

All,

Please note, due to an unexpected schedule conflict involving a key
=

participant, these bi-weekly meetings have been rescheduled to begin on=

Wednesday, December 7.  The conference bridge and passcode will re=
main the

same:

Time: Alternating Wednesdays, beginning December 7, 2005.  10:00am=
 Eastern.

US/Canada: +1-877-283-2663 

Italy: 800781687      

Japan: 00531160347

Norway: 8057408

UK: 08006920816

Other: +1.416.621.1671

Passcode: 0986279

We look forward to your participation.

Regards,

-jre

-----Original Message-----

From: Jonathan Engelsma [mailto:jonathan.engelsma@motorola.com] 

Sent: Monday, November 21, 2005 4:41 PM

To: 'Jonathan.Engelsma@motorola.com'; 'James.Ferrans@motorola.com';
=

'David.Pearce@motorola.com'; 'Chris Cross'; 'Les Wilson'; 'Gregg Dagget=
t';

'nborenst@us.ibm.com'; 'daniel_zucker@access-us-inc.com';

'yam@access.co.jp'; 'jax@opera.no'; 'rfz@opera.com';

'awahbe@voicegenie.com'; 'paolo.baggia@loquendo.com'

Subject: DMSP bi-weekly meeting invitation

Hello,

You're receiving this email because of your interest and/or involvement=
 in

the Distributed Multimodal Synchronization Protocol (DMSP):

http://www.ietf.org/internet-drafts/draft-engelsma-dmsp-00=
.txt

We will advance this work within the IETF during early 2006, and in the=

interim are establishing a more formal mechanism to proactively collect=

everybody's feedback and progress the specification further. We will be=

establishing a mailing list shortly and will begin having one hour bi-w=
eekly

conference calls on November 30:

Time: Alternating Wednesdays, beginning November 30, 2005.  10:00a=
m Eastern.

US/Canada: +1-877-283-2663 

Italy: 800781687      

Japan: 00531160347

Norway: 8057408

UK: 08006920816

Other: +1.416.621.1671

Passcode: 0986279

On the initial November 30 call we will have a general discussion of th=
e

protocol's background and identify and discuss the objectives for this<=
br>
activity moving forward.  We look forward to your participation.

Regards,

-jre

All,

Just a friendly reminder of the DMSP call scheduled for tomorrow.

Time: Wednesday, December 21, 2005, 10:00am Eastern.

US/Canada: +1-877-283-2663 

Italy: 800781687      

Japan: 00531160347

Norway: 8057408

UK: 08006920816

Other: +1.416.621.1671

Passcode: 0986279

The agenda for tomorrow's call is to discuss the draft charter for an I=
ETF

working group.  A strawman will be circulated later today.

The minutes from the December 7 call are attached.  Thanks Gregg, =
for

putting these together.

Regards,

-jre

On Wed, 21 Dec 2005 16:03:00 +0100, Chris Cross <xcross@us.ibm.c=
om> wrote:

> Team,

> Here is my strawman:

I didn't add anything substantial or inspirational but I fiddled with t=
he  

language of the preamble (more of the same will be needed):

The convergence of wireless communications with information technology =
and  

the miniaturization of computing platforms have resulted in advanced &n=
bsp;

mobile devices that offer high resolution displays, application program=
s  

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 compute=
r.  

However the miniaturization that has made the technology possible and &=
nbsp;

commercially successful also puts constraints on the user interface. Ti=
ny  

displays and keypads significantly reduce the usability of application =

programs.

Multimodal user interfaces, UIs that offer multiple modes of interactio=
n,  

have been developed that greatly improve the usability of mobile device=
s.  

In particular multimodal UIs that combine speech and graphical interact=
ion  

are proving themselves in the marketplace.

However, not all mobile devices provide the computing resources to perf=
orm  

speech recognition and synthesis locally on the device. For these devic=
es  

it is necessary to distribute the speech modality to a server in the &n=
bsp;

network.

-- 

Jonny Axelsson, Core Technology, Opera Software ASA

Greetings,

This message has been automatically generated in response to the

creation of a ticket regarding:

		 "Request for Distributed Multimodal Synchronization Protocol (D=
MSP) 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 d=
o so, 

you may reply to this message.

                     =
   Thank you,

                     =
   agenda@ietf.org

-----------------------------------------------------------------------=
--

Allison,

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

details:

    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 les=
s. Please do

not schedule during the SPEECHSC meeting.

    Expected Attendance: 10

    Special requests (i.e. multicast, specific day of the wee=
k): None

    Number of slots: 1

    Length of slot: 2 hours

AGENDA FOR DMSP BOF

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,

Motorola

      (Initial I-D at

http://www.ietf.org/internet-drafts/draft-engelsma-dmsp-00=
.txt
)

III.  Goals for a Possible WG

      (we hope to circulate a draft charter before the m=
eeting)

IV.  Next Steps

      -- Revise I-D?

      -- New mailing list?

      -- Create WG?

Description:

    The goal of this BoF is to understand the need and discus=
s the creation

              of

    a working group to create a protocol for the synchronizat=
ion of

              modalities

    in a distributed multimodal system.

   The advancement of wireless networking, mobile computing, and v=
oice

   processing technologies have created a mobile computing environ=
ment

   where access to network based content and services is possible =
from

   mobile devices.  While the compact form factor of these de=
vices is an

   essential and desirable characteristic from the mobility perspe=
ctive,

   it unfortunately gives rise to a "user interface bottlenec=
k".  That

   is, the small displays and limited keypads are significant barr=
iers

   to usability.  The aim of multimodal user interfaces is to=
 enhance

   the usability of mobile devices.

   The term "multimodal interface" in the context of thi=
s 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. &=
nbsp;For

   example, use speech to enter data that would be tedious to ente=
r on a

   small keypad.  Similarly, use tactile input to disambiguat=
e or

   confirm speech recognition results, or in lieu of speech recogn=
ition

   in a noisy environment.  Speech output also improves the
   accessibility of mobile applications for visually impaired user=
s and

   is a means for addressing growing safety concerns by providing =
hands-

   free operation.  A visual display helps the user better re=
tain and

   interpret information presented audibly via speech prompts.
=

   The  DMSP internet draft elaborates on a broad architectur=
al 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 coordina=
tion

   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 lo=
cated at

http://www.ietf.org/internet-drafts/draft-engelsma=
-dmsp-00.txt

Hello all,

Just a friendly reminder:  Bi-weekly DMSP meetings will begin tomo=
rrow.

Time: Alternating Wednesdays, beginning December 7, 2005.  10:00am=
 Eastern.

US/Canada: +1-877-283-2663 

Italy: 800781687      

Japan: 00531160347

Norway: 8057408

UK: 08006920816

Other: +1.416.621.1671

Passcode: 0986279

We look forward to your participation.

Regards,

-jre

-------------

COMMENTS INLINE

-------------

4.2.6.10.  Start and Stop Playback Event Message

------------

SECTION CAPTION COPY PASTED AND DOES NOT REFLECT CONTENT

------------

   The VUA notifies the GUI User Agent when playback of TTS encoun=
ters a

   mark in the prompt text.  In addition to the common event =
fields, the

   payload for the Playback Mark Event includes:

   Mark: The mark label or tag contained in the prompt text.

Engelsma & Cross         Expires August 10, 200=
6               [Page 34]

=0C

Internet-Draft                D=
MSP Protocol                Feb=
ruary 2006

   +-----------------+--------------+--------------+--------------=
-----+

   | Field           | Type    =
     | Byte Length  | Value         =
    |

   +-----------------+--------------+--------------+--------------=
-----+

   | Message Type    | Integer      | 1 &=
nbsp;          | MSG_EVENT      =
;   |

   | Message Subtype | Integer      | 1   &nbs=
p;        | EVT_PLAYBACK_MARK |

   | Correlation     | Integer      | 4 &=
nbsp;          |         &=
nbsp;         |

   | Target Node     | String       | Var=
iable     |               =
    |

   | Mark            | String  =
     | Variable     |         &=
nbsp;         |

   +-----------------+--------------+--------------+--------------=
-----+

            Table 42: Extended Recognitio=
n Result Event Message

----------------

TABLE CAPTION  COPY PASTED AND DOES NOT REFLECT CONTENT

----------------

4.2.6.11.  Custom Event Message

   The VUA and GUA may implement custom events not specified in th=
e

   protocol.  Custom events may hinder interoperation between=
 user

   agents from different vendors.  In addition to the common =
event

   fields, the payload for the Custom Event includes:

   Name: The custom event name.

   Value: The value for the event.

   +-----------------+--------------+--------------+--------------=
-----+

   | Field           | Type    =
     | Byte Length  | Value         =
    |

   +-----------------+--------------+--------------+--------------=
-----+

   | Message Type    | Integer      | 1 &=
nbsp;          | MSG_EVENT      =
;   |

   | Message Subtype | Integer      | 1   &nbs=
p;        | EVT_PLAYBACK_MARK |

   | Correlation     | Integer      | 4 &=
nbsp;          |         &=
nbsp;         |

   | Target Node     | String       | Var=
iable     |               =
    |

   | Name            | String  =
     | Variable     |         &=
nbsp;         |

   | Value           | String   &nbs=
p;   | Variable     |          =
         |

   +-----------------+--------------+--------------+--------------=
-----+

            Table 43: Extended Recognitio=
n Result Event Message

--------------------

 TABLE CONTENT AND CAPTION COPY PASTED AND DOES NOT COVER CONTENT OF SE=
CTION

--------------------

_______________________________________________

Dmsp mailing list

Dmsp@ietf.org

https:=
//www1.ietf.org/mailman/listinfo/dmsp

[I seem to have missed responding to this mail when it came in, sor=
ry]

Hi, Chris,

Ted aired your BOF request to the IESG and IAB and we had a little

bit of discussion.  We did draw the conclusion that we'd like you =
to

grow more of an IETF-based constituency before holding a BOF.

This sounds strange, because a BOF sounds like the time when one gets <=
br>
the constituency, but as Thomas Narten has written in his 

draft-narten-successful-bof-01.txt, the good BOF builds up a lot

of discussion beforehand.  Although talented people and interestin=
g

work can get a good reception at an unprepared IETF meeting, we've

found that strong working groups grow best out of BOFs which have

prepared, already active participants.

So please do not interpret the delay of the BOF as a negative.

As I suggested when I set up the mailing list, get some email

out to the ietf, app-area, and other lists, inviting participation

and discussion of the draft.  Read Thomas's draft, actually, it de=
scribes

great next steps.  Go through these steps and work on participatio=
n.

Then present a BOF proposal again for the Summer IETF.

Starting these next steps is timely before Dallas.  In addition,
as I mentioned before, we're ready to set up a timeslot for 

you to get some attention for the topic during the raiarea 

meeting in Dallas.

Best regards,

Allison