idnits 2.17.1 

draft-melanchuk-sipping-moml-06.txt:
-(194): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding
-(218): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding
-(221): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding
-(971): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding
-(1046): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding
-(1083): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding
-(1084): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding
-(1284): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding
-(1289): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding
-(2441): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding
-(3640): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding
-(3651): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  https://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

  ** It looks like you're using RFC 3978 boilerplate.  You should update this
     to the boilerplate described in the IETF Trust License Policy document
     (see https://trustee.ietf.org/license-info), which is required now.

  -- Found old boilerplate from RFC 3978, Section 5.1 on line 17.

  -- Found old boilerplate from RFC 3978, Section 5.5 on line 3717.

  -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3688.

  -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3695.

  -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3701.

  ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line
     3707), which is fine, but *also* found old RFC 2026, Section 10.4C,
     paragraph 1 text on line 38.

  ** This document has an original RFC 3978 Section 5.4 Copyright Line,
     instead of the newer IETF Trust Copyright according to RFC 4748.

  ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78
     -- however, there's a paragraph with a matching beginning. Boilerplate
     error?

  ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead
     of the newer disclaimer which includes the IETF Trust according to RFC
     4748.


  Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

  == There are 28 instances of lines with non-ascii characters in the
     document.

  == No 'Intended status' indicated for this document; assuming Proposed
     Standard


  Checking nits according to https://www.ietf.org/id-info/checklist :
  ----------------------------------------------------------------------------

  ** The document seems to lack separate sections for Informative/Normative
     References.  All references will be assumed normative when checking for
     downward references.


  Miscellaneous warnings:
  ----------------------------------------------------------------------------

  == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not
     match the current year

  == Line 2085 has weird spacing: '...   code    len...'

  == Line 2393 has weird spacing: '...  <moml  versi...'

  == Line 2439 has weird spacing: '...  <moml  versi...'

  == Line 2569 has weird spacing: '...  <moml  versi...'

  == Line 2655 has weird spacing: '...nts and  platf...'

  -- The document seems to lack a disclaimer for pre-RFC5378 work, but may
     have content which was first submitted before 10 November 2008.  If you
     have contacted all the original authors and they are all willing to grant
     the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
     this comment.  If not, you may need to add the pre-RFC5378 disclaimer. 
     (See the Legal Provisions document at
     https://trustee.ietf.org/license-info for more information.)

  -- The document date (October 21, 2005) is 6755 days in the past.  Is this
     intentional?


  Checking references for intended status: Proposed Standard
  ----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative references
     to lower-maturity documents in RFCs)

  == Unused Reference: '1' is defined on line 3593, but no explicit reference
     was found in the text

  == Unused Reference: '10' is defined on line 3628, but no explicit
     reference was found in the text

  == Unused Reference: '11' is defined on line 3631, but no explicit
     reference was found in the text

  == Unused Reference: '13' is defined on line 3637, but no explicit
     reference was found in the text

  -- Possible downref: Non-RFC (?) normative reference: ref. '2'

  -- Possible downref: Non-RFC (?) normative reference: ref. '3'

  -- Possible downref: Non-RFC (?) normative reference: ref. '4'

  -- Possible downref: Non-RFC (?) normative reference: ref. '5'

  -- Possible downref: Non-RFC (?) normative reference: ref. '6'

  -- Possible downref: Non-RFC (?) normative reference: ref. '7'

  -- Possible downref: Non-RFC (?) normative reference: ref. '8'

  -- Possible downref: Non-RFC (?) normative reference: ref. '9'

  -- Possible downref: Non-RFC (?) normative reference: ref. '10'

  ** Obsolete normative reference: RFC 3265 (ref. '11') (Obsoleted by RFC
     6665)

  ** Obsolete normative reference: RFC 3023 (ref. '14') (Obsoleted by RFC
     7303)


     Summary: 8 errors (**), 0 flaws (~~), 12 warnings (==), 16 comments (--).

     Run idnits with the --verbose option for more detailed information about
     the items above.

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

1	Internet-draft   Media Objects Markup Language (MOML)     October 2005

3	   SIPPING                                                    A. Saleem
4	   Internet Draft                                           G. Sharratt
5	   Expires: April 24, 2006                                     Convedia

7	                                                       October 21, 2005

9	                   Media Objects Markup Language (MOML)
10	                      draft-melanchuk-sipping-moml-06

12	Status of this Memo

14	   By submitting this Internet-Draft, each author represents that any
15	   applicable patent or other IPR claims of which he or she is aware
16	   have been or will be disclosed, and any of which he or she becomes
17	   aware will be disclosed, in accordance with Section 6 of BCP 79.

19	   Internet-Drafts are working documents of the Internet Engineering
20	   Task Force (IETF), its areas, and its working groups. Note that other
21	   groups may also distribute working documents as Internet-Drafts.

23	   Internet-Drafts are draft documents valid for a maximum of six months
24	   and may be updated, replaced, or obsoleted by other documents at any
25	   time. It is inappropriate to use Internet-Drafts as reference
26	   material or to cite them other than as "work in progress."

28	   The list of current Internet-Drafts can be accessed at
29	   http://www.ietf.org/ietf/1id-abstracts.txt.

31	   The list of Internet-Draft Shadow Directories can be accessed at
32	   http://www.ietf.org/shadow.html.

34	   This Internet-Draft will expire on April 14, 2005.

36	Copyright Notice

38	   Copyright (C) The Internet Society (2005). All Rights Reserved.

40	Abstract

42	   The Media Objects Markup Language (MOML) is a modular and extensible
43	   language to define media processing objects which execute on media
44	   servers. The base language defines a set of primitive media objects
45	   (called primitives) and provides tools to group primitives together
46	   and specify how they interact with each other. Clients use the base
47	   MOML, or extend MOML, to create precisely tailored media processing
48	   objects which may be used as parts of application interactions with
49	   users or conferences or to transform media flowing internal to a
50	   media server. IVR is an example of an application interaction with a
51	   user.

53	Table of Contents

55	   1. Introduction...................................................4
56	   2. Conventions used in this document..............................5
57	   3. Overview.......................................................5
58	      3.1 Primitives.................................................7
59	      3.2 Groups.....................................................8
60	      3.3 Events....................................................11
61	   4. Usage with SIP................................................12
62	   5. Package Scheme................................................14
63	   6. Profile Scheme................................................14
64	   7. Structure and Modularity......................................15
65	   8. <moml>........................................................17
66	   9. MOML Core Module..............................................17
67	      9.1 Elements Received by a Media Server.......................17
68	         9.1.1 <send>...............................................17
69	         9.1.2 <exit>...............................................18
70	         9.1.3 <disconnect>.........................................18
71	      9.2 Elements Sent by a Media Server...........................19
72	         9.2.1 <event>..............................................19
73	   10. Group Module.................................................19
74	      10.1 <group>..................................................19
75	      10.2 <groupexit>..............................................20
76	   11. Basic Primitives Module......................................20
77	      11.1 <play>...................................................20
78	         11.1.1 Child Elements......................................22
79	            11.1.1.1 <audio>........................................22
80	            11.1.1.2 <video>........................................23
81	            11.1.1.3 <media>........................................24
82	            11.1.1.4 <var>..........................................25
83	            11.1.1.5 <playexit>.....................................25
84	      11.2 <dtmfgen>................................................25
85	         11.2.1 Child Elements......................................26
86	            11.2.1.1 <dtmfgenexit>..................................26
87	      11.3 <record>.................................................26
88	         11.3.1 Child Elements......................................30
89	            11.3.1.1 <play>.........................................30
90	            11.3.1.2 <recordexit>...................................30
91	      11.4 <dtmf> or <collect>......................................30
92	         11.4.1 Child Elements......................................33
93	            11.4.1.1 <play>.........................................33
94	            11.4.1.2 <pattern>......................................33
95	            11.4.1.3 <detect>.......................................33
96	            11.4.1.4 <noinput>......................................33
97	            11.4.1.5 <nomatch>......................................34
98	            11.4.1.6 <dtmfexit>.....................................34
99	   12. Transform Primitives Module..................................34
100	      12.1 <vad>....................................................34
101	         12.1.1 Child Elements......................................35
102	            12.1.1.1 <voice>, <silence>, <tvoice>, <tsilence>.......35
103	      12.2 <gain>...................................................35
104	      12.3 <agc>....................................................36
105	      12.4 <gate>...................................................36
106	      12.5 <clamp>..................................................37
107	      12.6 <relay>..................................................37
108	   13. Speech Module................................................37
109	      13.1 <speech>.................................................37
110	         13.1.1 Child Elements......................................39
111	            13.1.1.1 <grammar>......................................39
112	            13.1.1.2 <match>........................................39
113	            13.1.1.3 <noinput>......................................39
114	            13.1.1.4 <nomatch>......................................40
115	            13.1.1.5 <speechexit>...................................40
116	      13.2 <play>...................................................40
117	         13.2.1 Child Elements......................................40
118	            13.2.1.1 <tts>..........................................40
119	   14. Fax Module...................................................41
120	      14.1 <faxdetect>..............................................41
121	      14.2 <faxsend>................................................41
122	         14.2.1 Child Elements......................................43
123	            14.2.1.1 <sendobj>......................................43
124	            14.2.1.2 <hdrfooter>....................................43
125	            14.2.1.3 <rxpoll>.......................................44
126	            14.2.1.4 <faxstart>.....................................45
127	            14.2.1.5 <faxnegotiate>.................................45
128	            14.2.1.6 <faxpagedone>..................................45
129	            14.2.1.7 <faxobjectdone>................................45
130	            14.2.1.8 <faxopcomplete>................................46
131	            14.2.1.9 <faxpollstarted>...............................46
132	      14.3 <faxrcv>.................................................46
133	         14.3.1 Child Elements......................................47
134	            14.3.1.1 <rcvobj>.......................................47
135	            14.3.1.2 <txpoll>.......................................48
136	   15. Failure Codes................................................48
137	   16. Examples.....................................................49
138	      16.1 Announcement.............................................49
139	      16.2 Voice Mail Retrieval.....................................49
140	      16.3 Play and Record..........................................50
141	      16.4 Speech Recognition.......................................51
142	      16.5 Play and Collect.........................................52
143	      16.6 User Controlled Gain.....................................54
144	   17. Change Summary...............................................54
145	   18. XML Schema...................................................56
146	   Security Considerations..........................................74
147	   IANA Considerations..............................................74
148	   References.......................................................75
149	   Acknowledgments..................................................76
150	   Authors' Addresses...............................................76
151	   Intellectual Property Statement..................................77
152	   Copyright Statement..............................................77
153	   Disclaimer of Validity...........................................77
154	   Acknowledgement..................................................78

156	1. Introduction

158	   This document describes a markup language to configure and define
159	   media resource objects within a media server. The language allows the
160	   definition of sophisticated and complex media processing objects
161	   which may be used for application interactions with users, i.e. as
162	   part of a user dialog, or as media transformation operations. Media
163	   Objects Markup Language (MOML) itself does not specify a language
164	   suitable for constructing complete user interfaces as does VoiceXML
165	   [7]. Rather, it defines a language from which individual pieces of a
166	   dialog may be specified.

168	   MOML is not a standalone language but will generally be used in
169	   conjunction with other languages such as the Media Sessions Markup
170	   Language (MSML) [8] or protocols such as the Session Initiation
171	   Protocol (SIP). MSML is used to invoke and control many different
172	   services on a media server and to manipulate the flow of media
173	   streams within a media server. SIP is used to establish media
174	   sessions and there are conventions to use the SIP Request-URI to
175	   invoke common media server services [9].

177	   MOML has both a framework, which describes the composition of media
178	   resource objects, and the definition of an initial set of primitive
179	   media resource objects. The following sections describe the structure
180	   and usage of MOML followed by sections defining all of the MOML XML
181	   elements.

183	   Simple media resources and their composition into more complex
184	   operations is a central concept of this specification. This concept
185	   is used to precisely define the required behaviors. It is not meant
186	   to imply that media servers must be implemented from the same
187	   building blocks used to describe the behavior.

189	2. Conventions used in this document

191	   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
192	   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
193	   document are to be interpreted as described in RFC 2119 [7 (Bradner,
194	   S., �Key words for use in RFCs to Indicate Requirement Levels,� March
195	   1997.)].

197	3. Overview

199	   MOML is an XML [4] language for composing complex media objects from
200	   a vocabulary of simple media resource objects called primitives. It
201	   is primarily a descriptive or declarative language to describe media
202	   processing objects.

204	   MOML is intended to be used in different environments. As such, the
205	   language itself does not define how MOML is used. Each environment in
206	   which MOML is used must define how it is used, the set of services
207	   provided and the mechanism for passing information between the
208	   environment and MOML. The specific mechanisms used to realize the
209	   interface between MOML and its environment are platform specific.

211	   This specification defines using MOML with directly with SIP. The
212	   Media Session Markup Language [8] is an example of another
213	   environment which uses MOML.

