draft-ietf-mediactrl-mrb-05.txt   draft-ietf-mediactrl-mrb-06.txt 
Network Working Group C. Boulton Network Working Group C. Boulton
Internet-Draft NS-Technologies Internet-Draft NS-Technologies
Intended status: Standards Track L. Miniero Intended status: Standards Track L. Miniero
Expires: November 15, 2010 University of Napoli Expires: December 11, 2010 University of Napoli
May 14, 2010 June 9, 2010
Media Resource Brokering Media Resource Brokering
draft-ietf-mediactrl-mrb-05 draft-ietf-mediactrl-mrb-06
Abstract Abstract
The MediaCtrl work group in the IETF has proposed an architecture for The MediaCtrl work group in the IETF has proposed an architecture for
controlling media services. The Session Initiation Protocol (SIP) is controlling media services. The Session Initiation Protocol (SIP) is
used as the signalling protocol which provides many inherent used as the signalling protocol which provides many inherent
capabilities for message routing. In addition to such signalling capabilities for message routing. In addition to such signalling
properties, a need exists for intelligent, application level media properties, a need exists for intelligent, application level media
service selection based on non-static signalling properties. This is service selection based on non-static signalling properties. This is
especially true when considered in conjunction with deployment especially true when considered in conjunction with deployment
skipping to change at page 1, line 43 skipping to change at page 1, line 43
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 15, 2010. This Internet-Draft will expire on December 11, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 37 skipping to change at page 2, line 37
5.1.2. Element Definitions . . . . . . . . . . . . . . . . . 17 5.1.2. Element Definitions . . . . . . . . . . . . . . . . . 17
5.1.3. <mrbrequest> . . . . . . . . . . . . . . . . . . . . 17 5.1.3. <mrbrequest> . . . . . . . . . . . . . . . . . . . . 17
5.1.4. <mrbnotification> . . . . . . . . . . . . . . . . . . 19 5.1.4. <mrbnotification> . . . . . . . . . . . . . . . . . . 19
5.1.5. <mrbresponse> . . . . . . . . . . . . . . . . . . . . 28 5.1.5. <mrbresponse> . . . . . . . . . . . . . . . . . . . . 28
5.2. Media Service Resource Consumer Interface . . . . . . . . 30 5.2. Media Service Resource Consumer Interface . . . . . . . . 30
5.2.1. HTTP Consumer Interface Usage . . . . . . . . . . . . 30 5.2.1. HTTP Consumer Interface Usage . . . . . . . . . . . . 30
5.2.2. SIP Consumer Interface Usage . . . . . . . . . . . . 31 5.2.2. SIP Consumer Interface Usage . . . . . . . . . . . . 31
5.2.3. Consumer Interface Lease Mechanism . . . . . . . . . 32 5.2.3. Consumer Interface Lease Mechanism . . . . . . . . . 32
5.2.4. Media Service Resource Request . . . . . . . . . . . 35 5.2.4. Media Service Resource Request . . . . . . . . . . . 35
5.2.5. Media Service Resource Response . . . . . . . . . . . 46 5.2.5. Media Service Resource Response . . . . . . . . . . . 46
5.3. In-Line MRB Interface . . . . . . . . . . . . . . . . . . 48 5.3. In-Line MRB Interface . . . . . . . . . . . . . . . . . . 49
5.3.1. In-line Unaware MRB Mode . . . . . . . . . . . . . . 48 5.3.1. In-line Unaware MRB Mode . . . . . . . . . . . . . . 49
5.3.2. In-line Aware MRB Mode . . . . . . . . . . . . . . . 49 5.3.2. In-line Aware MRB Mode . . . . . . . . . . . . . . . 49
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 51 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.1. Publish Example . . . . . . . . . . . . . . . . . . . . . 51 6.1. Publish Example . . . . . . . . . . . . . . . . . . . . . 51
6.2. Consumer Example . . . . . . . . . . . . . . . . . . . . 57 6.2. Consumer Example . . . . . . . . . . . . . . . . . . . . 57
6.2.1. Query Example . . . . . . . . . . . . . . . . . . . . 57 6.2.1. Query Example . . . . . . . . . . . . . . . . . . . . 57
6.2.2. IAMM Example . . . . . . . . . . . . . . . . . . . . 59 6.2.2. IAMM Example . . . . . . . . . . . . . . . . . . . . 59
7. Media Service Resource Publisher Interface XML Schema . . . . 66 7. Media Service Resource Publisher Interface XML Schema . . . . 66
8. Media Service Resource Consumer Interface XML Schema . . . . 88 8. Media Service Resource Consumer Interface XML Schema . . . . 88
9. Security Considerations . . . . . . . . . . . . . . . . . . . 109 9. Security Considerations . . . . . . . . . . . . . . . . . . . 109
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 110 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 110
skipping to change at page 20, line 38 skipping to change at page 20, line 38
The <active-mixer-sessions> element provides information detailing The <active-mixer-sessions> element provides information detailing
the current active mixed RTP sessions. The element MAY be present. the current active mixed RTP sessions. The element MAY be present.
The <active-mixer-sessions> element has no attributes. The <active-mixer-sessions> element has no attributes.
The <active-mixer-sessions> element has the following child element: The <active-mixer-sessions> element has the following child element:
active-mix: Is a container which represents a mixed active RTP active-mix: Is a container which represents a mixed active RTP
session. The <active-mix> element has one attribute. The session. The <active-mix> element has one attribute. The
attribute 'conferenceid' represents the name of the mix being attribute 'conferenceid' represents the name of the mix being
represented. The <active-mix> element has one child elements. represented. The <active-mix> element has one child element. The
The child element, <rtp-codec>, contains the same information child element, <rtp-codec>, contains the same information relating
relating to RTP sessions as defined in Section 5.1.4.3. The to RTP sessions as defined in Section 5.1.4.3. The element MAY be
element MAY be present. present.
5.1.4.5. <non-active-rtp-sessions> 5.1.4.5. <non-active-rtp-sessions>
The <non-active-rtp-sessions> element provides information detailing The <non-active-rtp-sessions> element provides information detailing
the currently available inactive RTP sessions. The element MAY be the currently available inactive RTP sessions. The element MAY be
present. present.
The <non-active-rtp-sessions> element has no attributes. The <non-active-rtp-sessions> element has no attributes.
The <non-active-rtp-sessions> element has the following child The <non-active-rtp-sessions> element has the following child
skipping to change at page 21, line 32 skipping to change at page 21, line 32
The <non-active-rtp-sessions> element has no attributes. The <non-active-rtp-sessions> element has no attributes.
The <non-active-mixer-sessions> element has the following child The <non-active-mixer-sessions> element has the following child
element: element:
non-active-mix: Is a container which representing an available non-active-mix: Is a container which representing an available
mixed RTP session. The <non-active-mix> element has one mixed RTP session. The <non-active-mix> element has one
attribute. The attribute 'available' represents the number of attribute. The attribute 'available' represents the number of
mixes that could be used using that profile. The <non-active-mix> mixes that could be used using that profile. The <non-active-mix>
element has one child elements. The child element, <rtp-codec>, element has one child element. The child element, <rtp-codec>,
contains the same information relating to RTP sessions as defined contains the same information relating to RTP sessions as defined
in Section 5.1.4.5. The element MAY be present. in Section 5.1.4.5. The element MAY be present.
5.1.4.7. <media-server-status> 5.1.4.7. <media-server-status>
The <media-server-status> element provides information detailing the The <media-server-status> element provides information detailing the
current status of the media server. The element MUST be present. It current status of the media server. The element MUST be present. It
can return one of the following values: can return one of the following values:
active: Indicating that the Media Server is available for service. active: Indicating that the Media Server is available for service.
skipping to change at page 25, line 15 skipping to change at page 25, line 15
video-mixing-modes: Is a container representing the available video video-mixing-modes: Is a container representing the available video
presentation layouts and the supported functionality for what presentation layouts and the supported functionality for what
concerns video mixing. The <video-mixing-modes> element has two concerns video mixing. The <video-mixing-modes> element has two
attributes, 'vas' and 'activespeakermix'. The 'vas' attribute is attributes, 'vas' and 'activespeakermix'. The 'vas' attribute is
of type boolean with a value of 'true' indicating the Media Server of type boolean with a value of 'true' indicating the Media Server
supports automatic Voice Activated Switching. The supports automatic Voice Activated Switching. The
'activespeakermix' is of type boolean with a value of 'true' 'activespeakermix' is of type boolean with a value of 'true'
indicating that the Media Server is able to prepare an additional indicating that the Media Server is able to prepare an additional
video stream for the loudest speaker participant without its video stream for the loudest speaker participant without its
contribution. The <video-mixing-modes> element has one child contribution. The <video-mixing-modes> element has one child
element. The child element, <video-mixing-mode>, contains a element. The child element, <video-mixing-mode>, contains the
specific video presentation layout. It has a single attribute, name of a specific video presentation layout. The name may refer
'package'. The attribute 'package' provides the name of the Media to one of predefined video layouts defined in the XCON conference
Control Channel Framework package, compliant with the information data model, or to non-XCON layouts as well, as long as
specification in the related IANA registry (e.g., "msc-ivr/1.0"), they are properly prefixed. The <video-mixing-mode> element has a
for which the algorithm support applies. single attribute, 'package'. The attribute 'package' provides the
name of the Media Control Channel Framework package, compliant
with the specification in the related IANA registry (e.g., "msc-
ivr/1.0"), for which the algorithm support applies.
5.1.4.14. <supported-tones> 5.1.4.14. <supported-tones>
The <supported-tones> element provides information about which tones The <supported-tones> element provides information about which tones
a media server supports. In particular, the support is reported a media server supports. In particular, the support is reported
referring to both country codes support (ISO 3166-1 [ISO.3166-1]) and referring to both country codes support (ISO 3166-1 [ISO.3166-1]) and
supported functionality (ITU-T Recommendation Q.1950 [ITU-T.Q.1950]). supported functionality (ITU-T Recommendation Q.1950 [ITU-T.Q.1950]).
The element MAY be present. The element MAY be present.
The <supported-tones> element has no attributes. The <supported-tones> element has no attributes.
skipping to change at page 27, line 17 skipping to change at page 27, line 17
support> has one child element. The child element, <language>, support> has one child element. The child element, <language>,
reports the MS supports tts for a specific language. The reports the MS supports tts for a specific language. The
<language> element has a single attribute, 'xml:lang'. The <language> element has a single attribute, 'xml:lang'. The
attribute 'xml:lang' contains the ISO-639-1 [ISO.639.1988] code of attribute 'xml:lang' contains the ISO-639-1 [ISO.639.1988] code of
the supported language. the supported language.
5.1.4.17. <vxml-support> 5.1.4.17. <vxml-support>
The <vxml-support> element specifies if the Media Server supports The <vxml-support> element specifies if the Media Server supports
VoiceXML and if it does which protocols the support is exposed VoiceXML and if it does which protocols the support is exposed
through (e.g., via the control framework, or RFC5552 [RFC5552]). The through (e.g., via the control framework, RFC4240 [RFC4240], or
element MAY be present. RFC5552 [RFC5552]). The element MAY be present.
The <vxml-support> element has a single attribute 'support'. The The <vxml-support> element has a single attribute 'support'. The
'support' attribute is of type boolean with a value of 'true' 'support' attribute is of type boolean with a value of 'true'
indicating that the media server does support VXML, and a value of indicating that the media server does support VXML, and a value of
'false' indicating it does not support VXML. The default value is 'false' indicating it does not support VXML. The default value is
'false'. 'false'.
The <vxml-support> element has the following child element: The <vxml-support> element has the following child element:
vxml-mode: has two attributes, 'package' and 'support'. The vxml-mode: has two attributes, 'package' and 'support'. The
'package' attribute provides the name of the Media Control Channel 'package' attribute provides the name of the Media Control Channel
Framework package, compliant with the specification in the related Framework package, compliant with the specification in the related
IANA registry (e.g., "msc-ivr/1.0"), for which the VXML support IANA registry (e.g., "msc-ivr/1.0"), for which the VXML support
applies. The 'support' attribute provides the type of VXML applies. The 'support' attribute provides the type of VXML
support provided by the Media Server (RFC5552 [RFC5552] or IVR- support provided by the Media Server (RFC5552 [RFC5552], RFC4240
Package [I-D.ietf-mediactrl-ivr-control-package]). [RFC4240] or IVR-Package
[I-D.ietf-mediactrl-ivr-control-package]).
5.1.4.18. <media-server-location> 5.1.4.18. <media-server-location>
The <media-server-location> element provides information about the The <media-server-location> element provides information about the
civic location of a media server. Its description makes use of the civic location of a media server. Its description makes use of the
Civic Address Schema standardized in RFC 5139 [RFC5139]. The element Civic Address Schema standardized in RFC 5139 [RFC5139]. The element
MAY be present. MAY be present.
The <media-server-location> element has no attributes. The <media-server-location> element has no attributes.
skipping to change at page 28, line 40 skipping to change at page 28, line 40
5.1.4.21. <encryption> 5.1.4.21. <encryption>
The <encyption> element allows a Media Server to declare support for The <encyption> element allows a Media Server to declare support for
encrypting RTP media streams using RFC 3711 [RFC3711]. A value of encrypting RTP media streams using RFC 3711 [RFC3711]. A value of
'true' indicates that a Media Server does support RFC 3711 [RFC3711] 'true' indicates that a Media Server does support RFC 3711 [RFC3711]
for RTP. A value of 'false' indicates that a Media Server does not for RTP. A value of 'false' indicates that a Media Server does not
support RFC 3711 [RFC3711] for RTP. The element MAY be present. support RFC 3711 [RFC3711] for RTP. The element MAY be present.
The <encryption> element has no attributes. The <encryption> element has no attributes.
The <application-data> element has no child elements. The <encryption> element has no child elements.
5.1.5. <mrbresponse> 5.1.5. <mrbresponse>
Responses to requests are indicated by a <response> element from Responses to requests are indicated by a <response> element from
Section 7. Section 7.
The <response> element has following attributes: The <response> element has following attributes:
status: numeric code indicating the response status. The attribute status: numeric code indicating the response status. The attribute
MUST be present. MUST be present.
skipping to change at page 37, line 45 skipping to change at page 37, line 45
5.2.4.1.2.2. <file-formats> element 5.2.4.1.2.2. <file-formats> element
The <file-formats> element provides a list of file formats required The <file-formats> element provides a list of file formats required
for the purpose of playing media. The element MAY be present. for the purpose of playing media. The element MAY be present.
The <file-formats> element has no attributes. The <file-formats> element has no attributes.
The <file-formats> element has the following child element: The <file-formats> element has the following child element:
supported-format: has a single attribute, 'name', which provides required-format: has a single attribute, 'name', which provides the
the type of file format that is supported. The <supported-format> type of file format that is required. A valid value is a MIME
element then has a further child element, <supported-file- media type which, depending on its definition, can include
package>. The <supported-file-package> element provides the name additional parameters (e.g., [RFC4281]). The <supported-format>
of the Media Control Channel Framework package, compliant with the element then has a further child element, <required-file-package>.
The <required-file-package> element provides the name of the Media
Control Channel Framework package, compliant with the
specification in the related IANA registry (e.g., "msc-ivr/1.0"), specification in the related IANA registry (e.g., "msc-ivr/1.0"),
for which the file format support applies. for which the file format support applies.
5.2.4.1.2.3. <dtmf> element 5.2.4.1.2.3. <dtmf> element
The <dtmf> element supplies the required methods to detect DTMF tones The <dtmf> element supplies the required methods to detect DTMF tones
and to generate them. The element MAY be present. and to generate them. The element MAY be present.
The <dtmf> element has no attributes. The <dtmf> element has no attributes.
skipping to change at page 40, line 17 skipping to change at page 40, line 25
support> has one child element. The child element, <language>, support> has one child element. The child element, <language>,
requests the MS supports tts for a specific language. The requests the MS supports tts for a specific language. The
<language> element has a single attribute, 'xml:lang'. The <language> element has a single attribute, 'xml:lang'. The
attribute 'xml:lang' contains the ISO-639-1 [ISO.639.1988] code of attribute 'xml:lang' contains the ISO-639-1 [ISO.639.1988] code of
the supported language. the supported language.
5.2.4.1.2.6. <vxml> element 5.2.4.1.2.6. <vxml> element
The <vxml> element specifies if the Consumer client required VoiceXML The <vxml> element specifies if the Consumer client required VoiceXML
and if it does which protocols the support is exposed through (e.g., and if it does which protocols the support is exposed through (e.g.,
via the control framework, or RFC5552 [RFC5552]). The element MAY be via the control framework, RFC4240 [RFC4240], or RFC5552 [RFC5552]).
present. The element MAY be present.
The <vxml> element has a single attribute 'support'. The 'support' The <vxml> element has a single attribute 'support'. The 'support'
attribute is of type boolean with a value of 'true' indicating that attribute is of type boolean with a value of 'true' indicating that
the Consumer client requires VXML support, and a value of 'false' the Consumer client requires VXML support, and a value of 'false'
indicating it does not require VXML support. The default value is indicating it does not require VXML support. The default value is
'false'. 'false'.
The <vxml> element has the following child element: The <vxml> element has the following child element:
vxml-mode: has two attributes, 'package' and 'require'. The vxml-mode: has two attributes, 'package' and 'require'. The
'package' attribute provides the name of the Media Control Channel 'package' attribute provides the name of the Media Control Channel
Framework package, compliant with the specification in the related Framework package, compliant with the specification in the related
IANA registry (e.g., "msc-ivr/1.0"), for which the VXML support IANA registry (e.g., "msc-ivr/1.0"), for which the VXML support
applies. The 'require' attribute specifies the type of VXML applies. The 'require' attribute specifies the type of VXML
support required by the Consumer client (RFC5552 [RFC5552] or IVR- support required by the Consumer client (RFC5552 [RFC5552],
Package [I-D.ietf-mediactrl-ivr-control-package]). RFC4240 [RFC4240] or IVR-Package
[I-D.ietf-mediactrl-ivr-control-package]).
5.2.4.1.2.7. <location> 5.2.4.1.2.7. <location>
The <location> element requests a civic location for an IVR media The <location> element requests a civic location for an IVR media
server. The request makes use of the Civic Address Schema server. The request makes use of the Civic Address Schema
standardized in RFC 5139 [RFC5139]. The element MAY be present. standardized in RFC 5139 [RFC5139]. The element MAY be present.
The <location> element has no attributes. The <location> element has no attributes.
The <location> element one child element: The <location> element one child element:
skipping to change at page 41, line 16 skipping to change at page 41, line 22
The <encryption> element allows a Consumer client to request support The <encryption> element allows a Consumer client to request support
for encrypting RTP media streams using RFC 3711 [RFC3711]. A value for encrypting RTP media streams using RFC 3711 [RFC3711]. A value
of 'true' indicates that Consumer client requires support of RFC 3711 of 'true' indicates that Consumer client requires support of RFC 3711
[RFC3711] for RTP. A value of 'false' indicates that a Consumer [RFC3711] for RTP. A value of 'false' indicates that a Consumer
client does not require support of RFC 3711 [RFC3711] for RTP. The client does not require support of RFC 3711 [RFC3711] for RTP. The
element MAY be present. The default value is 'false' element MAY be present. The default value is 'false'
The <encryption> element has no attributes. The <encryption> element has no attributes.
The <application-data> element has no child elements. The <encryption> element has no child elements.
5.2.4.1.2.9. <application-data> 5.2.4.1.2.9. <application-data>
The <application-data> element provides IVR application level data. The <application-data> element provides IVR application level data.
The element MAY be present. The element MAY be present.
The <application-data> element has no attributes. The <application-data> element has no attributes.
The <application-data> element has no child elements. The <application-data> element has no child elements.
skipping to change at page 42, line 36 skipping to change at page 42, line 44
The <mixers> element provides information detailing the required The <mixers> element provides information detailing the required
mixed RTP sessions. The element MAY be present. mixed RTP sessions. The element MAY be present.
The <mixers> element has no attributes. The <mixers> element has no attributes.
The <mixers> element has the following child element: The <mixers> element has the following child element:
mix: Is a container which represents a required mixed RTP session. mix: Is a container which represents a required mixed RTP session.
The <mix> element has one attribute. The attribute 'users' The <mix> element has one attribute. The attribute 'users'
represents the number of participants required in the mix. The represents the number of participants required in the mix. The
<mix> element has one child elements. The child element, <codec>, <mix> element has one child element. The child element, <rtp-
contains the same information relating to RTP sessions as defined codec>, contains the same information relating to RTP sessions as
in Section 5.1.4.3. The element MAY be present. defined in Section 5.1.4.3. The element MAY be present.
5.2.4.1.3.2. <file-formats> 5.2.4.1.3.2. <file-formats>
The <file-formats> element provides a list of file formats required The <file-formats> element provides a list of file formats required
by the Consumer client for the purpose of playing media to a mix. by the Consumer client for the purpose of playing media to a mix.
The element MAY be present. The element MAY be present.
The <file-formats> element has no attributes. The <file-formats> element has no attributes.
The <file-formats> element has the following child element: The <file-formats> element has the following child element:
required-format: has a single attribute, 'name', which provides the required-format: has a single attribute, 'name', which provides the
type of file format that is supported. The <required-format> type of file format that is supported. A valid value is a MIME
media type which, depending on its definition, can include
additional parameters (e.g., [RFC4281]). The <required-format>
element then has a further child element, <required-file-package>. element then has a further child element, <required-file-package>.
The <required-file-package> element provides the name of the Media The <required-file-package> element provides the name of the Media
Control Channel Framework package, compliant with the Control Channel Framework package, compliant with the
specification in the related IANA registry (e.g., "msc-ivr/1.0"), specification in the related IANA registry (e.g., "msc-ivr/1.0"),
for which the file format support applies. for which the file format support applies.
5.2.4.1.3.3. <dtmf> element 5.2.4.1.3.3. <dtmf> element
The <dtmf> element supplies the required methods to detect DTMF tones The <dtmf> element supplies the required methods to detect DTMF tones
and to generate them in a mix. The element MAY be present. and to generate them in a mix. The element MAY be present.
skipping to change at page 45, line 27 skipping to change at page 45, line 36
video-mixing-modes: Is a container representing the requested video video-mixing-modes: Is a container representing the requested video
presentation layouts for video mixing. The <video-mixing-modes> presentation layouts for video mixing. The <video-mixing-modes>
element has two attributes, 'vas' and 'activespeakermix'. The element has two attributes, 'vas' and 'activespeakermix'. The
'vas' attribute is of type boolean with a value of 'true' 'vas' attribute is of type boolean with a value of 'true'
indicating that the Consumer Client requires automatic Voice indicating that the Consumer Client requires automatic Voice
Activated Switching. The 'activespeakermix' attribute is of type Activated Switching. The 'activespeakermix' attribute is of type
boolean with a value of 'true' indicating that the Consumer Client boolean with a value of 'true' indicating that the Consumer Client
requires an additional video stream for the loudest speaker requires an additional video stream for the loudest speaker
participant without its contribution. The <video-mixing-modes> participant without its contribution. The <video-mixing-modes>
element has one child element. The child element, <video-mixing- element has one child element. The child element, <video-mixing-
mode>, contains a requested video presentation layout. It has a mode>, contains the name of a specific video presentation layout.
single attribute, 'package'. The attribute 'package' provides the The name may refer to one of predefined video layouts defined in
name of the Media Control Channel Framework package, compliant the XCON conference information data model, or to non-XCON layouts
with the specification in the related IANA registry (e.g., "msc- as well, as long as they are properly prefixed. The <video-
ivr/1.0"), for which the algorithm support is requested. mixing-mode> element has a single attribute, 'package'. The
attribute 'package' provides the name of the Media Control Channel
Framework package, compliant with the specification in the related
IANA registry (e.g., "msc-ivr/1.0"), for which the algorithm
support is requested.
5.2.4.1.3.6. <application-data> 5.2.4.1.3.6. <application-data>
The <application-data> element provides IVR application level data. The <application-data> element provides IVR application level data.
The element MAY be present. The element MAY be present.
The <application-data> element has no attributes. The <application-data> element has no attributes.
The <application-data> element has no child elements. The <application-data> element has no child elements.
skipping to change at page 87, line 32 skipping to change at page 87, line 32
<xsd:simpleType name="boolean.datatype"> <xsd:simpleType name="boolean.datatype">
<xsd:restriction base="xsd:NMTOKEN"> <xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="true" /> <xsd:enumeration value="true" />
<xsd:enumeration value="false" /> <xsd:enumeration value="false" />
</xsd:restriction> </xsd:restriction>
</xsd:simpleType> </xsd:simpleType>
<xsd:simpleType name="vxml.datatype"> <xsd:simpleType name="vxml.datatype">
<xsd:restriction base="xsd:NMTOKEN"> <xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="RFC4240" />
<xsd:enumeration value="RFC5552" /> <xsd:enumeration value="RFC5552" />
<xsd:enumeration value="IVR-Package" /> <xsd:enumeration value="IVR-Package" />
</xsd:restriction> </xsd:restriction>
</xsd:simpleType> </xsd:simpleType>
<xsd:simpleType name="label.datatype"> <xsd:simpleType name="label.datatype">
<xsd:restriction base="xsd:NMTOKEN" /> <xsd:restriction base="xsd:NMTOKEN" />
</xsd:simpleType> </xsd:simpleType>
<xsd:simpleType name="subscriptionid.datatype"> <xsd:simpleType name="subscriptionid.datatype">
skipping to change at page 104, line 48 skipping to change at page 104, line 48
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="mixers" type="mixerssessionsType" /> <xsd:element name="mixers" type="mixerssessionsType" />
<xsd:complexType name="mixType"> <xsd:complexType name="mixType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence> <xsd:sequence>
<xsd:element name="codec" type="xsd:string" minOccurs="0" <xsd:element ref="rtp-codec" minOccurs="0"
maxOccurs="unbounded" /> maxOccurs="unbounded" />
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="users" type="xsd:nonNegativeInteger" <xsd:attribute name="users" type="xsd:nonNegativeInteger"
use="required" /> use="required" />
<xsd:anyAttribute namespace="##other" processContents="lax" /> <xsd:anyAttribute namespace="##other" processContents="lax" />
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
skipping to change at page 107, line 48 skipping to change at page 107, line 48
<xsd:simpleType name="boolean.datatype"> <xsd:simpleType name="boolean.datatype">
<xsd:restriction base="xsd:NMTOKEN"> <xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="true" /> <xsd:enumeration value="true" />
<xsd:enumeration value="false" /> <xsd:enumeration value="false" />
</xsd:restriction> </xsd:restriction>
</xsd:simpleType> </xsd:simpleType>
<xsd:simpleType name="vxml.datatype"> <xsd:simpleType name="vxml.datatype">
<xsd:restriction base="xsd:NMTOKEN"> <xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="RFC4240" />
<xsd:enumeration value="RFC5552" /> <xsd:enumeration value="RFC5552" />
<xsd:enumeration value="IVR-Package" /> <xsd:enumeration value="IVR-Package" />
</xsd:restriction> </xsd:restriction>
</xsd:simpleType> </xsd:simpleType>
<xsd:simpleType name="appdata.datatype"> <xsd:simpleType name="appdata.datatype">
<xsd:restriction base="xsd:NMTOKEN" /> <xsd:restriction base="xsd:NMTOKEN" />
</xsd:simpleType> </xsd:simpleType>
</xsd:schema> </xsd:schema>
skipping to change at page 118, line 23 skipping to change at page 118, line 23
December 2005. December 2005.
[W3C.REC-soap12-part1-20030624] [W3C.REC-soap12-part1-20030624]
Nielsen, H., Gudgin, M., Hadley, M., Moreau, J., and N. Nielsen, H., Gudgin, M., Hadley, M., Moreau, J., and N.
Mendelsohn, "SOAP Version 1.2 Part 1: Messaging Mendelsohn, "SOAP Version 1.2 Part 1: Messaging
Framework", World Wide Web Consortium FirstEdition REC- Framework", World Wide Web Consortium FirstEdition REC-
soap12-part1-20030624, June 2003, soap12-part1-20030624, June 2003,
<http://www.w3.org/TR/2003/REC-soap12-part1-20030624>. <http://www.w3.org/TR/2003/REC-soap12-part1-20030624>.
[W3C.REC-soap12-part2-20030624] [W3C.REC-soap12-part2-20030624]
Mendelsohn, N., Nielsen, H., Moreau, J., Gudgin, M., and Mendelsohn, N., Moreau, J., Hadley, M., Gudgin, M., and H.
M. Hadley, "SOAP Version 1.2 Part 2: Adjuncts", World Wide Nielsen, "SOAP Version 1.2 Part 2: Adjuncts", World Wide
Web Consortium FirstEdition REC-soap12-part2-20030624, Web Consortium FirstEdition REC-soap12-part2-20030624,
June 2003, June 2003,
<http://www.w3.org/TR/2003/REC-soap12-part2-20030624>. <http://www.w3.org/TR/2003/REC-soap12-part2-20030624>.
13.2. Informative References 13.2. Informative References
[I-D.ietf-mediactrl-ivr-control-package] [I-D.ietf-mediactrl-ivr-control-package]
McGlashan, S., Melanchuk, T., and C. Boulton, "An McGlashan, S., Melanchuk, T., and C. Boulton, "An
Interactive Voice Response (IVR) Control Package for the Interactive Voice Response (IVR) Control Package for the
Media Control Channel Framework", Media Control Channel Framework",
 End of changes. 21 change blocks. 
44 lines changed or deleted 59 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/