215	   MOML provides two models for access to media resources and service
216	   creation building blocks. Both models MAY be used in conjunction with
217	   each other in a complementary manner. The first model (referred to as
218	   �Media Primitives and Composites�) contains media primitives (such as
219	   digit collection and announcements) and composite functions (such as
220	   play and collect combined as a single operation). The second model
221	   (referred to as �Media Groups� allows the ability to define complex
222	   customized interactions, via event passing mechanisms, between media
223	   primitives, if required.

225	      Media Primitives and Composites

227	         Media Primitives
228	            <dtmf> or <collect>
229	                        DTMF digit collection
230	            <play>
231	                        Playing of Announcements
232	            <dtmfgen>
233	                        Generation of DTMF digits
234	            <record>
235	                        Media recording

237	         Media Composites
238	            <collect>
239	                        Supports play and collect operation.
240	                        Composite function with inclusion of play.
241	            <record>
242	                        Supports play and record operation.
243	                        Composite function with inclusion of play.
244	      Media Groups

246	            <group>
247	                        Allows grouping of media primitives for parallel
248	                        execution, with an event exchange mechanism
249	                        between the media primitives to achieve
250	                        customized media operations. All the above media
251	                        primitive elements are accepted within the
252	                        group.

254	   Following operations MUST be supported using elements described above
255	   using either the Media Primitive model or the Media Group model.

257	     Announcement only
258	                        <play>
259	     Collection only

261	                        <dtmf> or <collect>
262	     Recording only
263	                        <record>

265	     Play and Collect
266	                        <collect>
267	                           <play/>
268	                        </collect>

270	     Play and Record
271	                        <record>
272	                           <play/>
273	                        </record>

275	   MOML MAY be used to simply expose primitive media resource objects
276	   but will be used more often to describe dialog operations and media
277	   transformation objects which can be controlled via user interaction.

279	   MOML does not contain any computation or flow control constructs.
280	   There are no results automatically generated when media operations
281	   complete. Results MUST be explicitly requested using a <send> or
282	   <exit> element within the definition of the MOML object.

284	3.1 Primitives

286	   Primitives perform a single function on a media stream such as
287	   generating audio, recognizing speech or DTMF, or adjusting the gain.
288	   They may be composed so that primitives execute concurrently.
289	   Primitives not composed for concurrent execution MUST simply execute
290	   sequentially in the order they occur in a MOML document. All
291	   concurrently executing primitives in the same MOML object (defined in
292	   one MOML document) MAY interact with each other through events.

294	   Currently all primitives use audio media but primitives for text and
295	   video will be defined in a future version of this specification.
296	   Primitives can roughly be considered to fall into one of three
297	   descriptive categories.

299	      o  recognizers have a media input but no output. They allow
300	         different things within a media stream to be recognized or
301	         detected and for events to be generated based upon received
302	         media.

304	      o  transformers have one media input and output and may send and
305	         receive events;

307	      o  sources and sinks generate or consume media. They have either a
308	         media input or a media output but not both. They may receive
309	         and generate events.

311	      o  composites combine underlying primitives to provide higher-
312	         level user interaction, without the need for specific event
313	         based exchange between the primitives. The composite elements
314	         provide a simpler mechanism for more commonly used services,
315	         such as play and collect or play and record.

317	   Primitives may define different media processing behavior (states)
318	   based upon the events which they receive. Primitives which support
319	   different processing states must define their default starting state
320	   and should support the "initial" attribute to allow that state to be
321	   specified when the primitive is instantiated. All primitives must
322	   support the "terminate" event class.

324	   The following types of primitives are defined within this
325	   specification:

327	       Recognizers    Transformers   Source/Sink   Composites
328	       ------------------------------------------------------
329	         dtmf           agc           play          collect
330	         faxtone        clamp         record        record
331	         speech         gain          dtmfgen
332	         vad            gate          faxsend
333	                        relay         faxrcv

335	   Primitives have shadow variables, similar to those within VoiceXML
336	   [7], which are automatically assigned values when the primitives are
337	   used. Upon initialization of a MOML context, all shadow variables
338	   have the string value "undefined". Each primitive has its own
339	   instance of shadow variables which are global in scope to the entire
340	   MOML context.

342	   Names SHOULD be assigned to individual primitives when more than one
343	   primitive of the same type is used within one MOML document. Shadow
344	   variables are overwritten if the primitive has not been named and is
345	   instantiated a second time.

347	   Shadow variables cannot be modified under user control. They may be
348	   returned from the MOML context using the <send> element.

350	3.2 Groups

352	   Primitives are composed for concurrent execution by placing them
353	   within a <group> element. Groups define how media flows between
354	   multiple concurrently executing primitives. They have one or more
355	   inputs and one or more outputs. A <group> represents the declaration
356	   of a complex media processing operation. The event interaction
357	   between primitives (see the following sub-section) is defined within
358	   the context of one or more groups. However groups themselves do not
359	   scope events, they simply define that primitives are concurrently
360	   executing and a primitive must be executing in order to receive an
361	   event.

363	   Placing primitives within a group structure is an optional feature of
364	   this specification. It allows for complex services to created using
365	   the event exchange mechanism between the primitives. For simpler
366	   services, such as play/collect or play/record, the use of group
367	   mechanism is not necessary. These basic services MAY be accomplished
368	   using composites and primitives instead.

370	   Groups may also be used to describe media objects which transform a
371	   media stream while optionally allowing application or user control of
372	   the transformation. For example a gain control could be defined which
373	   responds to user speech or DTMF input. In this case a recognition
374	   primitive would send events to a gain control primitive.

376	   Groups have one attribute which defines the media flow within them.
377	   They also have a dimension which defines how many media inputs and
378	   outputs they have. Currently dimensions of 1 and 2 are supported
379	   based upon the group topology. These correspond to a group with one
380	   input and one output and a group with two inputs and two outputs.

382	   Media flow to and from the primitives within the group is based upon
383	   a topology attribute of the <group> element. This differs from a
384	   similar mechanism in Media Policy Manipulation in the Conference
385	   Policy Control Protocol [3] which explicitly defined connections. The
386	   topology attribute defines a topology schema and implies the group
387	   dimension.

389	   There are several common ways in which primitives are often connected
390	   together. A schema provides a convenient template which can be
391	   applied to multiple primitives without having to define all of the
392	   individual media relationships. The following two schemas are
393	   initially defined for 1 dimensional groups:

395	      o  parallel: specifies that media sent to the group is sent to
396	         every primitive which has an input. The group bridges the
397	         output from every primitive which has an output into a single
398	         common group output;

400	      o  serial: specifies that the first primitive listed in the group
401	         receives the media sent to the group. Its output is to be
402	         connected to the input of the next primitive defined within the
403	         group and so on until the last primitive within the group which
404	         becomes the group output.

406	   Groups with these topologies are shown in the two diagrams below. The
407	   group on the left has a parallel topology and that on the right has a
408	   serial topology.

410	           /-> P1 --\
411	          /          \
412	   G(in) +---> P2 ----> G(out)     G(in) --> P1 --> P2 --> P3 --> G(out)
413	          \          /
414	           \-> P3 --/

416	   More complex media flows MAY be created by nesting groups of serial
417	   and parallel topologies within each other. For example, the diagram
418	   below has a group with a serial topology nested within a star
419	   topology.

421	                  /-----> P1 ------------------------\
422	                 /                                    \
423	         Gs(in) +-> Gp(in) --> P2 --> P3 --> Gp(out) -+> Gs(out)

425	   This combination could be used to create record operation where DTMF
426	   was to be clamped from the recording itself, but a DTMF key press is
427	   still used to stop the recording. In this case, P1 would be a DTMF
428	   recognizer, P2 would be a clamp primitive, and P3 a recorder as shown
429	   by the following example. This example omits child elements and
430	   attributes not concerned with the core concept. The following section
431	   discusses sending events and the details of each of the primitives is
432	   defined in section 4.

434	   <group topology="parallel">
435	      <dtmf/>
436	      <group topology="serial">
437	         <clamp/>
438	         <record/>
439	      </group>
440	   </group>

442	   A single schema, "fullduplex" is defined for a two dimensional group.
443	   A full-duplex two dimensional group is has exactly two immediate
444	   children. Those children may be primitives or other one dimensional
445	   groups. A "fullduplex" group must only be used as the top most group
446	   and must not be nested. Each primitive (P1) and group (G2) becomes
447	   half of the full-duplex group as shown in the diagram below.

449	                  G-A(in1) +-> G2 --> G-B(out1)

451	                 G-A(out2) <-- P1 <-+ G-B(in2)

453	   Full duplex groups are symmetrical when both halves are the same.
454	   They are asymmetrical when they differ. Asymmetric groups need to
455	   have a name associated with each side. The left side is defined as
456	   the input of the first child of the full-duplex group combined with
457	   the output of the second child. The right side is reverse. These
458	   sides were labeled A and B respectively in the preceding diagram.

460	   An example of a full-duplex group is the user operated gain control
461	   mentioned at the beginning of this sub-section. The gain should
462	   operate on the audio which a user hears, but the gain is controlled
463	   by recognizing things such as DTMF or spoken commands in media which
464	   the user originates. The following shows the XML tag grouping which
465	   would accomplish this and corresponds to the media flow shown in the
466	   diagram above. If the user's audio is not required for anything other
467	   than control of the gain, then the <relay> is not required and the
468	   internal group could be omitted. A complete XML description for this
469	   is included in the examples section.

471	   <group topology="fullduplex">
472	      <group topology="parallel">
473	         <dtmf/>
474	         <relay/>
475	      </group>
476	      <gain/>
477	   </group>

479	   Primitives within a group MUST begin concurrently but MAY finish
480	   asynchronously based upon events which they receive or their task
481	   completes. A group MUST terminate when all of the primitives within
482	   it have completed. If the group contains a <groupexit> element, then
483	   the contents of that element MUST be executed as part of group
484	   termination.

486	   A group itself MAY receive a terminate event requesting termination.
487	   A terminate event sent to the group causes a terminate event to be
488	   sent to each of its currently active primitives. The <groupexit>
489	   element is not executed until all primitives have processed their
490	   respective terminate events.

492	3.3 Events

494	   Events provide the mechanism for primitives to interact with each
495	   other and for a MOML context to interact with its external
496	   environment. The external environment is defined by the way in which
497	   a MOML context has been invoked. This will often be through MSML but
498	   other languages and protocols such as SIP may also be used.

500	   Every primitive and group conceptually implements their own event
501	   queue. Events sent to them get placed into their associated queue.
502	   Events are removed from their queues and processed in order.
503	   Primitives within a group conceptually have their own thread of
504	   execution. Due to the asynchronous nature of servicing events from
505	   multiple queues, it cannot be assumed that several events sent in
506	   sequence to different queues, will be processed in the order in which
507	   they were sent. For example, if recognition of something led to
508	   sending events to both a <play> and a <record> in that order, it is
509	   possible that the <record> may process its event before the <play>

511	   Primitives each define the set of events which they support and the
512	   behavior associated with their handling of each event. This allow
513	   many types of behaviors to be defined. For example, VCR type controls
514	   can be constructed by defining primitives which support events
515	   corresponding to each control. Media recognition/detection can be
516	   used to cause those events to be generated.

518	   Alternatively, events can be originated elsewhere, such as from an
519	   application server, and simply received by the primitive implementing
520	   the control. Examples of the use of events include adjusting volume
521	   (gain) and pause and resume of both announcement playout and record
522	   creation.

524	   Primitives act on events based upon the longest match of an event
525	   name. Event names are a period '.' delimited sequence of tokens. The
526	   first token, or the root of the name, can be considered an event
527	   class. Matching allows a standard meaning to be defined and then
528	   extended based upon what triggers an event's generation. For example,
529	   a record primitive has different behavior depending upon whether it
530	   completed because a user stopped speaking or because it was
531	   cancelled. The recording is retained in the first case but not the
532	   second.

534	   Longest match allows new recognizers to be created and used without
535	   changing how existing primitives are defined. For example, a face
536	   recognition capability could be created which generates a
537	   terminate.frowning event when a user looks puzzled. Although no
538	   primitive directly defines this event, it will still effect a generic
539	   terminate action. Primitives which require specialized behavior based
540	   upon frowning may be extended to support this. As well, the event can
541	   still be exported from the MOML context without requiring that
542	   primitives receiving the event understand facial expressions.

544	4. Usage with SIP

546	   MOML MAY be used directly with SIP for IVR or fax dialog
547	   interactions. It can be initially invoked as part of the "Prompt and
548	   Collect" service described in "Basic Network Media Services with SIP"
549	   [9]. That defines service indicators for a small number of well
550	   defined services using the user part of the SIP Request-URI (R-URI).

552	   The prompt and collect service uses "dialog" as the service
553	   indicator. URI parameters further refine the specific IVR request.
554	   This document defines an additional parameter "moml-param" for the
555	   dialog service indicator as follows:

557	   dialog-parameters = ";" ( dialog-param [ vxml-parameters ] )
558	                           | moml-param
559	   dialog-param      = "voicexml=" dialog-url
560	   moml-param        = "moml=" moml-url
561	   There are no additional URI parameters when MOML is used as the
562	   dialog language.

564	   MOML defines discrete IVR dialog commands. These commands MAY be
565	   included directly in the body of the INVITE to the "dialog" service
566	   indicator by using the "cid" [12] URL scheme. This scheme identifies
567	   a message body part which in this case would contain the MOML
568	   command. Note that a multipart message body, containing a single
569	   part, MUST be present even if the INVITE does not contain an SDP
570	   offer. Subsequent MOML requests are sent in the body of SIP INFO
571	   messages as are all messages from a media server.

573	   An example of SIP URI as described above is:

575	      sip:dialog@mediaserver.example.net;\
576	          moml=cid:14864099865376@appserver.example.net

578	   The body part that contained the MOML referenced by the URL would
579	   have a Content-Id header of:

581	      Content-Id: <14864099865376@appserver.example.net>

583	   The results of executing an <exit> or <disconnect>, or of executing a
584	   <send> which has a "target" attribute value equal to "source", are
585	   notified in SIP INFO messages using the <event> element. No messages
586	   are sent if execution completes normally without executing one of
587	   these elements.

589	   If there is an error during validation or execution, then a media
590	   server MUST notify the error as described above and must include the
591	   namelist items "moml.error.status" and "moml.error.description". The
592	   values for these items are defined in section 15.

594	   A restricted subset of MOML can also be used with the "Announcement"
595	   service defined in [9]. This service uses "ann" as the service
596	   indicator and defines parameters that describe an announcement. The
597	   "play=" parameter identifies the URL of a prompt or a provisioned
598	   announcement sequence. The value of the "play=" parameter can refer
599	   to a MOML body part using a "cid" URL as described above. That body
600	   part must only contain the <play> primitive.

602	   Using MOML enhances the announcement service by allowing the client
603	   to specify a sequence of audio segments rather than requiring each
604	   sequence to be provisioned. Moreover, MOML defines a standard set of
605	   variables in contrast to [9] which defines a parameterization
606	   mechanism but does not formally specify any semantics.

608	   If a media server does not understand the "cid" scheme or does not
609	   understand MOML, it must respond with the SIP response code "488 -
610	   not acceptable here". If the MOML body contains elements other than
611	   the <play> primitive, or there are errors during validation, a media
612	   server must respond with a SIP response code "400 - bad request".
613	   Finally, if there is a discrepancy between parameters specified in
614	   the Request-URI and corresponding attributes defined in the MOML
615	   body, the Request-URI parameters must be silently ignored.

617	   MOML MUST NOT change the operation of the announcement service from
618	   that defined in [9]. When the announcement completes, a media server
619	   issues a SIP BYE request. The INFO method MUST NOT used with the
620	   announcement service.

622	5. Package Scheme

624	   The primary mechanism for extending MOML is the "package". A package
625	   is an integrated set of one or more XML schemas that define
626	   additional features and functions via new or extended use of elements
627	   and attributes. Each package is defined in a separate standards
628	   document, e.g., an Internet Draft or an RFC. All packages, extending
629	   the base MOML functionality, MUST include references to the MOML base
630	   set of schemas provided in the Internet drafts.

632	   A schema in a package MUST extend MSML or MOML, i.e., may not mix
633	   MSML and MOML. A package MAY contain any combination of schemas
634	   extending MSML and schemas extending MOML.

636	   A particular MSML or MOML script will include references to all the
637	   schemas defining the packages whose elements and attributes it makes
638	   use of. A particular script MUST reference either MSML base and
639	   optionally package(s) or MOML base and optionally package(s). See
640	   IANA Considerations section.

642	   Each package MUST have its own namespace so that elements or
643	   attributes with the same name in different packages do not conflict.
644	   A script using a particular element or attribute MUST prefix the
645	   namespace name on that element or attribute's name if it is defined
646	   in a package (as opposed to being defined in the base).

648	6. Profile Scheme

650	   Not all devices and applications using MSML/MOML will need to support
651	   the entire MSML/MOML base schema.  For example, a media processing
652	   device might support only audio announcements, only audio simple
653	   conferencing, or only multimedia IVR.  It is high desirable to have a
654	   system for describing what portion of the MSML/MOML base a particular
655	   media processing device or application server supports.

657	   Since packages are the scheme used for describing chunks of MSML/MOML
658	   functionality beyond the MSML/MOML base, one possibility might be to
659	   break the MSML/MOML base into a number of packages.  MSML/MOML,
660	   however, is an XML-based language with sophisticated capabilities,
661	   and audio and video capabilities, for example, are intertwined in the
662	   schema.  So it would not be technically feasible to break the MSML
663	   base and the MOML base into individual packages.

665	   A better solution, and one more suited to the XML nature of
666	   MSML/MOML, is to create profiles of the MSML/MOML for the different
667	   uses. Each profile would identify a subset of the MOML/MOML base
668	   element and attributes, and each profile would be accompanied by one
669	   or two corresponding schemas that are a subset of the MSML base
670	   and/or the MOML base.  To use the examples above, there could be an
671	   audio announcements profile, an audio simple conferencing profile,
672	   and a multimedia IVR profile.

674	   These profiles would be published separately from the MSML/MOML base
675	   documents, in one or more standards documents (e.g., Internet Drafts
676	   or RFCs) dedicated to profiles.  Public profiles would not be
677	   registered with IANA and any organization would be free to create its
678	   own private profile(s) if required.

680	7. Structure and Modularity

682	   MOML is designed to be a modular language. Defining the language in
683	   terms of modules allows different vendors and communities to choose a
684	   specific language subset, or define different language extensions,
685	   for achieving a wide range of applications across a diverse set of
686	   platforms. Modularity combined with namespaces allow independent
687	   development of new extensions.

689	   MOML is structured as a set of modules. Only a single module is
690	   required. That simple core module, moml-core-module, defines a MOML
691	   request to a media server. It consists of the �primitive�
692	   abstraction, an abstract element for control flow, the sequential
693	   execution model, and the <send> element. That is, the core module
694	   allows for the execution of a sequence of one or more media
695	   processing primitives with the ability to notify events to the
696	   invocation environment.

698	   Primitives are divided into four modules. The first, moml-basic-
699	   primitives, defines the basic <play>, <record>, <dtmf>, and <vad>
700	   elements. Another module, moml-transform-primitives, defines the
701	   simple half duplex filters. More advanced primitives are defined in
702	   the speech and fax modules. The speech module depends on the play
703	   module as it extends the capability of <play> by adding synthesized
704	   speech. Finally, the group execution model, which is currently the
705	   only element which changes the flow of control is defined in a
706	   separate module. All of these module are optional although at least
707	   one primitive module is required to have a functional implementation.

709	   The formal process for defining extensions to MOML is to define a new
710	   module. The new module MUST provide a text description of what
711	   extensions are included and how they work. It MUST also define an XML
712	   schema file (if applicable) that defines the new module (which may be
713	   through extension or restriction of an existing module). Dependencies
714	   upon other modules MUST be stated. For example a module that extends
715	   or restricts has a dependency on the original. Finally, the new
716	   module MUST be assigned a unique name and version.

718	   The types of things which can be defined in new modules are:

720	      o  new primitives

722	      o  extensions to existing primitives (events, shadow variables,
723	         attributes, content)

725	      o  new recognition grammars for existing primitives

727	      o  new markup languages for speech generation

729	      o  languages for specifying a topology schema

731	      o  new pre-defined topology schemas

733	      o  new variables / segment types (sets & languages)

735	      o  new control flow elements

737	   Modules are assembled together to form a specific MOML profile that
738	   is shared between different implementations. The base MOML profile
739	   which is defined in this documents consists of the moml-core, group,
740	   and basic and transform primitives modules. Speech and facsimile are
741	   examples of optional modules which extend the base language.

743	   Modules which define primitives must define the following for each
744	   primitive within the module:

746	      o  the function which the primitive performs

748	      o  the attributes which may be used to tailor its behavior

750	      o  the events which it is capable of understanding

752	      o  the shadow variables which provide access to information
753	         determined as a result of the primitive's operation.

755	   The mechanism used to insure that a media server and its client share
756	   a compatible set of modules is not defined. Currently it is expected
757	   that provisioning will be used, possibly coupled with a future
758	   auditing capability. Additionally, when used in SIP networks, modules
759	   could be defined using feature tags and the procedures defined for
760	   Indicating User Agent Capabilities in SIP [2] used to allow a media
761	   server to describe its capabilities to other user agents and its
762	   domain registrar.

764	8. <moml>

766	   The root element for MOML. The contents of this element describe
767	   either a complete execution context for a media resource object or
768	   the event to be notified to a MOML client.

770	      Attributes:

772	         version: "1.0" Mandatory.

774	         id: an identifier unique to this object. Events returned from
775	         MOML (the "target" attribute of a <send> is equal to "source")
776	         will be correlated with this identifier. Mandatory.

778	      Events:

780	         terminate: terminates the MOML context. A terminate event gets
781	         sent to the currently executing <group> or primitive.

783	9. MOML Core Module

785	   The core module defines the structural framework and abstractions for
786	   MOML (via its schema). It also defines the basic elements which are
787	   not part of the core primitive or control abstractions. These
788	   elements are defined below.

790	9.1 Elements Received by a Media Server

792	9.1.1 <send>

794	   Sends an event and optional namelist to the recipient identified by
795	   the target attribute. Event names are defined by the recipient. In
796	   the case where the recipient is a MOML group or primitive, the events
797	   are defined within this document. Other recipients MAY use names that
798	   are suitable for their environment.

800	   The "target" attribute specifies the recipient of the event.
801	   Recipients MAY be other MOML primitives or groups executing within
802	   the object, the object itself, or the environment which invoked MOML.
803	   Any target which is unknown within the object is assumed to be
804	   destined to the external environment. By convention, the string
805	   "source" SHOULD used to address that environment but any target name
806	   distinct from the MOML namespace MAY be used.

808	      Attributes:

810	         event: the name of an event.

812	         target: the recipient of the event. The recipient MUST be a
813	         MOML primitive, the currently executing group, or the MOML
814	         environment. A primitive is specified by a primitive type,
815	         optionally appended by a period '.' followed by the identifier
816	         of a primitive. Identifiers are only needed when more than one
817	         primitive of the same type exists in the object. The executing
818	         group is specified using the token "group". The environment is
819	         specified using the token "source", optionally appended by a
820	         period '.' followed by any environment specific target.

822	         namelist: a list of zero or more shadow variables which are
823	         included with the event.

825	9.1.2 <exit>

827	   Exit causes execution of the MOML object to terminate.

829	      Attributes:

831	         namelist: a list of one or more shadow variables which MAY
832	         optionally be sent to the context which invoked the MOML
833	         object.

835	9.1.3 <disconnect>

837	   Disconnect is similar to <exit> but has the additional semantics of
838	   indicating to the context which invoked the MOML object, that it
839	   should disconnect from a media server, the media stream associated
840	   with the object. The method of disconnection depends upon how the
841	   media stream was initially established. If SIP was used, a
842	   <disconnect> would cause a media server to issue a BYE request. The
843	   request would be sent for the SIP dialog associated with media
844	   session on which the MOML object was operating.

846	      Attributes:

848	         namelist: a list of one or more shadow variables which MAY
849	         optionally be sent to the context which invoked the MOML
850	         object.

852	9.2 Elements Sent by a Media Server

854	9.2.1 <event>

856	   The <event> element is used to describe an event and its associated
857	   namelist when MOML is used as a standalone dialog language such as
858	   with SIP. Events are generated and formatted when a <send>, <exit>,
859	   or <disconnect> is executed.

861	      attributes:

863	         name: the type of event. If the event is generated because of
864	         the execution of a <send>, the value MUST be the value of the
865	         "event" attribute from the <send> element. If the event is
866	         generated because of the execution of an <exit>, the value MUST
867	         be "moml.exit". If the event is generated because of the
868	         execution of a <disconnect>, the value MUST be
869	         "moml.disconnect". If the even is generated because of an
870	         error, the value must be "moml.error". Mandatory.

872	         id: the identifier of the MOML object generating the event.
873	         Mandatory.

875	   <event> has two children, <name> and <value>, which contain the name
876	   and value respectively of each namelist item associated with the
877	   event.

879	10. Group Module

881	   The group module defines a single control flow construct that
882	   specifies concurrent execution. Future modules may define additional
883	   flow control constructs.

885	10.1 <group>

887	   The <group> element allows the contained primitives to be executed
888	   concurrently.

890	      Attributes:

892	         topology: specifies a schema which defines the flow of media
893	         within the group. Three schemas are initially defined.
894	         "fullduplex" is specified for use with two dimensional groups.
895	         "parallel" and "serial" are for use with one dimensional
896	         groups. The definition of these topologies is defined in
897	         section 2. Mandatory.

899	         id: identifies name of the group. Mandatory when groups are
900	         nested.

902	      Events:

904	         terminate: causes a terminate event to be sent to each element
905	         contained within the group.

907	10.2 <groupexit>

909	   The <groupexit> element allows events to be sent when group
910	   processing completes. Group processing completes when all contained
911	   primitives terminate.

913	      Attributes:

915	         none

917	      Events:

919	         none

921	11. Basic Primitives Module

923	   Subsections of a primitive define child elements of that primitive
924	   and are not themselves considered primitives. They do not receive
925	   events or populate shadow variables.

927	11.1 <play>

929	   Play is used to generate an audio or video stream. It MUST play in
930	   sequence the media created by the child media elements <audio>,
931	   <video>, <media>, <tts>, and <var>. When the play stops, either
932	   because the terminate event is received or all media generation has
933	   completed, the <playexit> element, if present, is executed. At least
934	   one media generation element must be present.

936	   Play supports two states; generate and suspend. Media generation
937	   occurs in the generate state and is suspended in the suspend state.
938	   Once in the suspend state, media generation continues upon receiving
939	   the generate event. The default initial state is generate.

941	   Audio MAY be generated in different languages by specifying the
942	   xml:lang attribute for <play> and/or the child elements of <play>.
943	   The language is inherited by the child elements but each child MAY
944	   specify its own language. Except for physical audio clips, it is an
945	   error if a language is specified but the media server can not render
946	   the audio in the requested language.

948	      Attributes:

950	         id: an optional identifier which may be referenced elsewhere
951	         for sending events to the play primitive.

953	         interval: specifies the delay between stopping one iteration
954	         and beginning another. The attribute has no effect if
955	         iterations is not also specified. Default is no interval.

957	         iterate: specifies the number of times the media specified by
958	         the child media elements should be played. Each iteration is a
959	         complete play of each of the child media elements in document
960	         order. Defaults to once '1'.

962	         initial: defines the initial state for the play element.
963	         Default is "generate".

965	         maxtime: defines the maximum allowed time for the <play> to
966	         complete.

968	         barge: defines whether or not audio announcements MAY be
969	         interrupted by DTMF detection during play-out. The DTMF digit
970	         barging the announcement is stored in the digit buffer. Valid
971	         values for barge are �true� or �false�, and the attribute is
972	         mandatory.

974	         cleardb: defines whether the digit buffer is cleared or not,
975	         prior to starting the announcement. Valid values for cleardb
976	         are �true� or �false�, and the attribute is mandatory.

978	         offset: defines an offset, measured in units of time, where the
979	         <play> is to begin media generation. Offset is only valid when
980	         all child media elements are <audio>.

982	         skip: an amount, expressed in time, which will be used to skip
983	         through the media when "forward" and "backward" events are
984	         received. Default is 3s (three seconds).

986	         xml:lang: specifies the language to use for content which can
987	         be rendered in different languages.

989	      Events:

991	         pause: causes the play to enter the suspend state.

993	         resume: causes play to enter the generate state.

995	         forward: skips forward through the media. Only has effect when
996	         all child media elements are <audio>.

998	         backward: skips backward through the media. Only has effect
999	         when all child media elements are <audio>.

1001	         restart: skips to the beginning of the media. Only has effect
1002	         when all child media elements are <audio>.

1004	         toggle-state: causes the suspend / generate state to toggle.

1006	         terminate: terminates the play and assigns values to the shadow
1007	         variables.

1009	      Shadow Variables:

1011	         play.amt: identifies the length of time for which media was
1012	         generated before the play was stopped. This does not include
1013	         time which may have elapsed while the play was in the suspend
1014	         state.

1016	         play.end: contains the event which caused the play to stop.
1017	         When the play stops because all media generation has completed,
1018	         end is assigned the value "play.complete".

1020	   Note: Attributes barge and cleardb provide a simplified mechanism for
1021	   controlling play operations with implicit DTMF without the use of
1022	   <group> and event exchange mechanism. When using the <play> element
1023	   within the group framework and barge is specified, detection of barge
1024	   condition generates an implicit terminate event to the play
1025	   primitive.

1027	11.1.1 Child Elements

1029	11.1.1.1 <audio>

1031	   Identifies pre-recorded audio to play. Local URI references may
1032	   resolve to a single physical audio clip, a logical clip, or a
1033	   provisioned sequence of clips (physical or logical). A logical clip
1034	   is one which can be rendered differently based on the language
1035	   attribute. Logical clips are provisioned for each of the languages
1036	   that a media server supports. Remote URI references are resolved
1037	   according to the capabilities of the remote server.

1039	      Attributes:

1041	         uri: Identifies the location of the audio to be played. The
1042	         file and http schemes are supported.

1044	         format: defines the encoding and file type of the audio
1045	         resource. The format attribute is defined as a string type of
1046	         form �audio/<filetype>;codecs=<codec>�. The keyword �audio�
1047	         identifies an audio content. The codecs field identifies the
1048	         audio file�s codec to be used for decoding the audio content.
1049	         If format attribute is not specified, the filetype MUST be
1050	         determined from the URI and the codec information MUST be
1051	         determined from the media resource.

1053	         audiosamplerate: Identifies audio sample rate in kHz. If not
1054	         specified, the sample rate SHOULD be determined from the media
1055	         resource.

1057	         audiosamplesize: Identifies audio sample size in bits. If not
1058	         specified, the sample size SHOULD be determined from the media
1059	         resource.

1061	         iterate: specifies the number of times the audio is to be
1062	         played. Defaults to once '1'.

1064	         xml:lang: specifies the language to use when the URI identifies
1065	         a logical clip, either directly, or as part of a sequence.

1067	11.1.1.2 <video>

1069	   Identifies pre-recorded multimedia to play. Contents identified by
1070	   the URI attribute may contain audio only, video only, or both audio
1071	   and video. Media Server SHOULD attempt to play both audio and video
1072	   from the identified URI, if both are available in the content.

1074	      Attributes:

1076	         uri: Identifies the location of the video or multimedia to be
1077	         played. The file and http schemes are supported.

1079	         format: defines the encoding and file type of the video or
1080	         multimedia resource. The format attribute is defined as a
1081	         string type of form
1082	         �video/<filetype>;codecs=<codecx>,<codecy>�. The keyword
1083	         �video� identifies video only media or media containing audio
1084	         and video. The �codecs� field identifies the audio and/or video
1085	         codecs to be used for decoding the file content, where the
1086	         order of the codec values is not significant. In the event of
1087	         audio and video content, using �video� keyword, the
1088	         codecs=<codecx>,<codecy> field MAY be used to identify the
1089	         audio codec and the video codec. If not specified, the codec
1090	         information SHOULD be determined from the media file.

1092	         audiosamplerate: Identifies audio sample rate in kHz. If not
1093	         specified, the sample rate SHOULD be determined from the media
1094	         file.

1096	         audiosamplesize: Identifies audio sample size in bits. If not
1097	         specified, the sample size SHOULD be determined from the media
1098	         file.

1100	         codecconfig: Identifies an optional special instruction string
1101	         for codec configuration. Default is to send no special
1102	         configuration string to the codec.

1104	         profile: Identifies a video profile name specific to the codec.
1105	         If not specified, default video profile of the codec SHOULD be
1106	         selected.

1108	         level: Identifies a video profile level to the codec. Default
1109	         is to send no profile information to the codec and allow the
1110	         codec to select an internal default.

1112	         imagewidth: Identifies the width of video image in pixels.
1113	         Default is to use image width information from media file.

1115	         imageheight: Identifies the height of video image in pixels.
1116	         Default is to use image height information from media file.

1118	         maxbitrate: Identifies the bitrate of the video signal in kbps.
1119	         Default is to use maximum bitrate information from the media
1120	         file.

1122	         framerate: Identifies the video frame rate in frames per
1123	         second. Default is to use frame rate information from the media
1124	         file.

1126	         iterate: specifies the number of times the audio is to be
1127	         played. Defaults to once '1'.

1129	11.1.1.3 <media>

1131	   Identifies multimedia content for play. All content of <media>
1132	   element MUST start to play concurrently. This element may be used to
1133	   generate a multi-media stream from two independent media resources,
1134	   one identifying audio and the other identifying video.

1136	   The <media> element MUST contain at least one child element. Valid
1137	   child elements of <media> are <audio> and <video>, as described
1138	   earlier. <media> element MUST contain at most one <audio> element or
1139	   at most one <video> element.

1141	11.1.1.4 <var>

1143	   Specifies the generation of audio from a variable using prerecorded
1144	   audio segments. A variable represents a semantic concept (such as
1145	   date or number) and dynamically produces the appropriate speech.

1147	   Prerecorded audio allows an application vendor or service provider to
1148	   choose the exact voice for their audio and therefore completely
1149	   control the "sound and feel" of the service provided to end users. It
1150	   provides very high audio quality and allows the variables to blend
1151	   seamlessly into the surrounding audio segments.

1153	   Text to speech (TTS) using SSML may also be used to render variables,
1154	   but may not provide as good quality, or allow as complete control of
1155	   the "sound and feel" or user experience. TTS is normally used for
1156	   reading text such as emails and for very large vocabularies such as
1157	   stock names. TTS results in a very clear difference between the
1158	   variables and the surrounding audio segments.

1160	      Attributes:

1162	         type: specifies the type of variable. Mandatory. Variable type
1163	         must be one of "date", "digits", "duration", "month", "money",
1164	         "number", "silence", "time", or "weekday".

1166	         subtype: specifies an optional clarification of type. Specific
1167	         values depend upon the type.

1169	         value: text which should be rendered appropriate to the type
1170	         and subtype attributes.

1172	         xml:lang: specifies the language to use when rendering the
1173	         variable.

1175	11.1.1.5 <playexit>

1177	   The <playexit> element MUST be invoked when generation of all content
1178	   of the <play> has come to completion. The contents of this element
1179	   MAY be used to send events.

1181	      Attributes:

1183	         none

1185	11.2 <dtmfgen>

1187	   DTMF generator originates one or more DTMF digits in sequence.

1189	      Attributes:

1191	         id: an optional identifier which may be referenced elsewhere
1192	         for sending events to the dtmfgen primitive.

1194	         digits: A string of characters from the alphabet "0-9a-d#*"
1195	         which correspond to a sequence of DTMF tones. Mandatory.

1197	         level: used to define the power level for which the tones will
1198	         be generated. Expressed in dBm0 in a range of 0 to -96 dBm0.
1199	         Larger negative values express lower power levels. Note that
1200	         values lower than -55 dBm0 will be rejected by most receivers
1201	         (TR-TSY-000181, ITU-T Q.24A). Default is -6 dBm0.

1203	         dur: the duration in milliseconds for which each tone should be
1204	         generated. Implementations may round the value if they only
1205	         support discrete durations. Default 100 ms.

1207	         interval: the duration in milliseconds of a silence interval
1208	         following each generated tone. Implementations may round the
1209	         value if they only support discrete durations. Default 100 ms.

1211	      Events:

1213	         terminate: terminates DTMF generation and assigns values to the
1214	         shadow variables.

1216	      Shadow Variables:

1218	         dtmfgen.end: contains the event which caused DTMF generation to
1219	         stop.

1221	11.2.1 Child Elements

1223	11.2.1.1 <dtmfgenexit>

1225	   The <dtmfgenexit> element MUST be invoked when the DTMF generation
1226	   operation completes or is terminated as a result of receiving the
1227	   terminate event. The <dtmfgenexit> element MAY be used to send events
1228	   when the recording has completed.

1230	      Attributes:

1232	         none

1234	11.3 <record>

1236	   Record creates a recording. Similar to play, <record> supports two
1237	   states; create and suspend. Received media becomes part of the
1238	   recording when <record> is in the create state and is discarded when
1239	   it is in the suspend state.

1241	   Recording MUST be terminated when a terminate event is received or
1242	   when a nospeech event is received and no audio has yet been recorded.
1243	   <record> differentiates different types of terminate events.

1245	   An optional <play> element MAY be specified as a child element of
1246	   <record>. This mechanism provides a complete play-record operation,
1247	   where the prompt(s) specified within the <play> element are played in
1248	   advance of start of recording.

1250	   Note: Attributes prespeech, postspeech, and termkey provide a
1251	   simplified mechanism for controlling record operations using implicit
1252	   DTMF and VAD, without the use of <group> and event exchange
1253	   mechanism.

1255	      Attributes:

1257	         id: an optional identifier which may be referenced elsewhere
1258	         for sending events to the record primitive.

1260	         append: a boolean which defines whether the recording is
1261	         allowed to be appended to an existing file if dest already
1262	         exists. Default is "false". The attribute is ignored if the
1263	         scheme is http.

1265	         dest: the destination for the recording, which will contain
1266	         either audio only, video only, or both audio and video
1267	         depending on the stream(s) being recorded. Recording MAY be
1268	         either local or external based upon the attribute value. File
1269	         and http schemes are supported.

1271	         audiodest: the destination for the audio only recording.
1272	         Recording MAY be either local or external based upon the
1273	         attribute value. All combinations of dest, audiodest, and
1274	         videodest are valid. File and http schemes are supported.

1276	         videodest: the destination for the video only recording.
1277	         Recording MAY be either local or external based upon the
1278	         attribute value. All combinations of dest, audiodest, and
1279	         videodest are valid. File and http schemes are supported.

1281	         format: defines the encoding and file type of the recording.
1282	         The format attribute is defined as a string type of form
1283	         �audio|video/filetype;codecs=x,y�. The keyword �audio�
1284	         identifies an audio only recording, while the keyword �video�
1285	         identifies video only recording or an audio plus video
1286	         recording. The codecs field identifies the audio and/or video
1287	         codecs to be used for the recording, where the order of the
1288	         codec values is not significant. In the event of audio and
1289	         video recording, using �video� keyword, the codecs=x,y field
1290	         MAY be used to identify the audio codec and the video codec.

1292	         codecconfig: Identifies an optional special instruction string
1293	         for codec configuration. Default is to send no special
1294	         configuration string to the codec.

1296	         audiosamplerate: Identifies audio sample rate in kHz. If not
1297	         specified, the sample rate SHOULD be determined from the media
1298	         source.

1300	         audiosamplesize: Identifies audio sample size in bits. If not
1301	         specified, the sample size SHOULD be determined from the media
1302	         source.

1304	         profile: Identifies a video profile name specific to the codec.
1305	         If not specified, default video profile of the codec SHOULD be
1306	         selected for the recording.

1308	         level: Identifies a video profile level to the codec. Default
1309	         is to send no profile information to the codec and allow the
1310	         codec to select an internal default.

1312	         imagewidth: Identifies the width of video image in pixels.
1313	         Default is to use image width information from the media
1314	         source.

1316	         imageheight: Identifies the height of video image in pixels.
1317	         Default is to use image height information from the media
1318	         source.

1320	         maxbitrate: Identifies the bitrate of the video signal in kbps.
1321	         Default is to use maximum bitrate information from the media
1322	         source.

1324	         framerate: Identifies the video frame rate in frames per
1325	         second. Default is to use frame rate information from the media
1326	         source.

1328	         initial: defines the initial state for the record element.
1329	         Default is "create", which starts the recording as soon as the
1330	         <record> element is executed. The �initial� attribute is
1331	         applicable only when <record> is used within the <group>
1332	         structure.

1334	         maxtime: defines the maximum length of the recording in units
1335	         of time.

1337	         prespeech: defines a timer value, in seconds, for detection of
1338	         absence of audio energy at the start of the record operation.
1339	         If no audio energy is detection for the amount of time
1340	         specified by prespeech, the recording is terminated. Default is
1341	         �0s�, which does not activate the prespeech timer.

1343	         postspeech: defines a timer value, in seconds, for detection of
1344	         absence of audio energy while the recoding is in progress.
1345	         During an in progress recording, if absence of audio energy is
1346	         detected as specified by the postspeech timer, the recording is
1347	         terminated. Default is �0s�, which disables the ability to
1348	         terminate a recording due to postspeech silence.

1350	         termkey: defines a single DTMF key which when detection
1351	         terminates the recording. Absence of this attribute prevents
1352	         the recording from being terminated due to detection of DTMF
1353	         digits. When termkey is specified, the detected DTMF digit
1354	         terminates the recording and the DTMF digit is not entered in
1355	         the digit buffer.

1357	      Events:

1359	         Following describes input events to the media primitive object.
1360	         The Group Model allows an event exchange mechanism between
1361	         primitives.

1363	         pause: causes the record to enter the suspend state. Received
1364	         media is discarded.

1366	         resume: causes record to resume if it was suspended. It has no
1367	         effect otherwise.

1369	         toggle-state: causes the suspend / create state to toggle.

1371	         terminate: terminates the recording and assigns values to the
1372	         shadow variables.

1374	         terminate.cancelled: terminates the recording and assigns
1375	         values to the shadow variables. If the dest attribute used the
1376	         file scheme, the local recording is deleted. Applications are
1377	         responsible for removing external files created using the http
1378	         scheme.

1380	         terminate.finalsilence: terminates the recording and assigns
1381	         values to the shadow variables. If the dest attribute used the
1382	         file scheme, the final silence is removed from the recording.

1384	         nospeech: terminates the recording and assigns values to the
1385	         shadow variables if it is received and no recording has yet
1386	         been created. The "nospeech" event is ignored if audio has
1387	         already been recorded.

1389	      Shadow Variables:

1391	         record.len: the actual length of the recording measured in
1392	         units of time. This does not include time which may have
1393	         elapsed while the record was in the suspend state.

1395	         record.end: contains the event which caused the record to
1396	         terminate. When the record terminates because maxtime is
1397	         exceeded, end is assigned the value
1398	         "record.complete.maxlength".

1400	         Record termination due to prespeech silence, results in
1401	         assigned value of �record.failed.prespeech�

1403	         Record termination due to postspeech silence, results in
1404	         assigned value of �record.complete.postspeech�

1406	         Record termination due to DTMF detection, results in assigned
1407	         value of �record.complete.termkey�

1409	11.3.1 Child Elements

1411	11.3.1.1 <play>

1413	   The optional <play> element as a child element of <record> allows a
1414	   prompt to be played prior to start of recording. The record operation
1415	   starts at the end of the play sequence or if the play is barged by
1416	   DTMF, assuming that barge=true is specified for <play>. For a
1417	   complete description, refer to <play> element.

1419	11.3.1.2 <recordexit>

1421	   The <recordexit> element MUST be invoked when the record operation
1422	   completes or when the recording is terminated as a result of
1423	   receiving the terminate event. The <recordexit> element MAY be used
1424	   to send events when the recording has completed.

1426	      Attributes:

1428	         none

1430	11.4 <dtmf> or <collect>

1432	   DTMF input fulfils several roles within MOML. It is used to trigger
1433	   events which will affect the media processing operation of other
1434	   primitives. It is also used to collect DTMF digits from a media
1435	   stream which are to be reported back to the user of MOML. Often DTMF
1436	   detection is used for both purposes. Barge is the most common
1437	   example, where a prompt is stopped based upon DTMF input but more
1438	   digits may remain to be collected.

1440	   DTMF detection supports multiple simultaneous recognition patterns.
1441	   Different patterns can be used to trigger sending different events in
1442	   order to implement DTMF controls. Alternatively one pattern may be
1443	   used to represent a collection and another pattern, a substring of
1444	   the first, used as a barge indication.

1446	   An optional <play> element MAY be specified as a child element of
1447	   <dtmf> or <collect>. This mechanism provides a complete play-collect
1448	   operation, where the prompt(s) specified within the <play> element
1449	   are played in advance of DTMF digit collection.

1451	   Note that all patterns share the same digit collection buffer, inter-
1452	   digit timing, a single <nomatch> element, and a single <noinput>
1453	   element. As such, multiple patterns may not be suitable to support
1454	   simultaneous collections for different purposes. When this is
1455	   required, separate <dtmf> elements should be used instead.

1457	   <dtmf> terminates if any of the <pattern>, <noinput>, or <nomatch>
1458	   elements are matched the maximum number of times that they are
1459	   allowed. The number of times they may match may be specified as an
1460	   attribute of <dtmf> or of the individual child elements.

1462	   Element identifier <dtmf> is equivalent to <collect>. However,
1463	   <collect> is the preferred name. MOML clients should use <collect>,
1464	   while MOML servers should support both.

1466	      Attributes:

1468	         id: an optional identifier which may be referenced elsewhere
1469	         for sending events to this primitive.

1471	         cleardb: a boolean indication of whether the buffer for digit
1472	         collection should be cleared of any collected digits when the
1473	         element is instantiated. If set to false, any digits currently
1474	         in the buffer MUST be immediately compared against the pattern
1475	         elements.

1477	         fdt: defines the first-digit timer value. The first-digit timer
1478	         is started when DTMF detection is initially invoked. If no DTMF
1479	         digits are detected during this initial interval, the <noinput>
1480	         element MUST be invoked.

1482	         idt: defines the inter-digit timer to be used when digits are
1483	         being collected. When specified, the timers is started when the
1484	         first digit is detected and restarted on each subsequent digit.
1485	         Timer expiration is applied to all patterns. After that, if any
1486	         patterns remain active and a nomatch element is specified, the
1487	         nomatch is executed and DTMF input MUST terminate. The idt
1488	         attribute should only be used when digit collection is being
1489	         performed. No default.

1491	         starttimer: boolean value which defines whether the first digit
1492	         timer (fdt) is started initially. When set to false, the
1493	         starttimer event must be received for it to start. Default
1494	         false.

1496	         iterate: specifies the number of times the <pattern>,
1497	         <noinput>, and <nomatch> elements may be executed unless those
1498	         elements specify differently. The value "forever" MAY be used
1499	         to indicate that these may be executed any number of times.
1500	         Default is once '1'.

1502	      Events:

1504	         Following describes input events to the media primitive object.
1505	         The Group Model allows an event exchange mechanism between
1506	         primitives.

1508	         starttimer: starts the first digit timer (fdt) if it has not
1509	         already been started. Has no effect otherwise.

1511	         terminate: terminates the DTMF input and assigns values to the
1512	         shadow variables.

1514	      Shadow Variables:

1516	         dtmf.digits: the string of DTMF digits which have been received
1517	         (the contents of the digit buffer).

1519	         dtmf.len: the number of digits in the digit buffer.

1521	         dtmf.last: the last digit in the digit buffer.

1523	         dtmf.end: contains the event which caused the <dtmf> to
1524	         terminate or is assigned one of "dtmf.match", "dtmf.noinput",
1525	         or "dtmf.nomatch" depending upon which of the corresponding
1526	         elements reached its maximum.

1528	11.4.1 Child Elements

1530	11.4.1.1 <play>

1532	   The optional <play> element as a child element of <dtmf> or <collect>
1533	   allows a prompt to be played prior to DTMF digit collection. DTMF
1534	   digit collection starts at the end of the play sequence or if the
1535	   play is barged by DTMF, assuming that barge=true is specified for
1536	   <play>. For a complete description, refer to <play> element.

1538	11.4.1.2 <pattern>

1540	   The pattern element describes one or more DTMF digits that are to be
1541	   recognized. When the pattern is matched, the child elements MUST be
1542	   executed.

1544	      Attributes:

1546	         digits: The digit pattern which should be matched.

1548	         format: an enumerated value which defines the format used to
1549	         express the digit pattern. The format may be "mgcp" or "megaco"
1550	         for patterns expressed as digit map from those specifications,
1551	         or as one of the simple built-in formats defined within this
1552	         specification. Currently, a single built-in format
1553	         "moml+digits" is defined which allows a match based on either
1554	         one or more specific digits, or based upon a specific length
1555	         specification with an optional return key. "moml+digits" is the
1556	         default.

1558	         iterate: specifies the number of times the <pattern> may be
1559	         matched. The value "forever" may be used to indicate that
1560	         <pattern> may be matched any number of times. This value
1561	         overrides any specified in <dtmf>. Default is once '1'.

1563	11.4.1.3 <detect>

1565	   The contents of the <detect> element MUST be executed whenever any
1566	   DTMF is first detected. It MUST be matched at most once.

1568	      Attributes:

1570	         none

1572	11.4.1.4 <noinput>

1574	   The <noinput> element is used when DTMF is being collected. Children
1575	   of the <noinput> element MUST be executed when DTMF has not been
1576	   detected and the first digit timeout occurs.

1578	      Attributes:

1580	         iterate: specifies the number of times the <noinput> may be
1581	         triggered. The value "forever" may be used to indicate that
1582	         <noinput> may be triggered any number of times. This value
1583	         overrides any specified in <dtmf>. Default is once '1'.

1585	11.4.1.5 <nomatch>

1587	   The <nomatch> element is used when DTMF is being collected. Children
1588	   of the <nomatch> element MUST be executed when it is determined that
1589	   none of the individual patterns can be matched.

1591	      Attributes:

1593	         iterate: specifies the number of times the <nomatch> may be
1594	         triggered. The value "forever" may be used to indicate that
1595	         <nomatch> may be triggered any number of times. This value
1596	         overrides any specified in <dtmf>. Default is once '1'.

1598	11.4.1.6 <dtmfexit>

1600	   The <dtmfexit> element MUST be invoked when the dtmf input completes
1601	   because one of <pattern>, <noinput>, or <nomatch> occurred its
1602	   maximum number of times.

1604	      Attributes:

1606	         none

1608	12. Transform Primitives Module

1610	   The transform primitives module gathers together the simple
1611	   primitives which work as filters on half duplex media streams.

1613	12.1 <vad>

1615	   Voice activity detection (VAD) is used to detect voice and silence
1616	   when speech recognition is not required. Similar to both speech and
1617	   DTMF, a VAD has different media conditions which it can match. Those
1618	   conditions can be qualified by a minimum length of time which is
1619	   required for them to be considered recognized.

1621	      Attributes:

1623	         starttimer: boolean value which defines whether the timer is
1624	         started to allow recognition of the initial condition (voice,
1625	         silence). When set to false, the starttimer event must be
1626	         received in order for the initial condition to be recognized.
1627	         The timer does not affect recognition of the transition
1628	         conditions. Default false.

1630	      Events:

1632	         starttimer: starts the timer to allow recognition of the
1633	         initial condition if it has not already been started. Has no
1634	         effect otherwise.

1636	         terminate: terminates voice activity detection.

1638	      Shadow Variables:

1640	         none

1642	12.1.1 Child Elements

1644	12.1.1.1 <voice>, <silence>, <tvoice>, <tsilence>

1646	   Each child element corresponds to a condition which a VAD can detect.
1647	   The first two detect when voice or silence has been initially present
1648	   for a minimum length of time since the VAD was started. The second
1649	   two require that a transition to the voice or silence condition first
1650	   occur.

1652	      Attributes:

1654	         len: the length of time the condition must persist in order to
1655	         be recognized. In the case of <tvoice> and <tsilence>, the
1656	         length of time applies only to the final recognized condition.

1658	         sen: the maximum length of time the condition not being
1659	         detected may occur without causing the detector to begin
1660	         measuring that condition.

1662	12.2 <gain>

1664	   Gain MAY be used to adjust of the gain of a media stream by a
1665	   specific amount.

1667	      attributes:

1669	         incr: an increment, expressed in dB, which will be used to
1670	         adjust the gain when "louder" and "softer" events are received.
1671	         Default is 3 dB.

1673	         amt: a specific gain to apply specified in dB.

1675	      events:

1677	         mute: self explanatory.

1679	         unmute: self explanatory.

1681	         reset: sets the gain to zero dB.

1683	         louder: makes the audio on a stream louder.

1685	         softer: makes the audio on a stream quieter.

1687	         amt: sets the gain to the specified value between -96 dB and 9
1688	         dB.

1690	12.3 <agc>

1692	   Automatic gain control MAY be used to have a media server
1693	   automatically adjust the gain of a media stream.

1695	      attributes:

1697	         tgtlvl: the desired target level for AGC specified in dBm0.

1699	         maxgain: the maximum gain that AGC will apply specified in dB.

1701	      events:

1703	         mute: self explanatory.

1705	         unmute: self explanatory.

1707	12.4 <gate>

1709	   A simple filter which will pass or halt media, regardless of the
1710	   format of the media stream, based on the events it receives. <gate>
1711	   shares the same mute and unmute events for compatibility with the
1712	   gain primitives <gain> and <agc>.

1714	      attributes:

1716	         initial: the values "pass" and "halt" define whether media is
1717	         initially allowed to pass. Default is to pass.

1719	      events:

1721	         mute: halts media flow through the primitive.

1723	         unmute: allows media to pass through the primitive.

1725	12.5 <clamp>

1727	   This element MAY be used to filter DTMF tones from a media stream.
1728	   Media other than DTMF tones is passed unchanged.

1730	      attributes:

1732	         none.

1734	      events:

1736	         none.

1738	12.6 <relay>

1740	   This element is a simple primitive which copies its input to its
1741	   output.

1743	      attributes:

1745	         none.

1747	      events:

1749	         none.

1751	13. Speech Module

1753	   The speech module defines a standalone primitive which MAY be used
1754	   for automatic speech recognition <speech> and extends the <play>
1755	   primitive defined in the basic primitives module to include speech
1756	   synthesis. As such, this module depends on the basic primitives
1757	   module.

1759	13.1 <speech>

1761	   Activates grammars or user input rules associated with speech
1762	   recognition. If multiple grammars are specified, all are activated.
1763	   All active grammars share the same timers, recognition attributes,
1764	   and <noinput> and <nomatch> elements. Each grammar may have its own
1765	   <match> element.

1767	   <speech> terminates if any of the <grammar>, <noinput>, or <nomatch>
1768	   elements are matched the maximum number of times that they are
1769	   allowed. The number of times they may match may be specified as an
1770	   attribute of <speech> or of the individual child elements.

1772	      Attributes:

1774	         noint: specifies a time period during which speech input must
1775	         be started, otherwise the associated <noinput> element is
1776	         invoked.

1778	         norect: specifies a maximum time period during in which speech
1779	         must begin to be matched, otherwise the associated <nomatch>
1780	         element is invoked.

1782	         spcmplt: specifies the length of silence necessary after speech
1783	         before a result will be finalized in the case where there is a
1784	         complete match of an active grammar. Following the silence, the
1785	         appropriate <match> element will be triggered if the result is
1786	         above the confidence level. Otherwise a <nomatch> element will
1787	         be triggered.

1789	         spincmplt: specifies the length of silence necessary after
1790	         speech before a result will be finalized in the case where
1791	         there is a incomplete match of all active grammars. Following
1792	         the silence, the <nomatch> element will be triggered.

1794	         confidence: the minimum confidence level which the recognizer
1795	         must have to consider a recognition result as matching a
1796	         grammar. Expressed as an integer between 1-100.

1798	         sens: specifies the sensitivity of the recognizer to determine
1799	         whether speech is present. Lower sensitivity may be required
1800	         for the recognizer to work well in the presence of high
1801	         background noise or line echo.

1803	         starttimer: boolean value which defines whether the no input
1804	         (noint) and no recognition (norect) are started initially. When
1805	         set to false, the starttimer event must be received in order to
1806	         start them. Default false.

1808	         iterate: specifies the number of times the <grammar>,
1809	         <noinput>, and <nomatch> elements may be executed unless those
1810	         elements specify differently. The value "forever" may be used
1811	         to indicate that these may be executed any number of times.
1812	         Default is once '1'.

1814	      Events:

1816	         sens: sets the sensitivity of the recognizer as described
1817	         above.

1819	         starttimer: starts the no input (noint) and no recognition
1820	         (norect) timers if they have not already been started. Has no
1821	         effect otherwise.

1823	         terminate: terminates the speech input and assigns values to
1824	         the shadow variables.

1826	      Shadow Variables:

1828	         speech.end: contains the event which caused the <speech> to
1829	         terminate or is assigned one of "speech.match",
1830	         "speech.noinput", or "speech.nomatch" depending upon which of
1831	         the corresponding elements reached its maximum.

1833	         speech.results: contains the results of a matched grammar. The
1834	         results are formatted using the Natural Language Semantics
1835	         Markup Language (NLSML) [6]. When this variable is referenced
1836	         to return results, the results are returned as a separate MIME
1837	         entity.

1839	13.1.1 Child Elements

1841	13.1.1.1 <grammar>

1843	   Specifies and activates a speech grammar based on Speech Recognition
1844	   Grammar Specification (SRGS) [5] XML notation. Grammars may be
1845	   referenced by a URI or defined inline. Child elements of <match> MUST
1846	   be executed when the specified speech grammar is matched.

1848	      Attributes:

1850	         uri: specifies the location of an SRGS grammar when the grammar
1851	         is not defined inline.

1853	         iterate: specifies the number of times the <grammar> may be
1854	         matched. The value "forever" MAY be used to indicate that
1855	         <grammar> may be matched any number of times. This value
1856	         overrides any specified in <speech>. Default is once '1'.

1858	13.1.1.2 <match>

1860	   <match> is a child of <grammar> and specifies the actions to take
1861	   when the corresponding grammar is matched.

1863	13.1.1.3 <noinput>

1865	   The <noinput> element is used when speech is being recognized.
1866	   Children of the <noinput> element MUST be executed when speech has
1867	   not been detected and the no input timeout (noint) occurs.

1869	      Attributes:

1871	         iterate: specifies the number of times the <noinput> may be
1872	         triggered. The value "forever" may be used to indicate that
1873	         <noinput> may be triggered any number of times. This value
1874	         overrides any specified in <speech>. Default is once '1'.

1876	13.1.1.4 <nomatch>

1878	   The <nomatch> element is used when speech is being recognized.
1879	   Children of the <nomatch> element MUST be executed when it is
1880	   determined that none of the active grammars will match.

1882	      Attributes:

1884	         iterate: specifies the maximum number of times the <nomatch>
1885	         may be triggered. The value "forever" MAY be used to indicate
1886	         that <nomatch> may be triggered any number of times. This value
1887	         overrides any specified in <speech>. Default is once '1'.

1889	13.1.1.5 <speechexit>

1891	   The <speechexit> element MUST be invoked when the speech input
1892	   completes because one of <grammar>, <noinput>, or <nomatch> occurred
1893	   its maximum number of times.

1895	      Attributes:

1897	         none

1899	13.2 <play>

1901	   The <play> element, as defined in the basic primitives module, is
1902	   extended with a new child element for synthesizing speech. From an
1903	   XML perspective, <tts> is a member of a media substitution group. See
1904	   the schema at the end of this document for details.

1906	13.2.1 Child Elements

1908	13.2.1.1 <tts>

1910	   Contents of the <tts> element are rendered using Text To Speech
1911	   services and must be compliant to the SSML specification. Element
1912	   content MAY be plain text, contain the SSML <speak> element, or the
1913	   uri attribute should identify the location of text to be rendered.

1915	      Attributes:

1917	         uri: Identifies the location of the text to be rendered. The
1918	         file and http schemes are supported.

1920	         iterate: specifies the number of times the text to speech block
1921	         is to be rendered. Defaults to once '1'.

1923	         xml:lang: specifies the language to use when it is not
1924	         explicitly specified as an attribute for <speak>.

1926	14. Fax Module

1928	   The fax module defines primitives which allow a media server to
1929	   provide facsimile services.

1931	14.1 <faxdetect>

1933	   Fax tone detection is used to detect the presence of the T.30 CNG
1934	   tone in a media stream. Child elements of <faxtone> are executed when
1935	   the CNG tone is detected.

1937	      Attributes:

1939	         none

1941	14.2 <faxsend>

1943	   The <faxsend> primitive provides the functionality of a calling fax
1944	   terminal. This typically means sending a set of pages. However, it
1945	   can also mean requesting the called terminal to send pages instead
1946	   of, or in addition to, sending pages. The fax images to send are
1947	   defined by the <sendobj> elements, described below.

1949	   Requesting the called terminal to send pages happens when the
1950	   <rxpoll> element is included as part of <faxsend>. This element may
1951	   be included in addition to, or instead of, the <sendobj> element. One
1952	   <sendobj> (at a minimum) or <rxpoll> element must be present. When
1953	   both are present, a media server will first send pages and will then
1954	   poll the other terminal, requesting pages.

1956	   Because fax is a distinct media type, the <faxsend> primitive is not
1957	   expected to interact with other primitives. Rather, it will interact
1958	   using fax protocols with a remote fax terminal (or gateway) and will
1959	   send requested status events to its invoking environment. During fax
1960	   operation, shadow variables are used to record the progress and
1961	   parameters of the varying stages of fax operation.

1963	   Status events are requested by including one or more status request
1964	   elements. These elements correspond to different stages or events in
1965	   fax operation and cause pre-defined events to be sent to the invoking
1966	   environment when they occur. Since the only recipient of these events
1967	   is expected to be a fax application server, requests are simplified
1968	   by associating a pre-defined namelist of shadow variables with each
1969	   event. This decision may be revisited to allowed tailored namelists
1970	   based on further implementation experience. Status requests apply
1971	   both to sending and polling operation.

1973	      Attributes:

1975	         lclid: the identifier that a media server uses to identify
1976	         itself.

1978	         minspeed: the minimum acceptable speed to negotiate for the
1979	         operation.

1981	         maxspeed: the maximum speed to negotiate for the operation.
1982	         This attribute is primarily for testing purposes.

1984	         ecm: specifies whether Error Correction Mode (ECM) is allowed
1985	         to be used if supported by the remote terminal. Defaults to
1986	         "true".

1988	      Events:

1990	         terminate: terminates the fax send operation.

1992	      Shadow Variables:

1994	         fax.rmtid: the identifier of the remote fax terminal.

1996	         fax.rate: the negotiated speed for the operation.

1998	         fax.resolution: identifies the resolution of the image. Both
1999	         metric and inch based resolutions are defined. Metric based
2000	         resolutions are: 75x75, 150x150, 204x98, 204x196, 204x391,
2001	         408x391. Inch based resolutions are: 200x200, 300x300, 400x400,
2002	         600x600.

2004	         fax.pagesize: identifies the negotiated page size. Metric sizes
2005	         are "A3", "A4", "A5", "A6", and "B4". Inch based page sizes are
2006	         "Letter" and "Legal".

2008	         fax.encoding: identifies the image encoding utilized. Valid
2009	         values are "MH", "R", "MMR", and "JPEG".

2011	         fax.ecm: identifies whether ECM operation was used.

2013	         fax.pagebadlines: the number of bad lines in a page.

2015	         fax.objbadlines: the number of bad lines in an object.

2017	         fax.opbadlines: the number of bad lines in an operation.

2019	         fax.objuri: the objuri of the current object.

2021	         fax.resendcount: the number of pages resent due to errors.

2023	         fax.totalpages: the number of pages processed or stored.

2025	         fax.totalobjects: the count of the objects used in the
2026	         operation.

2028	         fax.duration: the duration of the operation expressed as a
2029	         duration in seconds and milliseconds (e.g. "23s250ms").

2031	         fax.result: contains the reason which caused the fax operation
2032	         to complete. When the operation completes successfully, the
2033	         value will be assigned "fax.success". Other values include:
2034	         "fax.partial", "fax.nofax", "fax.remotedisconnect",
2035	         "fax.uri.access.error", and "fax.invalid.startpage".

2037	14.2.1 Child Elements

2039	14.2.1.1 <sendobj>

2041	   <sendobj> is used to define a fax transmission. There MAY be multiple
2042	   instances of the element which will be transmitted in order.

2044	      Attributes:

2046	         objuri: a URI that points to the fax image that will be
2047	         transmitted. Mandatory.

2049	         startpage: the first page of a multi-page objuri to send.

2051	         pagecount: page count.

2053	14.2.1.2 <hdrfooter>

2055	   <hdrfooter> describes the header/footer that a media server MAY put
2056	   on pages. The header or footer may be defined as the content of the
2057	   <format> child element. The <format> element is only allowed if the
2058	   type attribute has a value of "header" or "footer".

2060	      Attributes:

2062	         type: specifies whether a header or a footer should be put on
2063	         pages and identifies the source of the header or footer. The
2064	         following enumerated values may be used:

2066	            "header" indicates that the media server should put a header
2067	                     on pages using the contents of the <format>
2068	                     element.

2070	            "nohdr"  indicates that there should be no header or footer.

2072	            "footer" indicates that the media server should put a footer
2073	                     on pages using the contents of the <format>
2074	                     element.

2076	         style: defines the style of insertion onto a fax page that a
2077	         media server should use for the header or footer. Valid styles
2078	         are "append", "overlay", or "replace".

2080	   <format> is a child of the <hdrfooter> element that defines the style
2081	   format to be used for the header or footer. It uses a "C" language
2082	   style format statement (as shown below) to define the contents and
2083	   layout of the header or footer.

2085	     code    length   name              format

2087	      %a       3     day of week       3-character abbreviation
2088	      %d       2     date              01-31
2089	      %m       2     month             01-12
2090	      %y       2     year              00-99
2091	      %Y       4     year              0000-9999
2092	      %I       2     12 hour           01-12
2093	      %H       2     24 hour           00-23
2094	      %M       2     minute            00-59
2095	      %S       2     seconds           00-59
2096	      %p       2     AM/PM             AM or PM
2097	      %P       2     page number       01-99
2098	      %T       2     total pages       01-99
2099	      %l       20    local ID (sender) 0-9, + or spaces
2100	      %r       20    remote ID (rcvr)  0-9, + or spaces
2101	      %%       1     percent           display % in header/ftr

2103	14.2.1.3 <rxpoll>

2105	   <rxpoll> provides the information necessary for a receive polling
2106	   operation to occur. The object(s) to be received are defined by one
2107	   or more <rcvobj> elements. The <rcvobj> is defined further under the
2108	   child elements of <faxrcv>. The <rxpoll> element MAY also include a
2109	   description of the header/footer that a media server SHOULD put on
2110	   received pages. The <hdrfooter> element and it's usage is described
2111	   above.

2113	      Attributes:

2115	         rmtid: specifies the identifier of the remote fax terminal that
2116	         to be associated with a polling operation. A media server MUST
2117	         NOT execute a polling operation unless the value of rmtid
2118	         matches that of the connected remote machine.

2120	14.2.1.4 <faxstart>

2122	   Requests that an event be sent when fax operation has begun. When
2123	   triggered, the following will be executed:

2125	   <send target="source" event="fax.start"/>

2127	14.2.1.5 <faxnegotiate>

2129	   Requests that an event be sent when a negotiation has been completed.
2130	   Multiple events MAY be sent each time a DCS frame is sent or
2131	   received. When triggered, the following will be executed:

2133	   <send target="source" event="fax.negotiate"
2134	      namelist="fax.rmtid
2135	         fax.rate
2136	         fax.resolution
2137	         fax.pagesize
2138	         fax.encoding
2139	         fax.ecm"/>

2141	14.2.1.6 <faxpagedone>

2143	   Requests that an event be sent when a page has been sent or received.
2144	   When triggered, the following will be executed:

2146	   <send target="source" event="fax.pagedone"
2147	         namelist="fax.resolution
2148	         fax.pagesize
2149	         fax.encoding
2150	         fax.pagebadlines
2151	         fax.resendcount"/>

2153	14.2.1.7 <faxobjectdone>

2155	   Requests that an event be sent when an objuri has been completed.
2156	   When triggered, the following will be executed:

2158	   <send target="source" event="fax.objectdone"
2159	         namelist="fax.objuri
2160	         fax.objbadlines
2161	         fax.resendcount
2162	         fax.totalpages
2163	         fax.result"/>

2165	14.2.1.8 <faxopcomplete>

2167	   Requests that an event be sent when an operation has been completed.
2168	   When triggered, the following will be executed:

2170	   <send target="source" event="fax.opcomplete"
2171	         namelist="fax.totalpages
2172	         fax.opbadlines
2173	         fax.resendcount
2174	         fax.totalobjects
2175	         fax.duration
2176	         fax.result"/>

2178	14.2.1.9 <faxpollstarted>

2180	   Requests that an event be sent when a polling operation has started.
2181	   When triggered, the following will be executed:

2183	   <send target="source" event="fax.opcomplete"
2184	         namelist="fax.rmtid
2185	         fax.rate
2186	         fax.resolution
2187	         fax.pagesize
2188	         fax.encoding
2189	         fax.ecm"/>

2191	14.3 <faxrcv>

2193	   The <faxrcv> primitive provides the functionality of a called fax
2194	   terminal. Typically this type of operation is to receive pages.
2195	   However, it can include sending pages instead of, or in addition to,
2196	   receiving them. The fax objects to receive are defined by the
2197	   <rcvobj> elements, described below.

2199	   A media server SHOULD send pages as a polled terminal when the
2200	   <txpoll> element is included as part of <faxrcv>. This element may be
2201	   included in addition to, or instead of, the <rcvobj> element. One
2202	   <rcvobj> or <txpoll> element must be present. When both are present,
2203	   a media server SHOULD first receive pages and will then allow the
2204	   other terminal to poll the media server, requesting pages.

2206	   Because fax is a distinct media type, the <faxrcv> primitive is not
2207	   expected to interact with other primitives. Rather, it will interact
2208	   using fax protocols with a remote fax terminal and will send
2209	   requested status events to its invoking environment. During fax
2210	   operation, shadow variables are used to record the progress and
2211	   parameters of the varying stages of fax operation.

2213	   Status events are requested by including one or more status request
2214	   elements. These elements correspond to different stages or events in
2215	   fax operation and cause pre-defined events to be sent to the invoking
2216	   environment when they occur. Since the only recipient of these events
2217	   is expected to be a fax application server, requests are simplified
2218	   by associating a pre-defined namelist of shadow variables with each
2219	   event. This decision may be revisited to allowed tailored namelists
2220	   based on further implementation experience. Status requests apply
2221	   both to receiving and polling operation.

2223	      Attributes:

2225	         lclid: the identifier that a media server uses to identify
2226	         itself.

2228	         ecm: specifies whether ECM mode is allowed to be used if
2229	         supported by the remote terminal. Defaults to "true".

2231	      Events:

2233	         terminate: terminates the fax reception operation.

2235	      Shadow Variables:

2237	         <faxrcv> supports the same set of shadow variables as <faxsend>

2239	14.3.1 Child Elements

2241	   In addition to the elements defined below, <faxrcv> MAY also have the
2242	   following child elements which were defined under <faxsend>:

2244	      o  <hdrfooter>
2245	      o  <faxstart>
2246	      o  <faxnegotiate>
2247	      o  <faxpagedone>
2248	      o  <faxobjectdone>
2249	      o  <faxopcomplete>
2250	      o  <faxpollstarted>

2252	   Their meaning and usage is the same as previously defined.

2254	14.3.1.1 <rcvobj>

2256	   <rcvobj> is used to define fax objects that a media server will
2257	   receive. There may be multiple instances of the element which will be
2258	   used in order.

2260	      Attributes:

2262	         objuri: a URI that points to the location that a received image
2263	         is to be stored. Mandatory.

2265	         maxpages: the maximum number of pages that will be stored in
2266	         objuri.

2268	14.3.1.2 <txpoll>

2270	   <txpoll> provides the information for a polling operation to occur as
2271	   part of a fax receive operation. Multiple object(s) to be send may be
2272	   supplied by one or more <sendobj> elements. In the event of multiple
2273	   occurrences, a media server MUST select the <sendobj> element whose
2274	   rmtid attribute matches that of the remote terminal.

2276	   The <sendobj> element was defined previously as a child element of
2277	   <faxsend>. For <txpoll> is extended with an rmtid attribute that
2278	   specifies the identifier of the remote fax terminal and is used to
2279	   select the specific <sendobj> to send.

2281	   A media server SHOULD put a header/footer on transmitted pages based
2282	   on any <hdrfooter> element included as part of <txpoll>.

2284	      Attributes:

2286	         none

2288	15. Failure Codes

2290	   Failure codes are used to indicate reasons for failures. The
2291	   appropriate code and description must be passed to the invoking
2292	   environment on failure.

2294	         Request Error (4xx)

2296	   400  Bad Request
2297	   401  Unknown Element
2298	   402  Unsupported Element
2299	   403  Missing mandatory element content
2300	   404  Forbidden element content
2301	   405  Invalid element content
2302	   406  Unknown attribute
2303	   407  Attribute not supported
2304	   408  Missing mandatory attribute
2305	   409  Forbidden attribute is present
2306	   410  Invalid attribute value

2308	         Server Error (5xx)

2310	   500  Internal media server error
2311	   510  Not in service
2312	   511  Service Unavailable
2313	   520  No resource to fulfill request
2314	   521  Internal limit exceeded

2316	16. Examples

2318	16.1 Announcement

2320	   The following is a simple announcement scenario. Two recorded audio
2321	   files are played in sequence followed by generated speech followed by
2322	   a variable. The results are reported once media generation completes.

2324	   <?xml version="1.0" encoding="UTF-8"?>
2325	   <moml version="1.0" id="12345">
2326	      <play>
2327	         <audio uri="file://clip1.wav"/>
2328	         <audio uri="http://host1/clip2.wav"/>
2329	         <tts uri="http://host2/text.ssml"/>
2330	         <var type="date" subtype="mdy" value="20030601"/>
2331	      </play>
2332	      <send target="source" event="done" namelist="play.amt play.end"/>
2333	   </moml>

2335	16.2 Voice Mail Retrieval

2337	   Below is an example which shows a simple voice mail retrieval
2338	   operation consisting of playing a message and allowing the user to
2339	   pause and resume play using '5' to toggle the state. The operation
2340	   would terminate when the play completed or the user entered '#'.
2341	   During the play, the user can advance forward and backward through
2342	   the message as well as rewinding to the beginning.

2344	   <?xml version="1.0" encoding="UTF-8"?>
2345	   <moml version="1.0" id="12345">
2346	      <group topology="parallel">
2347	         <play>
2348	            <audio uri="file://message.wav"/>
2349	            <playexit>
2350	               <send target="group" event="terminate"/>
2351	            </playexit>
2352	         </play>
2353	         <dtmf iterate="forever">
2354	            <pattern digits="5">
2355	               <send target="play" event="toggle-state"/>
2356	            </pattern>
2357	            <pattern digits="6">
2358	               <send target="play" event="forward"/>
2359	            </pattern>
2360	            <pattern digits="7">
2361	               <send target="play" event="backward"/>
2362	            </pattern>
2363	            <pattern digits="8">
2364	               <send target="play" event="restart"/>
2365	            </pattern>
2366	            <pattern digits="#">
2367	               <send target="play" event="terminate"/>
2368	            </pattern>
2369	         </dtmf>
2370	      </group>
2371	   </moml>

2373	16.3 Play and Record

2375	   A more complex example is a play and record operation. This sources
2376	   and sinks media and uses voice activity DTMF detection and
2377	   recognition to influence behavior. Any DTMF input or voice activity
2378	   will barge the play and cause the record to begin. However, if the
2379	   prompt was barged with a DTMF digit of '#', the record terminates
2380	   without starting. When the play terminates, it send a starttimer
2381	   event to the VAD to allow it to recognize an initial silence
2382	   condition. The recording will be terminated (without starting) when
2383	   the VAD detects an initial 3 seconds of silence.

2385	   Once resumed (based upon voice detection) the recording may be
2386	   terminated under several conditions. It will terminate after 5
2387	   seconds of silence or after 60 seconds elapses. It will also
2388	   terminate if a '#' key is recognized. Every aspect of this behavior
2389	   can be modified by changing what is recognized and the events which
2390	   are sent.

2392	   <?xml version="1.0" encoding="UTF-8"?>
2393	   <moml  version="1.0" id="12345">
2394	      <group topology="parallel">
2395	         <play>
2396	            <audio uri="file://prompt.wav"/>
2397	            <playexit>
2398	               <send target="vad" event="starttimer"/>
2399	            </playexit>
2400	         </play>
2401	         <dtmf>
2402	            <pattern digits="#">
2403	               <send target="record" event="terminate.termkey"/>
2404	            </pattern>
2405	            <detect>
2406	               <send target="play" event="terminate"/>
2407	            </detect>
2408	         </dtmf>
2409	         <vad>
2410	            <voice len="10ms">
2411	               <send target="play" event="terminate"/>
2412	               <send target="record" event="resume"/>
2413	            </voice>
2414	            <silence len="3s">
2415	               <send target="record" event="nospeech"/>
2416	            </silence>
2417	            <tsilence len="5s">
2418	               <send target="record" event="terminate.finalsilence"/>
2419	            </tsilence>
2420	         </vad>
2421	         <record initial="suspend" maxtime="60s"
2422	                 dest="file://record.wav" format="g729">
2423	            <recordexit>
2424	               <send target="group" event="terminate"/>
2425	            </recordexit>
2426	         </record>
2427	         <groupexit>
2428	            <send target="source" event="done"
2429	                  namelist="record.len record.end"/>
2430	         </groupexit>
2431	      </group>
2432	   </moml>

2434	   The following implements the same functionality, as described above,
2435	   in an alternate mechanism, using the <record> composite mechanism for
2436	   the play and record operation.

2438	   <?xml version="1.0" encoding="UTF-8"?>
2439	   <moml  version="1.0" id="12345">

2441	      <record prespeech=�3s� postspeech=�5s� maxtime="60s" termkey=�#�
2442	                 dest="file://record.wav" format="g729">
2443	         <play barge=�true�>
2444	            <audio uri="file://prompt.wav"/>
2445	         </play>
2446	         <recordexit>
2447	            <send target="source" event="done"
2448	                  namelist="record.len record.end"/>
2449	         </recordexit>
2450	      </record>

2452	   </moml>

2454	16.4 Speech Recognition

2456	   The following simple example requests that a user speak the name of a
2457	   city and returns the result.

2459	   <?xml version="1.0" encoding="UTF-8"?>
2460	   <moml version="1.0" id="12345">
2461	      <group topology="parallel">
2462	         <play>
2463	            <audio uri="file://prompt.wav"/>
2464	         </play>
2465	         <speech>
2466	            <grammar version="1.0">
2467	               <rule id="city" scope="public">
2468	                  <item>
2469	                     <one-of>
2470	                        <item>vancouver</item>
2471	                        <item>new york</item>
2472	                        <item>london</item>
2473	                     </one-of>
2474	                  </item>
2475	               </rule>
2476	               <match>
2477	                  <send target="group" event="terminate"/>
2478	               </match>
2479	            </grammar>
2480	            <noinput>
2481	               <send target="group" event="terminate"/>
2482	            </noinput>
2483	            <nomatch>
2484	               <send target="group" event="terminate"/>
2485	            </nomatch>
2486	         </speech>
2487	         <groupexit>
2488	            <send target="source" event="done"
2489	                          namelist="speech.end speech.results"/>
2490	         </groupexit>
2491	      </group>
2492	   </moml>

2494	16.5 Play and Collect

2496	   This example prompts a user to enter 4 DTMF digits terminated by the
2497	   '#' key. The prompt will be barged and the user has 10 seconds to
2498	   begin entering input or no input will be indicated.

2500	   <?xml version="1.0" encoding="UTF-8"?>
2501	   <moml version="1.0" id="12345">
2502	      <group topology="parallel">
2503	         <play>
2504	            <audio uri="file://prompt.wav"/>
2505	            <playexit>
2506	               <send target="dtmf" event="starttimer"/>
2507	            </playexit>

2509	         </play>
2510	         <dtmf fdt="10s" idt="16s">
2511	            <pattern digits="xxxx#">
2512	               <send target="group" event="terminate"/>
2513	            </pattern>
2514	            <detect>
2515	               <send target="play" event="terminate"/>
2516	            </detect>
2517	            <noinput>
2518	               <send target="group" event="terminate"/>
2519	            </noinput>
2520	            <nomatch>
2521	               <send target="group" event="terminate"/>
2522	            </nomatch>
2523	         </dtmf>
2524	         <groupexit>
2525	            <send target="source" event="done"
2526	                  namelist="dtmf.digits dtmf.end"/>
2527	         </groupexit>
2528	      </group>
2529	   </moml>

2531	   The following implements the same functionality, as described above,
2532	   in an alternate mechanism, using the <collect> composite mechanism
2533	   for the play and collect operation.

2535	   <?xml version="1.0" encoding="UTF-8"?>
2536	   <moml version="1.0" id="12345">

2538	      <collect fdt="10s" idt="16s">
2539	         <play barge=�true�>
2540	            <audio uri="file://prompt.wav"/>
2541	         </play>
2542	         <pattern digits="xxxx#">
2543	            <send target="source" event="done"
2544	                  namelist="dtmf.digits dtmf.end"/>
2545	         </pattern>
2546	         <noinput>
2547	            <send target="source" event="done"
2548	                  namelist="dtmf.end"/>
2549	         </noinput>
2550	         <nomatch>
2551	            <send target="source" event="done"
2552	                  namelist="dtmf.end"/>
2553	         </nomatch>
2554	      </dtmf>

2556	   </moml>

2558	16.6 User Controlled Gain

2560	   This shows an example of nesting groups to create an arbitrary full
2561	   duplex media control. DTMF is detected on media flowing in one
2562	   direction and used to adjust the gain applied to media flowing in the
2563	   opposite direction. Additionally, the stream which is used to detect
2564	   DTMF has DTMF removed and its gain automatically adjusted before
2565	   leaving the group. This widget could be used between a conference
2566	   participant and a conference mixer.

2568	   <?xml version="1.0" encoding="UTF-8"?>
2569	   <moml  version="1.0" id="12345">
2570	      <group topology="fullduplex">
2571	         <group topology="parallel">
2572	            <dtmf>
2573	               <pattern digits="1" iterate="forever">
2574	                  <send target="gain" event="louder"/>
2575	               </pattern>
2576	               <pattern digits="2" iterate="forever">
2577	                  <send target="gain" event="softer"/>
2578	               </pattern>
2579	            </dtmf>
2580	            <group topology="serial">
2581	               <clamp/>
2582	               <agc tgtlvl="0"/>
2583	            </group>
2584	         </group>
2585	         <gain amt="0" incr="5"/>
2586	      </group>
2587	   </moml>

2589	17. Change Summary

2591	   The following are the changes between the -06 version of the draft
2592	   and the -05 version:

2594	      o  added support for video play and video record

2596	      o  added ability for record operation to make separate audio and
2597	         video recordings, as well as combined audio and video recording

2599	      o  added functionality to allow MOML scripts using play, to
2600	         optionally specify and override the audio and video format
2601	         attributes from the media file

2603	      o  added functionality to allow MOML scripts using record, to
2604	         optionally specify audio and video format attributes to be used
2605	         when creating the recorded file

2607	      o  added new Package Scheme section describing the ability and
2608	         process for defining new MOML packages

2610	      o  added composite functions (play/collect and play/record) using
2611	         <collect> and <record> elements

2613	      o  added <play> as valid child element for <dtmf> or <collect>

2615	      o  added <play> as valid child element for <record>

2617	      o  added new element named <collect>, which is identical to <dtmf>

2619	      o  added notes to Overview section to define and describe
2620	         differences between the Media Primitives and Composites model
2621	         and the Media Groups model.

2623	      o  added sample MOML script for play and collection operation
2624	         using the Media Primitives and Composites model. (See section
2625	         13.5)

2627	      o  added sample MOML script for play and record operation using
2628	         the Media Primitives and Composites model. (See section 13.5)

2630	      o  added RFC 2119 conformance section and related updates

2632	   The following are the changes between the -05 version of the draft
2633	   and the -04 version:

2635	      o  no changes.

2637	   The following are the primary changes between -04 version of the
2638	   draft and the -01 version:

2640	      o  specified the use of MOML directly in SIP (see section 4)

2642	      o  specified the <event> element for notifying events in SIP INFO
2643	         messages

2645	      o  added <gate> transform primitive which can gate the flow of
2646	         media regardless of its format

2648	      o  extended sending events to "source" to allow event names
2649	         specific to the source naming conventions to be included. This
2650	         can allow such features as the source relaying an event to
2651	         another MOML object it has created.

2653	      o  modularized the language and specified rules to extend it in
2654	         order to allow it to be independently tailored to different
2655	         environments and  platforms (see section 5)

2657	   Between the -01 version and the -00 version the changes were:

2659	      o  added primitives to detect, send, and receive fax

2661	      o  added "xml:lang" attribute to <play> <audio> <var> and <tts>.
2662	         children of <play> inherit from play unless overridden.

2664	      o  allow the uri in <audio> to refer to a logical clip (physical
2665	         determined by language) and sequence as well as a physical clip
2666	         (for local uri references).

2668	      o  restructured the schema as a partial step towards
2669	         modularization and the ability to subset and extend the
2670	         language in a standards compliant manner.

2672	      o  made <dtmfgen> to be the same level as <play> and not a child
2673	         of <play>

2675	      o  changed "pipe" and "star" to be "serial" and "parallel"

2677	      o  made all termination events consistently use the root
2678	         "terminate". previously some primitives used the root  "stop"

2680	      o  changed "max" attribute to "iterate" for the <dtmf>, <pattern>,
2681	         <noinput>, and <nomatch>, and <speech> elements.

2683	      o  change "iterations" attribute of <play> and <audio> to
2684	         "iterate".

2686	      o  removed explicit "lhs" / "rhs" labeling of full duplex objects

2688	18. XML Schema

2690	   The base MOML schema defines the <moml> element and includes all of
2691	   the modules which together define the full language. The <moml>
2692	   element defines that a given document may be either a request to a
2693	   media server or an event notified by a media server.

2695	   <?xml version="1.0" encoding="UTF-8"?>
2696	   <xs:schema elementFormDefault="unqualified"
2697	      attributeFormDefault="unqualified"
2698	      xmlns:xs="http://www.w3.org/2001/XMLSchema">
2699	     <xs:include schemaLocation="moml-group-module.xsd"/>
2700	     <xs:include schemaLocation="moml-basic-primitives-module.xsd"/>
2701	     <xs:include schemaLocation="moml-transform-primitives-module.xsd"/>
2702	     <xs:include schemaLocation="moml-speech-module.xsd"/>
2703	     <xs:element name="moml">
2704	      <xs:complexType>
2705	         <xs:choice>
2706	            <xs:group ref="momlRequest"/>
2707	            <xs:element ref="event"/>
2708	         </xs:choice>
2709	         <xs:attribute name="version" type="xs:string"
2710	             use="required" fixed="1.0"/>
2711	         <xs:attribute name="id" type="momlID.datatype" use="required"/>
2712	      </xs:complexType>
2713	   </xs:element>
2714	   </xs:schema>

2716	   Following is the schema which defines the datatypes module (moml-
2717	   datatypes.xsd). It is included by each of the other MOML modules.

2719	   <?xml version="1.0" encoding="UTF-8"?>
2720	   <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
2721	              elementFormDefault="qualified"
2722	              attributeFormDefault="unqualified">
2723	    <xs:simpleType name="momlID.datatype">
2724	     <xs:restriction base="xs:string">
2725	      <xs:pattern value="[a-zA-Z0-9][a-zA-Z0-9._\-]*"/>
2726	     </xs:restriction>
2727	    </xs:simpleType>
2728	    <xs:simpleType name="momlEvent.datatype">
2729	     <xs:restriction base="xs:string">
2730	      <xs:pattern value="[a-zA-Z0-9][a-zA-Z0-9._\-]*"/>
2731	     </xs:restriction>
2732	    </xs:simpleType>
2733	    <xs:simpleType name="momlNamelist.datatype">
2734	     <xs:restriction base="xs:string"/>
2735	    </xs:simpleType>
2736	    <xs:simpleType name="dtmfDigits.datatype">
2737	     <xs:restriction base="xs:string">
2738	      <xs:pattern value="[0-9#*]+"/>
2739	     </xs:restriction>
2740	    </xs:simpleType>
2741	    <xs:simpleType name="iterate.datatype">
2742	     <xs:union memberTypes="xs:positiveInteger">
2743	      <xs:simpleType>
2744	       <xs:restriction base="xs:negativeInteger">
2745	        <xs:minInclusive value="-1"/>
2746	       </xs:restriction>
2747	      </xs:simpleType>
2748	      <xs:simpleType>
2749	       <xs:restriction base="xs:string">
2750	        <xs:enumeration value="forever"/>
2751	       </xs:restriction>
2752	      </xs:simpleType>
2753	     </xs:union>
2754	    </xs:simpleType>
2755	    <xs:simpleType name="momlTarget.datatype">
2756	     <xs:restriction base="xs:string">
2757	      <xs:pattern value="[a-zA-Z0-9][a-zA-Z0-9._\-]*"/>
2758	     </xs:restriction>
2759	    </xs:simpleType>
2760	    <xs:simpleType name="boolean.datatype">
2761	     <xs:restriction base="xs:string">
2762	      <xs:enumeration value="true"/>
2763	      <xs:enumeration value="false"/>
2764	     </xs:restriction>
2765	    </xs:simpleType>
2766	    <xs:simpleType name="duration.datatype">
2767	     <xs:restriction base="xs:string">
2768	      <xs:pattern value="(\+|\-)?([0-9]*\.)?[0-9]+(ms|s)"/>
2769	     </xs:restriction>
2770	    </xs:simpleType>
2771	    <xs:simpleType name="posDuration.datatype">
2772	     <xs:restriction base="xs:string">
2773	      <xs:pattern value="(\+)?([0-9]*\.)?[0-9]+(ms|s)"/>
2774	     </xs:restriction>
2775	    </xs:simpleType>
2776	   </xs:schema>

2778	   Following is the schema which defines the core module (moml-core-
2779	   module.xsd). It is included by each of the other MOML modules.

2781	   <?xml version="1.0" encoding="UTF-8"?>
2782	   <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
2783	      elementFormDefault="unqualified"
2784	      attributeFormDefault="unqualified">
2785	    <xs:include schemaLocation="moml-datatypes.xsd"/>
2786	    <xs:group name="momlRequest">
2787	     <xs:choice maxOccurs="unbounded">
2788	      <xs:group ref="executeType"/>
2789	      <xs:element ref="send" maxOccurs="unbounded"/>
2790	     </xs:choice>
2791	    </xs:group>
2792	    <xs:element name="primitive" type="primitiveType" abstract="true"/>
2793	    <xs:complexType name="primitiveType">
2794	     <xs:attribute name="id" type="momlID.datatype"/>
2795	    </xs:complexType>
2796	    <xs:element name="control" abstract="true"/>
2797	    <xs:group name="executeType">
2798	     <xs:choice maxOccurs="unbounded">
2799	      <xs:element ref="primitive"/>
2800	      <xs:element ref="control"/>
2801	     </xs:choice>
2802	    </xs:group>
2803	    <xs:group name="sendType">
2804	     <xs:choice>
2805	      <xs:choice>
2806	       <xs:element name="exit" type="exitType"/>
2807	       <xs:element name="disconnect" type="exitType"/>
2808	      </xs:choice>
2809	      <xs:sequence>
2810	       <xs:element ref="send" maxOccurs="unbounded"/>
2811	       <xs:choice minOccurs="0">
2812	        <xs:element name="exit" type="exitType"/>
2813	        <xs:element name="disconnect" type="exitType"/>
2814	       </xs:choice>
2815	      </xs:sequence>
2816	     </xs:choice>
2817	    </xs:group>
2818	    <xs:element name="send">
2819	     <xs:complexType>
2820	      <xs:attribute name="event" type="momlEvent.datatype"
2821	          use="required"/>
2822	      <xs:attribute name="target" type="momlTarget.datatype"
2823	          use="required"/>
2824	      <xs:attribute name="namelist" type="momlNamelist.datatype"/>
2825	     </xs:complexType>
2826	    </xs:element>
2827	    <xs:complexType name="exitType">
2828	     <xs:attribute name="namelist" type="momlNamelist.datatype"/>
2829	    </xs:complexType>
2830	    <xs:element name="event">
2831	     <xs:complexType>
2832	      <xs:sequence maxOccurs="unbounded">
2833	       <xs:element name="name" type="xs:string"/>
2834	       <xs:element name="value" type="xs:string"/>
2835	      </xs:sequence>
2836	      <xs:attribute name="name" type="xs:string" use="required"/>
2837	      <xs:attribute name="id" type="xs:string" use="required"/>
2838	     </xs:complexType>
2839	    </xs:element>
2840	   </xs:schema>

2842	   The schema for the group module (moml-group-module.xsd) is:

2844	   <?xml version="1.0" encoding="UTF-8"?>
2845	   <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
2846	      elementFormDefault="unqualified"
2847	      attributeFormDefault="unqualified">
2848	    <xs:include schemaLocation="moml-datatypes.xsd"/>
2849	    <xs:include schemaLocation="moml-core-module.xsd"/>
2850	    <xs:element name="group" substitutionGroup="control">
2851	     <xs:complexType>
2852	      <xs:sequence>
2853	       <xs:group ref="executeType"/>
2854	       <xs:element name="groupexit" minOccurs="0">
2855	        <xs:complexType>
2856	         <xs:group ref="sendType"/>
2857	        </xs:complexType>
2858	       </xs:element>
2859	      </xs:sequence>
2860	      <xs:attribute name="id" type="momlID.datatype"/>
2861	      <xs:attribute name="topology" use="required">
2862	       <xs:simpleType>
2863	        <xs:restriction base="xs:string">
2864	         <xs:enumeration value="serial"/>
2865	         <xs:enumeration value="parallel"/>
2866	         <xs:enumeration value="fullduplex"/>
2867	        </xs:restriction>
2868	       </xs:simpleType>
2869	      </xs:attribute>
2870	     </xs:complexType>
2871	    </xs:element>
2872	   </xs:schema>

2874	   The schema for the basic primitives module (moml-basic-primitives-
2875	   module.xsd) is:

2877	   <?xml version="1.0" encoding="UTF-8"?>
2878	   <xs:schema elementFormDefault="unqualified"
2879	      attributeFormDefault="unqualified"
2880	      xmlns:xs="http://www.w3.org/2001/XMLSchema">
2881	    <xs:include schemaLocation="moml-datatypes.xsd"/>
2882	    <xs:include schemaLocation="moml-core-module.xsd"/>
2883	    <xs:import namespace="http://www.w3.org/XML/1998/namespace"
2884	       schemaLocation="http://www.w3.org/2001/xml.xsd"/>
2885	    <xs:element name="play" substitutionGroup="primitive">
2886	     <xs:complexType>
2887	      <xs:complexContent>
2888	       <xs:extension base="primitiveType">
2889	        <xs:sequence>
2890	         <xs:choice maxOccurs="unbounded">
2891	          <xs:element name="audio" minOccurs="0" maxOccurs="unbounded">
2892	           <xs:complexType>
2893	            <xs:attribute name="uri" type="xs:anyURI" use="required"/>
2894	            <xs:attribute name="iterate" type="iterate.datatype"
2895	                          default="1"/>
2896	            <xs:attribute name="format" type="xs:string"
2897	                          use="optional"/>
2898	            <xs:attribute name="audiosamplerate"
2899	                          type="xs:positiveInteger" use="optional"/>
2900	            <xs:attribute name="audiosamplesize"
2901	                          type="xs:positiveInteger" use="optional"/>
2902	            <xs:attribute ref="xml:lang"/>
2903	           </xs:complexType>
2904	          </xs:element>
2905	          <xs:element name="video" minOccurs="0" maxOccurs="unbounded">
2906	           <xs:complexType>
2907	            <xs:attribute name="uri" type="xs:anyURI" use="required"/>
2908	            <xs:attribute name="iterate" type="iterate.datatype"
2909	                          use="optional" default="1"/>
2910	            <xs:attribute name="format" type="xs:string"
2911	                          use="optional"/>
2912	            <xs:attribute name="audiosamplerate"
2913	                          type="xs:positiveInteger" use="optional"/>
2914	            <xs:attribute name="audiosamplesize"
2915	                          type="xs:positiveInteger" use="optional"/>
2916	            <xs:attribute name="codecconfig" type="xs:string"
2917	                          use="optional"/>
2918	            <xs:attribute name="profile" type="xs:string"
2919	                          use="optional"/>
2920	            <xs:attribute name="level" type="xs:string" use="optional"/>
2921	            <xs:attribute name="imagewidth" type="xs:positiveInteger"
2922	                          use="optional"/>
2923	            <xs:attribute name="imageheight" type="xs:positiveInteger"
2924	                          use="optional"/>
2925	            <xs:attribute name="maxbitrate" type="xs:positiveInteger"
2926	                          use="optional"/>
2927	            <xs:attribute name="framerate" type="xs:positiveInteger"
2928	                          use="optional"/>
2929	           </xs:complexType>
2930	          </xs:element>
2931	          <xs:element name="media" minOccurs="0" maxOccurs="unbounded">
2932	           <xs:complexType>
2933	            <xs:choice>
2934	             <xs:element name="audio" minOccurs="0">
2935	              <xs:complexType>
2936	               <xs:attribute name="uri" type="xs:anyURI"
2937	                             use="required"/>
2938	               <xs:attribute name="iterate" type="iterate.datatype"
2939	                             default="1"/>
2940	               <xs:attribute name="format" type="xs:string"
2941	                             use="optional"/>
2942	               <xs:attribute name="audiosamplerate"
2943	                             type="xs:positiveInteger"
2944	                             use="optional"/>
2945	               <xs:attribute name="audiosamplesize"
2946	                             type="xs:positiveInteger"
2947	                             use="optional"/>
2948	               <xs:attribute ref="xml:lang"/>
2949	              </xs:complexType>

2951	             </xs:element>
2952	             <xs:element name="video" minOccurs="0">
2953	              <xs:complexType>
2954	               <xs:attribute name="uri" type="xs:anyURI"
2955	                             use="required"/>
2956	               <xs:attribute name="iterate" type="iterate.datatype"
2957	                             use="optional" default="1"/>
2958	               <xs:attribute name="format" type="xs:string"
2959	                             use="optional"/>
2960	               <xs:attribute name="audiosamplerate"
2961	                             type="xs:positiveInteger" use="optional"/>
2962	               <xs:attribute name="audiosamplesize"
2963	                             type="xs:positiveInteger" use="optional"/>
2964	               <xs:attribute name="codecconfig" type="xs:string"
2965	                             use="optional"/>
2966	               <xs:attribute name="profile" type="xs:string"
2967	                             use="optional"/>
2968	               <xs:attribute name="level" type="xs:string"
2969	                             use="optional"/>
2970	               <xs:attribute name="imagewidth" type="xs:positiveInteger"
2971	                             use="optional"/>
2972	               <xs:attribute name="imageheight"
2973	                             type="xs:positiveInteger" use="optional"/>
2974	               <xs:attribute name="maxbitrate" type="xs:positiveInteger"
2975	                             use="optional"/>
2976	               <xs:attribute name="framerate" type="xs:positiveInteger"
2977	                             use="optional"/>
2978	              </xs:complexType>
2979	             </xs:element>
2980	            </xs:choice>
2981	           </xs:complexType>
2982	          </xs:element>
2983	          <xs:element ref="smedia" minOccurs="0" maxOccurs="unbounded"/>
2984	         </xs:choice>
2985	         <xs:choice minOccurs="0">
2986	          <xs:element name="playexit">
2987	           <xs:complexType>
2988	            <xs:group ref="sendType"/>
2989	           </xs:complexType>
2990	          </xs:element>
2991	         </xs:choice>
2992	        </xs:sequence>
2993	        <xs:attribute name="interval" type="posDuration.datatype"
2994	                      use="optional"/>
2995	        <xs:attribute name="iterate" type="iterate.datatype"
2996	                      use="optional" default="1"/>
2997	        <xs:attribute name="offset" type="duration.datatype"
2998	                      use="optional"/>
2999	        <xs:attribute name="initial" use="optional" default="generate">
3000	         <xs:simpleType>
3001	          <xs:restriction base="xs:string">
3002	           <xs:enumeration value="generate"/>
3003	           <xs:enumeration value="suspend"/>
3004	          </xs:restriction>
3005	         </xs:simpleType>
3006	        </xs:attribute>
3007	        <xs:attribute name="maxtime" type="posDuration.datatype"
3008	                      use="optional"/>
3009	        <xs:attribute name="skip" type="duration.datatype"
3010	                      use="optional" default="3s"/>
3011	        <xs:attribute name="barge" type="boolean.datatype"
3012	                      use="optional" default="false"/>
3013	        <xs:attribute name="cleardb" type="boolean.datatype"
3014	                      use="optional" default="false"/>
3015	        <xs:attribute ref="xml:lang"/>
3016	       </xs:extension>
3017	      </xs:complexContent>
3018	     </xs:complexType>
3019	    </xs:element>
3020	    <xs:element name="record" substitutionGroup="primitive">
3021	     <xs:complexType>
3022	      <xs:complexContent>
3023	       <xs:extension base="primitiveType">
3024	        <xs:choice minOccurs="0">
3025	         <xs:element ref="play" minOccurs="0"/>
3026	         <xs:element name="recordexit">
3027	          <xs:complexType>
3028	           <xs:group ref="sendType"/>
3029	          </xs:complexType>
3030	         </xs:element>
3031	        </xs:choice>
3032	        <xs:attribute name="append" type="boolean.datatype"
3033	                      use="optional" default="false"/>
3034	        <xs:attribute name="dest" type="xs:anyURI" use="optional"/>
3035	        <xs:attribute name="audiodest" type="xs:anyURI" use="optional"/>
3036	        <xs:attribute name="videodest" type="xs:anyURI" use="optional"/>
3037	        <xs:attribute name="format" use="required">
3038	         <xs:simpleType>
3039	          <xs:restriction base="xs:string"/>
3040	         </xs:simpleType>
3041	        </xs:attribute>
3042	        <xs:attribute name="codecconfig" use="optional">
3043	         <xs:simpleType>
3044	          <xs:restriction base="xs:string"/>
3045	         </xs:simpleType>
3046	        </xs:attribute>
3047	        <xs:attribute name="audiosamplerate" type="xs:positiveInteger"
3048	                      use="optional"/>

3050	        <xs:attribute name="audiosamplesize" type="xs:positiveInteger"
3051	                      use="optional"/>
3052	        <xs:attribute name="profile" use="optional">
3053	         <xs:simpleType>
3054	          <xs:restriction base="xs:string"/>
3055	         </xs:simpleType>
3056	        </xs:attribute>
3057	        <xs:attribute name="level" use="optional">
3058	         <xs:simpleType>
3059	          <xs:restriction base="xs:string"/>
3060	         </xs:simpleType>
3061	        </xs:attribute>
3062	        <xs:attribute name="imagewidth" type="xs:positiveInteger"
3063	                      use="optional"/>
3064	        <xs:attribute name="imageheight" type="xs:positiveInteger"
3065	                      use="optional"/>
3066	        <xs:attribute name="maxbitrate" type="xs:positiveInteger"
3067	                      use="optional"/>
3068	        <xs:attribute name="framerate" type="xs:positiveInteger"
3069	                      use="optional"/>
3070	        <xs:attribute name="maxtime" type="posDuration.datatype"
3071	                      use="required"/>
3072	        <xs:attribute name="initial" use="optional" default="create">
3073	         <xs:simpleType>
3074	          <xs:restriction base="xs:string">
3075	           <xs:enumeration value="create"/>
3076	           <xs:enumeration value="suspend"/>
3077	          </xs:restriction>
3078	         </xs:simpleType>
3079	        </xs:attribute>
3080	        <xs:attribute name="prespeech" type="posDuration.datatype"
3081	                      use="optional" default="0s"/>
3082	        <xs:attribute name="postspeech" type="posDuration.datatype"
3083	                      use="optional" default="0s"/>
3084	        <xs:attribute name="termkey" use="optional">
3085	         <xs:simpleType>
3086	          <xs:restriction base="xs:string">
3087	           <xs:pattern value="[0-9#*ABCD]"/>
3088	           <xs:enumeration value="create"/>
3089	           <xs:enumeration value="suspend"/>
3090	          </xs:restriction>
3091	         </xs:simpleType>
3092	        </xs:attribute>
3093	       </xs:extension>
3094	      </xs:complexContent>
3095	     </xs:complexType>
3096	    </xs:element>
3097	    <xs:element name="dtmf" substitutionGroup="primitive">
3098	     <xs:complexType>
3099	      <xs:complexContent>
3100	       <xs:extension base="primitiveType">
3101	        <xs:sequence>
3102	         <xs:element name="pattern" maxOccurs="unbounded">
3103	          <xs:complexType>
3104	           <xs:group ref="sendType"/>
3105	           <xs:attribute name="digits" type="xs:string" use="required"/>
3106	           <xs:attribute name="format">
3107	            <xs:simpleType>
3108	             <xs:restriction base="xs:string">
3109	              <xs:enumeration value="mgcp"/>
3110	              <xs:enumeration value="megaco"/>
3111	              <xs:enumeration value="moml+digits"/>
3112	             </xs:restriction>
3113	            </xs:simpleType>
3114	           </xs:attribute>
3115	           <xs:attribute name="iterate" type="iterate.datatype"
3116	                         default="1"/>
3117	          </xs:complexType>
3118	         </xs:element>
3119	         <xs:element name="detect" minOccurs="0">
3120	          <xs:complexType>
3121	           <xs:group ref="sendType"/>
3122	          </xs:complexType>
3123	         </xs:element>
3124	         <xs:element name="noinput" type="iterateSendType"
3125	                     minOccurs="0"/>
3126	         <xs:element name="nomatch" type="iterateSendType"
3127	                     minOccurs="0"/>
3128	         <xs:element name="dtmfexit" minOccurs="0">
3129	          <xs:complexType>
3130	           <xs:group ref="sendType"/>
3131	          </xs:complexType>
3132	         </xs:element>
3133	         <xs:element ref="play" minOccurs="0"/>
3134	        </xs:sequence>
3135	        <xs:attribute name="cleardb" type="boolean.datatype"
3136	                      default="true"/>
3137	        <xs:attribute name="fdt" type="posDuration.datatype"
3138	                      default="0s"/>
3139	        <xs:attribute name="idt" type="posDuration.datatype"
3140	                      default="4s"/>
3141	        <xs:attribute name="edt" type="posDuration.datatype"
3142	                      default="4s"/>
3143	        <xs:attribute name="starttimer" type="boolean.datatype"
3144	                      default="false"/>
3145	        <xs:attribute name="iterate" type="iterate.datatype"
3146	                      default="1"/>
3147	       </xs:extension>

3149	      </xs:complexContent>
3150	     </xs:complexType>
3151	    </xs:element>
3152	    <xs:element name="collect" substitutionGroup="primitive">
3153	     <xs:complexType>
3154	      <xs:complexContent>
3155	       <xs:extension base="primitiveType">
3156	        <xs:sequence>
3157	         <xs:element name="pattern" maxOccurs="unbounded">
3158	          <xs:complexType>
3159	           <xs:group ref="sendType"/>
3160	           <xs:attribute name="digits" type="xs:string" use="required"/>
3161	           <xs:attribute name="format">
3162	            <xs:simpleType>
3163	             <xs:restriction base="xs:string">
3164	              <xs:enumeration value="mgcp"/>
3165	              <xs:enumeration value="megaco"/>
3166	              <xs:enumeration value="moml+digits"/>
3167	             </xs:restriction>
3168	            </xs:simpleType>
3169	           </xs:attribute>
3170	           <xs:attribute name="iterate" type="iterate.datatype"
3171	                         default="1"/>
3172	          </xs:complexType>
3173	         </xs:element>
3174	         <xs:element name="detect" minOccurs="0">
3175	          <xs:complexType>
3176	           <xs:group ref="sendType"/>
3177	          </xs:complexType>
3178	         </xs:element>
3179	         <xs:element name="noinput" type="iterateSendType"
3180	                     minOccurs="0"/>
3181	         <xs:element name="nomatch" type="iterateSendType"
3182	                     minOccurs="0"/>
3183	         <xs:element name="dtmfexit" minOccurs="0">
3184	          <xs:complexType>
3185	           <xs:group ref="sendType"/>
3186	          </xs:complexType>
3187	         </xs:element>
3188	         <xs:element ref="play" minOccurs="0"/>
3189	        </xs:sequence>
3190	        <xs:attribute name="cleardb" type="boolean.datatype"
3191	                      default="true"/>
3192	        <xs:attribute name="fdt" type="posDuration.datatype"
3193	                      default="0s"/>
3194	        <xs:attribute name="idt" type="posDuration.datatype"
3195	                      default="4s"/>
3196	        <xs:attribute name="edt" type="posDuration.datatype"
3197	                      default="4s"/>

3199	        <xs:attribute name="starttimer" type="boolean.datatype"
3200	                      default="false"/>
3201	        <xs:attribute name="iterate" type="iterate.datatype"
3202	                      default="1"/>
3203	       </xs:extension>
3204	      </xs:complexContent>
3205	     </xs:complexType>
3206	    </xs:element>
3207	    <xs:element name="dtmfgen" substitutionGroup="primitive">
3208	     <xs:complexType>
3209	      <xs:complexContent>
3210	       <xs:extension base="primitiveType">
3211	        <xs:choice minOccurs="0">
3212	         <xs:element name="dtmfgenexit">
3213	          <xs:complexType>
3214	           <xs:group ref="sendType"/>
3215	          </xs:complexType>
3216	         </xs:element>
3217	        </xs:choice>
3218	        <xs:attribute name="level" use="optional" default="-6">
3219	         <xs:simpleType>
3220	          <xs:restriction base="xs:nonPositiveInteger">
3221	           <xs:maxInclusive value="0"/>
3222	           <xs:minInclusive value="-96"/>
3223	          </xs:restriction>
3224	         </xs:simpleType>
3225	        </xs:attribute>
3226	        <xs:attribute name="digits" type="dtmfDigits.datatype"
3227	                      use="required"/>
3228	        <xs:attribute name="dur" type="posDuration.datatype"
3229	                      use="optional" default="100ms"/>
3230	        <xs:attribute name="interval" type="posDuration.datatype"
3231	                      use="optional" default="100ms"/>
3232	       </xs:extension>
3233	      </xs:complexContent>
3234	     </xs:complexType>
3235	    </xs:element>
3236	    <xs:complexType name="iterateSendType">
3237	     <xs:group ref="sendType"/>
3238	     <xs:attribute name="iterate" type="iterate.datatype" default="1"/>
3239	    </xs:complexType>
3240	    <xs:element name="smedia" type="smediaType" abstract="true"/>
3241	    <xs:complexType name="smediaType">
3242	     <xs:attribute ref="xml:lang"/>
3243	     <xs:attribute name="iterate" type="iterate.datatype"/>
3244	    </xs:complexType>
3245	    <xs:element name="var" type="smediaType"
3246	                substitutionGroup="smedia"/>
3247	   </xs:schema>
3248	   The schema for the transform primitives module (moml-transform-
3249	   primitives-module.xsd) is:

3251	   <?xml version="1.0" encoding="UTF-8"?>
3252	   <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
3253	              elementFormDefault="unqualified"
3254	              attributeFormDefault="unqualified">
3255	    <xs:include schemaLocation="moml-datatypes.xsd"/>
3256	    <xs:include schemaLocation="moml-core-module.xsd"/>
3257	    <xs:import namespace="http://www.w3.org/XML/1998/namespace"
3258	               schemaLocation="http://www.w3.org/2001/xml.xsd"/>
3259	    <xs:element name="vad" substitutionGroup="primitive">
3260	     <xs:complexType>
3261	      <xs:complexContent>
3262	      <xs:extension base="primitiveType">
3263	      <xs:all>
3264	       <xs:element name="voice" type="vadPatternType" minOccurs="0"/>
3265	       <xs:element name="silence" type="vadPatternType" minOccurs="0"/>
3266	       <xs:element name="tvoice" type="vadPatternType" minOccurs="0"/>
3267	       <xs:element name="tsilence" type="vadPatternType" minOccurs="0"/>
3268	      </xs:all>
3269	      <xs:attribute name="starttimer" type="boolean.datatype"
3270	                    default="false"/>
3271	      </xs:extension>
3272	      </xs:complexContent>
3273	     </xs:complexType>
3274	    </xs:element>
3275	    <xs:element name="gain" substitutionGroup="primitive">
3276	     <xs:complexType>
3277	      <xs:complexContent>
3278	      <xs:extension base="primitiveType">
3279	      <xs:attribute name="incr" default="3">
3280	       <xs:simpleType>
3281	        <xs:restriction base="xs:positiveInteger">
3282	         <xs:maxInclusive value="96"/>
3283	        </xs:restriction>
3284	       </xs:simpleType>
3285	      </xs:attribute>
3286	      <xs:attribute name="amt" use="required">
3287	       <xs:simpleType>
3288	        <xs:restriction base="xs:integer">
3289	         <xs:minInclusive value="-96"/>
3290	         <xs:maxInclusive value="96"/>
3291	        </xs:restriction>
3292	       </xs:simpleType>
3293	      </xs:attribute>
3294	      </xs:extension>
3295	      </xs:complexContent>
3296	     </xs:complexType>
3297	    </xs:element>
3298	    <xs:element name="agc" substitutionGroup="primitive">
3299	     <xs:complexType>
3300	      <xs:complexContent>
3301	      <xs:extension base="primitiveType">
3302	      <xs:attribute name="tgtlvl" use="required">
3303	       <xs:simpleType>
3304	        <xs:restriction base="xs:nonPositiveInteger">
3305	         <xs:minInclusive value="-40"/>
3306	         <xs:maxInclusive value="0"/>
3307	        </xs:restriction>
3308	       </xs:simpleType>
3309	      </xs:attribute>
3310	      <xs:attribute name="maxgain" default="10">
3311	       <xs:simpleType>
3312	        <xs:restriction base="xs:nonNegativeInteger">
3313	         <xs:minInclusive value="0"/>
3314	         <xs:maxInclusive value="40"/>
3315	        </xs:restriction>
3316	       </xs:simpleType>
3317	      </xs:attribute>
3318	      </xs:extension>
3319	      </xs:complexContent>
3320	     </xs:complexType>
3321	    </xs:element>
3322	    <xs:element name="gate" substitutionGroup="primitive">
3323	     <xs:complexType>
3324	      <xs:complexContent>
3325	      <xs:extension base="primitiveType">
3326	      <xs:attribute name="initial" default="pass">
3327	       <xs:simpleType>
3328	        <xs:restriction base="xs:string">
3329	         <xs:enumeration value="pass"/>
3330	         <xs:enumeration value="halt"/>
3331	        </xs:restriction>
3332	       </xs:simpleType>
3333	      </xs:attribute>
3334	      </xs:extension>
3335	      </xs:complexContent>
3336	     </xs:complexType>
3337	    </xs:element>
3338	    <xs:element name="clamp" substitutionGroup="primitive">
3339	     <xs:complexType>
3340	      <xs:complexContent>
3341	       <xs:extension base="primitiveType"/>
3342	      </xs:complexContent>
3343	     </xs:complexType>

3345	    </xs:element>
3346	    <xs:element name="relay" substitutionGroup="primitive">
3347	     <xs:complexType>
3348	      <xs:complexContent>
3349	       <xs:extension base="primitiveType"/>
3350	      </xs:complexContent>
3351	     </xs:complexType>
3352	    </xs:element>
3353	    <xs:complexType name="vadPatternType">
3354	     <xs:group ref="sendType"/>
3355	     <xs:attribute name="iterate" type="iterate.datatype" default="1"/>
3356	     <xs:attribute name="len" type="posDuration.datatype"
3357	                   use="required"/>
3358	     <xs:attribute name="sen" type="posDuration.datatype"
3359	                   use="optional"/>
3360	    </xs:complexType>
3361	   </xs:schema>

3363	   Following is the schema for the speech primitives module (moml-
3364	   speech-module.xsd). Note that several URL were split across several
3365	   lines for formatting reasons.

3367	   <?xml version="1.0" encoding="UTF-8"?>
3368	   <xs:schema elementFormDefault="qualified"
3369	              attributeFormDefault="unqualified"
3370	              xmlns:xs="http://www.w3.org/2001/XMLSchema">
3371	    <xs:include schemaLocation="moml-datatypes.xsd"/>
3372	    <xs:include schemaLocation="moml-core-module.xsd"/>
3373	    <xs:include schemaLocation="moml-basic-primitives-module.xsd"/>
3374	    <xs:include schemaLocation="http://www.w3.org/TR/2002/WD-speech-
3375	                synthesis-20020405/synthesis-core.xsd"/>
3376	    <xs:include schemaLocation="http://www.w3.org/TR/speech-
3377	                grammar/grammar-core.xsd"/>
3378	    <xs:element name="speech" substitutionGroup="primitive">
3379	     <xs:complexType>
3380	      <xs:complexContent>
3381	       <xs:extension base="primitiveType">
3382	        <xs:sequence>
3383	         <xs:element name="grammar" maxOccurs="unbounded">
3384	          <xs:complexType>
3385	           <xs:complexContent>
3386	            <xs:extension base="grammar">
3387	             <xs:choice>
3388	              <xs:element name="match" type="iterateSendType"
3389	                          minOccurs="0"/>
3390	             </xs:choice>
3391	             <xs:attribute name="uri" type="xs:anyURI"/>
3392	             <xs:attribute name="iterate" type="iterate.datatype"
3393	                           default="1"/>
3394	            </xs:extension>
3395	           </xs:complexContent>
3396	          </xs:complexType>
3397	         </xs:element>
3398	         <xs:element name="noinput" type="iterateSendType"
3399	                     minOccurs="0"/>
3400	         <xs:element name="nomatch" type="iterateSendType"
3401	                     minOccurs="0"/>
3402	         <xs:element name="speechexit" minOccurs="0">
3403	          <xs:complexType>
3404	           <xs:group ref="sendType"/>
3405	          </xs:complexType>
3406	         </xs:element>
3407	        </xs:sequence>
3408	        <xs:attribute name="noint" type="posDuration.datatype"/>
3409	        <xs:attribute name="norect" type="posDuration.datatype"/>
3410	        <xs:attribute name="spcmplt" type="posDuration.datatype"/>
3411	        <xs:attribute name="confidence">
3412	         <xs:simpleType>
3413	          <xs:restriction base="xs:positiveInteger">
3414	           <xs:maxInclusive value="100"/>
3415	          </xs:restriction>
3416	         </xs:simpleType>
3417	        </xs:attribute>
3418	        <xs:attribute name="sens" type="xs:positiveInteger"/>
3419	        <xs:attribute name="starttimer" type="boolean.datatype"
3420	                      default="false"/>
3421	        <xs:attribute name="iterate" type="iterate.datatype"
3422	                      default="1"/>
3423	       </xs:extension>
3424	      </xs:complexContent>
3425	     </xs:complexType>
3426	    </xs:element>
3427	    <xs:element name="tts" type="smediaType"
3428	                substitutionGroup="smedia"/>
3429	   </xs:schema>

3431	   Following is the schema for the fax primitives module (moml-fax-
3432	   module.xsd).

3434	   <?xml version="1.0" encoding="UTF-8"?>
3435	   <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
3436	              elementFormDefault="qualified"
3437	              attributeFormDefault="unqualified">
3438	    <xs:include schemaLocation="moml-datatypes.xsd"/>
3439	    <xs:include schemaLocation="moml-core-module.xsd"/>
3440	    <xs:element name="faxdetect" substitutionGroup="primitive">
3441	     <xs:complexType>
3442	      <xs:choice>
3443	       <xs:group ref="sendType"/>
3444	      </xs:choice>
3445	     </xs:complexType>
3446	    </xs:element>
3447	    <xs:element name="faxsend" substitutionGroup="primitive">
3448	     <xs:complexType>
3449	      <xs:sequence>
3450	       <xs:element name="sendobj" type="sendobjType" minOccurs="0"
3451	                   maxOccurs="unbounded"/>
3452	       <xs:element name="hdrfooter" type="hdrfooterType" minOccurs="0"/>
3453	       <xs:element name="rxpoll" minOccurs="0">
3454	        <xs:complexType>
3455	         <xs:sequence>
3456	          <xs:element name="rcvobj" type="rcvobjType"
3457	                      maxOccurs="unbounded"/>
3458	          <xs:element name="hdrfooter" type="hdrfooterType"
3459	                      minOccurs="0"/>
3460	         </xs:sequence>
3461	         <xs:attribute name="rmtid" type="faxid.datatype"
3462	                       use="required"/>
3463	        </xs:complexType>
3464	       </xs:element>
3465	       <xs:group ref="faxstatusrequest"/>
3466	      </xs:sequence>
3467	      <xs:attribute name="lclid" type="faxid.datatype" use="optional"/>
3468	      <xs:attribute name="minspeed" type="faxspeed.datatype"
3469	                    use="optional"/>
3470	      <xs:attribute name="maxspeed" type="faxspeed.datatype"
3471	                    use="optional"/>
3472	      <xs:attribute name="ecm" type="boolean.datatype" use="optional"/>
3473	     </xs:complexType>
3474	    </xs:element>
3475	    <xs:element name="faxrecv" substitutionGroup="primitive">
3476	     <xs:complexType>
3477	      <xs:sequence>
3478	       <xs:element name="rcvobj" type="rcvobjType" minOccurs="0"
3479	                   maxOccurs="unbounded"/>
3480	       <xs:element name="hdrfooter" type="hdrfooterType" minOccurs="0"/>
3481	       <xs:element name="txpoll" minOccurs="0">
3482	        <xs:complexType>
3483	         <xs:sequence>
3484	          <xs:element name="sendobj" type="sendobjType"
3485	                      maxOccurs="unbounded"/>
3486	          <xs:element name="hdrfooter" type="hdrfooterType"
3487	                      minOccurs="0"/>
3488	         </xs:sequence>
3489	         <xs:attribute name="rmtid" type="faxid.datatype"/>

3491	        </xs:complexType>
3492	       </xs:element>
3493	       <xs:group ref="faxstatusrequest"/>
3494	      </xs:sequence>
3495	      <xs:attribute name="lclid" type="faxid.datatype" use="optional"/>
3496	      <xs:attribute name="ecm" type="boolean.datatype" default="true"/>
3497	     </xs:complexType>
3498	    </xs:element>
3499	    <xs:group name="faxstatusrequest">
3500	     <xs:all>
3501	      <xs:element name="faxstart" minOccurs="0"/>
3502	      <xs:element name="faxnegotiate" minOccurs="0"/>
3503	      <xs:element name="faxpagedone" minOccurs="0"/>
3504	      <xs:element name="faxobjectdone" minOccurs="0"/>
3505	      <xs:element name="faxopcomplete" minOccurs="0"/>
3506	      <xs:element name="faxpollstart" minOccurs="0"/>
3507	     </xs:all>
3508	    </xs:group>
3509	    <xs:complexType name="hdrfooterType">
3510	     <xs:choice>
3511	      <xs:element name="format" type="xs:string" minOccurs="0"
3512	                  maxOccurs="unbounded"/>
3513	     </xs:choice>
3514	     <xs:attribute name="type" type="hdrfooter.datatype"/>
3515	     <xs:attribute name="style" type="hdrfooterstyle.datatype"/>
3516	    </xs:complexType>
3517	    <xs:complexType name="formatType">
3518	     <xs:simpleContent>
3519	      <xs:extension base="xs:string">
3520	       <xs:attribute name="style">
3521	        <xs:simpleType>
3522	         <xs:restriction base="xs:string">
3523	          <xs:enumeration value="append"/>
3524	          <xs:enumeration value="overlay"/>
3525	          <xs:enumeration value="replace"/>
3526	         </xs:restriction>
3527	        </xs:simpleType>
3528	       </xs:attribute>
3529	      </xs:extension>
3530	     </xs:simpleContent>
3531	    </xs:complexType>
3532	    <xs:complexType name="rcvobjType">
3533	     <xs:attribute name="objuri" type="xs:anyURI" use="required"/>
3534	     <xs:attribute name="maxpages" type="xs:positiveInteger"/>
3535	    </xs:complexType>
3536	    <xs:complexType name="sendobjType">
3537	     <xs:attribute name="objuri" type="xs:anyURI" use="required"/>
3538	     <xs:attribute name="startpage" type="xs:positiveInteger"/>
3539	     <xs:attribute name="pagecount" type="xs:positiveInteger"/>

3541	    </xs:complexType>
3542	    <xs:simpleType name="faxid.datatype">
3543	     <xs:restriction base="xs:string">
3544	      <xs:pattern value="[0-9+*- ]{20}"/>
3545	     </xs:restriction>
3546	    </xs:simpleType>
3547	    <xs:simpleType name="faxspeed.datatype">
3548	     <xs:restriction base="xs:string">
3549	      <xs:enumeration value="2400"/>
3550	      <xs:enumeration value="4800"/>
3551	      <xs:enumeration value="7200"/>
3552	      <xs:enumeration value="9600"/>
3553	      <xs:enumeration value="12000"/>
3554	      <xs:enumeration value="14400"/>
3555	     </xs:restriction>
3556	    </xs:simpleType>
3557	    <xs:simpleType name="hdrfooter.datatype">
3558	     <xs:restriction base="xs:string">
3559	      <xs:enumeration value="header"/>
3560	      <xs:enumeration value="footer"/>
3561	      <xs:enumeration value="autohdr"/>
3562	      <xs:enumeration value="nohdr"/>
3563	     </xs:restriction>
3564	    </xs:simpleType>
3565	    <xs:simpleType name="hdrfooterstyle.datatype">
3566	     <xs:restriction base="xs:string">
3567	      <xs:enumeration value="append"/>
3568	      <xs:enumeration value="overlay"/>
3569	      <xs:enumeration value="replace"/>
3570	     </xs:restriction>
3571	    </xs:simpleType>
3572	   </xs:schema>

3574	Security Considerations

3576	   MOML is invoked through other languages and protocols and as such
3577	   security considerations depend on those environments.

3579	   MOML being an XML based language, security considerations as defined
3580	   by RFC 3023 [14] are applicable.

3582	IANA Considerations

3584	   IANA registration for 'application/moml+xml' media type is planned.

3586	   MGCP and Megaco/H.248 packages are registered with IANA so that there
3587	   is no conflict between packages developed by different authors. The
3588	   package scheme planned for future extensibility of MSML/MOML will
3589	   also require IANA registry of packages.

3591	References

3593	   [1] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J.
3594	   Peterson, R. Sparks, M. Handley, and E. Schooler, "SIP: Session
3595	   Initiation Protocol", RFC3261, Internet Engineering Taskforce, June
3596	   2002.

3598	   [2] J. Rosenberg, H. Schulzrinne, and P. Kyzivat, "Indicating User
3599	   Agent Capabilities in the Session Initiation Protocol (SIP)",
3600	   Internet Engineering Taskforce, December 2003. Work in progress.

3602	   [3] R. Mahy and N. Ismail, "Media Policy Manipulation in the
3603	   Conference Policy Control Protocol", Internet Draft, Internet
3604	   Engineering Taskforce, Feb. 2003. Work in progress.

3606	   [4] World Wide Web Consortium, "Extensible Markup Language (XML) 1.0
3607	   (Second Edition)", W3C Recommendation, Oct. 2000.

3609	   [5] World Wide Web Consortium, "Speech Recognition Grammar
3610	   Specification Version 1.0" (SRGS), W3C Candidate Recommendation, June
3611	   26, 2002

3613	   [6] World Wide Web Consortium, "Natural Language Semantics Markup
3614	   Language (NLSML) for the Speech Interface Framework", W3C Working
3615	   Draft, May 2001.

3617	   [7] World Wide Web Consortium, "Voice Extensible Markup Language
3618	   (VoiceXML) Version 2.0, W3C Candidate Recommendation, February 20,
3619	   2003

3621	   [8] T. Melanchuk, "Media Sessions Markup Language (MSML)", Internet
3622	   Draft, Internet Engineering Task Force, Feb. 2005. Work in progress.

3624	   [9] J. Van Dyke, E. Burger, A. Spitzer, "Basic Network Media Services
3625	   with SIP", Internet Draft, Internet Engineering Task Force, February
3626	   2005. Work in progress.

3628	   [10] C. Jennings, SIP Support for Application Initiation, Internet
3629	   Draft, Internet Engineering Taskforce, Oct. 2002. Work in progress.

3631	   [11] A. B. Roach, Session Initiation Protocol (SIP)-Specific Event
3632	   Notification, RFC 3265, Internet Engineering Taskforce, June 2002.

3634	   [12] E. Levinson, "Content-ID and Message-ID Uniform Resource
3635	   Locators", RFC 2392, Internet Engineering Taskforce, August 1998.

3637	   [13] S. Bradner, �Key words for use in RFCs to Indicate Requirement
3638	   Levels,� RFC 2119, Internet Engineering Taskforce, March 1997.

3640	   [14] M. Murata, S. St.Laurent, and D. Kohn, �XML Media Types,� RFC
3641	   3023, Internet Engineering Taskforce, January 2001.

3643	Acknowledgments

3645	   Version -06 was derived from earlier versions co-authored by Tim
3646	   Melanchuk (contact: <tim.melanchuk@gmail.com>) and Garland Sharratt.
3647	   Adnan Saleem and Yong Xin of Convedia, have provided key insights,
3648	   both theoretic and through development experience, on several
3649	   versions of the drafts. Stephen Buko and George Raskulinec of Intel
3650	   made numerous valuable contributions for new feature additions to
3651	   MSML and MOML versions �06. Gilles Compienne of Ubiquity Software has
3652	   provided feedback on several versions of this draft. Chris Boulton
3653	   and Ben Smith, both of Ubiquity, and Michael Rice of VocalData helped
3654	   clarify several issues in the -00 draft, while Bruce Walsh and Kevin
3655	   Fitzgerald, both of Spectel, provided important feedback on that
3656	   draft. Cliff Schornak of Commetrex significantly contributed to the
3657	   facsimile work.

3659	Authors' Addresses

3661	   Adnan Saleem
3662	   Convedia
3663	   4190 Still Creek Drive, Suite 300
3664	   Vancouver, BC, V5C 6C6
3665	   Canada

3667	   Phone: +1 604 918 6376
3668	   Email: asaleem@convedia.com

3670	   Garland Sharratt
3671	   Convedia
3672	   4190 Still Creek Drive, Suite 300
3673	   Vancouver, BC, V5C 6C6
3674	   Canada

3676	   Phone: +1 604 918 6393
3677	   Email: gsharratt@convedia.com

3679	Intellectual Property Statement

3681	   The IETF takes no position regarding the validity or scope of any
3682	   Intellectual Property Rights or other rights that might be claimed to
3683	   pertain to the implementation or use of the technology described in
3684	   this document or the extent to which any license under such rights
3685	   might or might not be available; nor does it represent that it has
3686	   made any independent effort to identify any such rights. Information
3687	   on the procedures with respect to rights in RFC documents can be
3688	   found in BCP 78 and BCP 79.

3690	   Copies of IPR disclosures made to the IETF Secretariat and any
3691	   assurances of licenses to be made available, or the result of an
3692	   attempt made to obtain a general license or permission for the use of
3693	   such proprietary rights by implementers or users of this
3694	   specification can be obtained from the IETF on-line IPR repository at
3695	   http://www.ietf.org/ipr.

3697	   The IETF invites any interested party to bring to its attention any
3698	   copyrights, patents or patent applications, or other proprietary
3699	   rights that may cover technology that may be required to implement
3700	   this standard. Please address the information to the IETF at ietf-
3701	   ipr@ietf.org.

3703	Copyright Statement

3705	   Copyright (C) The Internet Society (2005). This document is subject
3706	   to the rights, licenses and restrictions contained in BCP 78, and
3707	   except as set forth therein, the authors retain all their rights

3709	Disclaimer of Validity

3711	   This document and the information contained herein are provided on an
3712	   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
3713	   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
3714	   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
3715	   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
3716	   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
3717	   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

3719	Acknowledgement

3721	   Funding for the RFC Editor function is currently provided by the
3722	   Internet Society.