Debian Codegraph @

rfc6917.html

raw
1 <pre>Internet Engineering Task Force (IETF) C. Boulton
2 Request for Comments: 6917 NS-Technologies
3 Category: Standards Track L. Miniero
4 ISSN: 2070-1721 Meetecho
5 G. Munson
6 AT&amp;T
7 April 2013
8
9
10 <span class="h1">Media Resource Brokering</span>
11
12 Abstract
13
14 The MediaCtrl working group in the IETF has proposed an architecture
15 for controlling media services. The Session Initiation Protocol
16 (SIP) is used as the signaling protocol that provides many inherent
17 capabilities for message routing. In addition to such signaling
18 properties, a need exists for intelligent, application-level media
19 service selection based on non-static signaling properties. This is
20 especially true when considered in conjunction with deployment
21 architectures that include 1:M and M:N combinations of Application
22 Servers and Media Servers. This document introduces a Media Resource
23 Broker (MRB) entity, which manages the availability of Media Servers
24 and the media resource demands of Application Servers. The document
25 includes potential deployment options for an MRB and appropriate
26 interfaces to Application Servers and Media Servers.
27
28 Status of This Memo
29
30 This is an Internet Standards Track document.
31
32 This document is a product of the Internet Engineering Task Force
33 (IETF). It represents the consensus of the IETF community. It has
34 received public review and has been approved for publication by the
35 Internet Engineering Steering Group (IESG). Further information on
36 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
37
38 Information about the current status of this document, any errata,
39 and how to provide feedback on it may be obtained at
40 <a href="http://www.rfc-editor.org/info/rfc6917">http://www.rfc-editor.org/info/rfc6917</a>.
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Boulton, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2013 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72 Table of Contents
73
74 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
75 <a href="#section-2">2</a>. Conventions and Terminology .....................................<a href="#page-6">6</a>
76 <a href="#section-3">3</a>. Problem Discussion ..............................................<a href="#page-6">6</a>
77 <a href="#section-4">4</a>. Deployment Scenario Options .....................................<a href="#page-7">7</a>
78 <a href="#section-4.1">4.1</a>. Query MRB ..................................................<a href="#page-8">8</a>
79 <a href="#section-4.1.1">4.1.1</a>. Hybrid Query MRB ....................................<a href="#page-9">9</a>
80 <a href="#section-4.2">4.2</a>. In-Line MRB ...............................................<a href="#page-11">11</a>
81 <a href="#section-5">5</a>. MRB Interface Definitions ......................................<a href="#page-12">12</a>
82 <a href="#section-5.1">5.1</a>. Media Server Resource Publish Interface ...................<a href="#page-12">12</a>
83 <a href="#section-5.1.1">5.1.1</a>. Control Package Definition .........................<a href="#page-13">13</a>
84 <a href="#section-5.1.2">5.1.2</a>. Element Definitions ................................<a href="#page-15">15</a>
85 <a href="#section-5.1.3">5.1.3</a>. &lt;mrbrequest&gt; .......................................<a href="#page-15">15</a>
86 <a href="#section-5.1.4">5.1.4</a>. &lt;mrbresponse&gt; ......................................<a href="#page-17">17</a>
87 <a href="#section-5.1.5">5.1.5</a>. &lt;mrbnotification&gt; ..................................<a href="#page-19">19</a>
88 <a href="#section-5.2">5.2</a>. Media Service Resource Consumer Interface .................<a href="#page-30">30</a>
89 <a href="#section-5.2.1">5.2.1</a>. Query Mode/HTTP Consumer Interface Usage ...........<a href="#page-31">31</a>
90 <a href="#section-5.2.2">5.2.2</a>. In-Line Aware Mode/SIP Consumer Interface Usage ....<a href="#page-32">32</a>
91 <a href="#section-5.2.3">5.2.3</a>. Consumer Interface Lease Mechanism .................<a href="#page-35">35</a>
92 <a href="#section-5.2.4">5.2.4</a>. &lt;mrbconsumer&gt; ......................................<a href="#page-38">38</a>
93 <a href="#section-5.2.5">5.2.5</a>. Media Service Resource Request .....................<a href="#page-39">39</a>
94 <a href="#section-5.2.6">5.2.6</a>. Media Service Resource Response ....................<a href="#page-51">51</a>
95 <a href="#section-5.3">5.3</a>. In-Line Unaware MRB Interface .............................<a href="#page-54">54</a>
96 <a href="#section-6">6</a>. MRB Acting as a B2BUA ..........................................<a href="#page-54">54</a>
97 <a href="#section-7">7</a>. Multimodal MRB Implementations .................................<a href="#page-55">55</a>
98 <a href="#section-8">8</a>. Relative Merits of Query Mode, IAMM, and IUMM ..................<a href="#page-56">56</a>
99 <a href="#section-9">9</a>. Examples .......................................................<a href="#page-58">58</a>
100 <a href="#section-9.1">9.1</a>. Publish Example ...........................................<a href="#page-58">58</a>
101 <a href="#section-9.2">9.2</a>. Consumer Examples .........................................<a href="#page-64">64</a>
102 <a href="#section-9.2.1">9.2.1</a>. Query Example ......................................<a href="#page-64">64</a>
103 <a href="#section-9.2.2">9.2.2</a>. IAMM Examples ......................................<a href="#page-68">68</a>
104 <a href="#section-10">10</a>. Media Service Resource Publisher Interface XML Schema .........<a href="#page-83">83</a>
105
106
107
108 <span class="grey">Boulton, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
111
112
113 <a href="#section-11">11</a>. Media Service Resource Consumer Interface XML Schema .........<a href="#page-106">106</a>
114 <a href="#section-12">12</a>. Security Considerations ......................................<a href="#page-127">127</a>
115 <a href="#section-13">13</a>. IANA Considerations ..........................................<a href="#page-130">130</a>
116 <a href="#section-13.1">13.1</a>. Media Control Channel Framework Package Registration ....<a href="#page-130">130</a>
117 <a href="#section-13.2">13.2</a>. application/mrb-publish+xml Media Type ..................<a href="#page-130">130</a>
118 <a href="#section-13.3">13.3</a>. application/mrb-consumer+xml Media Type .................<a href="#page-131">131</a>
119 <a href="#section-13.4">13.4</a>. URN Sub-Namespace Registration for mrb-publish ..........<a href="#page-132">132</a>
120 <a href="#section-13.5">13.5</a>. URN Sub-Namespace Registration for mrb-consumer .........<a href="#page-132">132</a>
121 <a href="#section-13.6">13.6</a>. XML Schema Registration for mrb-publish .................<a href="#page-132">132</a>
122 <a href="#section-13.7">13.7</a>. XML Schema Registration for mrb-consumer ................<a href="#page-133">133</a>
123 <a href="#section-14">14</a>. Acknowledgements .............................................<a href="#page-133">133</a>
124 <a href="#section-15">15</a>. References ...................................................<a href="#page-133">133</a>
125 <a href="#section-15.1">15.1</a>. Normative References ....................................<a href="#page-133">133</a>
126 <a href="#section-15.2">15.2</a>. Informative References ..................................<a href="#page-135">135</a>
127
128 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
129
130 As IP-based multimedia infrastructures mature, the complexity and
131 demands from deployments increase. Such complexity will result in a
132 wide variety of capabilities from a range of vendors that should all
133 be interoperable using the architecture and protocols produced by the
134 MediaCtrl working group. It should be possible for a controlling
135 entity to be assisted in Media Server selection so that the most
136 appropriate resource is selected for a particular operation. The
137 importance increases when one introduces a flexible level of
138 deployment scenarios, as specified in <a href="./rfc5167">RFC 5167</a> [<a href="./rfc5167" title="&quot;Media Server Control Protocol Requirements&quot;">RFC5167</a>] and <a href="./rfc5567">RFC 5567</a>
139 [<a href="./rfc5567" title="&quot;An Architectural Framework for Media Server Control&quot;">RFC5567</a>]. These documents make statements like "it should be
140 possible to have a many-to-many relationship between Application
141 Servers and Media Servers that use this protocol". This leads to the
142 following deployment architectures being possible when considering
143 media resources, to provide what can be effectively described as
144 media resource brokering.
145
146 The simplest deployment view is illustrated in Figure 1.
147
148 +---+-----+---+ +---+-----+---+
149 | Application | | Media |
150 | Server |&lt;-------MS Control------&gt;| Server |
151 +-------------+ +-------------+
152
153 Figure 1: Basic Architecture
154
155 This simply involves a single Application Server and Media Server.
156 Expanding on this view, it is also possible for an Application Server
157 to control multiple (greater than 1) Media Server instances at any
158 one time. This deployment view is illustrated in Figure 2.
159 Typically, such architectures are associated with application logic
160 that requires high-demand media services. It is more than possible
161
162
163
164 <span class="grey">Boulton, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
167
168
169 that each Media Server possesses a different media capability set.
170 Media Servers may offer different media services as specified in the
171 MediaCtrl architecture document [<a href="./rfc5567" title="&quot;An Architectural Framework for Media Server Control&quot;">RFC5567</a>]. A Media Server may have
172 similar media functionality but may have different capacity or media
173 codec support.
174
175 +---+-----+---+
176 | Media |
177 +-----&gt;| Server |
178 | +-------------+
179 |
180 +---+-----+---+ | +---+-----+---+
181 | Application | | | Media |
182 | Server |&lt;--MS Control-----+-----&gt;| Server |
183 +-------------+ | +-------------+
184 |
185 | +---+-----+---+
186 +-----&gt;| Media |
187 | Server |
188 +-------------+
189
190 Figure 2: Multiple Media Servers
191
192 Figure 3 conveys the opposite view to that in Figure 2. In this
193 model, there are a number of (greater than 1) Application Servers,
194 possibly supporting dissimilar applications, controlling a single
195 Media Server. Typically, such architectures are associated with
196 application logic that requires low-demand media services.
197
198 +---+-----+---+
199 | Application |
200 | Server |&lt;-----+
201 +-------------+ |
202 |
203 +---+-----+---+ | +---+-----+---+
204 | Application | | | Media |
205 | Server |&lt;-----+-----MS Control--&gt;| Server |
206 +-------------+ | +-------------+
207 |
208 +---+-----+---+ |
209 | Application | |
210 | Server |&lt;-----+
211 +-------------+
212
213 Figure 3: Multiple Application Servers
214
215
216
217
218
219
220 <span class="grey">Boulton, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
223
224
225 The final deployment view is the most complex (Figure 4). In this
226 model (M:N), there exist any number of Application Servers and any
227 number of Media Servers. It is again possible in this model that
228 Media Servers might not be homogeneous, and they might have different
229 capability sets and capacities.
230
231 +---+-----+---+ +---+-----+---+
232 | Application | | Media |
233 | Server |&lt;-----+ +----&gt;| Server |
234 +-------------+ | | +-------------+
235 | |
236 +---+-----+---+ | | +---+-----+---+
237 | Application | | | | Media |
238 | Server |&lt;-----+-MS Control-+----&gt;| Server |
239 +-------------+ | | +-------------+
240 | |
241 +---+-----+---+ | | +---+-----+---+
242 | Application | | +----&gt;| Media |
243 | Server |&lt;-----+ | Server |
244 +-------------+ +---+-----+---+
245
246 Figure 4: Many-to-Many Architecture
247
248 The remaining sections in this specification will focus on a new
249 entity called a Media Resource Broker (MRB), which can be utilized in
250 the deployment architectures described previously in this section.
251 The MRB entity provides the ability to obtain media resource
252 information and appropriately allocate (broker) on behalf of client
253 applications.
254
255 The high-level deployment options discussed in this section rely on
256 network architecture and policy to prohibit inappropriate use. Such
257 policies are out of scope for this document.
258
259 This document will take a look at the specific problem areas related
260 to such deployment architectures. It is recognized that the
261 solutions proposed in this document should be equally adaptable to
262 all of the previously described deployment models. It is also
263 recognized that the solution is far more relevant to some of the
264 previously discussed deployment models and can almost be viewed as
265 redundant on others.
266
267
268
269
270
271
272
273
274
275
276 <span class="grey">Boulton, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
279
280
281 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions and Terminology</span>
282
283 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
284 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
285 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
286
287 This document inherits terminology proposed in <a href="./rfc5567">RFC 5567</a> [<a href="./rfc5567" title="&quot;An Architectural Framework for Media Server Control&quot;">RFC5567</a>] and
288 in "Media Control Channel Framework" [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>]. In addition, the
289 following terms are defined for use in this document and for use in
290 the context of the MediaCtrl working group in the IETF:
291
292 Media Resource Broker (MRB): A logical entity that is responsible
293 for both collection of appropriate published Media Server (MS)
294 information and selecting appropriate Media Server resources on
295 behalf of consuming entities.
296
297 Query MRB: An instantiation of an MRB (see previous definition) that
298 provides an interface for an Application Server to retrieve the
299 address of an appropriate Media Server. The result returned to
300 the Application Server can be influenced by information contained
301 in the query request.
302
303 In-line MRB: An instantiation of an MRB (see previous definition)
304 that directly receives requests on the signaling path. There is
305 no separate query.
306
307 CFW: Media Control Channel Framework, as specified in [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>].
308
309 Within the context of In-line MRBs, additional terms are defined:
310
311 In-line Aware MRB Mode (IAMM): Defined in <a href="#section-5.2.2.1">Section 5.2.2.1</a>.
312
313 In-line Unaware MRB Mode (IUMM): Defined in <a href="#section-5.3">Section 5.3</a>.
314
315 The document will often specify when a specific identifier in a
316 protocol message needs to be unique. Unless stated otherwise, such
317 uniqueness will always be within the scope of the Media Servers
318 controlled by the same MRB. The interaction between different MRB
319 instances, e.g., the partitioning of a logical MRB, is out of scope
320 for this document.
321
322 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Problem Discussion</span>
323
324 As discussed in <a href="#section-1">Section 1</a>, a goal of the MediaCtrl working group is
325 to produce a solution that will service a wide variety of deployment
326 architectures. Such architectures range from the simplest 1:1
327 relationship between Media Servers and Application Servers to
328 potentially linearly scaling 1:M, M:1, and M:N deployments.
329
330
331
332 <span class="grey">Boulton, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
335
336
337 Managing such deployments is itself non-trivial for the proposed
338 solution until an additional number of factors that increase
339 complexity are included in the equation. As Media Servers evolve, it
340 must be taken into consideration that, where many can exist in a
341 deployment, they may not have been produced by the same vendor and
342 may not have the same capability set. It should be possible for an
343 Application Server that exists in a deployment to select a media
344 service based on a common, appropriate capability set. In
345 conjunction with capabilities, it is also important to take available
346 resources into consideration. The ability to select an appropriate
347 media service function is an extremely useful feature but becomes
348 even more powerful when considered with available resources for
349 servicing a request.
350
351 In conclusion, the intention is to create a toolkit that allows
352 MediaCtrl deployments to effectively utilize the available media
353 resources. It should be noted that in the simplest deployments where
354 only a single Media Server exists, an MRB function is probably not
355 required. Only a single capability set exists, and resource
356 availability can be handled using the appropriate underlying
357 signaling, e.g., SIP response. This document does not prohibit such
358 uses of an MRB; it simply provides the tools for various entities to
359 interact where appropriate. It is also worth noting that the
360 functions specified in this document aim to provide a 'best effort'
361 view of media resources at the time of request for initial Media
362 Server routing decisions. Any dramatic change in media capabilities
363 or capacity after a request has taken place should be handled by the
364 underlying protocol.
365
366 It should be noted that there may be additional information that is
367 desirable for the MRB to have for purposes of selecting a Media
368 Server resource, such as resource allocation rules across different
369 applications, planned or unplanned downtime of Media Server
370 resources, the planned addition of future Media Server resources, or
371 Media Server resource capacity models. How the MRB acquires such
372 information is outside the scope of this document. The specific
373 techniques used for selecting an appropriate media resource by an MRB
374 is also outside the scope of this document.
375
376 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Deployment Scenario Options</span>
377
378 Research into media resource brokering concluded that a couple of
379 high-level models provided an appropriate level of flexibility. The
380 general principles of "in-line" and "query" MRB concepts are
381 discussed in the rest of this section. It should be noted that while
382 the interfaces are different, they both use common underlying
383 mechanisms defined in this specification.
384
385
386
387
388 <span class="grey">Boulton, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
391
392
393 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Query MRB</span>
394
395 The "Query" model for MRB interactions provides the ability for a
396 client of media services (for example, an Application Server) to
397 "ask" an MRB for an appropriate Media Server, as illustrated in
398 Figure 5.
399
400 +---+-----+---+
401 +------------&gt;| MRB |&lt;----------+----&lt;-----+---+
402 | +-------------+ (1)| | |
403 | | | |
404 |(2) +---+--+--+---+ | |
405 | | Media | | |
406 | +----&gt;| Server | | |
407 | | +-------------+ | |
408 | | (1)| |
409 +---+--+--+---+ | +---+-----+---+ | |
410 | Application | | | Media | | |
411 | Server |&lt;-----+-MS Control-+----&gt;| Server |-&gt;-+ |
412 +-------------+ (3) | +-------------+ |
413 | |
414 | +---+-----+---+ (1)|
415 +----&gt;| Media | |
416 | Server |---&gt;---+
417 +---+-----+---+
418
419 Figure 5: Query MRB
420
421 In this deployment, the Media Servers use the Media Server Resource
422 Publish interface, as discussed in <a href="#section-5.1">Section 5.1</a>, to convey capability
423 sets as well as resource information. This is depicted by (1) in
424 Figure 5. It is then the MRB's responsibility to accumulate all
425 appropriate information relating to media services in the logical
426 deployment cluster. The Application Server (or other media services
427 client) is then able to query the MRB for an appropriate resource (as
428 identified by (2) in Figure 5). Such a query would carry specific
429 information related to the media service required and enable the MRB
430 to provide increased accuracy in its response. This particular
431 interface is discussed in "Media Service Resource Consumer Interface"
432 (<a href="#section-5.2">Section 5.2</a>). The Application Server is then able to direct control
433 commands (for example, create a conference) and media dialogs to the
434 appropriate Media Server, as shown by (3) in Figure 5. Additionally,
435 with Query mode, the MRB is not directly in the signaling path
436 between the Application Server and the selected Media Server
437 resource.
438
439
440
441
442
443
444 <span class="grey">Boulton, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
447
448
449 <span class="h4"><a class="selflink" id="section-4.1.1" href="#section-4.1.1">4.1.1</a>. Hybrid Query MRB</span>
450
451 As mentioned previously, it is the intention that a toolkit is
452 provided for MRB functionality within a MediaCtrl architecture. It
453 is expected that in specific deployment scenarios the role of the MRB
454 might be co-hosted as a hybrid logical entity with an Application
455 Server, as shown in Figure 6.
456
457 +------------&lt;----------------&lt;---------+----&lt;-----+---+
458 | (1) | | |
459 | | | |
460 | +---+--+--+---+ | |
461 | | Media | | |
462 V +----&gt;| Server | | |
463 +------+------+ | +-------------+ | |
464 | MRB | | | |
465 +---+--+--+---+ | +---+-----+---+ | |
466 | Application | | | Media | | |
467 | Server |&lt;-----+-MS Control-+----&gt;| Server |-&gt;-+ |
468 +-------------+ | +-------------+ |
469 | |
470 | +---+-----+---+ |
471 +----&gt;| Media | |
472 | Server |---&gt;---+
473 +---+-----+---+
474
475 Figure 6: Hybrid Query MRB - Application Server Hosted
476
477 This diagram is identical to that in Figure 5 with the exception that
478 the MRB is now hosted on the Application Server. The Media Server
479 Publish interface is still being used to accumulate resource
480 information at the MRB, but as it is co-hosted on the Application
481 Server, the Media Server Consumer interface has collapsed. It might
482 still exist within the Application Server/MRB interaction, but this
483 is an implementation issue. This type of deployment suits a single
484 Application Server environment, but it should be noted that a Media
485 Server Consumer interface could then be offered from the hybrid if
486 required.
487
488
489
490
491
492
493
494
495
496
497
498
499
500 <span class="grey">Boulton, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
503
504
505 In a similar manner, the Media Server could also act as a hybrid for
506 the deployment cluster, as illustrated in Figure 7.
507
508 (1) +---+-----+---+
509 +---+---+-------------&gt;----------------&gt;-----------&gt;| MRB |
510 | | | +---+--+--+---+ +---+-----+---+
511 | | +-&lt;-| Application | | Media |
512 | | | Server |&lt;--+-MS Control-+-------&gt;| Server |
513 | | +-------------+ | +-------------+
514 | | |
515 | | +---+--+--+---+ |
516 | +---&lt;---| Application | |
517 | | Server |&lt;--+-MS Control-+--+
518 | +-------------+ |
519 | |
520 | +---+--+--+---+ |
521 +---&lt;-------| Application | |
522 | Server |&lt;--+-MS Control-+--+
523 +-------------+
524
525 Figure 7: Hybrid Query MRB - MS Hosted
526
527 In this example, the MRB has collapsed and is co-hosted by the Media
528 Server. The Media Server Consumer interface is still available to
529 the Application Servers (1) to query Media Server resources. The
530 Media Server Publish interface has collapsed onto the Media Server.
531 It might still exist within the Media Server/MRB interaction, but
532 this is an implementation issue. This type of deployment suits a
533 single Media Server environment, but it should be noted that a Media
534 Server Publish interface could then be offered from the hybrid if
535 required. A typical use case scenario for such a topology would be a
536 single Media Server representing a pool of MSs in a cluster. In this
537 case, the MRB would actually be handling a cluster of Media Servers,
538 rather than one.
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556 <span class="grey">Boulton, et al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
559
560
561 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. In-Line MRB</span>
562
563 The "In-line" MRB is architecturally different from the "Query" model
564 discussed in the previous section. The concept of a separate query
565 disappears. The client of the MRB simply uses the media resource
566 control and media dialog signaling to involve the MRB. This type of
567 deployment is illustrated in Figure 8.
568
569 +-------&lt;----------+----&lt;-------+---+
570 | | (1) | |
571 | | | |
572 | +---+--+--+---+ | |
573 | | Media | | |
574 | +------&gt;| Server | | |
575 | |(3) +-------------+ | |
576 | | (1)| |
577 +---+--+--+---+ | | +---+-----+---+ | |
578 | Application | (2) +---+--V--+---+ (3) | Media | | |
579 | Server |-----&gt;| MRB |-----&gt;| Server |-&gt;-+ |
580 +-------------+ +---+-----+---+ +-------------+ |
581 | |
582 | (3) +---+-----+---+ (1)|
583 +------&gt;| Media | |
584 | Server |---&gt;---+
585 +---+-----+---+
586
587 Figure 8: In-Line MRB
588
589 The Media Servers still use the Media Server Publish interface to
590 convey capabilities and resources to the MRB, as illustrated by (1).
591 The Media Server Control Channels (and media dialogs as well, if
592 required) are sent to the MRB (2), which then selects an appropriate
593 Media Server (3) and remains in the signaling path between the
594 Application Server and the Media Server resources.
595
596 The In-line MRB can be split into two distinct logical roles that can
597 be applied on a per-request basis. They are:
598
599 In-line Unaware MRB Mode (IUMM): Allows an MRB to act on behalf of
600 clients requiring media services who are not aware of an MRB or
601 its operation. In this case, the Application Server does not
602 provide explicit information on the kind of Media Server resource
603 it needs (as in <a href="#section-5.2">Section 5.2</a>), and the MRB is left to deduce it by
604 potentially inspecting other information in the request from the
605 Application Server (for example, Session Description Protocol
606 (SDP) content, or address of the requesting Application Server, or
607 additional Request-URI parameters as per <a href="./rfc4240">RFC 4240</a> [<a href="./rfc4240" title="&quot;Basic Network Media Services with SIP&quot;">RFC4240</a>]).
608
609
610
611
612 <span class="grey">Boulton, et al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
615
616
617 In-line Aware MRB Mode (IAMM): Allows an MRB to act on behalf of
618 clients requiring media services who are aware of an MRB and its
619 operation. In particular, it allows the Application Server to
620 explicitly convey matching characteristics to those provided by
621 Media Servers, as does the Query MRB mode (as in <a href="#section-5.2">Section 5.2</a>).
622
623 In either of the previously described roles, signaling as specified
624 by the Media Control Channel Framework ([<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>]) would be involved,
625 and the MRB would deduce that the selected Media Server resources are
626 no longer needed when the Application Server or Media Server
627 terminates the corresponding SIP dialog. The two modes are discussed
628 in more detail in <a href="#section-5.3">Section 5.3</a>.
629
630 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. MRB Interface Definitions</span>
631
632 The intention of this specification is to provide a toolkit for a
633 variety of deployment architectures where media resource brokering
634 can take place. Two main interfaces are required to support the
635 differing requirements. The two interfaces are described in the
636 remainder of this section and have been named the Media Server
637 Resource Publish and Media Server Resource Consumer interfaces.
638
639 It is beyond the scope of this document to define exactly how to
640 construct an MRB using the interfaces described. It is, however,
641 important that the two interfaces are complimentary so that
642 development of appropriate MRB functionality is supported.
643
644 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Media Server Resource Publish Interface</span>
645
646 The Media Server Resource Publish interface is responsible for
647 providing an MRB with appropriate Media Server resource information.
648 As such, this interface is assumed to provide both general and
649 specific details related to Media Server resources. This information
650 needs to be conveyed using an industry standard mechanism to provide
651 increased levels of adoption and interoperability. A Control Package
652 for the Media Control Channel Framework will be specified to fulfill
653 this interface requirement. It provides an establishment and
654 monitoring mechanism to enable a Media Server to report appropriate
655 statistics to an MRB. The Publish interface is used with both the
656 Query mode and In-line mode of MRB operation.
657
658 As already discussed in <a href="#section-1">Section 1</a>, the MRB view of Media Server
659 resource availability will in reality be approximate -- i.e., partial
660 and imperfect. The MRB Publish interface does not provide an
661 exhaustive view of current Media Server resource consumption; the
662 Media Server may in some cases provide a best-effort computed view of
663 resource consumption parameters conveyed in the Publish interface
664 (e.g., Digital Signal Processors (DSPs) with a fixed number of
665
666
667
668 <span class="grey">Boulton, et al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
671
672
673 streams versus Graphics Processing Units (GPUs) with CPU
674 availability). Media resource information may only be reported
675 periodically over the Publish interface to an MRB.
676
677 It is also worth noting that while the scope of the MRB is in
678 providing interested Application Servers with the available
679 resources, the MRB also allows for the retrieval of information about
680 consumed resources. While this is of course a relevant piece of
681 information (e.g., for monitoring purposes), such functionality
682 inevitably raises security considerations, and implementations should
683 take this into account. See <a href="#section-12">Section 12</a> for more details.
684
685 The MRB Publish interface uses the Media Control Channel Framework
686 ([<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>]) as the basis for interaction between a Media Server and
687 an MRB. The Media Control Channel Framework uses an extension
688 mechanism to allow specific usages that are known as Control
689 Packages. <a href="#section-5.1.1">Section 5.1.1</a> defines the Control Package that MUST be
690 implemented by any Media Server wanting to interact with an MRB
691 entity.
692
693 <span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>. Control Package Definition</span>
694
695 This section fulfills the requirement for information that must be
696 specified during the definition of a Control Framework package, as
697 detailed in <a href="./rfc6230#section-8">Section&nbsp;8 of [RFC6230]</a>.
698
699 <span class="h5"><a class="selflink" id="section-5.1.1.1" href="#section-5.1.1.1">5.1.1.1</a>. Control Package Name</span>
700
701 The Media Channel Control Framework requires a Control Package
702 definition to specify and register a unique name and version.
703
704 The name and version of this Control Package is "mrb-publish/1.0".
705
706 <span class="h5"><a class="selflink" id="section-5.1.1.2" href="#section-5.1.1.2">5.1.1.2</a>. Framework Message Usage</span>
707
708 The MRB Publish interface allows a Media Server to convey available
709 capabilities and resources to an MRB entity.
710
711 This package defines XML elements in <a href="#section-5.1.2">Section 5.1.2</a> and provides an
712 XML schema in <a href="#section-10">Section 10</a>.
713
714 The XML elements in this package are split into requests, responses,
715 and event notifications. Requests are carried in CONTROL message
716 bodies; the &lt;mrbrequest&gt; element is defined as a package request.
717 This request can be used for creating new subscriptions and updating/
718 removing existing subscriptions. Event notifications are also
719 carried in CONTROL message bodies; the &lt;mrbnotification&gt; element is
720
721
722
723
724 <span class="grey">Boulton, et al. Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
727
728
729 defined for package event notifications. Responses are carried
730 either in REPORT message or Control Framework 200 response bodies;
731 the &lt;mrbresponse&gt; element is defined as a package-level response.
732
733 Note that package responses are different from framework response
734 codes. Framework error response codes (see <a href="./rfc6230#section-7">Section&nbsp;7 of [RFC6230]</a>)
735 are used when the request or event notification is invalid; for
736 example, a request has invalid XML (400) or is not understood (500).
737 Package-level responses are carried in framework 200 response or
738 REPORT message bodies. This package's response codes are defined in
739 <a href="#section-5.1.4">Section 5.1.4</a>.
740
741 <span class="h5"><a class="selflink" id="section-5.1.1.3" href="#section-5.1.1.3">5.1.1.3</a>. Common XML Support</span>
742
743 The Media Control Channel Framework [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>] requires a Control
744 Package definition to specify if the attributes for media dialog or
745 conference references are required.
746
747 The Publish interface defined in <a href="#section-10">Section 10</a> does import and make use
748 of the common XML schema defined in the Media Control Channel
749 Framework.
750
751 The Consumer interface defined in <a href="#section-11">Section 11</a> does import and make use
752 of the common XML schema defined in the Media Control Channel
753 Framework.
754
755 <span class="h5"><a class="selflink" id="section-5.1.1.4" href="#section-5.1.1.4">5.1.1.4</a>. CONTROL Message Body</span>
756
757 A valid CONTROL message body MUST conform to the schema defined in
758 <a href="#section-10">Section 10</a> and described in <a href="#section-5.1.2">Section 5.1.2</a>. XML messages appearing in
759 CONTROL messages MUST contain either an &lt;mrbrequest&gt; or
760 &lt;mrbnotification&gt; element.
761
762 <span class="h5"><a class="selflink" id="section-5.1.1.5" href="#section-5.1.1.5">5.1.1.5</a>. REPORT Message Body</span>
763
764 A valid REPORT message body MUST conform to the schema defined in
765 <a href="#section-10">Section 10</a> and described in <a href="#section-5.1.2">Section 5.1.2</a>. XML messages appearing in
766 REPORT messages MUST contain an &lt;mrbresponse&gt; element.
767
768 <span class="h5"><a class="selflink" id="section-5.1.1.6" href="#section-5.1.1.6">5.1.1.6</a>. Audit</span>
769
770 The 'mrb-publish/1.0' Media Control Channel Framework package does
771 not require any additional auditing capability.
772
773
774
775
776
777
778
779
780 <span class="grey">Boulton, et al. Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
783
784
785 <span class="h4"><a class="selflink" id="section-5.1.2" href="#section-5.1.2">5.1.2</a>. Element Definitions</span>
786
787 This section defines the XML elements for the Publish interface Media
788 Control Channel package defined in <a href="#section-5.1">Section 5.1</a>. The formal XML
789 schema definition for the Publish interface can be found in
790 <a href="#section-10">Section 10</a>.
791
792 The root element is &lt;mrbpublish&gt;. All other XML elements (requests,
793 responses, notifications) are contained within it. The MRB Publish
794 interface request element is detailed in <a href="#section-5.1.3">Section 5.1.3</a>. The MRB
795 Publish interface notification element is detailed in <a href="#section-5.1.5">Section 5.1.5</a>.
796 The MRB Publish interface response element is detailed in
797 <a href="#section-5.1.4">Section 5.1.4</a>.
798
799 The &lt;mrbpublish&gt; element has the following attributes:
800
801 version: a token specifying the mrb-publish package version. The
802 value is fixed as '1.0' for this version of the package. The
803 attribute MUST be present.
804
805 The &lt;mrbpublish&gt; element has the following child elements, and there
806 MUST NOT be more than one such child element in any &lt;mrbpublish&gt;
807 message:
808
809 &lt;mrbrequest&gt; for sending an MRB request. See <a href="#section-5.1.3">Section 5.1.3</a>.
810
811 &lt;mrbresponse&gt; for sending an MRB response. See <a href="#section-5.1.4">Section 5.1.4</a>.
812
813 &lt;mrbnotification&gt; for sending an MRB notification. See
814 <a href="#section-5.1.5">Section 5.1.5</a>.
815
816 <span class="h4"><a class="selflink" id="section-5.1.3" href="#section-5.1.3">5.1.3</a>. &lt;mrbrequest&gt;</span>
817
818 This section defines the &lt;mrbrequest&gt; element used to initiate
819 requests from an MRB to a Media Server. The element describes
820 information relevant for the interrogation of a Media Server.
821
822 The &lt;mrbrequest&gt; element has no defined attributes.
823
824 The &lt;mrbrequest&gt; element has the following child element:
825
826 &lt;subscription&gt; for initiating a subscription to a Media Server
827 from an MRB. See <a href="#section-5.1.3.1">Section 5.1.3.1</a>.
828
829
830
831
832
833
834
835
836 <span class="grey">Boulton, et al. Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
839
840
841 <span class="h5"><a class="selflink" id="section-5.1.3.1" href="#section-5.1.3.1">5.1.3.1</a>. &lt;subscription&gt;</span>
842
843 The &lt;subscription&gt; element is included in a request from an MRB to a
844 Media Server to provide the details relating to the configuration of
845 updates (known as a subscription session). This element can be used
846 either to request a new subscription or to update an existing one
847 (e.g., to change the frequency of the updates), and to remove ongoing
848 subscriptions as well (e.g., to stop an indefinite update). The MRB
849 will inform the Media Server regarding how long it wishes to receive
850 updates and the frequency that updates should be sent. Updates
851 related to the subscription are sent using the &lt;mrbnotification&gt;
852 element.
853
854 The &lt;subscription&gt; element has the following attributes:
855
856 id: Indicates a unique token representing the subscription session
857 between the MRB and the Media Server. The attribute MUST be
858 present.
859
860 seqnumber: Indicates a sequence number to be used in conjunction
861 with the subscription session ID to identify a specific
862 subscription command. The first subscription MUST contain a
863 non-zero number 'seqnumber', and subsequent subscriptions MUST
864 contain a higher number than the previous 'seqnumber' value. If a
865 subsequent 'seqnumber' is not higher, a 405 response code is
866 generated as per <a href="#section-5.1.4">Section 5.1.4</a>. The attribute MUST be present.
867
868 action: Provides the operation that should be carried out on the
869 subscription:
870
871 * The value of 'create' instructs the Media Server to attempt to
872 set up a new subscription.
873
874 * The value of 'update' instructs the Media Server to attempt to
875 update an existing subscription.
876
877 * The value of 'remove' instructs the Media Server to attempt to
878 remove an existing subscription and consequently stop any
879 ongoing related notification.
880
881 The attribute MUST be present.
882
883
884
885
886
887
888
889
890
891
892 <span class="grey">Boulton, et al. Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
895
896
897 The &lt;subscription&gt; element has zero or more of the following child
898 elements:
899
900 &lt;expires&gt;: Provides the amount of time in seconds that a
901 subscription should be installed for notifications at the Media
902 Server. Once the amount of time has passed, the subscription
903 expires, and the MRB has to subscribe again if it is still
904 interested in receiving notifications from the Media Server. The
905 element MAY be present.
906
907 &lt;minfrequency&gt;: Provides the minimum frequency in seconds that the
908 MRB wishes to receive notifications from the Media Server. The
909 element MAY be present.
910
911 &lt;maxfrequency&gt;: Provides the maximum frequency in seconds that the
912 MRB wishes to receive notifications from the Media Server. The
913 element MAY be present.
914
915 Please note that these three optional pieces of information provided
916 by the MRB only act as a suggestion: the Media Server MAY change the
917 proposed values if it considers the suggestions unacceptable (e.g.,
918 if the MRB has requested a notification frequency that is too high).
919 In such a case, the request would not fail, but the updated,
920 acceptable values would be reported in the &lt;mrbresponse&gt; accordingly.
921
922 <span class="h4"><a class="selflink" id="section-5.1.4" href="#section-5.1.4">5.1.4</a>. &lt;mrbresponse&gt;</span>
923
924 Responses to requests are indicated by an &lt;mrbresponse&gt; element.
925
926 The &lt;mrbresponse&gt; element has the following attributes:
927
928 status: numeric code indicating the response status. The attribute
929 MUST be present.
930
931 reason: string specifying a reason for the response status. The
932 attribute MAY be present.
933
934 The &lt;mrbresponse&gt; element has a single child element:
935
936 &lt;subscription&gt; for providing details related to a subscription
937 requested by a Media Server (see below in this section).
938
939
940
941
942
943
944
945
946
947
948 <span class="grey">Boulton, et al. Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
951
952
953 The following status codes are defined for 'status':
954
955 +-----------+-------------------------------------------------------+
956 | code | description |
957 +-----------+-------------------------------------------------------+
958 | 200 | OK |
959 | | |
960 | 400 | Syntax error |
961 | | |
962 | 401 | Unable to create Subscription |
963 | | |
964 | 402 | Unable to update Subscription |
965 | | |
966 | 403 | Unable to remove Subscription |
967 | | |
968 | 404 | Subscription does not exist |
969 | | |
970 | 405 | Wrong sequence number |
971 | | |
972 | 406 | Subscription already exists |
973 | | |
974 | 420 | Unsupported attribute or element |
975 +-----------+-------------------------------------------------------+
976
977 Table 1: &lt;mrbresponse&gt; Status Codes
978
979 If a new subscription request made by an MRB (action='create') has
980 been accepted, the Media Server MUST reply with an &lt;mrbresponse&gt; with
981 status code 200. The same rule applies whenever a request to update
982 (action='update') or remove (action='remove') an existing transaction
983 can be fulfilled by the Media Server.
984
985 A subscription request, nevertheless, may fail for several reasons.
986 In such a case, the status codes defined in Table 1 must be used
987 instead. Specifically, if the Media Server fails to handle a request
988 due to a syntax error in the request itself (e.g., incorrect XML,
989 violation of the schema constraints, or invalid values in any of the
990 attributes/elements), the Media Server MUST reply with an
991 &lt;mrbresponse&gt; with status code 400. If a syntactically correct
992 request fails because the request also includes any attribute/element
993 the Media Server doesn't understand, the Media Server MUST reply with
994 an &lt;mrbresponse&gt; with status code 420. If a syntactically correct
995 request fails because the MRB wants to create a new subscription, but
996 the provided unique 'id' for the subscription already exists, the
997 Media Server MUST reply with an &lt;mrbresponse&gt; with status code 406.
998 If a syntactically correct request fails because the MRB wants to
999 update/remove a subscription that doesn't exist, the Media Server
1000 MUST reply with an &lt;mrbresponse&gt; with status code 404. If the Media
1001
1002
1003
1004 <span class="grey">Boulton, et al. Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1007
1008
1009 Server is unable to accept a request for any other reason (e.g., the
1010 MRB has no more resources to fulfill the request), the Media Server
1011 MUST reply with an &lt;mrbresponse&gt; with status code 401/402/403,
1012 depending on the action the MRB provided in its request:
1013
1014 o action='create' --&gt; 401;
1015
1016 o action='update' --&gt; 402;
1017
1018 o action='remove' --&gt; 403;
1019
1020 A response to a subscription request that has a status code of 200
1021 indicates that the request is successful. The response MAY also
1022 contain a &lt;subscription&gt; child that describes the subscription. The
1023 &lt;subscription&gt; child MAY contain 'expires', 'minfrequency', and
1024 'maxfrequency' values even if they were not contained in the request.
1025
1026 The Media Server can choose to change the suggested 'expires',
1027 'minfrequency', and 'maxfrequency' values provided by the MRB in its
1028 &lt;mrbrequest&gt; if it considers them unacceptable (e.g., the requested
1029 frequency range is too high). In such a case, the response MUST
1030 contain a &lt;subscription&gt; element describing the subscription as the
1031 Media Server accepted it, and the Media Server MUST include in the
1032 &lt;subscription&gt; element all of those values that it modified relative
1033 to the request, to inform the MRB about the change.
1034
1035 <span class="h4"><a class="selflink" id="section-5.1.5" href="#section-5.1.5">5.1.5</a>. &lt;mrbnotification&gt;</span>
1036
1037 The &lt;mrbnotification&gt; element is included in a request from a Media
1038 Server to an MRB to provide the details relating to current status.
1039 The Media Server will inform the MRB of its current status as defined
1040 by the information in the &lt;subscription&gt; element. Updates are sent
1041 using the &lt;mrbnotification&gt; element.
1042
1043 The &lt;mrbnotification&gt; element has the following attributes:
1044
1045 id: indicates a unique token representing the session between the
1046 MRB and the Media Server and is the same as the one appearing in
1047 the &lt;subscription&gt; element. The attribute MUST be present.
1048
1049 seqnumber: indicates a sequence number to be used in conjunction
1050 with the subscription session ID to identify a specific
1051 notification update. The first notification update MUST contain a
1052 non-zero number 'seqnumber', and subsequent notification updates
1053 MUST contain a higher number than the previous 'seqnumber' value.
1054 If a subsequent 'seqnumber' is not higher, the situation should be
1055
1056
1057
1058
1059
1060 <span class="grey">Boulton, et al. Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1063
1064
1065 considered an error by the entity receiving the notification
1066 update. How the receiving entity deals with this situation is
1067 implementation specific. The attribute MUST be present.
1068
1069 It's important to point out that the 'seqnumber' that appears in an
1070 &lt;mrbnotification&gt; is not related to the 'seqnumber' appearing in a
1071 &lt;subscription&gt;. In fact, the latter is associated with subscriptions
1072 and would increase at every command issued by the MRB, while the
1073 former is associated with the asynchronous notifications the Media
1074 Server would trigger according to the subscription and as such would
1075 increase at every notification message to enable the MRB to keep
1076 track of them.
1077
1078 The following sub-sections provide details of the child elements that
1079 make up the contents of the &lt;mrbnotification&gt; element.
1080
1081 <span class="h5"><a class="selflink" id="section-5.1.5.1" href="#section-5.1.5.1">5.1.5.1</a>. &lt;media-server-id&gt;</span>
1082
1083 The &lt;media-server-id&gt; element provides a unique system-wide
1084 identifier for a Media Server instance. The element MUST be present
1085 and MUST be chosen such that it is extremely unlikely that two
1086 different Media Servers would present the same id to a given MRB.
1087
1088 <span class="h5"><a class="selflink" id="section-5.1.5.2" href="#section-5.1.5.2">5.1.5.2</a>. &lt;supported-packages&gt;</span>
1089
1090 The &lt;supported-packages&gt; element provides the list of Media Control
1091 Channel packages supported by the Media Server. The element MAY be
1092 present.
1093
1094 The &lt;supported-packages&gt; element has no attributes.
1095
1096 The &lt;supported-packages&gt; element has a single child element:
1097
1098 &lt;package&gt;: Gives the name of a package supported by the Media
1099 Server. The &lt;package&gt; element has a single attribute, 'name',
1100 which provides the name of the supported Media Control Channel
1101 Framework package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>.
1102
1103 <span class="h5"><a class="selflink" id="section-5.1.5.3" href="#section-5.1.5.3">5.1.5.3</a>. &lt;active-rtp-sessions&gt;</span>
1104
1105 The &lt;active-rtp-sessions&gt; element provides information detailing the
1106 current active Real-time Transport Protocol (RTP) sessions. The
1107 element MAY be present.
1108
1109 The &lt;active-rtp-sessions&gt; element has no attributes.
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Boulton, et al. Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1119
1120
1121 The &lt;active-rtp-sessions&gt; element has a single child element:
1122
1123 &lt;rtp-codec&gt;: Describes a supported codec and the number of active
1124 sessions using that codec. The &lt;rtp-codec&gt; element has one
1125 attribute. The value of the attribute, 'name', is a media type
1126 (which can include parameters per [<a href="./rfc6381" title="&quot;The 'Codecs' and 'Profiles' Parameters for &quot;">RFC6381</a>]). The &lt;rtp-codec&gt;
1127 element has two child elements. The child element &lt;decoding&gt; has
1128 as content the decimal number of RTP sessions being decoded using
1129 the specified codec, and the child element &lt;encoding&gt; has as
1130 content the decimal number of RTP sessions being encoded using the
1131 specified codec.
1132
1133 <span class="h5"><a class="selflink" id="section-5.1.5.4" href="#section-5.1.5.4">5.1.5.4</a>. &lt;active-mixer-sessions&gt;</span>
1134
1135 The &lt;active-mixer-sessions&gt; element provides information detailing
1136 the current active mixed RTP sessions. The element MAY be present.
1137
1138 The &lt;active-mixer-sessions&gt; element has no attributes.
1139
1140 The &lt;active-mixer-sessions&gt; element has a single child element:
1141
1142 &lt;active-mix&gt;: Describes a mixed active RTP session. The
1143 &lt;active-mix&gt; element has one attribute. The value of the
1144 attribute, 'conferenceid', is the name of the mix. The
1145 &lt;active-mix&gt; element has one child element. The child element,
1146 &lt;rtp-codec&gt;, contains the same information relating to RTP
1147 sessions as that defined in <a href="#section-5.1.5.3">Section 5.1.5.3</a>. The element MAY be
1148 present.
1149
1150 <span class="h5"><a class="selflink" id="section-5.1.5.5" href="#section-5.1.5.5">5.1.5.5</a>. &lt;non-active-rtp-sessions&gt;</span>
1151
1152 The &lt;non-active-rtp-sessions&gt; element provides information detailing
1153 the currently available inactive RTP sessions, that is, how many more
1154 RTP streams this Media Server can support. The element MAY be
1155 present.
1156
1157 The &lt;non-active-rtp-sessions&gt; element has no attributes.
1158
1159 The &lt;non-active-rtp-sessions&gt; element has a single child element:
1160
1161 &lt;rtp-codec&gt;: Describes a supported codec and the number of
1162 non-active sessions for that codec. The &lt;rtp-codec&gt; element has
1163 one attribute. The value of the attribute, 'name', is a media
1164 type (which can include parameters per [<a href="./rfc6381" title="&quot;The 'Codecs' and 'Profiles' Parameters for &quot;">RFC6381</a>]). The
1165 &lt;rtp-codec&gt; element has two child elements. The child element
1166 &lt;decoding&gt; has as content the decimal number of RTP sessions
1167
1168
1169
1170
1171
1172 <span class="grey">Boulton, et al. Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1175
1176
1177 available for decoding using the specified codec, and the child
1178 element &lt;encoding&gt; has as content the decimal number of RTP
1179 sessions available for encoding using the specified codec.
1180
1181 <span class="h5"><a class="selflink" id="section-5.1.5.6" href="#section-5.1.5.6">5.1.5.6</a>. &lt;non-active-mixer-sessions&gt;</span>
1182
1183 The &lt;non-active-mixer-sessions&gt; element provides information
1184 detailing the current inactive mixed RTP sessions, that is, how many
1185 more mixing sessions this Media Server can support. The element MAY
1186 be present.
1187
1188 The &lt;non-active-mixer-sessions&gt; element has no attributes.
1189
1190 The &lt;non-active-mixer-sessions&gt; element has a single child element:
1191
1192 &lt;non-active-mix&gt;: Describes available mixed RTP sessions. The
1193 &lt;non-active-mix&gt; element has one attribute. The value of the
1194 attribute, 'available', is the number of mixes that could be used
1195 using that profile. The &lt;non-active-mix&gt; element has one child
1196 element. The child element, &lt;rtp-codec&gt;, contains the same
1197 information relating to RTP sessions as that defined in
1198 <a href="#section-5.1.5.5">Section 5.1.5.5</a>. The element MAY be present.
1199
1200 <span class="h5"><a class="selflink" id="section-5.1.5.7" href="#section-5.1.5.7">5.1.5.7</a>. &lt;media-server-status&gt;</span>
1201
1202 The &lt;media-server-status&gt; element provides information detailing the
1203 current status of the Media Server. The element MUST be present. It
1204 can return one of the following values:
1205
1206 active: Indicates that the Media Server is available for service.
1207
1208 deactivated: Indicates that the Media Server has been withdrawn from
1209 service, and as such requests should not be sent to it before it
1210 becomes 'active' again.
1211
1212 unavailable: Indicates that the Media Server continues to process
1213 past requests but cannot accept new requests, and as such should
1214 not be contacted before it becomes 'active' again.
1215
1216 The &lt;media-server-status&gt; element has no attributes.
1217
1218 The &lt;media-server-status&gt; element has no child elements.
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Boulton, et al. Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1231
1232
1233 <span class="h5"><a class="selflink" id="section-5.1.5.8" href="#section-5.1.5.8">5.1.5.8</a>. &lt;supported-codecs&gt;</span>
1234
1235 The &lt;supported-codecs&gt; element provides information detailing the
1236 current codecs supported by a Media Server and associated actions.
1237 The element MAY be present.
1238
1239 The &lt;supported-codecs&gt; element has no attributes.
1240
1241 The &lt;supported-codecs&gt; element has a single child element:
1242
1243 &lt;supported-codec&gt;: Has a single attribute, 'name', which provides
1244 the name of the codec about which this element provides
1245 information. A valid value is a media type that, depending on its
1246 definition, can include additional parameters (e.g., [<a href="./rfc6381" title="&quot;The 'Codecs' and 'Profiles' Parameters for &quot;">RFC6381</a>]).
1247 The &lt;supported-codec&gt; element then has a further child element,
1248 &lt;supported-codec-package&gt;. The &lt;supported-codec-package&gt; element
1249 has a single attribute, 'name', which provides the name of the
1250 Media Control Channel Framework package, compliant with
1251 <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for which the codec support applies.
1252 The &lt;supported-codec-package&gt; element has zero or more
1253 &lt;supported-action&gt; children, each one of which describes an action
1254 that a Media Server can apply to this codec:
1255
1256 * 'decoding', meaning a decoder for this codec is available;
1257
1258 * 'encoding', meaning an encoder for this codec is available;
1259
1260 * 'passthrough', meaning the Media Server is able to pass a
1261 stream encoded using that codec through, without re-encoding.
1262
1263 <span class="h5"><a class="selflink" id="section-5.1.5.9" href="#section-5.1.5.9">5.1.5.9</a>. &lt;application-data&gt;</span>
1264
1265 The &lt;application-data&gt; element provides an arbitrary string of
1266 characters as application-level data. This data is meant to only
1267 have meaning at the application-level logic and as such is not
1268 otherwise restricted by this specification. The set of allowed
1269 characters is the same as those in XML (viz., tab, carriage return,
1270 line feed, and the legal characters of Unicode and ISO/IEC 10646
1271 [<a href="#ref-ISO.10646.2012">ISO.10646.2012</a>] (see also <a href="#section-2.2">Section 2.2</a> of
1272 &lt;<a href="http://www.w3.org/TR/xml/">http://www.w3.org/TR/xml/</a>&gt;)). The element MAY be present.
1273
1274 The &lt;application-data&gt; element has no attributes.
1275
1276 The &lt;application-data&gt; element has no child elements.
1277
1278
1279
1280
1281
1282
1283
1284 <span class="grey">Boulton, et al. Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1287
1288
1289 <span class="h5"><a class="selflink" id="section-5.1.5.10" href="#section-5.1.5.10">5.1.5.10</a>. &lt;file-formats&gt;</span>
1290
1291 The &lt;file-formats&gt; element provides a list of file formats supported
1292 for the purpose of playing media. The element MAY be present.
1293
1294 The &lt;file-formats&gt; element has no attributes.
1295
1296 The &lt;file-formats&gt; element has zero of more the following child
1297 elements:
1298
1299 &lt;supported-format&gt;: Has a single attribute, 'name', which provides
1300 the type of file format that is supported. A valid value is a
1301 media type that, depending on its definition, can include
1302 additional parameters (e.g., [<a href="./rfc6381" title="&quot;The 'Codecs' and 'Profiles' Parameters for &quot;">RFC6381</a>]). The &lt;supported-format&gt;
1303 element then has a further child element,
1304 &lt;supported-file-package&gt;. The &lt;supported-file-package&gt; element
1305 provides the name of the Media Control Channel Framework package,
1306 compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for which the file
1307 format support applies.
1308
1309 <span class="h5"><a class="selflink" id="section-5.1.5.11" href="#section-5.1.5.11">5.1.5.11</a>. &lt;max-prepared-duration&gt;</span>
1310
1311 The &lt;max-prepared-duration&gt; element provides the maximum amount of
1312 time a media dialog will be kept in the prepared state before timing
1313 out (see <a href="./rfc6231#section-4.4.2.2.6">Section&nbsp;4.4.2.2.6 of RFC 6231</a> [<a href="./rfc6231" title="&quot;An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework&quot;">RFC6231</a>]. The element MAY be
1314 present.
1315
1316 The &lt;max-prepared-duration&gt; element has no attributes.
1317
1318 The &lt;max-prepared-duration&gt; element has a single child element:
1319
1320 &lt;max-time&gt;: Has a single attribute, 'max-time-seconds', which
1321 provides the amount of time in seconds that a media dialog can be
1322 in the prepared state. The &lt;max-time&gt; element then has a further
1323 child element, &lt;max-time-package&gt;. The &lt;max-time-package&gt; element
1324 provides the name of the Media Control Channel Framework package,
1325 compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for which the time
1326 period applies.
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340 <span class="grey">Boulton, et al. Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1343
1344
1345 <span class="h5"><a class="selflink" id="section-5.1.5.12" href="#section-5.1.5.12">5.1.5.12</a>. &lt;dtmf-support&gt;</span>
1346
1347 The &lt;dtmf-support&gt; element specifies the supported methods to detect
1348 Dual-Tone Multi-Frequency (DTMF) tones and to generate them. The
1349 element MAY be present.
1350
1351 The &lt;dtmf-support&gt; element has no attributes.
1352
1353 The &lt;dtmf-support&gt; element has zero of more of the following child
1354 elements:
1355
1356 &lt;detect&gt;: Indicates the support for DTMF detection. The &lt;detect&gt;
1357 element has no attributes. The &lt;detect&gt; element then has a
1358 further child element, &lt;dtmf-type&gt;. The &lt;dtmf-type&gt; element has
1359 two attributes: 'name' and 'package'. The 'name' attribute
1360 provides the type of DTMF being used, and it can only be a case-
1361 insensitive string containing either '<a href="./rfc4733">RFC4733</a>' [<a href="./rfc4733" title="&quot;RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals&quot;">RFC4733</a>] or
1362 'Media' (detecting tones as signals from the audio stream). The
1363 'package' attribute provides the name of the Media Control Channel
1364 Framework package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for
1365 which the DTMF type applies.
1366
1367 &lt;generate&gt;: Indicates the support for DTMF generation. The
1368 &lt;generate&gt; element has no attributes. The &lt;generate&gt; element then
1369 has a further child element, &lt;dtmf-type&gt;. The &lt;dtmf-type&gt; element
1370 has two attributes: 'name' and 'package'. The 'name' attribute
1371 provides the type of DTMF being used, and it can only be a case-
1372 insensitive string containing either '<a href="./rfc4733">RFC4733</a>' [<a href="./rfc4733" title="&quot;RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals&quot;">RFC4733</a>] or
1373 'Media' (generating tones as signals in the audio stream). The
1374 'package' attribute provides the name of the Media Control Channel
1375 Framework package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for
1376 which the DTMF type applies.
1377
1378 &lt;passthrough&gt;: Indicates the support for passing DTMF through
1379 without re-encoding. The &lt;passthrough&gt; element has no attributes.
1380 The &lt;passthrough&gt; element then has a further child element,
1381 &lt;dtmf-type&gt;. The &lt;dtmf-type&gt; element has two attributes: 'name'
1382 and 'package'. The 'name' attribute provides the type of DTMF
1383 being used, and it can only be a case-insensitive string
1384 containing either '<a href="./rfc4733">RFC4733</a>' [<a href="./rfc4733" title="&quot;RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals&quot;">RFC4733</a>] or 'Media' (passing tones as
1385 signals through the audio stream). The 'package' attribute
1386 provides the name of the Media Control Channel Framework package,
1387 compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for which the DTMF
1388 type applies.
1389
1390
1391
1392
1393
1394
1395
1396 <span class="grey">Boulton, et al. Standards Track [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1399
1400
1401 <span class="h5"><a class="selflink" id="section-5.1.5.13" href="#section-5.1.5.13">5.1.5.13</a>. &lt;mixing-modes&gt;</span>
1402
1403 The &lt;mixing-modes&gt; element provides information about the support for
1404 audio and video mixing of a Media Server, specifically a list of
1405 supported algorithms to mix audio and a list of supported video
1406 presentation layouts. The element MAY be present.
1407
1408 The &lt;mixing-modes&gt; element has no attributes.
1409
1410 The &lt;mixing-modes&gt; element has zero or more of the following child
1411 elements:
1412
1413 &lt;audio-mixing-modes&gt;: Describes the available algorithms for audio
1414 mixing. The &lt;audio-mixing-modes&gt; element has no attributes. The
1415 &lt;audio-mixing-modes&gt; element has one child element. The child
1416 element, &lt;audio-mixing-mode&gt;, contains a specific available
1417 algorithm. Valid values for the &lt;audio-mixing-mode&gt; element are
1418 algorithm names, e.g., 'nbest' and 'controller' as defined in
1419 [<a href="./rfc6505" title="&quot;A Mixer Control Package for the Media Control Channel Framework&quot;">RFC6505</a>]. The element has a single attribute, 'package'. The
1420 attribute 'package' provides the name of the Media Control Channel
1421 Framework package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for
1422 which the algorithm support applies.
1423
1424 &lt;video-mixing-modes&gt;: Describes the available video presentation
1425 layouts and the supported functionality related to video mixing.
1426 The &lt;video-mixing-modes&gt; element has two attributes: 'vas' and
1427 'activespeakermix'. The 'vas' attribute is of type boolean with a
1428 value of 'true' indicating that the Media Server supports
1429 automatic Voice Activated Switching. The 'activespeakermix' is of
1430 type boolean with a value of 'true' indicating that the Media
1431 Server is able to prepare an additional video stream for the
1432 loudest speaker participant without its contribution. The
1433 &lt;video-mixing-modes&gt; element has one child element. The child
1434 element, &lt;video-mixing-mode&gt;, contains the name of a specific
1435 video presentation layout. The name may refer to one of the
1436 predefined video layouts defined in the XCON conference
1437 information data model [<a href="./rfc6501" title="&quot;Conference Information Data Model for Centralized Conferencing (XCON)&quot;">RFC6501</a>], or to non-XCON layouts as well,
1438 as long as they are properly prefixed according to the schema they
1439 belong to. The &lt;video-mixing-mode&gt; element has a single
1440 attribute, 'package'. The attribute 'package' provides the name
1441 of the Media Control Channel Framework package, compliant with
1442 <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for which the algorithm support
1443 applies.
1444
1445
1446
1447
1448
1449
1450
1451
1452 <span class="grey">Boulton, et al. Standards Track [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1455
1456
1457 <span class="h5"><a class="selflink" id="section-5.1.5.14" href="#section-5.1.5.14">5.1.5.14</a>. &lt;supported-tones&gt;</span>
1458
1459 The &lt;supported-tones&gt; element provides information about which tones
1460 a Media Server is able to play and recognize. In particular, the
1461 support is reported by referring to both support for country codes
1462 (ISO 3166-1 [<a href="#ref-ISO.3166-1">ISO.3166-1</a>]) and supported functionality (ITU-T
1463 Recommendation Q.1950 [<a href="#ref-ITU-T.Q.1950">ITU-T.Q.1950</a>]). The element MAY be present.
1464
1465 The &lt;supported-tones&gt; element has no attributes.
1466
1467 The &lt;supported-tones&gt; element has zero or more of the following child
1468 elements:
1469
1470 &lt;supported-country-codes&gt;: Describes the supported country codes
1471 with respect to tones. The &lt;supported-country-codes&gt; element has
1472 no attributes. The &lt;supported-country-codes&gt; element has one
1473 child element. The child element, &lt;country-code&gt;, reports support
1474 for a specific country code, compliant with the ISO 3166-1
1475 [<a href="#ref-ISO.3166-1">ISO.3166-1</a>] specification. The &lt;country-code&gt; element has a
1476 single attribute, 'package'. The attribute 'package' provides the
1477 name of the Media Control Channel Framework package, compliant
1478 with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, in which the tones from the
1479 specified country code are supported.
1480
1481 &lt;supported-h248-codes&gt;: Describes the supported H.248 codes with
1482 respect to tones. The &lt;supported-h248-codes&gt; element has no
1483 attributes. The &lt;supported-h248-codes&gt; element has one child
1484 element. The child element, &lt;h248-code&gt;, reports support for a
1485 specific H.248 code, compliant with the ITU-T Recommendation
1486 Q.1950 [<a href="#ref-ITU-T.Q.1950">ITU-T.Q.1950</a>] specification. The codes can be either
1487 specific (e.g., cg/dt to only report the Dial Tone from the Call
1488 Progress Tones package) or generic (e.g., cg/* to report all the
1489 tones from the Call Progress Tones package), using wildcards. The
1490 &lt;h248-code&gt; element has a single attribute, 'package'. The
1491 attribute 'package' provides the name of the Media Control Channel
1492 Framework package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, in
1493 which the specified codes are supported.
1494
1495 <span class="h5"><a class="selflink" id="section-5.1.5.15" href="#section-5.1.5.15">5.1.5.15</a>. &lt;file-transfer-modes&gt;</span>
1496
1497 The &lt;file-transfer-modes&gt; element allows the Media Server to specify
1498 which scheme names are supported for transferring files to a Media
1499 Server for each Media Control Channel Framework package type, for
1500 example, whether the Media Server supports fetching resources via
1501 HTTP, HTTPS, NFS, etc. The element MAY be present.
1502
1503 The &lt;file-transfer-modes&gt; element has no attributes.
1504
1505
1506
1507
1508 <span class="grey">Boulton, et al. Standards Track [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1511
1512
1513 The &lt;file-transfer-modes&gt; element has a single child element:
1514
1515 &lt;file-transfer-mode&gt;: Has two attributes: 'name' and 'package'. The
1516 'name' attribute provides the scheme name of the protocol that can
1517 be used for file transfer (e.g., HTTP, HTTPS, NFS, etc.); the
1518 value of the attribute is case insensitive. The 'package'
1519 attribute provides the name of the Media Control Channel Framework
1520 package, compliant with the specification in the related IANA
1521 registry (e.g., "msc-ivr/1.0"), for which the scheme name applies.
1522
1523 It is important to point out that this element provides no
1524 information about whether or not the Media Server supports any flavor
1525 of live streaming: for instance, a value of "HTTP" for the IVR
1526 (Interactive Voice Response) Package would only mean the 'http'
1527 scheme makes sense to the Media Server within the context of that
1528 package. Whether or not the Media Server can make use of HTTP to
1529 only fetch resources, or also to attach an HTTP live stream to a
1530 call, is to be considered implementation specific to the Media Server
1531 and irrelevant to the Application Server and/or MRB. Besides, the
1532 Media Server supporting a scheme does not imply that it also supports
1533 the related secure versions: for instance, if the Media Server
1534 supports both HTTP and HTTPS, both the schemes will appear in the
1535 element. A lack of the "HTTPS" value would need to be interpreted as
1536 a lack of support for the 'https' scheme.
1537
1538 <span class="h5"><a class="selflink" id="section-5.1.5.16" href="#section-5.1.5.16">5.1.5.16</a>. &lt;asr-tts-support&gt;</span>
1539
1540 The &lt;asr-tts-support&gt; element provides information about the support
1541 for Automatic Speech Recognition (ASR) and Text-to-Speech (TTS)
1542 functionality in a Media Server. The functionality is reported by
1543 referring to the supported languages (using ISO 639-1 [<a href="#ref-ISO.639.2002">ISO.639.2002</a>]
1544 codes) regarding both ASR and TTS. The element MAY be present.
1545
1546 The &lt;asr-tts-support&gt; element has no attributes.
1547
1548 The &lt;asr-tts-support&gt; element has zero or more of the following child
1549 elements:
1550
1551 &lt;asr-support&gt;: Describes the available languages for ASR. The
1552 &lt;asr-support&gt; element has no attributes. The &lt;asr-support&gt;
1553 element has one child element. The child element, &lt;language&gt;,
1554 reports that the Media Server supports ASR for a specific
1555 language. The &lt;language&gt; element has a single attribute,
1556 'xml:lang'. The attribute 'xml:lang' contains the ISO 639-1
1557 [<a href="#ref-ISO.639.2002">ISO.639.2002</a>] code of the supported language.
1558
1559
1560
1561
1562
1563
1564 <span class="grey">Boulton, et al. Standards Track [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1567
1568
1569 &lt;tts-support&gt;: Describes the available languages for TTS. The
1570 &lt;tts-support&gt; element has no attributes. The &lt;tts-support&gt;
1571 element has one child element. The child element, &lt;language&gt;,
1572 reports that the Media Server supports TTS for a specific
1573 language. The &lt;language&gt; element has a single attribute,
1574 'xml:lang'. The attribute 'xml:lang' contains the ISO 639-1
1575 [<a href="#ref-ISO.639.2002">ISO.639.2002</a>] code of the supported language.
1576
1577 <span class="h5"><a class="selflink" id="section-5.1.5.17" href="#section-5.1.5.17">5.1.5.17</a>. &lt;vxml-support&gt;</span>
1578
1579 The &lt;vxml-support&gt; element specifies if the Media Server supports
1580 VoiceXML (VXML) and, if it does, through which protocols the support
1581 is exposed (e.g., via the control framework, <a href="./rfc4240">RFC 4240</a> [<a href="./rfc4240" title="&quot;Basic Network Media Services with SIP&quot;">RFC4240</a>], or
1582 <a href="./rfc5552">RFC 5552</a> [<a href="./rfc5552" title="&quot;SIP Interface to VoiceXML Media Services&quot;">RFC5552</a>]). The element MAY be present.
1583
1584 The &lt;vxml-support&gt; element has no attributes.
1585
1586 The &lt;vxml-support&gt; element has a single child element:
1587
1588 &lt;vxml-mode&gt;: Has two attributes: 'package' and 'support'. The
1589 'package' attribute provides the name of the Media Control Channel
1590 Framework package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for
1591 which the VXML support applies. The 'support' attribute provides
1592 the type of VXML support provided by the Media Server (e.g.,
1593 <a href="./rfc5552">RFC 5552</a> [<a href="./rfc5552" title="&quot;SIP Interface to VoiceXML Media Services&quot;">RFC5552</a>], <a href="./rfc4240">RFC 4240</a> [<a href="./rfc4240" title="&quot;Basic Network Media Services with SIP&quot;">RFC4240</a>], or the IVR Package
1594 [<a href="./rfc6231" title="&quot;An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework&quot;">RFC6231</a>]), and valid values are case-insensitive RFC references
1595 (e.g., "<a href="./rfc6231">rfc6231</a>" to specify that the Media Server supports
1596 VoiceXML as provided by the IVR Package [<a href="./rfc6231" title="&quot;An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework&quot;">RFC6231</a>]).
1597
1598 The presence of at least one &lt;vxml-mode&gt; child element would indicate
1599 that the Media Server does support VXML as specified by the child
1600 element itself. An empty &lt;vxml&gt; element would otherwise indicate
1601 that the Media Server does not support VXML at all.
1602
1603 <span class="h5"><a class="selflink" id="section-5.1.5.18" href="#section-5.1.5.18">5.1.5.18</a>. &lt;media-server-location&gt;</span>
1604
1605 The &lt;media-server-location&gt; element provides information about the
1606 civic location of a Media Server. Its description makes use of the
1607 Civic Address Schema standardized in <a href="./rfc5139">RFC 5139</a> [<a href="./rfc5139" title="&quot;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5139</a>]. The element
1608 MAY be present. More precisely, this section is entirely optional,
1609 and it's implementation specific to fill it with just the details
1610 each implementer deems necessary for any optimization that may be
1611 needed.
1612
1613 The &lt;media-server-location&gt; element has no attributes.
1614
1615
1616
1617
1618
1619
1620 <span class="grey">Boulton, et al. Standards Track [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1623
1624
1625 The &lt;media-server-location&gt; element has a single child element:
1626
1627 &lt;civicAddress&gt;: Describes the civic address location of the Media
1628 Server, whose representation refers to <a href="./rfc5139#section-4">Section&nbsp;4 of RFC 5139</a>
1629 [<a href="./rfc5139" title="&quot;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5139</a>].
1630
1631 <span class="h5"><a class="selflink" id="section-5.1.5.19" href="#section-5.1.5.19">5.1.5.19</a>. &lt;label&gt;</span>
1632
1633 The &lt;label&gt; element allows a Media Server to declare a piece of
1634 information that will be understood by the MRB. For example, the
1635 Media Server can declare if it's a blue or green one. It's a string
1636 to allow arbitrary values to be returned to allow arbitrary
1637 classification. The element MAY be present.
1638
1639 The &lt;label&gt; element has no attributes.
1640
1641 The &lt;label&gt; element has no child elements.
1642
1643 <span class="h5"><a class="selflink" id="section-5.1.5.20" href="#section-5.1.5.20">5.1.5.20</a>. &lt;media-server-address&gt;</span>
1644
1645 The &lt;media-server-address&gt; element allows a Media Server to provide a
1646 direct SIP URI where it can be reached (e.g., the URI that the
1647 Application Server would call in order to set up a Control Channel
1648 and relay SIP media dialogs). The element MAY be present.
1649
1650 The &lt;media-server-address&gt; element has no attributes.
1651
1652 The &lt;media-server-address&gt; element has no child elements.
1653
1654 <span class="h5"><a class="selflink" id="section-5.1.5.21" href="#section-5.1.5.21">5.1.5.21</a>. &lt;encryption&gt;</span>
1655
1656 The &lt;encryption&gt; element allows a Media Server to declare support for
1657 encrypting RTP media streams using <a href="./rfc3711">RFC 3711</a> [<a href="./rfc3711" title="&quot;The Secure Real-time Transport Protocol (SRTP)&quot;">RFC3711</a>]. The element
1658 MAY be present. If the element is present, then the Media Server
1659 supports DTLS-SRTP (a Secure Real-time Transport Protocol (SRTP)
1660 extension for Datagram Transport Layer Security (DTLS)) [<a href="./rfc5763" title="&quot;Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)&quot;">RFC5763</a>].
1661
1662 The &lt;encryption&gt; element has no attributes.
1663
1664 The &lt;encryption&gt; element has no child elements.
1665
1666 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Media Service Resource Consumer Interface</span>
1667
1668 The Media Server Consumer interface provides the ability for clients
1669 of an MRB, such as Application Servers, to request an appropriate
1670 Media Server to satisfy specific criteria. This interface allows a
1671 client to pass detailed meta-information to the MRB to help select an
1672 appropriate Media Server. The MRB is then able to make an informed
1673
1674
1675
1676 <span class="grey">Boulton, et al. Standards Track [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1679
1680
1681 decision and provide the client with an appropriate Media Server
1682 resource. The MRB Consumer interface includes both 1) the In-line
1683 Aware MRB Mode (IAMM), which uses the Session Initiation Protocol
1684 (SIP) and 2) the Query mode, which uses the Hypertext Transfer
1685 Protocol (HTTP) [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>]. The MRB Consumer interface does not
1686 include the In-line Unaware Mode (IUMM), which is further explained
1687 in <a href="#section-5.3">Section 5.3</a>. The following sub-sections provide guidance on
1688 using the Consumer interface, which is represented by the
1689 'application/mrb-consumer+xml' media type in <a href="#section-11">Section 11</a>, with HTTP
1690 and SIP.
1691
1692 <span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. Query Mode/HTTP Consumer Interface Usage</span>
1693
1694 An appropriate interface for such a 'query' style interface is in
1695 fact an HTTP usage. Using HTTP and XML combined reduces complexity
1696 and encourages the use of common tools that are widely available in
1697 the industry today. The following information explains the primary
1698 operations required to request and then receive information from an
1699 MRB, by making use of HTTP [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>] and HTTPS [<a href="./rfc2818" title="&quot;HTTP Over TLS&quot;">RFC2818</a>] as transport
1700 for a query for a media resource, and the appropriate response.
1701
1702 The media resource query, as defined by the &lt;mediaResourceRequest&gt;
1703 element from <a href="#section-11">Section 11</a>, MUST be carried in the body of an HTTP/HTTPS
1704 POST request. The media type contained in the HTTP/HTTPS request/
1705 response MUST be 'application/mrb-consumer+xml'. This value MUST be
1706 reflected in the appropriate HTTP headers, such as 'Content-Type' and
1707 'Accept'. The body of the HTTP/HTTPS POST request MUST only contain
1708 an &lt;mrbconsumer&gt; root element with only one child
1709 &lt;mediaResourceRequest&gt; element as defined in <a href="#section-11">Section 11</a>.
1710
1711 The media resource response to a query, as defined by the
1712 &lt;mediaResourceResponse&gt; element from <a href="#section-11">Section 11</a>, MUST be carried in
1713 the body of an HTTP/HTTPS 200 response to the original HTTP/HTTPS
1714 POST request. The media type contained in the HTTP/HTTPS request/
1715 response MUST be 'application/mrb-consumer+xml'. This value MUST be
1716 reflected in the appropriate HTTP headers, such as 'Content-Type' and
1717 'Accept'. The body of the HTTP/HTTPS 200 response MUST only contain
1718 an &lt;mrbconsumer&gt; root element with only one child
1719 &lt;mediaResourceResponse&gt; element as defined in <a href="#section-11">Section 11</a>.
1720
1721 When an Application Server wants to release previously awarded media
1722 resources granted through a prior request/response exchange with an
1723 MRB, it will send a new request with an &lt;action&gt; element with value
1724 'remove', as described in <a href="#section-5.2.3">Section 5.2.3</a> ("Consumer Interface Lease
1725 Mechanism").
1726
1727
1728
1729
1730
1731
1732 <span class="grey">Boulton, et al. Standards Track [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1735
1736
1737 <span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>. In-Line Aware Mode/SIP Consumer Interface Usage</span>
1738
1739 This document provides a complete toolkit for MRB deployment that
1740 includes the ability to interact with an MRB using SIP for the
1741 Consumer interface. The following information explains the primary
1742 operations required to request and then receive information from an
1743 MRB, by making use of SIP [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>] as transport for a request for
1744 media resources, and the appropriate response when using IAMM as the
1745 mode of operation (as discussed in <a href="#section-5.2.2.1">Section 5.2.2.1</a>).
1746
1747 The use of IAMM, besides having the MRB select appropriate media
1748 resources on behalf of a client application, includes setting up
1749 either a Control Framework Control Channel between an Application
1750 Server and one of the Media Servers (<a href="#section-5.2.2.1">Section 5.2.2.1</a>) or a media
1751 dialog session between an Application Server and one of the Media
1752 Servers (<a href="#section-5.2.2.2">Section 5.2.2.2</a>). Note that in either case the SIP URIs of
1753 the selected Media Servers are made known to the requesting
1754 Application Server in the SIP 200 OK response by means of one or more
1755 &lt;media-server-address&gt; child elements in the &lt;response-session-info&gt;
1756 element (<a href="#section-5.2.6">Section 5.2.6</a>).
1757
1758 <span class="h5"><a class="selflink" id="section-5.2.2.1" href="#section-5.2.2.1">5.2.2.1</a>. IAMM and Setting Up a Control Framework Control Channel</span>
1759
1760 The media resource request information, as defined by the
1761 &lt;mediaResourceRequest&gt; element from <a href="#section-11">Section 11</a>, is carried in a SIP
1762 INVITE request. The INVITE request will be constructed as it would
1763 have been to connect to a Media Server, as defined by the Media
1764 Control Channel Framework [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>]. It should be noted that this
1765 specification does not exclude the use of an offerless INVITE as
1766 defined in <a href="./rfc3261">RFC 3261</a> [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>]. Using offerless INVITE messages to an
1767 MRB can potentially cause confusion when applying resource selection
1768 algorithms, and an MRB, like any other SIP device, can choose to
1769 reject with a 4xx response. For an offerless INVITE to be treated
1770 appropriately, additional contextual information would need to be
1771 provided with the request; this is out of scope for this document.
1772 The following additional steps MUST be followed when using the
1773 Consumer interface:
1774
1775 o The Consumer client will include a payload in the SIP INVITE
1776 request of type 'multipart/mixed' [<a href="./rfc2046" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types&quot;">RFC2046</a>]. One of the parts to
1777 be included in the 'multipart/mixed' payload MUST be the
1778 'application/sdp' format, which is constructed as specified in the
1779 Media Control Channel Framework [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>].
1780
1781 o Another part of the 'multipart/mixed' payload MUST be of type
1782 'application/mrb-consumer+xml', as specified in this document and
1783 defined in <a href="#section-11">Section 11</a>. The body part MUST be an XML document
1784 without prolog and whose root element is &lt;mediaResourceRequest&gt;.
1785
1786
1787
1788 <span class="grey">Boulton, et al. Standards Track [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1791
1792
1793 o The INVITE request will then be dispatched to the MRB, as defined
1794 by [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>].
1795
1796 On receiving a SIP INVITE request containing the multipart/mixed
1797 payload as specified previously, the MRB will complete a number of
1798 steps to fulfill the request. It will:
1799
1800 o Extract the multipart MIME payload from the SIP INVITE request.
1801 It will then use the contextual information provided by the client
1802 in the 'application/mrb-consumer+xml' part to determine which
1803 Media Server (or Media Servers, if more than one is deemed to be
1804 needed) should be selected to service the request.
1805
1806 o Extract the 'application/sdp' part from the payload and use it as
1807 the body of a new SIP INVITE request for connecting the client to
1808 one of the selected Media Servers, as defined in the Media Channel
1809 Control Framework [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>]. The policy the MRB follows to pick a
1810 specific Media Server out of the Media Servers it selects is
1811 implementation specific and out of scope for this document. It is
1812 important to configure the SIP elements between the MRB and the
1813 Media Server in such a way that the INVITE will not fork. In the
1814 case of a failure in reaching the chosen Media Server, the MRB
1815 SHOULD proceed to the next one, if available.
1816
1817 If none of the available Media Servers can be reached, the MRB MUST
1818 reply with a SIP 503 error message that includes a Retry-After header
1819 with a non-zero value. The Application Server MUST NOT attempt to
1820 set up a new session before the time that the MRB asked it to wait
1821 has passed.
1822
1823 If at least one Media Server is reachable, the MRB acts as a Back-to-
1824 Back User Agent (B2BUA) that extracts the 'application/
1825 mrb-consumer+xml' information from the SIP INVITE request and then
1826 sends a corresponding SIP INVITE request to the Media Server it has
1827 selected, to negotiate a Control Channel as defined in the Media
1828 Channel Control Framework [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>].
1829
1830 In the case of a failure in negotiating the Control Channel with the
1831 Media Server, the MRB SHOULD proceed to the next one, if available,
1832 as explained above. If none of the available Media Servers can be
1833 reached, or the negotiations of the Control Channel with all of them
1834 fail, the MRB MUST reply with a SIP 503 error message that includes a
1835 Retry-After header with a non-zero value. The Application Server
1836 MUST NOT attempt to set up a new session before the time that the MRB
1837 asked it to wait has expired.
1838
1839
1840
1841
1842
1843
1844 <span class="grey">Boulton, et al. Standards Track [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1847
1848
1849 Once the MRB receives the SIP response from the selected media
1850 resource (i.e., Media Server), it will in turn respond to the
1851 requesting client (i.e., Application Server).
1852
1853 The media resource response generated by an MRB to a request, as
1854 defined by the &lt;mediaResourceResponse&gt; element from <a href="#section-11">Section 11</a>, MUST
1855 be carried in the payload of a SIP 200 OK response to the original
1856 SIP INVITE request. The SIP 200 OK response will be constructed as
1857 it would have been to connect from a Media Server, as defined by the
1858 Media Control Channel Framework [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>]. The following additional
1859 steps MUST be followed when using the Consumer interface:
1860
1861 o Include a payload in the SIP 200 response of type 'multipart/
1862 mixed' as per <a href="./rfc2046">RFC 2046</a> [<a href="./rfc2046" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types&quot;">RFC2046</a>]. One of the parts to be included
1863 in the 'multipart/mixed' payload MUST be the 'application/sdp'
1864 format, which is constructed as specified in the Media Control
1865 Channel Framework [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>] and based on the incoming response
1866 from the selected media resource.
1867
1868 o Another part of the 'multipart/mixed' payload MUST be of type
1869 'application/mrb-consumer+xml', as specified in this document and
1870 defined in <a href="#section-11">Section 11</a>. Only the &lt;mediaResourceResponse&gt; and its
1871 child elements can be included in the payload.
1872
1873 o The SIP 200 response will then be dispatched from the MRB.
1874
1875 o A SIP ACK to the 200 response will then be sent back to the MRB.
1876
1877 Considering that the use of SIP as a transport for Consumer
1878 transactions may result in failure, the IAMM relies on a successful
1879 INVITE transaction to address the previously discussed sequence
1880 (using the 'seq' XML element) increment mechanism. This means that
1881 if the INVITE is unsuccessful for any reason, the Application Server
1882 MUST use the same 'seq' value as previously used for the next
1883 Consumer request that it may want to send to the MRB for the same
1884 session.
1885
1886 An MRB implementation may be programmed to conclude that the
1887 requested resources are no longer needed when it receives a SIP BYE
1888 from the Application Server or Media Server that concludes the SIP
1889 dialog that initiated the request, or when the lease (<a href="#section-5.2.3">Section 5.2.3</a>)
1890 interval expires.
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900 <span class="grey">Boulton, et al. Standards Track [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1903
1904
1905 <span class="h5"><a class="selflink" id="section-5.2.2.2" href="#section-5.2.2.2">5.2.2.2</a>. IAMM and Setting Up a Media Dialog</span>
1906
1907 This scenario is identical to the description in the previous section
1908 for setting up a Control Framework Control Channel, with the
1909 exception that the application/sdp payload conveys content
1910 appropriate for setting up the media dialog to the media resource, as
1911 per <a href="./rfc3261">RFC 3261</a> [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>], instead of setting up a Control Channel.
1912
1913 <span class="h4"><a class="selflink" id="section-5.2.3" href="#section-5.2.3">5.2.3</a>. Consumer Interface Lease Mechanism</span>
1914
1915 The Consumer interface defined in Sections <a href="#section-5.2">5.2</a> and <a href="#section-11">11</a> allows a client
1916 to request an appropriate media resource based on information
1917 included in the request (either an HTTP POST or SIP INVITE message).
1918 In the case of success, the response that is returned to the client
1919 MUST contain a &lt;response-session-info&gt; element in either the SIP 200
1920 or HTTP 200 response. The success response contains the description
1921 of certain resources that have been reserved to a specific Consumer
1922 client in a (new or revised) "resource session", which is identified
1923 in the &lt;response-session-info&gt;. The resource session is a "lease",
1924 in that the reservation is scheduled to expire at a particular time
1925 in the future, releasing the resources to be assigned for other uses.
1926 The lease may be extended or terminated earlier by future Consumer
1927 client requests that identify and reference a specific resource
1928 session.
1929
1930 Before delving into the details of such a lease mechanism, it is
1931 worth clarifying its role within the context of the Consumer
1932 interface. As explained in <a href="#section-5.1">Section 5.1</a>, the knowledge the MRB has of
1933 the resources of all the Media Servers it is provisioned to manage is
1934 not real-time. How an MRB actually manages such resources is
1935 implementation specific -- for example, an implementation may choose
1936 to have the MRB keeping track and state of the allocated resources,
1937 or simply rely on the Media Servers themselves to provide the
1938 information using the Publish interface. Further information may
1939 also be inferred by the signaling, in the case where an MRB is in the
1940 path of media dialogs.
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956 <span class="grey">Boulton, et al. Standards Track [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
1959
1960
1961 The &lt;mediaResourceResponse&gt; element returned from the MRB contains a
1962 &lt;response-session-info&gt; element if the request is successful. The
1963 &lt;response-session-info&gt; element has zero or more of the following
1964 child elements, which provide the appropriate resource session
1965 information:
1966
1967 o &lt;session-id&gt; is a unique identifier that enables a Consumer client
1968 and MRB to correlate future media resource requests related to an
1969 initial media resource request. The &lt;session-id&gt; MUST be included
1970 in all future related requests (see the &lt;session-id&gt; paragraph
1971 later in this section, where constructing a subsequent request is
1972 discussed).
1973
1974 o &lt;seq&gt; is a numeric value returned to the Consumer client. On
1975 issuing any future requests related to the media resource session
1976 (as determined by the &lt;session-id&gt; element), the Consumer client
1977 MUST increment the value returned in the &lt;seq&gt; element and include
1978 it in the request (see the &lt;seq&gt; paragraph later in this section,
1979 where constructing a subsequent request is discussed). Its value
1980 is a non-negative integer that MUST be limited within the
1981 0..2^31-1 range.
1982
1983 o &lt;expires&gt; provides a value indicating the number of seconds that
1984 the request for media resources is deemed alive. The Consumer
1985 client should issue a refresh of the request, as discussed later
1986 in this section, if the expiry is due to fire and the media
1987 resources are still required.
1988
1989 o &lt;media-server-address&gt; provides information representing an
1990 assigned Media Server. More instances of this element may appear
1991 should the MRB assign more Media Servers to a Consumer request.
1992
1993 The &lt;mediaResourceRequest&gt; element is used in subsequent Consumer
1994 interface requests if the client wishes to manipulate the session.
1995 The Consumer client MUST include the &lt;session-info&gt; element, which
1996 enables the receiving MRB to determine an existing media resource
1997 allocation session. The &lt;session-info&gt; element has the following
1998 child elements, which provide the appropriate resource session
1999 information to the MRB:
2000
2001 o &lt;session-id&gt; is a unique identifier that allows a Consumer client
2002 to indicate the appropriate existing media resource session to be
2003 manipulated by the MRB for this request. The value was provided
2004 by the MRB in the initial request for media resources, as
2005 discussed earlier in this section (&lt;session-id&gt; element included
2006 as part of the &lt;session-info&gt; element in the initial
2007 &lt;mediaResourceResponse&gt;).
2008
2009
2010
2011
2012 <span class="grey">Boulton, et al. Standards Track [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2015
2016
2017 o &lt;seq&gt; is a numeric value returned to the Consumer client in the
2018 initial request for media resources, as discussed earlier in this
2019 section (&lt;seq&gt; element included as part of the &lt;session-info&gt;
2020 element in the initial &lt;mediaResourceResponse&gt;). On issuing any
2021 future requests related to the specific media resource session (as
2022 determined by the &lt;session-id&gt; element), the Consumer client MUST
2023 increment the value returned in the &lt;seq&gt; element from the initial
2024 response (contained in the &lt;mediaResourceResponse&gt;) for every new
2025 request. The value of the &lt;seq&gt; element in requests acts as a
2026 counter and when used in conjunction with the unique &lt;session-id&gt;
2027 allows for unique identification of a request. As anticipated
2028 before, the &lt;seq&gt; value is limited to the 0..2^31-1 range: in the
2029 unlikely case that the counter increases to reach the highest
2030 allowed value, the &lt;seq&gt; value MUST be set to 0. The first
2031 numeric value for the &lt;seq&gt; element is not meant to be '1' but
2032 SHOULD be generated randomly by the MRB: this is to reduce the
2033 chances of a malicious MRB disrupting the session created by this
2034 MRB, as explained in <a href="#section-12">Section 12</a>.
2035
2036 o &lt;action&gt; provides the operation to be carried out by the MRB on
2037 receiving the request:
2038
2039 * The value of 'update' is a request by the Consumer client to
2040 update the existing session on the MRB with alternate media
2041 resource requirements. If the requested resource information
2042 is identical to the existing MRB session, the MRB will attempt
2043 a session refresh. If the information has changed, the MRB
2044 will attempt to update the existing session with the new
2045 information. If the operation is successful, the 200 status
2046 code in the response is returned in the status attribute of the
2047 &lt;mediaResourceResponseType&gt; element. If the operation is not
2048 successful, a 409 status code in the response is returned in
2049 the status attribute of the &lt;mediaResourceResponseType&gt;
2050 element.
2051
2052 * The value of 'remove' is a request by the Consumer client to
2053 remove the session on the MRB. This provides a mechanism for
2054 Consumer clients to release unwanted resources before they
2055 expire. If the operation is successful, a 200 status code in
2056 the response is returned in the status attribute of the
2057 &lt;mediaResourceResponseType&gt; element. If the operation is not
2058 successful, a 410 status code in the response is returned in
2059 the status attribute of the &lt;mediaResourceResponseType&gt;
2060 element.
2061
2062 Omitting the 'action' attribute means requesting a new set of
2063 resources.
2064
2065
2066
2067
2068 <span class="grey">Boulton, et al. Standards Track [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2071
2072
2073 When used with HTTP, the &lt;session-info&gt; element MUST be included in
2074 an HTTP POST message (as defined in [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>]). When used with SIP,
2075 the &lt;session-info&gt; element MUST instead be included in either a SIP
2076 INVITE or a SIP re-INVITE (as defined in [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>]), or in a SIP
2077 UPDATE (as defined in [<a href="./rfc3311" title="&quot;The Session Initiation Protocol (SIP) UPDATE Method&quot;">RFC3311</a>]) request: in fact, any SIP dialog, be
2078 it a new or an existing one, can be exploited to carry leasing
2079 information, and as such new SIP INVITE messages can update other
2080 leases as well as request a new one.
2081
2082 With IAMM, the Application Server or Media Server will eventually
2083 send a SIP BYE to end the SIP session, whether it was for a Control
2084 Channel or a media dialog. That BYE contains no Consumer interface
2085 lease information.
2086
2087 <span class="h4"><a class="selflink" id="section-5.2.4" href="#section-5.2.4">5.2.4</a>. &lt;mrbconsumer&gt;</span>
2088
2089 This section defines the XML elements for the Consumer interface.
2090 The formal XML schema definition for the Consumer interface can be
2091 found in <a href="#section-11">Section 11</a>.
2092
2093 The root element is &lt;mrbconsumer&gt;. All other XML elements (requests,
2094 responses) are contained within it. The MRB Consumer interface
2095 request element is detailed in <a href="#section-5.2.5.1">Section 5.2.5.1</a>. The MRB Consumer
2096 interface response element is detailed in <a href="#section-5.2.6.1">Section 5.2.6.1</a>.
2097
2098 The &lt;mrbconsumer&gt; element has the following attributes:
2099
2100 version: a token specifying the mrb-consumer package version. The
2101 value is fixed as '1.0' for this version of the package. The
2102 attribute MUST be present.
2103
2104 The &lt;mrbconsumer&gt; element may have zero or more children of one of
2105 the following child element types:
2106
2107 &lt;mediaResourceRequest&gt; for sending a Consumer request. See
2108 <a href="#section-5.2.5.1">Section 5.2.5.1</a>.
2109
2110 &lt;mediaResourceResponse&gt; for sending a Consumer response. See
2111 <a href="#section-5.2.6.1">Section 5.2.6.1</a>.
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124 <span class="grey">Boulton, et al. Standards Track [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2127
2128
2129 <span class="h4"><a class="selflink" id="section-5.2.5" href="#section-5.2.5">5.2.5</a>. Media Service Resource Request</span>
2130
2131 This section provides the element definitions for use in Consumer
2132 interface requests. The requests are carried in the
2133 &lt;mediaResourceRequest&gt; element.
2134
2135 <span class="h5"><a class="selflink" id="section-5.2.5.1" href="#section-5.2.5.1">5.2.5.1</a>. &lt;mediaResourceRequest&gt;</span>
2136
2137 The &lt;mediaResourceRequest&gt; element provides information for clients
2138 wishing to query an external MRB entity. The &lt;mediaResourceRequest&gt;
2139 element has a single mandatory attribute, 'id': this attribute
2140 contains a random identifier, generated by the client, that will be
2141 included in the response in order to map it to a specific request.
2142 The &lt;mediaResourceRequest&gt; element has &lt;generalInfo&gt;, &lt;ivrInfo&gt;, and
2143 &lt;mixerInfo&gt; as child elements. These three elements are used to
2144 describe the requirements of a client requesting a Media Server and
2145 are covered in Sections <a href="#section-5.2.5.1.1">5.2.5.1.1</a>, <a href="#section-5.2.5.1.2">5.2.5.1.2</a>, and <a href="#section-5.2.5.1.3">5.2.5.1.3</a>,
2146 respectively.
2147
2148 <span class="h6"><a class="selflink" id="section-5.2.5.1.1" href="#section-5.2.5.1.1">5.2.5.1.1</a>. &lt;generalInfo&gt;</span>
2149
2150 The &lt;generalInfo&gt; element provides general Consumer request
2151 information that is neither IVR specific nor mixer specific. This
2152 includes session information that can be used for subsequent requests
2153 as part of the leasing mechanism described in <a href="#section-5.2.3">Section 5.2.3</a>. The
2154 following sub-sections describe the &lt;session-info&gt; and &lt;packages&gt;
2155 elements, as used by the &lt;generalInfo&gt; element.
2156
2157 <span class="h6"><a class="selflink" id="section-5.2.5.1.1.1" href="#section-5.2.5.1.1.1">5.2.5.1.1.1</a>. &lt;session-info&gt;</span>
2158
2159 The &lt;session-info&gt; element is included in Consumer requests when an
2160 update is being made to an existing media resource session. The
2161 ability to change and remove an existing media resource session is
2162 described in more detail in <a href="#section-5.2.3">Section 5.2.3</a>. The element MAY be
2163 present.
2164
2165 The &lt;session-info&gt; element has no attributes.
2166
2167 The &lt;session-info&gt; element has zero or more of the following child
2168 elements:
2169
2170 &lt;session-id&gt;: A unique identifier that explicitly references an
2171 existing media resource session on the MRB. The identifier is
2172 included to update the existing session and is described in more
2173 detail in <a href="#section-5.2.3">Section 5.2.3</a>.
2174
2175
2176
2177
2178
2179
2180 <span class="grey">Boulton, et al. Standards Track [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2183
2184
2185 &lt;seq&gt;: Used in association with the &lt;session-id&gt; element in a
2186 subsequent request to update an existing media resource session on
2187 an MRB. The &lt;seq&gt; number is incremented from its original value
2188 returned in response to the initial request for media resources.
2189 Its value is a non-negative integer that MUST be limited within
2190 the 0..2^31-1 range. In the unlikely case that the counter
2191 increases to reach the highest allowed value, the &lt;seq&gt; value MUST
2192 be set to 0. More information about its use is provided in
2193 <a href="#section-5.2.3">Section 5.2.3</a>.
2194
2195 &lt;action&gt;: Provides the operation that should be carried out on an
2196 existing media resource session on an MRB:
2197
2198 * The value of 'update' instructs the MRB to attempt to update
2199 the existing media resource session with the information
2200 contained in the &lt;ivrInfo&gt; and &lt;mixerInfo&gt; elements.
2201
2202 * The value of 'remove' instructs the MRB to attempt to remove
2203 the existing media resource session. More information on its
2204 use is provided in <a href="#section-5.2.3">Section 5.2.3</a>.
2205
2206 <span class="h6"><a class="selflink" id="section-5.2.5.1.1.2" href="#section-5.2.5.1.1.2">5.2.5.1.1.2</a>. &lt;packages&gt;</span>
2207
2208 The &lt;packages&gt; element provides a list of Media Control Channel
2209 Framework compliant packages that are required by the Consumer
2210 client. The element MAY be present.
2211
2212 The &lt;packages&gt; element has no attributes.
2213
2214 The &lt;packages&gt; element has a single child element:
2215
2216 &lt;package&gt;: Contains a string representing the Media Control Channel
2217 Framework package required by the Consumer client. The &lt;package&gt;
2218 element can appear multiple times. A valid value is a Control
2219 Package name compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>.
2220
2221 <span class="h6"><a class="selflink" id="section-5.2.5.1.2" href="#section-5.2.5.1.2">5.2.5.1.2</a>. &lt;ivrInfo&gt;</span>
2222
2223 The &lt;ivrInfo&gt; element provides information for general Consumer
2224 request information that is IVR specific. The following sub-sections
2225 describe the elements of the &lt;ivrInfo&gt; element: &lt;ivr-sessions&gt;,
2226 &lt;file-formats&gt;, &lt;dtmf&gt;, &lt;tones&gt;, &lt;asr-tts&gt;, &lt;vxml&gt;, &lt;location&gt;,
2227 &lt;encryption&gt;, &lt;application-data&gt;, &lt;max-prepared-duration&gt;, and
2228 &lt;file-transfer-modes&gt;.
2229
2230
2231
2232
2233
2234
2235
2236 <span class="grey">Boulton, et al. Standards Track [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2239
2240
2241 <span class="h6"><a class="selflink" id="section-5.2.5.1.2.1" href="#section-5.2.5.1.2.1">5.2.5.1.2.1</a>. &lt;ivr-sessions&gt;</span>
2242
2243 The &lt;ivr-sessions&gt; element indicates the number of IVR sessions that
2244 a Consumer client requires from a media resource. The element MAY be
2245 present.
2246
2247 The &lt;ivr-sessions&gt; element has no attributes.
2248
2249 The &lt;ivr-sessions&gt; element has a single child element:
2250
2251 &lt;rtp-codec&gt;: Describes a required codec and the number of sessions
2252 using that codec. The &lt;rtp-codec&gt; element has one attribute. The
2253 value of the attribute, 'name', is a media type (which can include
2254 parameters per [<a href="./rfc6381" title="&quot;The 'Codecs' and 'Profiles' Parameters for &quot;">RFC6381</a>]). The &lt;rtp-codec&gt; element has two child
2255 elements. The child element &lt;decoding&gt; contains the number of RTP
2256 sessions required for decoding using the specified codec, and the
2257 child element &lt;encoding&gt; contains the number of RTP sessions
2258 required for encoding using the specified codec.
2259
2260 <span class="h6"><a class="selflink" id="section-5.2.5.1.2.2" href="#section-5.2.5.1.2.2">5.2.5.1.2.2</a>. &lt;file-formats&gt;</span>
2261
2262 The &lt;file-formats&gt; element provides a list of file formats required
2263 for the purpose of playing media. It should be noted that this
2264 element describes media types and might better have been named
2265 "media-formats", but due to existing implementations the name
2266 "file-formats" is being used. The element MAY be present.
2267
2268 The &lt;file-formats&gt; element has no attributes.
2269
2270 The &lt;file-formats&gt; element has a single child element:
2271
2272 &lt;required-format&gt;: Has a single attribute, 'name', which provides
2273 the type of file format that is required. A valid value is a
2274 media type that, depending on its definition, can include
2275 additional parameters (e.g., [<a href="./rfc6381" title="&quot;The 'Codecs' and 'Profiles' Parameters for &quot;">RFC6381</a>]). The &lt;required-format&gt;
2276 element then has a further child element, &lt;required-file-package&gt;.
2277 The &lt;required-file-package&gt; element has a single attribute,
2278 'required-file-package-name', which contains the name of the Media
2279 Control Channel Framework package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1
2280 of [RFC6230]</a>, for which the file format support applies.
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292 <span class="grey">Boulton, et al. Standards Track [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2295
2296
2297 <span class="h6"><a class="selflink" id="section-5.2.5.1.2.3" href="#section-5.2.5.1.2.3">5.2.5.1.2.3</a>. &lt;dtmf&gt;</span>
2298
2299 The &lt;dtmf&gt; element specifies the required methods to detect DTMF
2300 tones and to generate them. The element MAY be present.
2301
2302 The &lt;dtmf&gt; element has no attributes.
2303
2304 The &lt;dtmf&gt; element has zero or more of the following child elements:
2305
2306 &lt;detect&gt;: Indicates the required support for DTMF detection. The
2307 &lt;detect&gt; element has no attributes. The &lt;detect&gt; element has a
2308 further child element, &lt;dtmf-type&gt;. The &lt;dtmf-type&gt; element has
2309 two attributes: 'name' and 'package'. The 'name' attribute
2310 provides the type of DTMF required and is a case-insensitive
2311 string containing either '<a href="./rfc4733">RFC4733</a>' [<a href="./rfc4733" title="&quot;RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals&quot;">RFC4733</a>] or 'Media' (detecting
2312 tones as signals from the audio stream). The 'package' attribute
2313 provides the name of the Media Control Channel Framework package,
2314 compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for which the DTMF
2315 type applies.
2316
2317 &lt;generate&gt;: Indicates the required support for DTMF generation. The
2318 &lt;generate&gt; element has no attributes. The &lt;generate&gt; element has
2319 a single child element, &lt;dtmf-type&gt;. The &lt;dtmf-type&gt; element has
2320 two attributes: 'name' and 'package'. The 'name' attribute
2321 provides the type of DTMF required and is a case-insensitive
2322 string containing either '<a href="./rfc4733">RFC4733</a>' [<a href="./rfc4733" title="&quot;RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals&quot;">RFC4733</a>] or 'Media'
2323 (generating tones as signals in the audio stream). The 'package'
2324 attribute provides the name of the Media Control Channel Framework
2325 package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for which the
2326 DTMF type applies.
2327
2328 &lt;passthrough&gt;: Indicates the required support for passing DTMF
2329 through without re-encoding. The &lt;passthrough&gt; element has no
2330 attributes. The &lt;passthrough&gt; element then has a further child
2331 element, &lt;dtmf-type&gt;. The &lt;dtmf-type&gt; element has two attributes:
2332 'name' and 'package'. The 'name' attribute provides the type of
2333 DTMF required and is a case-insensitive string containing either
2334 '<a href="./rfc4733">RFC4733</a>' [<a href="./rfc4733" title="&quot;RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals&quot;">RFC4733</a>] or 'Media' (passing tones as signals through
2335 the audio stream). The 'package' attribute provides the name of
2336 the Media Control Channel Framework package, compliant with
2337 <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for which the DTMF type applies.
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348 <span class="grey">Boulton, et al. Standards Track [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2351
2352
2353 <span class="h6"><a class="selflink" id="section-5.2.5.1.2.4" href="#section-5.2.5.1.2.4">5.2.5.1.2.4</a>. &lt;tones&gt;</span>
2354
2355 The &lt;tones&gt; element provides requested tones that a Media Server must
2356 support for IVR. In particular, the request refers to both support
2357 for country codes (ISO 3166-1 [<a href="#ref-ISO.3166-1">ISO.3166-1</a>]) and requested
2358 functionality (ITU-T Recommendation Q.1950 [<a href="#ref-ITU-T.Q.1950">ITU-T.Q.1950</a>]). The
2359 element MAY be present.
2360
2361 The &lt;tones&gt; element has no attributes.
2362
2363 The &lt;tones&gt; element has zero or more of the following child elements:
2364
2365 &lt;country-codes&gt;: Describes the requested country codes in relation
2366 to tones. The &lt;country-codes&gt; element has no attributes. The
2367 &lt;country-codes&gt; element has one child element. The child element,
2368 &lt;country-code&gt;, requests a specific country code, compliant with
2369 the ISO 3166-1 [<a href="#ref-ISO.3166-1">ISO.3166-1</a>] specification. The &lt;country-code&gt;
2370 element has a single attribute, 'package'. The attribute
2371 'package' provides the name of the Media Control Channel Framework
2372 package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, in which the
2373 tones from the specified country code are requested.
2374
2375 &lt;h248-codes&gt;: Describes the requested H.248 codes in relation to
2376 tones. The &lt;h248-codes&gt; element has no attributes. The
2377 &lt;h248-codes&gt; element has one child element. The child element,
2378 &lt;h248-code&gt;, requests a specific H.248 code, compliant with the
2379 ITU-T Recommendation Q.1950 [<a href="#ref-ITU-T.Q.1950">ITU-T.Q.1950</a>] specification. The
2380 codes can be either specific (e.g., cg/dt to only report the Dial
2381 Tone from the Call Progress Tones package) or generic (e.g., cg/*
2382 to report all the tones from the Call Progress Tones package),
2383 using wildcards. The &lt;h248-code&gt; element has a single attribute,
2384 'package'. The attribute 'package' provides the name of the Media
2385 Control Channel Framework package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1
2386 of [RFC6230]</a>, in which the specified codes are requested.
2387
2388 <span class="h6"><a class="selflink" id="section-5.2.5.1.2.5" href="#section-5.2.5.1.2.5">5.2.5.1.2.5</a>. &lt;asr-tts&gt;</span>
2389
2390 The &lt;asr-tts&gt; element requests information about the support for
2391 Automatic Speech Recognition (ASR) and Text-to-Speech (TTS)
2392 functionality in a Media Server. The functionality is requested by
2393 referring to the supported languages (using ISO 639-1 [<a href="#ref-ISO.639.2002">ISO.639.2002</a>]
2394 codes) in relation to both ASR and TTS. The &lt;asr-tts&gt; element has no
2395 attributes. The &lt;asr-tts&gt; element has zero or more of the following
2396 child elements:
2397
2398 &lt;asr-support&gt;: Describes the available languages for ASR. The
2399 &lt;asr-support&gt; element has no attributes. The &lt;asr-support&gt;
2400 element has one child element. The child element, &lt;language&gt;,
2401
2402
2403
2404 <span class="grey">Boulton, et al. Standards Track [Page 43]</span></pre>
2405 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2406 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2407
2408
2409 requests that the Media Server supports ASR for a specific
2410 language. The &lt;language&gt; element has a single attribute,
2411 'xml:lang'. The attribute 'xml:lang' contains the ISO 639-1
2412 [<a href="#ref-ISO.639.2002">ISO.639.2002</a>] code of the supported language.
2413
2414 &lt;tts-support&gt;: Describes the available languages for TTS. The
2415 &lt;tts-support&gt; element has no attributes. The &lt;tts-support&gt;
2416 element has one child element. The child element, &lt;language&gt;,
2417 requests that the Media Server supports TTS for a specific
2418 language. The &lt;language&gt; element has a single attribute,
2419 'xml:lang'. The attribute 'xml:lang' contains the ISO 639-1
2420 [<a href="#ref-ISO.639.2002">ISO.639.2002</a>] code of the supported language.
2421
2422 <span class="h6"><a class="selflink" id="section-5.2.5.1.2.6" href="#section-5.2.5.1.2.6">5.2.5.1.2.6</a>. &lt;vxml&gt;</span>
2423
2424 The &lt;vxml&gt; element specifies if the Consumer client requires VoiceXML
2425 and, if so, which protocols are supported (e.g., via the control
2426 framework, <a href="./rfc4240">RFC 4240</a> [<a href="./rfc4240" title="&quot;Basic Network Media Services with SIP&quot;">RFC4240</a>], or <a href="./rfc5552">RFC 5552</a> [<a href="./rfc5552" title="&quot;SIP Interface to VoiceXML Media Services&quot;">RFC5552</a>]). The element
2427 MAY be present.
2428
2429 The &lt;vxml&gt; element has a single child element:
2430
2431 &lt;vxml-mode&gt;: Has two attributes: 'package' and 'require'. The
2432 'package' attribute provides the name of the Media Control Channel
2433 Framework package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for
2434 which the VXML support applies. The 'require' attribute specifies
2435 the type of VXML support required by the Consumer client (e.g.,
2436 <a href="./rfc5552">RFC 5552</a> [<a href="./rfc5552" title="&quot;SIP Interface to VoiceXML Media Services&quot;">RFC5552</a>], <a href="./rfc4240">RFC 4240</a> [<a href="./rfc4240" title="&quot;Basic Network Media Services with SIP&quot;">RFC4240</a>], or IVR Package [<a href="./rfc6231" title="&quot;An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework&quot;">RFC6231</a>]),
2437 and valid values are case-insensitive RFC references (e.g.,
2438 "<a href="./rfc6231">rfc6231</a>" to specify that the client requests support for VoiceXML
2439 as provided by the IVR Package [<a href="./rfc6231" title="&quot;An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework&quot;">RFC6231</a>]).
2440
2441 The presence of at least one &lt;vxml&gt; child element would indicate that
2442 the Consumer client requires VXML support as specified by the child
2443 element itself. An empty &lt;vxml&gt; element would otherwise indicate
2444 that the Consumer client does not require VXML support.
2445
2446 <span class="h6"><a class="selflink" id="section-5.2.5.1.2.7" href="#section-5.2.5.1.2.7">5.2.5.1.2.7</a>. &lt;location&gt;</span>
2447
2448 The &lt;location&gt; element requests a civic location for an IVR Media
2449 Server. The request makes use of the Civic Address Schema
2450 standardized in <a href="./rfc5139">RFC 5139</a> [<a href="./rfc5139" title="&quot;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5139</a>]. The element MAY be present.
2451 More precisely, this section is entirely optional and is
2452 implementation specific in its level of population.
2453
2454 The &lt;location&gt; element has no attributes.
2455
2456
2457
2458
2459
2460 <span class="grey">Boulton, et al. Standards Track [Page 44]</span></pre>
2461 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2462 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2463
2464
2465 The &lt;location&gt; element has a single child element:
2466
2467 &lt;civicAddress&gt;: Describes the civic address location of the
2468 requested Media Server, whose representation refers to <a href="./rfc5139#section-4">Section&nbsp;4
2469 of RFC 5139</a> [<a href="./rfc5139" title="&quot;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5139</a>].
2470
2471 <span class="h6"><a class="selflink" id="section-5.2.5.1.2.8" href="#section-5.2.5.1.2.8">5.2.5.1.2.8</a>. &lt;encryption&gt;</span>
2472
2473 The &lt;encryption&gt; element allows a Consumer client to request support
2474 for encrypting RTP media streams using <a href="./rfc3711">RFC 3711</a> [<a href="./rfc3711" title="&quot;The Secure Real-time Transport Protocol (SRTP)&quot;">RFC3711</a>]. The
2475 element MAY be present. If the element is present, then the Media
2476 Server supports DTLS-SRTP [<a href="./rfc5763" title="&quot;Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)&quot;">RFC5763</a>].
2477
2478 The &lt;encryption&gt; element has no attributes.
2479
2480 The &lt;encryption&gt; element has no child elements.
2481
2482 <span class="h6"><a class="selflink" id="section-5.2.5.1.2.9" href="#section-5.2.5.1.2.9">5.2.5.1.2.9</a>. &lt;application-data&gt;</span>
2483
2484 The &lt;application-data&gt; element provides an arbitrary string of
2485 characters as IVR application-level data. This data is meant to only
2486 have meaning at the application-level logic and as such is not
2487 otherwise restricted by this specification. The set of allowed
2488 characters is the same as those in XML (viz., tab, carriage return,
2489 line feed, and the legal characters of Unicode and ISO/IEC 10646
2490 [<a href="#ref-ISO.10646.2012">ISO.10646.2012</a>] (see also <a href="#section-2.2">Section 2.2</a> of
2491 &lt;<a href="http://www.w3.org/TR/xml/">http://www.w3.org/TR/xml/</a>&gt;)). The element MAY be present.
2492
2493 The &lt;application-data&gt; element has no attributes.
2494
2495 The &lt;application-data&gt; element has no child elements.
2496
2497 <span class="h6"><a class="selflink" id="section-5.2.5.1.2.10" href="#section-5.2.5.1.2.10">5.2.5.1.2.10</a>. &lt;max-prepared-duration&gt;</span>
2498
2499 The &lt;max-prepared-duration&gt; element indicates the amount of time
2500 required by the Consumer client representing media dialog preparation
2501 in the system before it is executed. The element MAY be present.
2502
2503 The &lt;max-prepared-duration&gt; element has no attributes.
2504
2505 The &lt;max-prepared-duration&gt; element has a single child element:
2506
2507 &lt;max-time&gt;: Has a single attribute, 'max-time-seconds', which
2508 provides the amount of time in seconds that a media dialog can be
2509 in the prepared state. The &lt;max-time&gt; element then has a further
2510 child element, &lt;max-time-package&gt;. The &lt;max-time-package&gt; element
2511
2512
2513
2514
2515
2516 <span class="grey">Boulton, et al. Standards Track [Page 45]</span></pre>
2517 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
2518 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2519
2520
2521 provides the name of the Media Control Channel Framework package,
2522 compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for which the time
2523 period applies.
2524
2525 <span class="h6"><a class="selflink" id="section-5.2.5.1.2.11" href="#section-5.2.5.1.2.11">5.2.5.1.2.11</a>. &lt;file-transfer-modes&gt;</span>
2526
2527 The &lt;file-transfer-modes&gt; element allows the Consumer client to
2528 specify which scheme names are required for file transfer to a Media
2529 Server for each Media Control Channel Framework package type. For
2530 example, does the Media Server support fetching media resources via
2531 HTTP, HTTPS, NFS, etc.? The element MAY be present.
2532
2533 The &lt;file-transfer-modes&gt; element has no attributes.
2534
2535 The &lt;file-transfer-modes&gt; element has a single child element:
2536
2537 &lt;file-transfer-mode&gt;: Has two attributes: 'name' and 'package'. The
2538 'name' attribute provides the scheme name of the protocol required
2539 for fetching resources: valid values are case-insensitive scheme
2540 names (e.g., HTTP, HTTPS, NFS, etc.). The 'package' attribute
2541 provides the name of the Media Control Channel Framework package,
2542 compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for which the scheme
2543 name applies.
2544
2545 The same considerations relating to file transfer and live streaming
2546 are explained further in <a href="#section-5.1.5.15">Section 5.1.5.15</a> and apply here as well.
2547
2548 <span class="h6"><a class="selflink" id="section-5.2.5.1.3" href="#section-5.2.5.1.3">5.2.5.1.3</a>. &lt;mixerInfo&gt;</span>
2549
2550 The &lt;mixerInfo&gt; element provides information for general Consumer
2551 request information that is mixer specific. The following
2552 sub-sections describe the elements of the &lt;mixerInfo&gt; element:
2553 &lt;mixers&gt;, &lt;file-formats&gt;, &lt;dtmf&gt;, &lt;tones&gt;, &lt;mixing-modes&gt;,
2554 &lt;application-data&gt;, &lt;location&gt;, and &lt;encryption&gt;.
2555
2556 <span class="h6"><a class="selflink" id="section-5.2.5.1.3.1" href="#section-5.2.5.1.3.1">5.2.5.1.3.1</a>. &lt;mixers&gt;</span>
2557
2558 The &lt;mixers&gt; element provides information detailing the required
2559 mixed RTP sessions. The element MAY be present.
2560
2561 The &lt;mixers&gt; element has no attributes.
2562
2563 The &lt;mixers&gt; element has a single child element:
2564
2565 &lt;mix&gt;: Describes the required mixed RTP sessions. The &lt;mix&gt; element
2566 has one attribute. The value of the attribute, 'users', is the
2567 number of participants required in the mix. The &lt;mix&gt; element has
2568
2569
2570
2571
2572 <span class="grey">Boulton, et al. Standards Track [Page 46]</span></pre>
2573 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
2574 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2575
2576
2577 one child element. The child element, &lt;rtp-codec&gt;, contains the
2578 same information relating to RTP sessions as that defined in
2579 <a href="#section-5.1.5.3">Section 5.1.5.3</a>. The element MAY be present.
2580
2581 <span class="h6"><a class="selflink" id="section-5.2.5.1.3.2" href="#section-5.2.5.1.3.2">5.2.5.1.3.2</a>. &lt;file-formats&gt;</span>
2582
2583 The &lt;file-formats&gt; element provides a list of file formats required
2584 by the Consumer client for the purpose of playing media to a mix.
2585 The element MAY be present.
2586
2587 The &lt;file-formats&gt; element has no attributes.
2588
2589 The &lt;file-formats&gt; element has a single child element:
2590
2591 &lt;required-format&gt;: Has a single attribute, 'name', which provides
2592 the type of file format supported. A valid value is a media type
2593 that, depending on its definition, can include additional
2594 parameters (e.g., [<a href="./rfc6381" title="&quot;The 'Codecs' and 'Profiles' Parameters for &quot;">RFC6381</a>]). The &lt;required-format&gt; element has a
2595 child element, &lt;required-file-package&gt;. The
2596 &lt;required-file-package&gt; element contains a single attribute,
2597 'required-file-package-name', which contains the name of the Media
2598 Control Channel Framework package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1
2599 of [RFC6230]</a>, for which the file format support applies.
2600
2601 <span class="h6"><a class="selflink" id="section-5.2.5.1.3.3" href="#section-5.2.5.1.3.3">5.2.5.1.3.3</a>. &lt;dtmf&gt;</span>
2602
2603 The &lt;dtmf&gt; element specifies the required methods to detect DTMF
2604 tones and to generate them in a mix. The element MAY be present.
2605
2606 The &lt;dtmf&gt; element has no attributes.
2607
2608 The &lt;dtmf&gt; element has zero or more of the following child elements:
2609
2610 &lt;detect&gt;: Indicates the required support for DTMF detection. The
2611 &lt;detect&gt; element has no attributes. The &lt;detect&gt; element then has
2612 a further child element, &lt;dtmf-type&gt;. The &lt;dtmf-type&gt; element has
2613 two attributes: 'name' and 'package'. The 'name' attribute
2614 provides the type of DTMF being used and is a case-insensitive
2615 string containing either '<a href="./rfc4733">RFC4733</a>' [<a href="./rfc4733" title="&quot;RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals&quot;">RFC4733</a>] or 'Media' (detecting
2616 tones as signals from the audio stream). The 'package' attribute
2617 provides the name of the Media Control Channel Framework package,
2618 compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for which the DTMF
2619 type applies.
2620
2621 &lt;generate&gt;: Indicates the required support for DTMF generation. The
2622 &lt;generate&gt; element has no attributes. The &lt;generate&gt; element has
2623 a single child element, &lt;dtmf-type&gt;. The &lt;dtmf-type&gt; element has
2624 two attributes: 'name' and 'package'. The 'name' attribute
2625
2626
2627
2628 <span class="grey">Boulton, et al. Standards Track [Page 47]</span></pre>
2629 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
2630 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2631
2632
2633 provides the type of DTMF being used and is a case-insensitive
2634 string containing either '<a href="./rfc4733">RFC4733</a>' [<a href="./rfc4733" title="&quot;RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals&quot;">RFC4733</a>] or 'Media'
2635 (generating tones as signals in the audio stream). The 'package'
2636 attribute provides the name of the Media Control Channel Framework
2637 package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for which the
2638 DTMF type applies.
2639
2640 &lt;passthrough&gt;: Indicates the required support for passing DTMF
2641 through without re-encoding. The &lt;passthrough&gt; element has no
2642 attributes. The &lt;passthrough&gt; element has a single child element,
2643 &lt;dtmf-type&gt;. The &lt;dtmf-type&gt; element has two attributes: 'name'
2644 and 'package'. The 'name' attribute provides the type of DTMF
2645 being used and is a case-insensitive string containing either
2646 '<a href="./rfc4733">RFC4733</a>' [<a href="./rfc4733" title="&quot;RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals&quot;">RFC4733</a>] or 'Media' (passing tones as signals through
2647 the audio stream). The 'package' attribute provides the name of
2648 the Media Control Channel Framework package, compliant with
2649 <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for which the DTMF type applies.
2650
2651 <span class="h6"><a class="selflink" id="section-5.2.5.1.3.4" href="#section-5.2.5.1.3.4">5.2.5.1.3.4</a>. &lt;tones&gt;</span>
2652
2653 The &lt;tones&gt; element provides requested tones that a Media Server must
2654 support for a mix. In particular, the request refers to both support
2655 for country codes (ISO 3166-1 [<a href="#ref-ISO.3166-1">ISO.3166-1</a>]) and requested
2656 functionality (ITU-T Recommendation Q.1950 [<a href="#ref-ITU-T.Q.1950">ITU-T.Q.1950</a>]). The
2657 element MAY be present.
2658
2659 The &lt;tones&gt; element has no attributes.
2660
2661 The &lt;tones&gt; element has zero or more of the following child elements:
2662
2663 &lt;country-codes&gt;: Describes the requested country codes in relation
2664 to tones. The &lt;country-codes&gt; element has no attributes. The
2665 &lt;country-codes&gt; element has a single child element. The child
2666 element, &lt;country-code&gt;, requests a specific country code,
2667 compliant with the ISO 3166-1 [<a href="#ref-ISO.3166-1">ISO.3166-1</a>] specification. The
2668 &lt;country-code&gt; element has a single attribute, 'package'. The
2669 attribute 'package' provides the name of the Media Control Channel
2670 Framework package, compliant with the specification in the related
2671 IANA registry (e.g., "msc-ivr/1.0"), in which the tones from the
2672 specified country code are requested.
2673
2674 &lt;h248-codes&gt;: Describes the requested H.248 codes with respect to
2675 tones. The &lt;h248-codes&gt; element has no attributes. The
2676 &lt;h248-codes&gt; element has a single child element. The child
2677 element, &lt;h248-code&gt;, requests a specific H.248 code, compliant
2678 with the ITU-T Recommendation Q.1950 [<a href="#ref-ITU-T.Q.1950">ITU-T.Q.1950</a>] specification.
2679 The codes can be either specific (e.g., cg/dt to only report the
2680 Dial Tone from the Call Progress Tones package) or generic (e.g.,
2681
2682
2683
2684 <span class="grey">Boulton, et al. Standards Track [Page 48]</span></pre>
2685 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
2686 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2687
2688
2689 cg/* to report all the tones from the Call Progress Tones
2690 package), using wildcards. The &lt;h248-code&gt; element has a single
2691 attribute, 'package'. The attribute 'package' provides the name
2692 of the Media Control Channel Framework package, compliant with
2693 <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, in which the specified codes are
2694 requested.
2695
2696 <span class="h6"><a class="selflink" id="section-5.2.5.1.3.5" href="#section-5.2.5.1.3.5">5.2.5.1.3.5</a>. &lt;mixing-modes&gt;</span>
2697
2698 The &lt;mixing-modes&gt; element requests information relating to support
2699 for audio and video mixing, more specifically a list of supported
2700 algorithms to mix audio and a list of supported video presentation
2701 layouts. The element MAY be present.
2702
2703 The &lt;mixing-modes&gt; element has no attributes.
2704
2705 The &lt;mixing-modes&gt; element has zero or more of the following child
2706 elements:
2707
2708 &lt;audio-mixing-modes&gt;: Describes the requested algorithms for audio
2709 mixing. The &lt;audio-mixing-modes&gt; element has no attributes. The
2710 &lt;audio-mixing-modes&gt; element has one child element. The child
2711 element, &lt;audio-mixing-mode&gt;, contains a requested mixing
2712 algorithm. Valid values for the &lt;audio-mixing-mode&gt; element are
2713 algorithm names, e.g., 'nbest' and 'controller' as defined in
2714 [<a href="./rfc6505" title="&quot;A Mixer Control Package for the Media Control Channel Framework&quot;">RFC6505</a>]. The element has a single attribute, 'package'. The
2715 attribute 'package' provides the name of the Media Control Channel
2716 Framework package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of [RFC6230]</a>, for
2717 which the algorithm support is requested.
2718
2719 &lt;video-mixing-modes&gt;: Describes the requested video presentation
2720 layouts for video mixing. The &lt;video-mixing-modes&gt; element has
2721 two attributes: 'vas' and 'activespeakermix'. The 'vas' attribute
2722 is of type boolean with a value of 'true' indicating that the
2723 Consumer client requires automatic Voice Activated Switching. The
2724 'activespeakermix' attribute is of type boolean with a value of
2725 'true' indicating that the Consumer client requires an additional
2726 video stream for the loudest speaker participant without its
2727 contribution. The &lt;video-mixing-modes&gt; element has one child
2728 element. The child element, &lt;video-mixing-mode&gt;, contains the
2729 name of a specific video presentation layout. The name may refer
2730 to one of the predefined video layouts defined in the XCON
2731 conference information data model, or to non-XCON layouts as well,
2732 as long as they are appropriately prefixed. The
2733 &lt;video-mixing-mode&gt; element has a single attribute, 'package'.
2734 The attribute 'package' provides the name of the Media Control
2735 Channel Framework package, compliant with <a href="./rfc6230#section-13.1.1">Section&nbsp;13.1.1 of
2736 [RFC6230]</a>, for which the algorithm support is requested.
2737
2738
2739
2740 <span class="grey">Boulton, et al. Standards Track [Page 49]</span></pre>
2741 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
2742 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2743
2744
2745 <span class="h6"><a class="selflink" id="section-5.2.5.1.3.6" href="#section-5.2.5.1.3.6">5.2.5.1.3.6</a>. &lt;application-data&gt;</span>
2746
2747 The &lt;application-data&gt; element provides an arbitrary string of
2748 characters as mixer application-level data. This data is meant to
2749 only have meaning at the application-level logic and as such is not
2750 otherwise restricted by this specification. The set of allowed
2751 characters is the same as those in XML (viz., tab, carriage return,
2752 line feed, and the legal characters of Unicode and ISO/IEC 10646
2753 [<a href="#ref-ISO.10646.2012">ISO.10646.2012</a>] (see also <a href="#section-2.2">Section 2.2</a> of
2754 &lt;<a href="http://www.w3.org/TR/xml/">http://www.w3.org/TR/xml/</a>&gt;)). The element MAY be present.
2755
2756 The &lt;application-data&gt; element has no attributes.
2757
2758 The &lt;application-data&gt; element has no child elements.
2759
2760 <span class="h6"><a class="selflink" id="section-5.2.5.1.3.7" href="#section-5.2.5.1.3.7">5.2.5.1.3.7</a>. &lt;location&gt;</span>
2761
2762 The &lt;location&gt; element requests a civic location for a mixer Media
2763 Server. The request makes use of the Civic Address Schema
2764 standardized in <a href="./rfc5139">RFC 5139</a> [<a href="./rfc5139" title="&quot;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5139</a>]. The element MAY be present.
2765 More precisely, this section is entirely optional, and it's
2766 implementation specific to fill it with just the details each
2767 implementer deems necessary for any optimization that may be needed.
2768
2769 The &lt;location&gt; element has no attributes.
2770
2771 The &lt;location&gt; element has a single child element:
2772
2773 &lt;civicAddress&gt;: Describes the civic address location of the
2774 requested Media Server, whose representation refers to <a href="./rfc5139#section-4">Section&nbsp;4
2775 of RFC 5139</a> [<a href="./rfc5139" title="&quot;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5139</a>].
2776
2777 <span class="h6"><a class="selflink" id="section-5.2.5.1.3.8" href="#section-5.2.5.1.3.8">5.2.5.1.3.8</a>. &lt;encryption&gt;</span>
2778
2779 The &lt;encryption&gt; element allows a Consumer client to request support
2780 for encrypting mixed RTP media streams using <a href="./rfc3711">RFC 3711</a> [<a href="./rfc3711" title="&quot;The Secure Real-time Transport Protocol (SRTP)&quot;">RFC3711</a>]. The
2781 element MAY be present. If the element is present, then the Media
2782 Server supports DTLS-SRTP [<a href="./rfc5763" title="&quot;Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)&quot;">RFC5763</a>].
2783
2784 The &lt;encryption&gt; element has no attributes.
2785
2786 The &lt;encryption&gt; element has no child elements.
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796 <span class="grey">Boulton, et al. Standards Track [Page 50]</span></pre>
2797 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
2798 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2799
2800
2801 <span class="h4"><a class="selflink" id="section-5.2.6" href="#section-5.2.6">5.2.6</a>. Media Service Resource Response</span>
2802
2803 This section provides the element definitions for use in Consumer
2804 interface responses. The responses are carried in the
2805 &lt;mediaResourceResponse&gt; element.
2806
2807 <span class="h5"><a class="selflink" id="section-5.2.6.1" href="#section-5.2.6.1">5.2.6.1</a>. &lt;mediaResourceResponse&gt;</span>
2808
2809 The &lt;mediaResourceResponse&gt; element provides information for clients
2810 receiving response information from an external MRB entity.
2811
2812 The &lt;mediaResourceResponse&gt; element has two mandatory attributes:
2813 'id' and 'status'. The 'id' attribute must contain the same value
2814 that the client provided in the 'id' attribute in the
2815 &lt;mediaResourceRequest&gt; to which the response is mapped. The 'status'
2816 attribute indicates the status code of the operation. The following
2817 status codes are defined for 'status':
2818
2819 +-----------+-------------------------------------------------------+
2820 | code | description |
2821 +-----------+-------------------------------------------------------+
2822 | 200 | OK |
2823 | | |
2824 | 400 | Syntax error |
2825 | | |
2826 | 405 | Wrong sequence number |
2827 | | |
2828 | 408 | Unable to find Resource |
2829 | | |
2830 | 409 | Unable to update Resource |
2831 | | |
2832 | 410 | Unable to remove Resource |
2833 | | |
2834 | 420 | Unsupported attribute or element |
2835 +-----------+-------------------------------------------------------+
2836
2837 Table 2: &lt;mediaResourceResponse&gt; Status Codes
2838
2839 If a new media resource request made by a client application has been
2840 accepted, the MRB MUST reply with a &lt;mediaResourceResponse&gt; with
2841 status code 200. The same rule applies whenever a request to update
2842 (action='update') or remove (action='remove') an existing transaction
2843 can be fulfilled by the MRB.
2844
2845 A media resource request, nevertheless, may fail for several reasons.
2846 In such a case, the status codes defined in Table 2 must be used
2847 instead. Specifically, if the MRB fails to handle a request due to a
2848 syntax error in the request itself (e.g., incorrect XML, violation of
2849
2850
2851
2852 <span class="grey">Boulton, et al. Standards Track [Page 51]</span></pre>
2853 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
2854 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2855
2856
2857 the schema constraints, or invalid values in any of the attributes/
2858 elements), the MRB MUST reply with a &lt;mediaResourceResponse&gt; with
2859 status code 400. If a syntactically correct request fails because
2860 the request also includes any attribute/element the MRB doesn't
2861 understand, the MRB MUST reply with a &lt;mediaResourceResponse&gt; with
2862 status code 420. If a syntactically correct request fails because it
2863 contains a wrong sequence number, that is, a 'seq' value not
2864 consistent with the increment the MRB expects according to
2865 <a href="#section-5.2.3">Section 5.2.3</a>, the MRB MUST reply with a &lt;mediaResourceResponse&gt; with
2866 status code 405. If a syntactically correct request fails because
2867 the MRB couldn't find any Media Server able to fulfill the
2868 requirements presented by the Application Server in its request, the
2869 MRB MUST reply with a &lt;mediaResourceResponse&gt; with status code 408.
2870 If a syntactically correct request fails because the MRB couldn't
2871 update an existing request according to the new requirements
2872 presented by the Application Server in its request, the MRB MUST
2873 reply with a &lt;mediaResourceResponse&gt; with status code 409. If a
2874 syntactically correct request fails because the MRB couldn't remove
2875 an existing request and release the related resources as requested by
2876 the Application Server, the MRB MUST reply with a
2877 &lt;mediaResourceResponse&gt; with status code 410.
2878
2879 Further details on status codes 409 and 410 are included in
2880 <a href="#section-5.2.3">Section 5.2.3</a>, where the leasing mechanism, along with its related
2881 scenarios, is described in more detail.
2882
2883 The &lt;mediaResourceResponse&gt; element has &lt;response-session-info&gt; as a
2884 child element. This element is used to describe the response of a
2885 Consumer interface query and is covered in the following sub-section.
2886
2887 <span class="h6"><a class="selflink" id="section-5.2.6.1.1" href="#section-5.2.6.1.1">5.2.6.1.1</a>. &lt;response-session-info&gt;</span>
2888
2889 The &lt;response-session-info&gt; element is included in Consumer
2890 responses. This applies to responses to both requests for new
2891 resources and requests to update an existing media resource session.
2892 The ability to change and remove an existing media resource session
2893 is described in more detail in <a href="#section-5.2.3">Section 5.2.3</a>. If the request was
2894 successful, the &lt;mediaResourceResponse&gt; MUST have one
2895 &lt;response-session-info&gt; child, which describes the media resource
2896 session addressed by the request. If the request was not successful,
2897 the &lt;mediaResourceResponse&gt; MUST NOT have a &lt;response-session-info&gt;
2898 child.
2899
2900 The &lt;response-session-info&gt; element has no attributes.
2901
2902
2903
2904
2905
2906
2907
2908 <span class="grey">Boulton, et al. Standards Track [Page 52]</span></pre>
2909 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
2910 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2911
2912
2913 The &lt;response-session-info&gt; element has zero or more of the following
2914 child elements:
2915
2916 &lt;session-id&gt;: A unique identifier that explicitly references an
2917 existing media resource session on the MRB. The identifier is
2918 included to update the existing session and is described in more
2919 detail in <a href="#section-5.2.3">Section 5.2.3</a>.
2920
2921 &lt;seq&gt;: Used in association with the &lt;session-id&gt; element in a
2922 subsequent request to update an existing media resource session on
2923 an MRB. The &lt;seq&gt; number is incremented from its original value
2924 returned in response to the initial request for media resources.
2925 More information on its use is provided in <a href="#section-5.2.3">Section 5.2.3</a>.
2926
2927 &lt;expires&gt;: Includes the number of seconds that the media resources
2928 are reserved as part of this interaction. If the lease is not
2929 refreshed before expiry, the MRB will reclaim the resources and
2930 they will no longer be guaranteed. It is RECOMMENDED that a
2931 minimum value of 300 seconds be used for the value of the
2932 'expires' attribute. It is also RECOMMENDED that a Consumer
2933 client refresh the lease at an interval that is not too close to
2934 the expiry time. A value of 80% of the timeout period could be
2935 used. For example, if the timeout period is 300 seconds, the
2936 Consumer client would refresh the transaction at 240 seconds.
2937 More information on its use is provided in <a href="#section-5.2.3">Section 5.2.3</a>.
2938
2939 &lt;media-server-address&gt;: Provides information to reach the Media
2940 Server handling the requested media resource. One or more
2941 instances of these elements may appear. The
2942 &lt;media-server-address&gt; element has a single attribute named 'uri',
2943 which supplies a SIP URI that reaches the specified Media Server.
2944 It also has three optional elements: &lt;connection-id&gt;,
2945 &lt;ivr-sessions&gt;, and &lt;mixers&gt;. The &lt;ivr-sessions&gt; and &lt;mixers&gt;
2946 elements are defined in Sections <a href="#section-5.2.5.1.2.1">5.2.5.1.2.1</a> and <a href="#section-5.2.5.1.3.1">5.2.5.1.3.1</a>,
2947 respectively, and have the same meaning but are applied to
2948 individual Media Server instances as a subset of the overall
2949 resources reported in the &lt;connection-id&gt; element. If multiple
2950 Media Servers are assigned in an IAMM operation, exactly one
2951 &lt;media-server-address&gt; element, more specifically the Media Server
2952 that provided the media dialog or CFW response, will have a
2953 &lt;connection-id&gt; element. Additional information relating to the
2954 use of the &lt;connection-id&gt; element for media dialogs is included
2955 in <a href="#section-6">Section 6</a>.
2956
2957
2958
2959
2960
2961
2962
2963
2964 <span class="grey">Boulton, et al. Standards Track [Page 53]</span></pre>
2965 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
2966 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
2967
2968
2969 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. In-Line Unaware MRB Interface</span>
2970
2971 An entity acting as an In-line MRB can act in one of two roles for a
2972 request, as introduced in <a href="#section-4.2">Section 4.2</a>: the In-line Unaware MRB Mode
2973 (IUMM) of operation and the In-line Aware MRB Mode (IAMM) of
2974 operation. This section further describes IUMM.
2975
2976 It should be noted that the introduction of an MRB entity into the
2977 network, as specified in this document, requires interfaces to be
2978 implemented by those requesting Media Server resources (for example,
2979 an Application Server). This applies when using the Consumer
2980 interface as discussed in Sections <a href="#section-5.2.1">5.2.1</a> (Query mode) and 5.2.2
2981 (IAMM). An MRB entity can also act in a client-unaware mode when
2982 deployed into the network. This allows any SIP-compliant client
2983 entity, as defined by <a href="./rfc3261">RFC 3261</a> [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>] and its extensions, to send
2984 requests to an MRB that in turn will select an appropriate Media
2985 Server based on knowledge of Media Server resources it currently has
2986 available transparently to the client entity. Using an MRB in this
2987 mode allows for easy migration of current applications and services
2988 that are unaware of the MRB concept and would simply require a
2989 configuration change resulting in the MRB being set as a SIP outbound
2990 proxy for clients requiring media services.
2991
2992 With IUMM, the MRB may conclude that an assigned media resource is no
2993 longer needed when it receives a SIP BYE from the Application Server
2994 or Media Server that ends the SIP dialog that initiated the request.
2995
2996 As with IAMM, in IUMM the SIP INVITE from the Application Server
2997 could convey the application/sdp payload to either set up a media
2998 dialog or a Control Framework Control Channel. In either case, in
2999 order to permit the Application Server to associate a media dialog
3000 with a Control Channel to the same Media Server, using the procedures
3001 of <a href="./rfc6230#section-6">[RFC6230] Section&nbsp;6</a>, the MRB should be acting as a SIP proxy (and
3002 not a B2BUA). This allows the SIP URI of the targeted Media Server
3003 to be transparently passed back to the Application Server in the SIP
3004 response, resulting in a direct SIP dialog between the Application
3005 Server and the Media Server.
3006
3007 While IUMM has the least impact on legacy Application Servers, it
3008 also provides the least versatility. See <a href="#section-8">Section 8</a>.
3009
3010 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. MRB Acting as a B2BUA</span>
3011
3012 An MRB entity can act as a SIP Back-to-Back User Agent (B2BUA) or a
3013 SIP Proxy Server as defined in <a href="./rfc3261">RFC 3261</a> [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>]. When an MRB acts
3014 as a B2BUA, issues can arise when using Media Control Channel
3015 packages such as the IVR [<a href="./rfc6231" title="&quot;An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework&quot;">RFC6231</a>] and mixer [<a href="./rfc6505" title="&quot;A Mixer Control Package for the Media Control Channel Framework&quot;">RFC6505</a>] packages.
3016 Specifically, the framework attribute 'connectionid' as provided in
3017
3018
3019
3020 <span class="grey">Boulton, et al. Standards Track [Page 54]</span></pre>
3021 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span>
3022 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3023
3024
3025 <a href="#appendix-A">Appendix A</a> ("Common Package Components") of [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>] uses a
3026 concatenation of the SIP dialog identifiers to be used for
3027 referencing SIP dialogs within the Media Control Channel. When a
3028 request traverses an MRB acting as a B2BUA, the SIP dialog
3029 identifiers change, and so the 'connectionid' cannot be used as
3030 intended due to this change. For this reason, when an MRB wishes to
3031 act as a SIP B2BUA when handling a request from an Application Server
3032 to set up a media dialog to a Media Server, it MUST include the
3033 optional &lt;connection-id&gt; element in a Consumer interface response
3034 with a value that provides the equivalent for the 'connectionid'
3035 ('Local Dialog Tag' + 'Remote Dialog Tag') for the far side of the
3036 B2BUA. If present, this value MUST be used as the value for the
3037 'connectionid' in packages where the Common Package Components are
3038 used. The &lt;connection-id&gt; element MUST NOT be included in an HTTP
3039 Consumer interface response.
3040
3041 It is important to point out that although more Media Server
3042 instances may be returned in a Consumer response (i.e., the MRB has
3043 assigned more than one Media Server to a Consumer request to fulfill
3044 the Application Server requirements), in IAMM the MRB will only act
3045 as a B2BUA with a single Media Server. In this case, exactly one
3046 &lt;media-server-address&gt; element, describing the media dialog or CFW
3047 response, will have a &lt;connection-id&gt; element that will not be
3048 included in any additional &lt;media-server-address&gt; elements.
3049
3050 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Multimodal MRB Implementations</span>
3051
3052 An MRB implementation may operate multimodally with a collection of
3053 Application Server clients all sharing the same pool of media
3054 resources. That is, an MRB may be simultaneously operating in Query
3055 mode, IAMM, and IUMM. It knows in which mode to act on any
3056 particular request from a client, depending on the context of the
3057 request:
3058
3059 o If the received request is an HTTP POST message with application/
3060 mrb-consumer+xml content, then the MRB processes it in Query mode.
3061
3062 o If the received request is a SIP INVITE with application/
3063 mrb-consumer+xml content and application/sdp content, then the MRB
3064 processes it in IAMM.
3065
3066 o If the received request is a SIP INVITE without application/
3067 mrb-consumer+xml content but with application/sdp content, then
3068 the MRB processes it in IUMM.
3069
3070
3071
3072
3073
3074
3075
3076 <span class="grey">Boulton, et al. Standards Track [Page 55]</span></pre>
3077 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span>
3078 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3079
3080
3081 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Relative Merits of Query Mode, IAMM, and IUMM</span>
3082
3083 At a high level, the possible Application Server MRB interactions can
3084 be distinguished by the following basic types:
3085
3086 a. Query mode - the client is requesting the assignment by the MRB
3087 of suitable Media Server resources;
3088
3089 b. IAMM/media dialog - the client is requesting the assignment by
3090 the MRB of suitable Media Server resources and the establishment
3091 of a media dialog to one of the Media Servers;
3092
3093 c. IAMM/Control Channel - the client is requesting the assignment by
3094 the MRB of suitable Media Server resources and the establishment
3095 of a CFW Control Channel to one of the Media Servers;
3096
3097 d. IUMM/media dialog - the client is requesting the establishment of
3098 a media dialog to a Media Server resource;
3099
3100 e. IUMM/Control Channel - the client is requesting the establishment
3101 of a CFW Control Channel to a Media Server resource.
3102
3103 Each type of interaction has advantages and disadvantages, where such
3104 considerations relate to the versatility of what the MRB can provide,
3105 technical aspects such as efficiency in different application
3106 scenarios, complexity, delay, use with legacy Application Servers, or
3107 use with the Media Control Channel Framework. Depending on the
3108 characteristics of a particular setting that an MRB is intended to
3109 support, some of the above interaction types may be more appropriate
3110 than others. This section provides a few observations on relative
3111 merits but is not intended to be exhaustive. Some constraints of a
3112 given interaction type may be subtle.
3113
3114 o Operation with other types of media control: Any of the types of
3115 interactions work with the mechanisms described in <a href="./rfc4240">RFC 4240</a>
3116 [<a href="./rfc4240" title="&quot;Basic Network Media Services with SIP&quot;">RFC4240</a>] and <a href="./rfc5552">RFC 5552</a> [<a href="./rfc5552" title="&quot;SIP Interface to VoiceXML Media Services&quot;">RFC5552</a>] where initial control
3117 instructions are conveyed in the SIP INVITE from the Application
3118 Server for the media dialog to the Media Server and subsequent
3119 instructions may be fetched using HTTP. Query mode (a), IAMM/
3120 media dialog (b), and IUMM/media dialog (d) work with the Media
3121 Server Markup Language (MSML) as per <a href="./rfc5707">RFC 5707</a> [<a href="./rfc5707" title="&quot;Media Server Markup Language (MSML)&quot;">RFC5707</a>] or the
3122 Media Server Control Markup Language (MSCML) as per <a href="./rfc5022">RFC 5022</a>
3123 [<a href="./rfc5022" title="&quot;Media Server Control Markup Language (MSCML) and Protocol&quot;">RFC5022</a>].
3124
3125 o As stated previously, IUMM has no interface impacts on an
3126 Application Server. When using IUMM, the Application Server does
3127 not specify the characteristics of the type of media resource it
3128 requires, as the &lt;mediaResourceRequest&gt; element is not passed to
3129
3130
3131
3132 <span class="grey">Boulton, et al. Standards Track [Page 56]</span></pre>
3133 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span>
3134 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3135
3136
3137 the MRB. For IUMM/media dialog (d), the MRB can deduce an
3138 appropriate media resource on a best-effort basis using
3139 information gleaned from examining information in the SIP INVITE.
3140 This includes the SDP information for the media dialog, or initial
3141 control information in the SIP Request-URI as per <a href="./rfc4240">RFC 4240</a>
3142 [<a href="./rfc4240" title="&quot;Basic Network Media Services with SIP&quot;">RFC4240</a>]. With IUMM/Control Channel (e), there is even less
3143 information for the MRB to use.
3144
3145 o If using IUMM/Control Channel (e), the subsequent sending of the
3146 media dialog to the Media Server should not be done using IUMM/
3147 media dialog. That is, the SIP signaling to send the media dialog
3148 to the selected Media Server must be directly between the
3149 Application Server and that Media Server, and not through the MRB.
3150 Unless resources can be confidentially identified, the MRB could
3151 send the media dialog to a different Media Server. Likewise, if
3152 using IUMM/media dialog (d), the subsequent establishment of a
3153 Control Channel should not be done with IUMM/Control Channel (e)
3154 unless definitive information is available.
3155
3156 o Query mode (a) and IAMM/Control Channel (c) lend themselves to
3157 requesting a pool of media resources (e.g., a number of IVR or
3158 conferencing ports) in advance of use and retaining use over a
3159 period of time, independent of whether there are media dialogs to
3160 those resources at any given moment, whereas the other types of
3161 interactions do not. This also applies to making a subsequent
3162 request to increase or decrease the amount of resources previously
3163 awarded.
3164
3165 o While Query mode (a) and IAMM/Control Channel (c) are the most
3166 versatile interaction types, the former is completely decoupled
3167 from the use or non-use of a Control Channel, whereas the latter
3168 requires the use of a Control Channel.
3169
3170 o When Media Control Channel Framework Control Channels are to be
3171 used in conjunction with the use of an MRB, Query mode (a) would
3172 typically result in fewer such channels being established over
3173 time, as compared to IAMM/Control Channel (c). That is because
3174 the latter would involve setting up an additional Control Channel
3175 every time an Application Server has a new request for an MRB for
3176 media resources.
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188 <span class="grey">Boulton, et al. Standards Track [Page 57]</span></pre>
3189 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span>
3190 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3191
3192
3193 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Examples</span>
3194
3195 This section provides examples of both the Publish and Consumer
3196 interfaces. Both the Query mode and In-line mode are addressed.
3197
3198 Note that due to RFC formatting conventions, this section often
3199 splits HTTP, SIP/SDP, and CFW across lines whose content would exceed
3200 72 characters. A backslash character marks where this line folding
3201 has taken place. This backslash, and its trailing CRLF and
3202 whitespace, would not appear in the actual protocol contents. Also
3203 note that the indentation of the XML content is only provided for
3204 readability: actual messages will follow strict XML syntax, which
3205 allows for but does not require indentation.
3206
3207 <span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Publish Example</span>
3208
3209 The following example assumes that a Control Channel has been
3210 established and synced as described in the Media Control Channel
3211 Framework ([<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>]).
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244 <span class="grey">Boulton, et al. Standards Track [Page 58]</span></pre>
3245 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span>
3246 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3247
3248
3249 Figure 9 shows the subscription/notification mechanism the Publish
3250 interface is based on, as defined in <a href="#section-5.1">Section 5.1</a>. The MRB subscribes
3251 for information at the Media Server (message A1.), and the Media
3252 Server accepts the subscription (A2.). Notifications are triggered
3253 by the Media Server (B1.) and acknowledged by the MRB (B2.).
3254
3255 MRB MS
3256 | |
3257 | A1. CONTROL (MRB subscription) |
3258 |---------------------------------------------&gt;|
3259 | A2. 200 OK |
3260 |&lt;---------------------------------------------|
3261 | |
3262 . .
3263 . .
3264 | |
3265 | |--+ collect
3266 | | | up-to-date
3267 | |&lt;-+ info
3268 | B1. CONTROL (MRB notification) |
3269 |&lt;---------------------------------------------|
3270 | B2. 200 OK |
3271 |---------------------------------------------&gt;|
3272 | |
3273 . .
3274 . .
3275
3276 Figure 9: Publish Example: Sequence Diagram
3277
3278 The rest of this section includes a full dump of the messages
3279 associated with the previous sequence diagram, specifically:
3280
3281 1. the subscription (A1.), in an &lt;mrbrequest&gt; (CFW CONTROL);
3282
3283 2. the Media Server accepting the subscription (A2.), in an
3284 &lt;mrbresponse&gt; (CFW 200);
3285
3286 3. a notification (B1.), in an &lt;mrbnotification&gt; (CFW CONTROL);
3287
3288 4. the ack to the notification (B2.), in a framework-level 200
3289 message (CFW 200).
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300 <span class="grey">Boulton, et al. Standards Track [Page 59]</span></pre>
3301 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span>
3302 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3303
3304
3305 A1. MRB -&gt; MS (CONTROL, publish request)
3306 ----------------------------------------
3307 CFW lidc30BZObiC CONTROL
3308 Control-Package: mrb-publish/1.0
3309 Content-Type: application/mrb-publish+xml
3310 Content-Length: 337
3311
3312 &lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&gt;
3313 &lt;mrbpublish version="1.0" xmlns="urn:ietf:params:xml:ns:mrb-publish"&gt;
3314 &lt;mrbrequest&gt;
3315 &lt;subscription action="create" seqnumber="1" id="p0T65U"&gt;
3316 &lt;expires&gt;600&lt;/expires&gt;
3317 &lt;minfrequency&gt;20&lt;/minfrequency&gt;
3318 &lt;maxfrequency&gt;20&lt;/maxfrequency&gt;
3319 &lt;/subscription&gt;
3320 &lt;/mrbrequest&gt;
3321 &lt;/mrbpublish&gt;
3322
3323
3324 A2. MRB &lt;- MS (200 to CONTROL, request accepted)
3325 ------------------------------------------------
3326 CFW lidc30BZObiC 200
3327 Timeout: 10
3328 Content-Type: application/mrb-publish+xml
3329 Content-Length: 139
3330
3331 &lt;mrbpublish version="1.0" xmlns="urn:ietf:params:xml:ns:mrb-publish"&gt;
3332 &lt;mrbresponse status="200" reason="OK: Request accepted"/&gt;
3333 &lt;/mrbpublish&gt;
3334
3335
3336 B1. MRB &lt;- MS (CONTROL, event notification from MS)
3337 ---------------------------------------------------
3338 CFW 03fff52e7b7a CONTROL
3339 Control-Package: mrb-publish/1.0
3340 Content-Type: application/mrb-publish+xml
3341 Content-Length: 4226
3342
3343 &lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&gt;
3344 &lt;mrbpublish version="1.0"
3345 xmlns="urn:ietf:params:xml:ns:mrb-publish"&gt;
3346 &lt;mrbnotification seqnumber="1" id="QQ6J3c"&gt;
3347 &lt;media-server-id&gt;a1b2c3d4&lt;/media-server-id&gt;
3348 &lt;supported-packages&gt;
3349 &lt;package name="msc-ivr/1.0"/&gt;
3350 &lt;package name="msc-mixer/1.0"/&gt;
3351
3352
3353
3354
3355
3356 <span class="grey">Boulton, et al. Standards Track [Page 60]</span></pre>
3357 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span>
3358 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3359
3360
3361 &lt;package name="mrb-publish/1.0"/&gt;
3362 &lt;package name="msc-example-pkg/1.0"/&gt;
3363 &lt;/supported-packages&gt;
3364 &lt;active-rtp-sessions&gt;
3365 &lt;rtp-codec name="audio/basic"&gt;
3366 &lt;decoding&gt;10&lt;/decoding&gt;
3367 &lt;encoding&gt;20&lt;/encoding&gt;
3368 &lt;/rtp-codec&gt;
3369 &lt;/active-rtp-sessions&gt;
3370 &lt;active-mixer-sessions&gt;
3371 &lt;active-mix conferenceid="7cfgs43"&gt;
3372 &lt;rtp-codec name="audio/basic"&gt;
3373 &lt;decoding&gt;3&lt;/decoding&gt;
3374 &lt;encoding&gt;3&lt;/encoding&gt;
3375 &lt;/rtp-codec&gt;
3376 &lt;/active-mix&gt;
3377 &lt;/active-mixer-sessions&gt;
3378 &lt;non-active-rtp-sessions&gt;
3379 &lt;rtp-codec name="audio/basic"&gt;
3380 &lt;decoding&gt;50&lt;/decoding&gt;
3381 &lt;encoding&gt;40&lt;/encoding&gt;
3382 &lt;/rtp-codec&gt;
3383 &lt;/non-active-rtp-sessions&gt;
3384 &lt;non-active-mixer-sessions&gt;
3385 &lt;non-active-mix available="15"&gt;
3386 &lt;rtp-codec name="audio/basic"&gt;
3387 &lt;decoding&gt;15&lt;/decoding&gt;
3388 &lt;encoding&gt;15&lt;/encoding&gt;
3389 &lt;/rtp-codec&gt;
3390 &lt;/non-active-mix&gt;
3391 &lt;/non-active-mixer-sessions&gt;
3392 &lt;media-server-status&gt;active&lt;/media-server-status&gt;
3393 &lt;supported-codecs&gt;
3394 &lt;supported-codec name="audio/basic"&gt;
3395 &lt;supported-codec-package name="msc-ivr/1.0"&gt;
3396 &lt;supported-action&gt;encoding&lt;/supported-action&gt;
3397 &lt;supported-action&gt;decoding&lt;/supported-action&gt;
3398 &lt;/supported-codec-package&gt;
3399 &lt;supported-codec-package name="msc-mixer/1.0"&gt;
3400 &lt;supported-action&gt;encoding&lt;/supported-action&gt;
3401 &lt;supported-action&gt;decoding&lt;/supported-action&gt;
3402 &lt;/supported-codec-package&gt;
3403 &lt;/supported-codec&gt;
3404 &lt;/supported-codecs&gt;
3405 &lt;application-data&gt;TestbedPrototype&lt;/application-data&gt;
3406
3407
3408
3409
3410
3411
3412 <span class="grey">Boulton, et al. Standards Track [Page 61]</span></pre>
3413 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span>
3414 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3415
3416
3417 &lt;file-formats&gt;
3418 &lt;supported-format name="audio/x-wav"&gt;
3419 &lt;supported-file-package&gt;
3420 msc-ivr/1.0
3421 &lt;/supported-file-package&gt;
3422 &lt;/supported-format&gt;
3423 &lt;/file-formats&gt;
3424 &lt;max-prepared-duration&gt;
3425 &lt;max-time max-time-seconds="3600"&gt;
3426 &lt;max-time-package&gt;msc-ivr/1.0&lt;/max-time-package&gt;
3427 &lt;/max-time&gt;
3428 &lt;/max-prepared-duration&gt;
3429 &lt;dtmf-support&gt;
3430 &lt;detect&gt;
3431 &lt;dtmf-type package="msc-ivr/1.0" name="<a href="./rfc4733">RFC4733</a>"/&gt;
3432 &lt;dtmf-type package="msc-mixer/1.0" name="<a href="./rfc4733">RFC4733</a>"/&gt;
3433 &lt;/detect&gt;
3434 &lt;generate&gt;
3435 &lt;dtmf-type package="msc-ivr/1.0" name="<a href="./rfc4733">RFC4733</a>"/&gt;
3436 &lt;dtmf-type package="msc-mixer/1.0" name="<a href="./rfc4733">RFC4733</a>"/&gt;
3437 &lt;/generate&gt;
3438 &lt;passthrough&gt;
3439 &lt;dtmf-type package="msc-ivr/1.0" name="<a href="./rfc4733">RFC4733</a>"/&gt;
3440 &lt;dtmf-type package="msc-mixer/1.0" name="<a href="./rfc4733">RFC4733</a>"/&gt;
3441 &lt;/passthrough&gt;
3442 &lt;/dtmf-support&gt;
3443 &lt;mixing-modes&gt;
3444 &lt;audio-mixing-modes&gt;
3445 &lt;audio-mixing-mode package="msc-ivr/1.0"&gt;
3446 nbest
3447 &lt;/audio-mixing-mode&gt;
3448 &lt;/audio-mixing-modes&gt;
3449 &lt;video-mixing-modes activespeakermix="true" vas="true"&gt;
3450 &lt;video-mixing-mode package="msc-mixer/1.0"&gt;
3451 single-view
3452 &lt;/video-mixing-mode&gt;
3453 &lt;video-mixing-mode package="msc-mixer/1.0"&gt;
3454 dual-view
3455 &lt;/video-mixing-mode&gt;
3456 &lt;video-mixing-mode package="msc-mixer/1.0"&gt;
3457 dual-view-crop
3458 &lt;/video-mixing-mode&gt;
3459 &lt;video-mixing-mode package="msc-mixer/1.0"&gt;
3460 dual-view-2x1
3461 &lt;/video-mixing-mode&gt;
3462 &lt;video-mixing-mode package="msc-mixer/1.0"&gt;
3463 dual-view-2x1-crop
3464 &lt;/video-mixing-mode&gt;
3465
3466
3467
3468 <span class="grey">Boulton, et al. Standards Track [Page 62]</span></pre>
3469 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span>
3470 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3471
3472
3473 &lt;video-mixing-mode package="msc-mixer/1.0"&gt;
3474 quad-view
3475 &lt;/video-mixing-mode&gt;
3476 &lt;video-mixing-mode package="msc-mixer/1.0"&gt;
3477 multiple-5x1
3478 &lt;/video-mixing-mode&gt;
3479 &lt;video-mixing-mode package="msc-mixer/1.0"&gt;
3480 multiple-3x3
3481 &lt;/video-mixing-mode&gt;
3482 &lt;video-mixing-mode package="msc-mixer/1.0"&gt;
3483 multiple-4x4
3484 &lt;/video-mixing-mode&gt;
3485 &lt;/video-mixing-modes&gt;
3486 &lt;/mixing-modes&gt;
3487 &lt;supported-tones&gt;
3488 &lt;supported-country-codes&gt;
3489 &lt;country-code package="msc-ivr/1.0"&gt;GB&lt;/country-code&gt;
3490 &lt;country-code package="msc-ivr/1.0"&gt;IT&lt;/country-code&gt;
3491 &lt;country-code package="msc-ivr/1.0"&gt;US&lt;/country-code&gt;
3492 &lt;/supported-country-codes&gt;
3493 &lt;supported-h248-codes&gt;
3494 &lt;h248-code package="msc-ivr/1.0"&gt;cg/*&lt;/h248-code&gt;
3495 &lt;h248-code package="msc-ivr/1.0"&gt;biztn/ofque&lt;/h248-code&gt;
3496 &lt;h248-code package="msc-ivr/1.0"&gt;biztn/erwt&lt;/h248-code&gt;
3497 &lt;h248-code package="msc-mixer/1.0"&gt;conftn/*&lt;/h248-code&gt;
3498 &lt;/supported-h248-codes&gt;
3499 &lt;/supported-tones&gt;
3500 &lt;file-transfer-modes&gt;
3501 &lt;file-transfer-mode package="msc-ivr/1.0" name="HTTP"/&gt;
3502 &lt;/file-transfer-modes&gt;
3503 &lt;asr-tts-support&gt;
3504 &lt;asr-support&gt;
3505 &lt;language xml:lang="en"/&gt;
3506 &lt;/asr-support&gt;
3507 &lt;tts-support&gt;
3508 &lt;language xml:lang="en"/&gt;
3509 &lt;/tts-support&gt;
3510 &lt;/asr-tts-support&gt;
3511 &lt;vxml-support&gt;
3512 &lt;vxml-mode package="msc-ivr/1.0" support="<a href="./rfc6231">RFC6231</a>"/&gt;
3513 &lt;/vxml-support&gt;
3514 &lt;media-server-location&gt;
3515 &lt;civicAddress xml:lang="it"&gt;
3516 &lt;country&gt;IT&lt;/country&gt;
3517 &lt;A1&gt;Campania&lt;/A1&gt;
3518 &lt;A3&gt;Napoli&lt;/A3&gt;
3519 &lt;A6&gt;Via Claudio&lt;/A6&gt;
3520 &lt;HNO&gt;21&lt;/HNO&gt;
3521
3522
3523
3524 <span class="grey">Boulton, et al. Standards Track [Page 63]</span></pre>
3525 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span>
3526 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3527
3528
3529 &lt;LMK&gt;University of Napoli Federico II&lt;/LMK&gt;
3530 &lt;NAM&gt;Dipartimento di Informatica e Sistemistica&lt;/NAM&gt;
3531 &lt;PC&gt;80210&lt;/PC&gt;
3532 &lt;/civicAddress&gt;
3533 &lt;/media-server-location&gt;
3534 &lt;label&gt;TestbedPrototype-01&lt;/label&gt;
3535 &lt;media-server-address&gt;sip:[email protected]&lt;/media-server-address&gt;
3536 &lt;encryption/&gt;
3537 &lt;/mrbnotification&gt;
3538 &lt;/mrbpublish&gt;
3539
3540
3541 B2. MRB -&gt; MS (200 to CONTROL)
3542 ------------------------------
3543 CFW 03fff52e7b7a 200
3544
3545 <span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Consumer Examples</span>
3546
3547 As specified in <a href="#section-5.2">Section 5.2</a>, the Consumer interface can be involved
3548 in two different modes: Query and In-line aware. When in Query mode,
3549 Consumer messages are transported in HTTP messages: an example of
3550 such an approach is presented in <a href="#section-9.2.1">Section 9.2.1</a>. When in In-line
3551 aware mode, messages are instead transported as part of SIP
3552 negotiations: considering that SIP negotiations may be related to
3553 either the creation of a Control Channel or to a User Agent Client
3554 (UAC) media dialog, two separate examples of such an approach are
3555 presented in <a href="#section-9.2.2">Section 9.2.2</a>.
3556
3557 <span class="h4"><a class="selflink" id="section-9.2.1" href="#section-9.2.1">9.2.1</a>. Query Example</span>
3558
3559 The following example assumes that the interested Application Server
3560 already knows the HTTP URL where an MRB is listening for Consumer
3561 messages.
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580 <span class="grey">Boulton, et al. Standards Track [Page 64]</span></pre>
3581 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span>
3582 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3583
3584
3585 Figure 10 shows the HTTP-based transaction between the Application
3586 Server (AS, as shown in the figure) and the MRB. The Application
3587 Server sends a Consumer request as payload of an HTTP POST message
3588 (1.), and the MRB provides an answer in an HTTP 200 OK message (2.).
3589 Specifically, as will be shown in the examples, the Application
3590 Server is interested in 100 IVR ports: the MRB finds two Media
3591 Servers that can satisfy the request (one providing 60 ports and the
3592 other providing 40 ports) and reports them to the Application Server.
3593
3594 AS MRB
3595 | |
3596 | 1. HTTP POST (Consumer request) |
3597 |---------------------------------------------&gt;|
3598 | |
3599 | |
3600 | |--+ Parse request
3601 | | | and see if any
3602 | |&lt;-+ MS applies
3603 | |
3604 | 2. 200 OK (Consumer response) |
3605 |&lt;---------------------------------------------|
3606 | |
3607 |--+ Parse response and |
3608 | | start session (SIP/COMEDIA/CFW) |
3609 |&lt;-+ with first MS reported by MRB |
3610 | |
3611 . .
3612 . .
3613
3614 Figure 10: Consumer Example (Query): Sequence Diagram
3615
3616 The rest of this section includes a full dump of the messages
3617 associated with the previous sequence diagram, specifically:
3618
3619 1. the Consumer request (1.), in a &lt;mediaResourceRequest&gt; (HTTP
3620 POST, Content-Type 'application/mrb-consumer+xml');
3621
3622 2. the Consumer response (2.), in a &lt;mediaResourceResponse&gt; (HTTP
3623 200 OK, Content-Type 'application/mrb-consumer+xml').
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636 <span class="grey">Boulton, et al. Standards Track [Page 65]</span></pre>
3637 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-66" ></span>
3638 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3639
3640
3641 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. AS -&gt; MRB (HTTP POST, Consumer request)</span>
3642 ------------------------------------------
3643 POST /Mrb/Consumer HTTP/1.1
3644 Content-Length: 893
3645 Content-Type: application/mrb-consumer+xml
3646 Host: mrb.example.net:8080
3647 Connection: Keep-Alive
3648 User-Agent: Apache-HttpClient/4.0.1 (java 1.5)
3649
3650 &lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&gt;
3651 &lt;mrbconsumer version="1.0" xmlns="urn:ietf:params:xml:ns:mrb-consumer"&gt;
3652 &lt;mediaResourceRequest id="gh11x23v"&gt;
3653 &lt;generalInfo&gt;
3654 &lt;packages&gt;
3655 &lt;package&gt;msc-ivr/1.0&lt;/package&gt;
3656 &lt;package&gt;msc-mixer/1.0&lt;/package&gt;
3657 &lt;/packages&gt;
3658 &lt;/generalInfo&gt;
3659 &lt;ivrInfo&gt;
3660 &lt;ivr-sessions&gt;
3661 &lt;rtp-codec name="audio/basic"&gt;
3662 &lt;decoding&gt;100&lt;/decoding&gt;
3663 &lt;encoding&gt;100&lt;/encoding&gt;
3664 &lt;/rtp-codec&gt;
3665 &lt;/ivr-sessions&gt;
3666 &lt;file-formats&gt;
3667 &lt;required-format name="audio/x-wav"/&gt;
3668 &lt;/file-formats&gt;
3669 &lt;file-transfer-modes&gt;
3670 &lt;file-transfer-mode package="msc-ivr/1.0" name="HTTP"/&gt;
3671 &lt;/file-transfer-modes&gt;
3672 &lt;/ivrInfo&gt;
3673 &lt;/mediaResourceRequest&gt;
3674 &lt;/mrbconsumer&gt;
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692 <span class="grey">Boulton, et al. Standards Track [Page 66]</span></pre>
3693 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-67" ></span>
3694 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3695
3696
3697 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. AS &lt;- MRB (200 to POST, Consumer response)</span>
3698 ---------------------------------------------
3699 HTTP/1.1 200 OK
3700 X-Powered-By: Servlet/2.5
3701 Server: Sun GlassFish Communications Server 1.5
3702 Content-Type: application/mrb-consumer+xml;charset=ISO-8859-1
3703 Content-Length: 1133
3704 Date: Mon, 12 Apr 2011 14:59:26 GMT
3705
3706 &lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&gt;
3707 &lt;mrbconsumer version="1.0" xmlns="urn:ietf:params:xml:ns:mrb-consumer" &gt;
3708 &lt;mediaResourceResponse reason="Resource found" status="200"
3709 id="gh11x23v"&gt;
3710 &lt;response-session-info&gt;
3711 &lt;session-id&gt;5t3Y4IQ84gY1&lt;/session-id&gt;
3712 &lt;seq&gt;9&lt;/seq&gt;
3713 &lt;expires&gt;3600&lt;/expires&gt;
3714 &lt;media-server-address
3715 uri="sip:[email protected]:5080"&gt;
3716 &lt;ivr-sessions&gt;
3717 &lt;rtp-codec name="audio/basic"&gt;
3718 &lt;decoding&gt;60&lt;/decoding&gt;
3719 &lt;encoding&gt;60&lt;/encoding&gt;
3720 &lt;/rtp-codec&gt;
3721 &lt;/ivr-sessions&gt;
3722 &lt;/media-server-address&gt;
3723 &lt;media-server-address
3724 uri="sip:[email protected]:5080"&gt;
3725 &lt;ivr-sessions&gt;
3726 &lt;rtp-codec name="audio/basic"&gt;
3727 &lt;decoding&gt;40&lt;/decoding&gt;
3728 &lt;encoding&gt;40&lt;/encoding&gt;
3729 &lt;/rtp-codec&gt;
3730 &lt;/ivr-sessions&gt;
3731 &lt;/media-server-address&gt;
3732 &lt;/response-session-info&gt;
3733 &lt;/mediaResourceResponse&gt;
3734 &lt;/mrbconsumer&gt;
3735
3736 As the example shows, the request and response are associated by
3737 means of the 'id' attribute (id="gh11x23v"). The MRB has picked '9'
3738 as the random sequence number that needs to be incremented by the
3739 Application Server for the subsequent request associated with the
3740 same session.
3741
3742
3743
3744
3745
3746
3747
3748 <span class="grey">Boulton, et al. Standards Track [Page 67]</span></pre>
3749 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-68" ></span>
3750 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3751
3752
3753 The rest of the scenario is omitted for brevity. After having
3754 received the 'mediaResourceResponse', the Application Server has the
3755 URIs of two Media Servers able to fulfill its media requirements and
3756 can start a control dialog with one or both of them.
3757
3758 <span class="h4"><a class="selflink" id="section-9.2.2" href="#section-9.2.2">9.2.2</a>. IAMM Examples</span>
3759
3760 Two separate examples are presented for the IAMM case: in fact, IAMM
3761 can take advantage of two different approaches with respect to the
3762 SIP dialogs to be exploited to carry Consumer messages, i.e., i) a
3763 SIP control dialog to create a Control Channel, and ii) a UAC media
3764 dialog to attach to a Media Server. To make things clearer for the
3765 reader, the same Consumer request as the one presented in the Query
3766 mode will be sent, in order to clarify how the behavior of the
3767 involved parties may differ.
3768
3769 <span class="h5"><a class="selflink" id="section-9.2.2.1" href="#section-9.2.2.1">9.2.2.1</a>. IAMM Example: CFW-Based Approach</span>
3770
3771 The following example assumes that the interested Application Server
3772 already knows the SIP URI of an MRB.
3773
3774 Figure 11 shows the first approach, i.e., SIP-based transactions
3775 between the Application Server, the MRB, and one Media Server that
3776 the MRB chooses from the two that are allocated to fulfill the
3777 request. The diagram is more complex than before. This is basically
3778 a scenario envisaging the MRB as a B2BUA. The Application Server
3779 sends a SIP INVITE (1.) containing both a CFW-related SDP and a
3780 Consumer request (multipart body). The MRB sends a provisional
3781 response to the Application Server (2.) and starts working on the
3782 request. First of all, it makes use of the Consumer request from the
3783 Application Server to determine which Media Servers should be
3784 exploited. Once the right Media Servers have been chosen (MS1 and
3785 MS2 in the example), the MRB sends a new SIP INVITE (3.) to one of
3786 the Media Servers (MS1 in the example) by just including the SDP part
3787 of the original request. That Media Server negotiates this INVITE as
3788 specified in [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>] (4., 5., 6.), providing the MRB with its own
3789 CFW-related SDP. The MRB replies to the original Application Server
3790 INVITE preparing a SIP 200 OK with another multipart body (7.): this
3791 multipart body includes the Consumer response used by the MRB to
3792 determine the right Media Servers and the SDP returned by the Media
3793 Server (MS1) in (5.). The Application Server finally acknowledges
3794 the 200 OK (8.), and can start a CFW connection towards that Media
3795 Server (MS1). Since the MRB provided the Application Server with two
3796 Media Server instances to fulfill its requirements, the Application
3797 Server can use the URI in the &lt;media-server-address&gt; element in the
3798 &lt;mediaResourceResponse&gt; that describes the other Media Server to
3799 establish a CFW channel with that Media Server (MS2) as well.
3800
3801
3802
3803
3804 <span class="grey">Boulton, et al. Standards Track [Page 68]</span></pre>
3805 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-69" ></span>
3806 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3807
3808
3809 Please note that to ease the reading of the protocol contents a
3810 simple '=_Part' is used whenever a boundary for a 'multipart/mixed'
3811 payload is provided, instead of the actual boundary that would be
3812 inserted in the SIP messages.
3813
3814 AS MRB MS1 MS2
3815 | | | |
3816 | 1. INVITE | | |
3817 | (multipart/mixed) | | |
3818 |----------------------&gt;| | |
3819 | 2. 100 (Trying) | | |
3820 |&lt;----------------------| | |
3821 | |--+ Extract SDP and | |
3822 | | | MRB payloads; handle | |
3823 | |&lt;-+ Consumer request to | |
3824 | | pick MSs (MS1 and MS2) | |
3825 | | | |
3826 | | 3. INVITE | |
3827 | | (only copy SDP from 1.) | |
3828 | |--------------------------&gt;| |
3829 | | 4. 100 (Trying) | |
3830 | |&lt;--------------------------| |
3831 | | |--+ Negotiate |
3832 | | | | CFW Control |
3833 | | |&lt;-+ Channel |
3834 | | 5. 200 OK | |
3835 | |&lt;--------------------------| |
3836 | | 6. ACK | |
3837 | |--------------------------&gt;| |
3838 | Prepare new +--| | |
3839 | payload with | | | |
3840 | SDP from MS and +-&gt;| | |
3841 | Consumer reply | | |
3842 | | | |
3843 | 7. 200 OK | | |
3844 | (multipart/mixed) | | |
3845 |&lt;----------------------| | |
3846 | 8. ACK | | |
3847 |----------------------&gt;| | |
3848 | | | |
3849 |--+ Read Cons. reply | | |
3850 | | and use SDP to | | |
3851 |&lt;-+ create CFW Chn. | | |
3852 | | | |
3853 | | |
3854 | Create TCP CFW channel towards MS1 (if needed) | |
3855 |--------------------------------------------------&gt;| |
3856 | | |
3857
3858
3859
3860 <span class="grey">Boulton, et al. Standards Track [Page 69]</span></pre>
3861 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-70" ></span>
3862 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3863
3864
3865 |&lt;&lt;############## TCP CONNECTION #################&gt;&gt;| |
3866 | | |
3867 | CFW SYNC | |
3868 |++++++++++++++++++++++++++++++++++++++++++++++++++&gt;| |
3869 | | |
3870 . . . .
3871 . . . .
3872 | | |
3873 | Negotiate SIP control dialog with MS2 |
3874 |&lt;------------------------------------------------------------------&gt;|
3875 | Create TCP CFW channel towards MS2 as well (if needed) |
3876 |-------------------------------------------------------------------&gt;|
3877 | |
3878 |&lt;&lt;######################## TCP CONNECTION ########################&gt;&gt;|
3879 | |
3880 | CFW SYNC |
3881 |+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++&gt;|
3882 | |
3883 | | | |
3884 . . . .
3885 . . . .
3886
3887 Figure 11: Consumer Example (IAMM/Control Channel): Sequence Diagram
3888
3889 The rest of this section includes an almost full trace of the
3890 messages associated with the previous sequence diagram. Only the
3891 relevant SIP messages are shown (both the INVITEs and the 200 OKs),
3892 and only the relevant headers are preserved for brevity (Content-Type
3893 and multipart-related information). Specifically:
3894
3895 1. the original INVITE (1.) containing both a CFW-related SDP
3896 (Connection-Oriented Media (COMEDIA) information to negotiate a
3897 new Control Channel) and a Consumer &lt;mediaResourceRequest&gt;;
3898
3899 2. the INVITE sent by the MRB (acting as a B2BUA) to the Media
3900 Server (3.), containing only the CFW-related SDP from the
3901 original INVITE;
3902
3903 3. the 200 OK sent by the Media Server back to the MRB (5.) to
3904 complete the CFW-related negotiation (SDP only);
3905
3906 4. the 200 OK sent by the MRB back to the Application Server in
3907 response to the original INVITE (7.), containing both the
3908 CFW-related information sent by the Media Server and a Consumer
3909 &lt;mediaResourceRequest&gt; documenting the MRB's decision to use that
3910 Media Server.
3911
3912
3913
3914
3915
3916 <span class="grey">Boulton, et al. Standards Track [Page 70]</span></pre>
3917 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-71" ></span>
3918 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3919
3920
3921 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. AS -&gt; MRB (INVITE multipart/mixed)</span>
3922 -------------------------------------
3923 [..]
3924 Content-Type: multipart/mixed;boundary="=_Part"
3925
3926 =_Part
3927 Content-Type: application/sdp
3928
3929 v=0
3930 o=- 2890844526 2890842807 IN IP4 as.example.com
3931 s=MediaCtrl
3932 c=IN IP4 as.example.com
3933 t=0 0
3934 m=application 48035 TCP cfw
3935 a=connection:new
3936 a=setup:active
3937 a=cfw-id:vF0zD4xzUAW9
3938 a=ctrl-package:msc-mixer/1.0
3939 a=ctrl-package:msc-ivr/1.0
3940
3941 =_Part
3942 Content-Type: application/mrb-consumer+xml
3943
3944 &lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&gt;
3945 &lt;mrbconsumer version="1.0"
3946 xmlns="urn:ietf:params:xml:ns:mrb-consumer"&gt;
3947 &lt;mediaResourceRequest id="pz78hnq1"&gt;
3948 &lt;generalInfo&gt;
3949 &lt;packages&gt;
3950 &lt;package&gt;msc-ivr/1.0&lt;/package&gt;
3951 &lt;package&gt;msc-mixer/1.0&lt;/package&gt;
3952 &lt;/packages&gt;
3953 &lt;/generalInfo&gt;
3954 &lt;ivrInfo&gt;
3955 &lt;ivr-sessions&gt;
3956 &lt;rtp-codec name="audio/basic"&gt;
3957 &lt;decoding&gt;100&lt;/decoding&gt;
3958 &lt;encoding&gt;100&lt;/encoding&gt;
3959 &lt;/rtp-codec&gt;
3960 &lt;/ivr-sessions&gt;
3961 &lt;file-formats&gt;
3962 &lt;required-format name="audio/x-wav"/&gt;
3963 &lt;/file-formats&gt;
3964 &lt;file-transfer-modes&gt;
3965 &lt;file-transfer-mode package="msc-ivr/1.0" name="HTTP"/&gt;
3966 &lt;/file-transfer-modes&gt;
3967 &lt;/ivrInfo&gt;
3968 &lt;/mediaResourceRequest&gt;
3969
3970
3971
3972 <span class="grey">Boulton, et al. Standards Track [Page 71]</span></pre>
3973 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-72" ></span>
3974 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
3975
3976
3977 &lt;/mrbconsumer&gt;
3978
3979 =_Part
3980
3981
3982 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. MRB -&gt; MS (INVITE sdp only)</span>
3983 ------------------------------
3984 [..]
3985 Content-Type: application/sdp
3986
3987 v=0
3988 o=- 2890844526 2890842807 IN IP4 as.example.com
3989 s=MediaCtrl
3990 c=IN IP4 as.example.com
3991 t=0 0
3992 m=application 48035 TCP cfw
3993 a=connection:new
3994 a=setup:active
3995 a=cfw-id:vF0zD4xzUAW9
3996 a=ctrl-package:msc-mixer/1.0
3997 a=ctrl-package:msc-ivr/1.0
3998
3999
4000 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. MRB &lt;- MS (200 OK sdp)</span>
4001 -------------------------
4002 [..]
4003 Content-Type: application/sdp
4004
4005 v=0
4006 o=lminiero 2890844526 2890842808 IN IP4 ms.example.net
4007 s=MediaCtrl
4008 c=IN IP4 ms.example.net
4009 t=0 0
4010 m=application 7575 TCP cfw
4011 a=connection:new
4012 a=setup:passive
4013 a=cfw-id:vF0zD4xzUAW9
4014 a=ctrl-package:msc-mixer/1.0
4015 a=ctrl-package:msc-ivr/1.0
4016 a=ctrl-package:mrb-publish/1.0
4017 a=ctrl-package:msc-example-pkg/1.0
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028 <span class="grey">Boulton, et al. Standards Track [Page 72]</span></pre>
4029 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-73" ></span>
4030 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4031
4032
4033 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. AS &lt;- MRB (200 OK multipart/mixed)</span>
4034 -------------------------------------
4035 [..]
4036 Content-Type: multipart/mixed;boundary="=_Part"
4037
4038 =_Part
4039 Content-Type: application/sdp
4040
4041 v=0
4042 o=lminiero 2890844526 2890842808 IN IP4 ms.example.net
4043 s=MediaCtrl
4044 c=IN IP4 ms.example.net
4045 t=0 0
4046 m=application 7575 TCP cfw
4047 a=connection:new
4048 a=setup:passive
4049 a=cfw-id:vF0zD4xzUAW9
4050 a=ctrl-package:msc-mixer/1.0
4051 a=ctrl-package:msc-ivr/1.0
4052 a=ctrl-package:mrb-publish/1.0
4053 a=ctrl-package:msc-example-pkg/1.0
4054
4055 =_Part
4056 Content-Type: application/mrb-consumer+xml
4057
4058 &lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&gt;
4059 &lt;mrbconsumer version="1.0"
4060 xmlns="urn:ietf:params:xml:ns:mrb-consumer" &gt;
4061 &lt;mediaResourceResponse reason="Resource found" status="200"
4062 id="pz78hnq1"&gt;
4063 &lt;response-session-info&gt;
4064 &lt;session-id&gt;z1skKYZQ3eFu&lt;/session-id&gt;
4065 &lt;seq&gt;9&lt;/seq&gt;
4066 &lt;expires&gt;3600&lt;/expires&gt;
4067 &lt;media-server-address
4068 uri="sip:[email protected]:5080"&gt;
4069 &lt;connection-id&gt;32pbdxZ8:KQw677BF&lt;/connection-id&gt;
4070 &lt;ivr-sessions&gt;
4071 &lt;rtp-codec name="audio/basic"&gt;
4072 &lt;decoding&gt;60&lt;/decoding&gt;
4073 &lt;encoding&gt;60&lt;/encoding&gt;
4074 &lt;/rtp-codec&gt;
4075 &lt;/ivr-sessions&gt;
4076 &lt;/media-server-address&gt;
4077 &lt;media-server-address
4078 uri="sip:[email protected]:5080"&gt;
4079 &lt;ivr-sessions&gt;
4080 &lt;rtp-codec name="audio/basic"&gt;
4081
4082
4083
4084 <span class="grey">Boulton, et al. Standards Track [Page 73]</span></pre>
4085 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-74" ></span>
4086 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4087
4088
4089 &lt;decoding&gt;40&lt;/decoding&gt;
4090 &lt;encoding&gt;40&lt;/encoding&gt;
4091 &lt;/rtp-codec&gt;
4092 &lt;/ivr-sessions&gt;
4093 &lt;/media-server-address&gt;
4094 &lt;/response-session-info&gt;
4095 &lt;/mediaResourceResponse&gt;
4096 &lt;/mrbconsumer&gt;
4097
4098 =_Part
4099
4100 As the previous example illustrates, the only difference in the
4101 response that the MRB provides to the Application Server is in the
4102 'connection-id' attribute that is added to the first allocated Media
4103 Server instance: this allows the Application Server to understand
4104 that the MRB has sent the CFW channel negotiation to that specific
4105 Media Server and that the connection-id to be used is the one
4106 provided. This will be described in more detail in the following
4107 section for the media dialog-based approach.
4108
4109 The continuation of the scenario (the Application Server connecting
4110 to MS1 to start the Control Channel and the related SYNC message, the
4111 Application Server connecting to MS2 as well later on, all the media
4112 dialogs being attached to either Media Server) is omitted for
4113 brevity.
4114
4115 <span class="h5"><a class="selflink" id="section-9.2.2.2" href="#section-9.2.2.2">9.2.2.2</a>. IAMM Example: Media Dialog-Based Approach</span>
4116
4117 The following example assumes that the interested Application Server
4118 already knows the SIP URI of an MRB.
4119
4120 Figure 12 shows the second approach, i.e., SIP-based transactions
4121 between a SIP client, the Application Server, the MRB, and the Media
4122 Server that the MRB chooses. The interaction is basically the same
4123 as previous examples (e.g., contents of the multipart body), but
4124 considering that a new party is involved in the communication, the
4125 diagram is slightly more complex than before. As before, the MRB
4126 acts as a B2BUA. A UAC sends a SIP INVITE to a SIP URI handled by
4127 the Application Server, since it is interested to its services (1.).
4128 The Application Server sends a provisional response (2.) and, since
4129 it doesn't have the resources yet, sends to the MRB a new SIP INVITE
4130 (3.) containing both the UAC media-related SDP and a Consumer request
4131 (multipart body). The MRB sends a provisional response to the
4132 Application Server (4.) and starts working on the request. First of
4133 all, it makes use of the Consumer request from the Application Server
4134 to determine which Media Servers should be chosen. Once the Media
4135 Server has been chosen, the MRB sends a new SIP INVITE to one of the
4136 Media Servers by including the SDP part of the original request (5.).
4137
4138
4139
4140 <span class="grey">Boulton, et al. Standards Track [Page 74]</span></pre>
4141 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-75" ></span>
4142 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4143
4144
4145 The Media Server negotiates this INVITE as specified in [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>]
4146 (6., 7., 8.) to allocate the needed media resources to handle the new
4147 media dialog, eventually providing the MRB with its own media-related
4148 SDP. The MRB replies to the original Application Server INVITE
4149 preparing a SIP 200 OK with a multipart body (9.): this multipart
4150 body includes the Consumer response from the MRB indicating the
4151 chosen Media Servers and the SDP returned by the Media Server in
4152 (7.). The Application Server finally acknowledges the 200 OK (10.)
4153 and ends the scenario by eventually providing the UAC with the SDP it
4154 needs to set up the RTP channels with the chosen Media Server: a
4155 separate direct SIP control dialog may be initiated by the
4156 Application Server to the same Media Server in order to set up a
4157 Control Channel to manipulate the media dialog.
4158
4159 As with the IAMM/Control Channel example in the prior section, this
4160 example has the MRB selecting Media Server resources across two Media
4161 Server instances. The convention could be that the MRB sent the SIP
4162 INVITE to the first Media Server in the list provided to the
4163 Application Server in the Consumer response information. For the
4164 sake of brevity, considerations related to connecting to the other
4165 Media Servers as well are omitted, since they have already been
4166 addressed in the previous section.
4167
4168 Please note that to ease the reading of the protocol contents, a
4169 simple '=_Part' is used whenever a boundary for a 'multipart/mixed'
4170 payload is provided, instead of the actual boundary that would be
4171 inserted in the SIP messages.
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196 <span class="grey">Boulton, et al. Standards Track [Page 75]</span></pre>
4197 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-76" ></span>
4198 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4199
4200
4201 UAC AS MRB MS
4202 | | | |
4203 | 1. INVITE | | |
4204 | (media SDP) | | |
4205 |--------------&gt;| | |
4206 | 2. 100 Trying | | |
4207 |&lt;--------------| | |
4208 | | 3. INVITE | |
4209 | | (multipart/mixed) | |
4210 | |----------------------&gt;| |
4211 | | 4. 100 (Trying) | |
4212 | |&lt;----------------------| |
4213 | | |--+ Extract SDP and |
4214 | | | | MRB payloads; handle |
4215 | | |&lt;-+ Consumer request to |
4216 | | | pick Media Servers |
4217 | | | |
4218 | | | 5. INVITE |
4219 | | | (only copy SDP from 3.) |
4220 | | |--------------------------&gt;|
4221 | | | 6. 100 (Trying) |
4222 | | |&lt;--------------------------|
4223 | | | +--|
4224 | | | Handle media dialog | |
4225 | | | (connection-id) +-&gt;|
4226 | | | |
4227 | | | 7. 200 OK |
4228 | | |&lt;--------------------------|
4229 | | | 8. ACK |
4230 | | |--------------------------&gt;|
4231 | | Prepare new +--| |
4232 | | payload with | | |
4233 | | SDP from MS and +-&gt;| |
4234 | | Consumer reply | |
4235 | | | |
4236 | | 9. 200 OK | |
4237 | | (multipart/mixed) | |
4238 | |&lt;----------------------| |
4239 | | 10. ACK | |
4240 | |----------------------&gt;| |
4241 | | | |
4242 | |--+ Read Cons. reply | |
4243 | | | and send SDP | |
4244 | |&lt;-+ back to UAC | |
4245 | 11. 200 OK | | |
4246 |&lt;--------------| | |
4247 | 12. ACK | | |
4248 |--------------&gt;| | |
4249
4250
4251
4252 <span class="grey">Boulton, et al. Standards Track [Page 76]</span></pre>
4253 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-77" ></span>
4254 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4255
4256
4257 | | | |
4258 |&lt;&lt;*************************** RTP *******************************&gt;&gt;|
4259 | | | |
4260 | |--+ Negotiate | |
4261 | | | CFW channel | |
4262 | |&lt;-+ towards MS | |
4263 | | (if needed) | |
4264 . . . .
4265 . . . .
4266 | | | |
4267 | | |
4268 | | Create TCP CFW channel towards MS (if needed) |
4269 | |--------------------------------------------------&gt;|
4270 | | |
4271 | |&lt;&lt;############## TCP CONNECTION #################&gt;&gt;|
4272 | | |
4273 | | CFW SYNC |
4274 | |++++++++++++++++++++++++++++++++++++++++++++++++++&gt;|
4275 | | |
4276 . . . .
4277 . . . .
4278
4279 Figure 12: Consumer Example (IAMM/Media Dialog): Sequence Diagram
4280
4281 The rest of this section includes a trace of the messages associated
4282 with the previous sequence diagram. Only the relevant SIP messages
4283 are shown (both the INVITEs and the 200 OKs), and only the relevant
4284 headers are preserved for brevity (Content-Type, From/To, and
4285 multipart-related information). Specifically:
4286
4287 1. the original INVITE (1.) containing the media-related SDP sent by
4288 a UAC;
4289
4290 2. the INVITE sent by the AS to the MRB (3.), containing both the
4291 media-related SDP and a Consumer &lt;mediaResourceRequest&gt;;
4292
4293 3. the INVITE sent by the MRB (acting as a B2BUA) to the Media
4294 Server (5.), containing only the media-related SDP from the
4295 original INVITE;
4296
4297 4. the 200 OK sent by the Media Server back to the MRB (7.) to
4298 complete the media-related negotiation (SDP only);
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308 <span class="grey">Boulton, et al. Standards Track [Page 77]</span></pre>
4309 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-78" ></span>
4310 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4311
4312
4313 5. the 200 OK sent by the MRB back to the Application Server in
4314 response to the original INVITE (9.), containing both the
4315 media-related information sent by the Media Server and a Consumer
4316 &lt;mediaResourceRequest&gt; documenting the MRB's decision to use that
4317 Media Server;
4318
4319 6. the 200 OK sent by the Application Server back to the UAC to have
4320 it set up the RTP channel(s) with the Media Server (11.).
4321
4322
4323 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. UAC -&gt; AS (INVITE with media SDP)</span>
4324 ------------------------------------
4325 [..]
4326 From: &lt;sip:[email protected]&gt;;tag=1153573888
4327 To: &lt;sip:[email protected]&gt;
4328 [..]
4329 Content-Type: application/sdp
4330
4331 v=0
4332 o=lminiero 123456 654321 IN IP4 203.0.113.2
4333 s=A conversation
4334 c=IN IP4 203.0.113.2
4335 t=0 0
4336 m=audio 7078 RTP/AVP 0 3 8 101
4337 a=rtpmap:0 PCMU/8000/1
4338 a=rtpmap:3 GSM/8000/1
4339 a=rtpmap:8 PCMA/8000/1
4340 a=rtpmap:101 telephone-event/8000
4341 a=fmtp:101 0-11
4342 m=video 9078 RTP/AVP 98
4343
4344
4345 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. AS -&gt; MRB (INVITE multipart/mixed)</span>
4346 -------------------------------------
4347 [..]
4348 From: &lt;sip:[email protected]&gt;;tag=fd4fush5
4349 To: &lt;sip:[email protected]&gt;
4350 [..]
4351 Content-Type: multipart/mixed;boundary="=_Part"
4352
4353 =_Part
4354 Content-Type: application/sdp
4355
4356 v=0
4357 o=lminiero 123456 654321 IN IP4 203.0.113.2
4358 s=A conversation
4359 c=IN IP4 203.0.113.2
4360 t=0 0
4361
4362
4363
4364 <span class="grey">Boulton, et al. Standards Track [Page 78]</span></pre>
4365 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-79" ></span>
4366 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4367
4368
4369 m=audio 7078 RTP/AVP 0 3 8 101
4370 a=rtpmap:0 PCMU/8000/1
4371 a=rtpmap:3 GSM/8000/1
4372 a=rtpmap:8 PCMA/8000/1
4373 a=rtpmap:101 telephone-event/8000
4374 a=fmtp:101 0-11
4375 m=video 9078 RTP/AVP 98
4376
4377 =_Part
4378 Content-Type: application/mrb-consumer+xml
4379
4380 &lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&gt;
4381 &lt;mrbconsumer version="1.0"
4382 xmlns="urn:ietf:params:xml:ns:mrb-consumer"&gt;
4383 &lt;mediaResourceRequest id="ns56g1x0"&gt;
4384 &lt;generalInfo&gt;
4385 &lt;packages&gt;
4386 &lt;package&gt;msc-ivr/1.0&lt;/package&gt;
4387 &lt;package&gt;msc-mixer/1.0&lt;/package&gt;
4388 &lt;/packages&gt;
4389 &lt;/generalInfo&gt;
4390 &lt;ivrInfo&gt;
4391 &lt;ivr-sessions&gt;
4392 &lt;rtp-codec name="audio/basic"&gt;
4393 &lt;decoding&gt;100&lt;/decoding&gt;
4394 &lt;encoding&gt;100&lt;/encoding&gt;
4395 &lt;/rtp-codec&gt;
4396 &lt;/ivr-sessions&gt;
4397 &lt;file-formats&gt;
4398 &lt;required-format name="audio/x-wav"/&gt;
4399 &lt;/file-formats&gt;
4400 &lt;file-transfer-modes&gt;
4401 &lt;file-transfer-mode package="msc-ivr/1.0" name="HTTP"/&gt;
4402 &lt;/file-transfer-modes&gt;
4403 &lt;/ivrInfo&gt;
4404 &lt;/mediaResourceRequest&gt;
4405 &lt;/mrbconsumer&gt;
4406
4407 =_Part
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420 <span class="grey">Boulton, et al. Standards Track [Page 79]</span></pre>
4421 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-80" ></span>
4422 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4423
4424
4425 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. MRB -&gt; MS (INVITE sdp only)</span>
4426 ------------------------------
4427 [..]
4428 From: &lt;sip:[email protected]:5060&gt;;tag=32pbdxZ8
4429 To: &lt;sip:[email protected]:5080&gt;
4430 [..]
4431 Content-Type: application/sdp
4432
4433 v=0
4434 o=lminiero 123456 654321 IN IP4 203.0.113.2
4435 s=A conversation
4436 c=IN IP4 203.0.113.2
4437 t=0 0
4438 m=audio 7078 RTP/AVP 0 3 8 101
4439 a=rtpmap:0 PCMU/8000/1
4440 a=rtpmap:3 GSM/8000/1
4441 a=rtpmap:8 PCMA/8000/1
4442 a=rtpmap:101 telephone-event/8000
4443 a=fmtp:101 0-11
4444 m=video 9078 RTP/AVP 98
4445
4446
4447 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. MRB &lt;- MS (200 OK sdp)</span>
4448 -------------------------
4449 [..]
4450 From: &lt;sip:[email protected]:5060&gt;;tag=32pbdxZ8
4451 To: &lt;sip:[email protected]:5080&gt;;tag=KQw677BF
4452 [..]
4453 Content-Type: application/sdp
4454
4455 v=0
4456 o=lminiero 123456 654322 IN IP4 203.0.113.1
4457 s=MediaCtrl
4458 c=IN IP4 203.0.113.1
4459 t=0 0
4460 m=audio 63442 RTP/AVP 0 3 8 101
4461 a=rtpmap:0 PCMU/8000
4462 a=rtpmap:3 GSM/8000
4463 a=rtpmap:8 PCMA/8000
4464 a=rtpmap:101 telephone-event/8000
4465 a=fmtp:101 0-15
4466 a=ptime:20
4467 a=label:7eda834
4468 m=video 33468 RTP/AVP 98
4469 a=rtpmap:98 H263-1998/90000
4470 a=fmtp:98 CIF=2
4471 a=label:0132ca2
4472
4473
4474
4475
4476 <span class="grey">Boulton, et al. Standards Track [Page 80]</span></pre>
4477 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-81" ></span>
4478 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4479
4480
4481 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. AS &lt;- MRB (200 OK multipart/mixed)</span>
4482 -------------------------------------
4483 [..]
4484 From: &lt;sip:[email protected]&gt;;tag=fd4fush5
4485 To: &lt;sip:[email protected]&gt;;tag=117652221
4486 [..]
4487 Content-Type: multipart/mixed;boundary="=_Part"
4488
4489 =_Part
4490 Content-Type: application/sdp
4491
4492 v=0
4493 o=lminiero 123456 654322 IN IP4 203.0.113.1
4494 s=MediaCtrl
4495 c=IN IP4 203.0.113.1
4496 t=0 0
4497 m=audio 63442 RTP/AVP 0 3 8 101
4498 a=rtpmap:0 PCMU/8000
4499 a=rtpmap:3 GSM/8000
4500 a=rtpmap:8 PCMA/8000
4501 a=rtpmap:101 telephone-event/8000
4502 a=fmtp:101 0-15
4503 a=ptime:20
4504 a=label:7eda834
4505 m=video 33468 RTP/AVP 98
4506 a=rtpmap:98 H263-1998/90000
4507 a=fmtp:98 CIF=2
4508 a=label:0132ca2
4509
4510 =_Part
4511 Content-Type: application/mrb-consumer+xml
4512
4513 &lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&gt;
4514 &lt;mrbconsumer version="1.0"
4515 xmlns="urn:ietf:params:xml:ns:mrb-consumer" &gt;
4516 &lt;mediaResourceResponse reason="Resource found" status="200"
4517 id="ns56g1x0"&gt;
4518 &lt;response-session-info&gt;
4519 &lt;session-id&gt;z1skKYZQ3eFu&lt;/session-id&gt;
4520 &lt;seq&gt;9&lt;/seq&gt;
4521 &lt;expires&gt;3600&lt;/expires&gt;
4522 &lt;media-server-address
4523 uri="sip:[email protected]:5080"&gt;
4524 &lt;connection-id&gt;32pbdxZ8:KQw677BF&lt;/connection-id&gt;
4525 &lt;ivr-sessions&gt;
4526 &lt;rtp-codec name="audio/basic"&gt;
4527 &lt;decoding&gt;60&lt;/decoding&gt;
4528 &lt;encoding&gt;60&lt;/encoding&gt;
4529
4530
4531
4532 <span class="grey">Boulton, et al. Standards Track [Page 81]</span></pre>
4533 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-82" ></span>
4534 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4535
4536
4537 &lt;/rtp-codec&gt;
4538 &lt;/ivr-sessions&gt;
4539 &lt;/media-server-address&gt;
4540 &lt;media-server-address
4541 uri="sip:[email protected]:5080"&gt;
4542 &lt;ivr-sessions&gt;
4543 &lt;rtp-codec name="audio/basic"&gt;
4544 &lt;decoding&gt;40&lt;/decoding&gt;
4545 &lt;encoding&gt;40&lt;/encoding&gt;
4546 &lt;/rtp-codec&gt;
4547 &lt;/ivr-sessions&gt;
4548 &lt;/media-server-address&gt;
4549 &lt;/response-session-info&gt;
4550 &lt;/mediaResourceResponse&gt;
4551 &lt;/mrbconsumer&gt;
4552
4553 =_Part
4554
4555
4556 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. UAC &lt;- AS (200 OK sdp)</span>
4557 --------------------------
4558 [..]
4559 From: &lt;sip:[email protected]&gt;;tag=1153573888
4560 To: &lt;sip:[email protected]&gt;;tag=bcd47c32
4561 [..]
4562 Content-Type: application/sdp
4563
4564 v=0
4565 o=lminiero 123456 654322 IN IP4 203.0.113.1
4566 s=MediaCtrl
4567 c=IN IP4 203.0.113.1
4568 t=0 0
4569 m=audio 63442 RTP/AVP 0 3 8 101
4570 a=rtpmap:0 PCMU/8000
4571 a=rtpmap:3 GSM/8000
4572 a=rtpmap:8 PCMA/8000
4573 a=rtpmap:101 telephone-event/8000
4574 a=fmtp:101 0-15
4575 a=ptime:20
4576 a=label:7eda834
4577 m=video 33468 RTP/AVP 98
4578 a=rtpmap:98 H263-1998/90000
4579 a=fmtp:98 CIF=2
4580 a=label:0132ca2
4581
4582 As the examples illustrate, as in the IAMM/Control Channel example,
4583 the MRB provides the Application Server with a &lt;media-server-address&gt;
4584 element in the Consumer response: the 'uri' attribute identifies the
4585
4586
4587
4588 <span class="grey">Boulton, et al. Standards Track [Page 82]</span></pre>
4589 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-83" ></span>
4590 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4591
4592
4593 specific Media Server to which the MRB has sent the SDP media
4594 negotiation, and the 'connection-id' enables the Application Server
4595 to identify to the Media Server the dialog between the MRB and Media
4596 Server. This attribute is needed, since according to the framework
4597 specification [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>] the connection-id is built out of the From/To
4598 tags of the dialog between the MRB and Media Server; since the MRB
4599 acts as a B2BUA in this scenario, without that attribute the
4600 Application Server does not know the relevant tags, thus preventing
4601 the CFW protocol from working as expected.
4602
4603 The continuation of the scenario (the Application Server connecting
4604 to the Media Server to start the Control Channel, the SYNC message,
4605 etc.) is omitted for brevity.
4606
4607 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Media Service Resource Publisher Interface XML Schema</span>
4608
4609 This section gives the XML Schema Definition
4610 [<a href="#ref-W3C.REC-xmlschema-1-20041028">W3C.REC-xmlschema-1-20041028</a>] [<a href="#ref-W3C.REC-xmlschema-2-20041028">W3C.REC-xmlschema-2-20041028</a>] of the
4611 "application/mrb-publish+xml" format.
4612
4613 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
4614 &lt;xsd:schema targetNamespace="urn:ietf:params:xml:ns:mrb-publish"
4615 elementFormDefault="qualified" blockDefault="#all"
4616 xmlns="urn:ietf:params:xml:ns:mrb-publish"
4617 xmlns:fw="urn:ietf:params:xml:ns:control:framework-attributes"
4618 xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
4619 xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt;
4620
4621 &lt;xsd:annotation&gt;
4622 &lt;xsd:documentation&gt;
4623 IETF MediaCtrl MRB 1.0
4624
4625 This is the schema of the IETF MediaCtrl MRB package.
4626
4627 The schema namespace is urn:ietf:params:xml:ns:mrb-publish
4628
4629 &lt;/xsd:documentation&gt;
4630 &lt;/xsd:annotation&gt;
4631
4632
4633 &lt;!--
4634 #############################################################
4635
4636 SCHEMA IMPORTS
4637
4638 #############################################################
4639 --&gt;
4640
4641
4642
4643
4644 <span class="grey">Boulton, et al. Standards Track [Page 83]</span></pre>
4645 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-84" ></span>
4646 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4647
4648
4649 &lt;xsd:import namespace="http://www.w3.org/XML/1998/namespace"
4650 schemaLocation="http://www.w3.org/2001/xml.xsd"&gt;
4651 &lt;xsd:annotation&gt;
4652 &lt;xsd:documentation&gt;
4653 This import brings in the XML attributes for
4654 xml:base, xml:lang, etc.
4655 &lt;/xsd:documentation&gt;
4656 &lt;/xsd:annotation&gt;
4657 &lt;/xsd:import&gt;
4658
4659 &lt;xsd:import
4660 namespace="urn:ietf:params:xml:ns:control:framework-attributes"
4661 schemaLocation="framework.xsd"&gt;
4662 &lt;xsd:annotation&gt;
4663 &lt;xsd:documentation&gt;
4664 This import brings in the framework attributes for
4665 conferenceid and connectionid.
4666 &lt;/xsd:documentation&gt;
4667 &lt;/xsd:annotation&gt;
4668 &lt;/xsd:import&gt;
4669
4670 &lt;xsd:import
4671 namespace="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
4672 schemaLocation="civicAddress.xsd"&gt;
4673 &lt;xsd:annotation&gt;
4674 &lt;xsd:documentation&gt;
4675 This import brings in the civicAddress specification
4676 from <a href="./rfc5139">RFC 5139</a>.
4677 &lt;/xsd:documentation&gt;
4678 &lt;/xsd:annotation&gt;
4679 &lt;/xsd:import&gt;
4680
4681 &lt;!--
4682 #####################################################
4683
4684 Extensible core type
4685
4686 #####################################################
4687 --&gt;
4688
4689 &lt;xsd:complexType name="Tcore"&gt;
4690 &lt;xsd:annotation&gt;
4691 &lt;xsd:documentation&gt;
4692 This type is extended by other (non-mixed) component types to
4693 allow attributes from other namespaces.
4694 &lt;/xsd:documentation&gt;
4695 &lt;/xsd:annotation&gt;
4696
4697
4698
4699
4700 <span class="grey">Boulton, et al. Standards Track [Page 84]</span></pre>
4701 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-85" ></span>
4702 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4703
4704
4705 &lt;xsd:sequence/&gt;
4706 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
4707 &lt;/xsd:complexType&gt;
4708
4709
4710 &lt;!--
4711 #####################################################
4712
4713 TOP-LEVEL ELEMENT: mrbpublish
4714
4715 #####################################################
4716 --&gt;
4717
4718 &lt;xsd:complexType name="mrbpublishType"&gt;
4719 &lt;xsd:complexContent&gt;
4720 &lt;xsd:extension base="Tcore"&gt;
4721 &lt;xsd:sequence&gt;
4722 &lt;xsd:choice&gt;
4723 &lt;xsd:element ref="mrbrequest" /&gt;
4724 &lt;xsd:element ref="mrbresponse" /&gt;
4725 &lt;xsd:element ref="mrbnotification" /&gt;
4726 &lt;xsd:any namespace="##other" minOccurs="0"
4727 maxOccurs="unbounded" processContents="lax" /&gt;
4728 &lt;/xsd:choice&gt;
4729 &lt;/xsd:sequence&gt;
4730 &lt;xsd:attribute name="version" type="version.datatype"
4731 use="required" /&gt;
4732 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
4733 &lt;/xsd:extension&gt;
4734 &lt;/xsd:complexContent&gt;
4735 &lt;/xsd:complexType&gt;
4736
4737 &lt;xsd:element name="mrbpublish" type="mrbpublishType" /&gt;
4738
4739 &lt;!--
4740 #####################################################
4741
4742 mrbrequest TYPE
4743
4744 #####################################################
4745 --&gt;
4746
4747 &lt;!-- mrbrequest --&gt;
4748
4749 &lt;xsd:complexType name="mrbrequestType"&gt;
4750 &lt;xsd:complexContent&gt;
4751 &lt;xsd:extension base="Tcore"&gt;
4752 &lt;xsd:sequence&gt;
4753
4754
4755
4756 <span class="grey">Boulton, et al. Standards Track [Page 85]</span></pre>
4757 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-86" ></span>
4758 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4759
4760
4761 &lt;xsd:element ref="subscription" /&gt;
4762 &lt;xsd:any namespace="##other" minOccurs="0"
4763 maxOccurs="unbounded" processContents="lax" /&gt;
4764 &lt;/xsd:sequence&gt;
4765 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
4766 &lt;/xsd:extension&gt;
4767 &lt;/xsd:complexContent&gt;
4768 &lt;/xsd:complexType&gt;
4769
4770 &lt;xsd:element name="mrbrequest" type="mrbrequestType" /&gt;
4771
4772 &lt;!-- subscription --&gt;
4773
4774 &lt;xsd:complexType name="subscriptionType"&gt;
4775 &lt;xsd:complexContent&gt;
4776 &lt;xsd:extension base="Tcore"&gt;
4777 &lt;xsd:sequence&gt;
4778 &lt;xsd:element name="expires" type="xsd:nonNegativeInteger"
4779 minOccurs="0" maxOccurs="1" /&gt;
4780 &lt;xsd:element name="minfrequency" type="xsd:nonNegativeInteger"
4781 minOccurs="0" maxOccurs="1" /&gt;
4782 &lt;xsd:element name="maxfrequency" type="xsd:nonNegativeInteger"
4783 minOccurs="0" maxOccurs="1" /&gt;
4784 &lt;xsd:any namespace="##other" minOccurs="0"
4785 maxOccurs="unbounded" processContents="lax" /&gt;
4786 &lt;/xsd:sequence&gt;
4787 &lt;xsd:attribute name="id" type="id.datatype" use="required" /&gt;
4788 &lt;xsd:attribute name="seqnumber" type="xsd:nonNegativeInteger"
4789 use="required" /&gt;
4790 &lt;xsd:attribute name="action" type="action.datatype"
4791 use="required" /&gt;
4792 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
4793 &lt;/xsd:extension&gt;
4794 &lt;/xsd:complexContent&gt;
4795 &lt;/xsd:complexType&gt;
4796
4797 &lt;xsd:element name="subscription" type="subscriptionType" /&gt;
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812 <span class="grey">Boulton, et al. Standards Track [Page 86]</span></pre>
4813 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-87" ></span>
4814 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4815
4816
4817 &lt;!--
4818 #####################################################
4819
4820 mrbresponse TYPE
4821
4822 #####################################################
4823 --&gt;
4824
4825 &lt;!-- mrbresponse --&gt;
4826
4827 &lt;xsd:complexType name="mrbresponseType"&gt;
4828 &lt;xsd:complexContent&gt;
4829 &lt;xsd:extension base="Tcore"&gt;
4830 &lt;xsd:sequence&gt;
4831 &lt;xsd:element ref="subscription" minOccurs="0" maxOccurs="1" /&gt;
4832 &lt;xsd:any namespace="##other" minOccurs="0"
4833 maxOccurs="unbounded" processContents="lax" /&gt;
4834 &lt;/xsd:sequence&gt;
4835 &lt;xsd:attribute name="status" type="status.datatype"
4836 use="required" /&gt;
4837 &lt;xsd:attribute name="reason" type="xsd:string" /&gt;
4838 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
4839 &lt;/xsd:extension&gt;
4840 &lt;/xsd:complexContent&gt;
4841 &lt;/xsd:complexType&gt;
4842
4843
4844 &lt;xsd:element name="mrbresponse" type="mrbresponseType" /&gt;
4845
4846 &lt;!--
4847 #####################################################
4848
4849 mrbnotification TYPE
4850
4851 #####################################################
4852 --&gt;
4853
4854 &lt;!-- mrbnotification --&gt;
4855
4856 &lt;xsd:complexType name="mrbnotificationType"&gt;
4857 &lt;xsd:complexContent&gt;
4858 &lt;xsd:extension base="Tcore"&gt;
4859 &lt;xsd:sequence&gt;
4860 &lt;xsd:element name="media-server-id"
4861 type="subscriptionid.datatype"/&gt;
4862 &lt;xsd:element ref="supported-packages" minOccurs="0" /&gt;
4863 &lt;xsd:element ref="active-rtp-sessions" minOccurs="0" /&gt;
4864 &lt;xsd:element ref="active-mixer-sessions" minOccurs="0" /&gt;
4865
4866
4867
4868 <span class="grey">Boulton, et al. Standards Track [Page 87]</span></pre>
4869 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-88" ></span>
4870 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4871
4872
4873 &lt;xsd:element ref="non-active-rtp-sessions" minOccurs="0" /&gt;
4874 &lt;xsd:element ref="non-active-mixer-sessions" minOccurs="0" /&gt;
4875 &lt;xsd:element ref="media-server-status" minOccurs="0" /&gt;
4876 &lt;xsd:element ref="supported-codecs" minOccurs="0" /&gt;
4877 &lt;xsd:element ref="application-data" minOccurs="0"
4878 maxOccurs="unbounded" /&gt;
4879 &lt;xsd:element ref="file-formats" minOccurs="0" /&gt;
4880 &lt;xsd:element ref="max-prepared-duration" minOccurs="0" /&gt;
4881 &lt;xsd:element ref="dtmf-support" minOccurs="0" /&gt;
4882 &lt;xsd:element ref="mixing-modes" minOccurs="0" /&gt;
4883 &lt;xsd:element ref="supported-tones" minOccurs="0" /&gt;
4884 &lt;xsd:element ref="file-transfer-modes" minOccurs="0" /&gt;
4885 &lt;xsd:element ref="asr-tts-support" minOccurs="0" /&gt;
4886 &lt;xsd:element ref="vxml-support" minOccurs="0" /&gt;
4887 &lt;xsd:element ref="media-server-location" minOccurs="0" /&gt;
4888 &lt;xsd:element ref="label" minOccurs="0" /&gt;
4889 &lt;xsd:element ref="media-server-address" minOccurs="0" /&gt;
4890 &lt;xsd:element ref="encryption" minOccurs="0" /&gt;
4891 &lt;xsd:any namespace="##other" minOccurs="0"
4892 maxOccurs="unbounded" processContents="lax" /&gt;
4893 &lt;/xsd:sequence&gt;
4894 &lt;xsd:attribute name="id" type="subscriptionid.datatype"
4895 use="required" /&gt;
4896 &lt;xsd:attribute name="seqnumber" type="xsd:nonNegativeInteger"
4897 use="required" /&gt;
4898 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
4899 &lt;/xsd:extension&gt;
4900 &lt;/xsd:complexContent&gt;
4901 &lt;/xsd:complexType&gt;
4902
4903 &lt;xsd:element name="mrbnotification" type="mrbnotificationType" /&gt;
4904
4905
4906 &lt;!-- supported-packages --&gt;
4907
4908 &lt;xsd:complexType name="supported-packagesType"&gt;
4909 &lt;xsd:complexContent&gt;
4910 &lt;xsd:extension base="Tcore"&gt;
4911 &lt;xsd:sequence&gt;
4912 &lt;xsd:element ref="package" minOccurs="0"
4913 maxOccurs="unbounded" /&gt;
4914 &lt;xsd:any namespace="##other" minOccurs="0"
4915 maxOccurs="unbounded" processContents="lax" /&gt;
4916 &lt;/xsd:sequence&gt;
4917 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
4918 &lt;/xsd:extension&gt;
4919 &lt;/xsd:complexContent&gt;
4920 &lt;/xsd:complexType&gt;
4921
4922
4923
4924 <span class="grey">Boulton, et al. Standards Track [Page 88]</span></pre>
4925 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-89" ></span>
4926 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4927
4928
4929 &lt;xsd:element name="supported-packages" type="supported-packagesType"/&gt;
4930
4931
4932 &lt;xsd:complexType name="packageType"&gt;
4933 &lt;xsd:complexContent&gt;
4934 &lt;xsd:extension base="Tcore"&gt;
4935 &lt;xsd:sequence&gt;
4936 &lt;xsd:any namespace="##other" minOccurs="0"
4937 maxOccurs="unbounded" processContents="lax" /&gt;
4938 &lt;/xsd:sequence&gt;
4939 &lt;xsd:attribute name="name" type="xsd:string" use="required" /&gt;
4940 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
4941 &lt;/xsd:extension&gt;
4942 &lt;/xsd:complexContent&gt;
4943 &lt;/xsd:complexType&gt;
4944
4945 &lt;xsd:element name="package" type="packageType" /&gt;
4946
4947
4948 &lt;!-- active-rtp-sessions --&gt;
4949
4950 &lt;xsd:complexType name="active-rtp-sessionsType"&gt;
4951 &lt;xsd:complexContent&gt;
4952 &lt;xsd:extension base="Tcore"&gt;
4953 &lt;xsd:sequence&gt;
4954 &lt;xsd:element ref="rtp-codec" minOccurs="0"
4955 maxOccurs="unbounded" /&gt;
4956 &lt;xsd:any namespace="##other" minOccurs="0"
4957 maxOccurs="unbounded" processContents="lax" /&gt;
4958 &lt;/xsd:sequence&gt;
4959 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
4960 &lt;/xsd:extension&gt;
4961 &lt;/xsd:complexContent&gt;
4962 &lt;/xsd:complexType&gt;
4963
4964 &lt;xsd:element name="active-rtp-sessions" type="active-rtp-sessionsType"/&gt;
4965
4966
4967 &lt;xsd:complexType name="rtp-codecType"&gt;
4968 &lt;xsd:complexContent&gt;
4969 &lt;xsd:extension base="Tcore"&gt;
4970 &lt;xsd:sequence&gt;
4971 &lt;xsd:element name="decoding" type="xsd:nonNegativeInteger" /&gt;
4972 &lt;xsd:element name="encoding" type="xsd:nonNegativeInteger" /&gt;
4973 &lt;xsd:any namespace="##other" minOccurs="0"
4974 maxOccurs="unbounded" processContents="lax" /&gt;
4975 &lt;/xsd:sequence&gt;
4976 &lt;xsd:attribute name="name" type="xsd:string" use="required" /&gt;
4977
4978
4979
4980 <span class="grey">Boulton, et al. Standards Track [Page 89]</span></pre>
4981 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-90" ></span>
4982 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
4983
4984
4985 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
4986 &lt;/xsd:extension&gt;
4987 &lt;/xsd:complexContent&gt;
4988 &lt;/xsd:complexType&gt;
4989
4990 &lt;xsd:element name="rtp-codec" type="rtp-codecType" /&gt;
4991
4992
4993 &lt;!-- active-mixer-sessions --&gt;
4994
4995 &lt;xsd:complexType name="active-mixer-sessionsType"&gt;
4996 &lt;xsd:complexContent&gt;
4997 &lt;xsd:extension base="Tcore"&gt;
4998 &lt;xsd:sequence&gt;
4999 &lt;xsd:element ref="active-mix" minOccurs="0"
5000 maxOccurs="unbounded" /&gt;
5001 &lt;xsd:any namespace="##other" minOccurs="0"
5002 maxOccurs="unbounded" processContents="lax" /&gt;
5003 &lt;/xsd:sequence&gt;
5004 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5005 &lt;/xsd:extension&gt;
5006 &lt;/xsd:complexContent&gt;
5007 &lt;/xsd:complexType&gt;
5008
5009 &lt;xsd:element name="active-mixer-sessions"
5010 type="active-mixer-sessionsType" /&gt;
5011
5012
5013 &lt;xsd:complexType name="active-mixType"&gt;
5014 &lt;xsd:complexContent&gt;
5015 &lt;xsd:extension base="Tcore"&gt;
5016 &lt;xsd:sequence&gt;
5017 &lt;xsd:element ref="rtp-codec" minOccurs="0"
5018 maxOccurs="unbounded" /&gt;
5019 &lt;xsd:any namespace="##other" minOccurs="0"
5020 maxOccurs="unbounded" processContents="lax" /&gt;
5021 &lt;/xsd:sequence&gt;
5022 &lt;xsd:attributeGroup ref="fw:framework-attributes" /&gt;
5023 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5024 &lt;/xsd:extension&gt;
5025 &lt;/xsd:complexContent&gt;
5026 &lt;/xsd:complexType&gt;
5027
5028 &lt;xsd:element name="active-mix" type="active-mixType" /&gt;
5029
5030
5031
5032
5033
5034
5035
5036 <span class="grey">Boulton, et al. Standards Track [Page 90]</span></pre>
5037 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-91" ></span>
5038 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5039
5040
5041 &lt;!-- non-active-rtp-sessions --&gt;
5042
5043 &lt;xsd:complexType name="non-active-rtp-sessionsType"&gt;
5044 &lt;xsd:complexContent&gt;
5045 &lt;xsd:extension base="Tcore"&gt;
5046 &lt;xsd:sequence&gt;
5047 &lt;xsd:element ref="rtp-codec" minOccurs="0"
5048 maxOccurs="unbounded" /&gt;
5049 &lt;xsd:any namespace="##other" minOccurs="0"
5050 maxOccurs="unbounded" processContents="lax" /&gt;
5051 &lt;/xsd:sequence&gt;
5052 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5053 &lt;/xsd:extension&gt;
5054 &lt;/xsd:complexContent&gt;
5055 &lt;/xsd:complexType&gt;
5056
5057 &lt;xsd:element name="non-active-rtp-sessions"
5058 type="non-active-rtp-sessionsType" /&gt;
5059
5060 &lt;!-- non-active-mixer-sessions --&gt;
5061
5062 &lt;xsd:complexType name="non-active-mixer-sessionsType"&gt;
5063 &lt;xsd:complexContent&gt;
5064 &lt;xsd:extension base="Tcore"&gt;
5065 &lt;xsd:sequence&gt;
5066 &lt;xsd:element ref="non-active-mix" minOccurs="0"
5067 maxOccurs="unbounded" /&gt;
5068 &lt;xsd:any namespace="##other" minOccurs="0"
5069 maxOccurs="unbounded" processContents="lax" /&gt;
5070 &lt;/xsd:sequence&gt;
5071 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5072 &lt;/xsd:extension&gt;
5073 &lt;/xsd:complexContent&gt;
5074 &lt;/xsd:complexType&gt;
5075
5076 &lt;xsd:element name="non-active-mixer-sessions"
5077 type="non-active-mixer-sessionsType" /&gt;
5078
5079 &lt;xsd:complexType name="non-active-mixType"&gt;
5080 &lt;xsd:complexContent&gt;
5081 &lt;xsd:extension base="Tcore"&gt;
5082 &lt;xsd:sequence&gt;
5083 &lt;xsd:element ref="rtp-codec" /&gt;
5084 &lt;xsd:any namespace="##other" minOccurs="0"
5085 maxOccurs="unbounded" processContents="lax" /&gt;
5086 &lt;/xsd:sequence&gt;
5087 &lt;xsd:attribute name="available" type="xsd:nonNegativeInteger"
5088 use="required" /&gt;
5089
5090
5091
5092 <span class="grey">Boulton, et al. Standards Track [Page 91]</span></pre>
5093 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-92" ></span>
5094 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5095
5096
5097 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5098 &lt;/xsd:extension&gt;
5099 &lt;/xsd:complexContent&gt;
5100 &lt;/xsd:complexType&gt;
5101
5102 &lt;xsd:element name="non-active-mix" type="non-active-mixType" /&gt;
5103
5104 &lt;!-- media-server-status --&gt;
5105
5106 &lt;xsd:element name="media-server-status" type="msstatus.datatype" /&gt;
5107
5108 &lt;!-- supported-codecs --&gt;
5109
5110 &lt;xsd:complexType name="supported-codecsType"&gt;
5111 &lt;xsd:complexContent&gt;
5112 &lt;xsd:extension base="Tcore"&gt;
5113 &lt;xsd:sequence&gt;
5114 &lt;xsd:element ref="supported-codec"
5115 minOccurs="0" maxOccurs="unbounded" /&gt;
5116 &lt;xsd:any namespace="##other" minOccurs="0"
5117 maxOccurs="unbounded" processContents="lax" /&gt;
5118 &lt;/xsd:sequence&gt;
5119 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5120 &lt;/xsd:extension&gt;
5121 &lt;/xsd:complexContent&gt;
5122 &lt;/xsd:complexType&gt;
5123
5124 &lt;xsd:element name="supported-codecs" type="supported-codecsType" /&gt;
5125
5126 &lt;xsd:complexType name="supported-codecType"&gt;
5127 &lt;xsd:complexContent&gt;
5128 &lt;xsd:extension base="Tcore"&gt;
5129 &lt;xsd:sequence&gt;
5130 &lt;xsd:element ref="supported-codec-package"
5131 minOccurs="0" maxOccurs="unbounded" /&gt;
5132 &lt;xsd:any namespace="##other" minOccurs="0"
5133 maxOccurs="unbounded" processContents="lax" /&gt;
5134 &lt;/xsd:sequence&gt;
5135 &lt;xsd:attribute name="name" type="xsd:string" use="required" /&gt;
5136 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5137 &lt;/xsd:extension&gt;
5138 &lt;/xsd:complexContent&gt;
5139 &lt;/xsd:complexType&gt;
5140
5141 &lt;xsd:element name="supported-codec" type="supported-codecType" /&gt;
5142
5143
5144
5145
5146
5147
5148 <span class="grey">Boulton, et al. Standards Track [Page 92]</span></pre>
5149 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-93" ></span>
5150 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5151
5152
5153 &lt;xsd:complexType name="supported-codec-packageType"&gt;
5154 &lt;xsd:complexContent&gt;
5155 &lt;xsd:extension base="Tcore"&gt;
5156 &lt;xsd:sequence&gt;
5157 &lt;xsd:element name="supported-action" type="actions.datatype"
5158 minOccurs="0" maxOccurs="unbounded" /&gt;
5159 &lt;xsd:any namespace="##other" minOccurs="0"
5160 maxOccurs="unbounded" processContents="lax" /&gt;
5161 &lt;/xsd:sequence&gt;
5162 &lt;xsd:attribute name="name" type="xsd:string" use="required" /&gt;
5163 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5164 &lt;/xsd:extension&gt;
5165 &lt;/xsd:complexContent&gt;
5166 &lt;/xsd:complexType&gt;
5167
5168 &lt;xsd:element name="supported-codec-package"
5169 type="supported-codec-packageType" /&gt;
5170
5171
5172 &lt;!-- application-data --&gt;
5173
5174 &lt;xsd:element name="application-data" type="appdata.datatype" /&gt;
5175
5176 &lt;!-- file-formats --&gt;
5177
5178 &lt;xsd:complexType name="file-formatsType"&gt;
5179 &lt;xsd:complexContent&gt;
5180 &lt;xsd:extension base="Tcore"&gt;
5181 &lt;xsd:sequence&gt;
5182 &lt;xsd:element ref="supported-format"
5183 minOccurs="0" maxOccurs="unbounded" /&gt;
5184 &lt;xsd:any namespace="##other" minOccurs="0"
5185 maxOccurs="unbounded" processContents="lax" /&gt;
5186 &lt;/xsd:sequence&gt;
5187 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5188 &lt;/xsd:extension&gt;
5189 &lt;/xsd:complexContent&gt;
5190 &lt;/xsd:complexType&gt;
5191
5192 &lt;xsd:element name="file-formats" type="file-formatsType" /&gt;
5193
5194 &lt;xsd:complexType name="supported-formatType"&gt;
5195 &lt;xsd:complexContent&gt;
5196 &lt;xsd:extension base="Tcore"&gt;
5197 &lt;xsd:sequence&gt;
5198 &lt;xsd:element ref="supported-file-package"
5199 minOccurs="0" maxOccurs="unbounded" /&gt;
5200 &lt;xsd:any namespace="##other" minOccurs="0"
5201
5202
5203
5204 <span class="grey">Boulton, et al. Standards Track [Page 93]</span></pre>
5205 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-94" ></span>
5206 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5207
5208
5209 maxOccurs="unbounded" processContents="lax" /&gt;
5210 &lt;/xsd:sequence&gt;
5211 &lt;xsd:attribute name="name" type="xsd:string" use="required" /&gt;
5212 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5213 &lt;/xsd:extension&gt;
5214 &lt;/xsd:complexContent&gt;
5215 &lt;/xsd:complexType&gt;
5216
5217 &lt;xsd:element name="supported-format" type="supported-formatType" /&gt;
5218
5219 &lt;xsd:element name="supported-file-package"
5220 type="xsd:string" /&gt;
5221
5222 &lt;!-- max-prepared-duration --&gt;
5223
5224 &lt;xsd:complexType name="max-prepared-durationType"&gt;
5225 &lt;xsd:complexContent&gt;
5226 &lt;xsd:extension base="Tcore"&gt;
5227 &lt;xsd:sequence&gt;
5228 &lt;xsd:element ref="max-time" /&gt;
5229 &lt;xsd:any namespace="##other" minOccurs="0"
5230 maxOccurs="unbounded" processContents="lax" /&gt;
5231 &lt;/xsd:sequence&gt;
5232 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5233 &lt;/xsd:extension&gt;
5234 &lt;/xsd:complexContent&gt;
5235 &lt;/xsd:complexType&gt;
5236
5237 &lt;xsd:element name="max-prepared-duration"
5238 type="max-prepared-durationType" /&gt;
5239
5240
5241 &lt;xsd:complexType name="max-timeType"&gt;
5242 &lt;xsd:complexContent&gt;
5243 &lt;xsd:extension base="Tcore"&gt;
5244 &lt;xsd:sequence&gt;
5245 &lt;xsd:element name="max-time-package" type="xsd:string" /&gt;
5246 &lt;xsd:any namespace="##other" minOccurs="0"
5247 maxOccurs="unbounded" processContents="lax" /&gt;
5248 &lt;/xsd:sequence&gt;
5249 &lt;xsd:attribute name="max-time-seconds" type="xsd:nonNegativeInteger"
5250 use="required" /&gt;
5251 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5252 &lt;/xsd:extension&gt;
5253 &lt;/xsd:complexContent&gt;
5254 &lt;/xsd:complexType&gt;
5255
5256 &lt;xsd:element name="max-time" type="max-timeType" /&gt;
5257
5258
5259
5260 <span class="grey">Boulton, et al. Standards Track [Page 94]</span></pre>
5261 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-95" ></span>
5262 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5263
5264
5265 &lt;!-- dtmf-support --&gt;
5266
5267 &lt;xsd:complexType name="dtmf-supportType"&gt;
5268 &lt;xsd:complexContent&gt;
5269 &lt;xsd:extension base="Tcore"&gt;
5270 &lt;xsd:sequence&gt;
5271 &lt;xsd:element ref="detect" /&gt;
5272 &lt;xsd:element ref="generate" /&gt;
5273 &lt;xsd:element ref="passthrough" /&gt;
5274 &lt;xsd:any namespace="##other" minOccurs="0"
5275 maxOccurs="unbounded" processContents="lax" /&gt;
5276 &lt;/xsd:sequence&gt;
5277 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5278 &lt;/xsd:extension&gt;
5279 &lt;/xsd:complexContent&gt;
5280 &lt;/xsd:complexType&gt;
5281
5282 &lt;xsd:element name="dtmf-support" type="dtmf-supportType" /&gt;
5283
5284 &lt;xsd:complexType name="detectType"&gt;
5285 &lt;xsd:complexContent&gt;
5286 &lt;xsd:extension base="Tcore"&gt;
5287 &lt;xsd:sequence&gt;
5288 &lt;xsd:element ref="dtmf-type"
5289 minOccurs="0" maxOccurs="unbounded" /&gt;
5290 &lt;xsd:any namespace="##other" minOccurs="0"
5291 maxOccurs="unbounded" processContents="lax" /&gt;
5292 &lt;/xsd:sequence&gt;
5293 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5294 &lt;/xsd:extension&gt;
5295 &lt;/xsd:complexContent&gt;
5296 &lt;/xsd:complexType&gt;
5297
5298 &lt;xsd:element name="detect" type="detectType" /&gt;
5299
5300 &lt;xsd:complexType name="generateType"&gt;
5301 &lt;xsd:complexContent&gt;
5302 &lt;xsd:extension base="Tcore"&gt;
5303 &lt;xsd:sequence&gt;
5304 &lt;xsd:element ref="dtmf-type"
5305 minOccurs="0" maxOccurs="unbounded" /&gt;
5306 &lt;xsd:any namespace="##other" minOccurs="0"
5307 maxOccurs="unbounded" processContents="lax" /&gt;
5308 &lt;/xsd:sequence&gt;
5309 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5310 &lt;/xsd:extension&gt;
5311 &lt;/xsd:complexContent&gt;
5312 &lt;/xsd:complexType&gt;
5313
5314
5315
5316 <span class="grey">Boulton, et al. Standards Track [Page 95]</span></pre>
5317 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-96" ></span>
5318 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5319
5320
5321 &lt;xsd:element name="generate" type="generateType" /&gt;
5322
5323 &lt;xsd:complexType name="passthroughType"&gt;
5324 &lt;xsd:complexContent&gt;
5325 &lt;xsd:extension base="Tcore"&gt;
5326 &lt;xsd:sequence&gt;
5327 &lt;xsd:element ref="dtmf-type"
5328 minOccurs="0" maxOccurs="unbounded" /&gt;
5329 &lt;xsd:any namespace="##other" minOccurs="0"
5330 maxOccurs="unbounded" processContents="lax" /&gt;
5331 &lt;/xsd:sequence&gt;
5332 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5333 &lt;/xsd:extension&gt;
5334 &lt;/xsd:complexContent&gt;
5335 &lt;/xsd:complexType&gt;
5336
5337 &lt;xsd:element name="passthrough" type="passthroughType" /&gt;
5338
5339
5340 &lt;xsd:complexType name="dtmf-typeType"&gt;
5341 &lt;xsd:complexContent&gt;
5342 &lt;xsd:extension base="Tcore"&gt;
5343 &lt;xsd:sequence&gt;
5344 &lt;xsd:any namespace="##other" minOccurs="0"
5345 maxOccurs="unbounded" processContents="lax" /&gt;
5346 &lt;/xsd:sequence&gt;
5347 &lt;xsd:attribute name="name" type="dtmf.datatype" use="required" /&gt;
5348 &lt;xsd:attribute name="package" type="xsd:string" use="required" /&gt;
5349 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5350 &lt;/xsd:extension&gt;
5351 &lt;/xsd:complexContent&gt;
5352 &lt;/xsd:complexType&gt;
5353
5354 &lt;xsd:element name="dtmf-type" type="dtmf-typeType" /&gt;
5355
5356
5357 &lt;!-- mixing-modes --&gt;
5358
5359 &lt;xsd:complexType name="mixing-modesType"&gt;
5360 &lt;xsd:complexContent&gt;
5361 &lt;xsd:extension base="Tcore"&gt;
5362 &lt;xsd:sequence&gt;
5363 &lt;xsd:element ref="audio-mixing-modes"
5364 minOccurs="0" maxOccurs="1" /&gt;
5365 &lt;xsd:element ref="video-mixing-modes"
5366 minOccurs="0" maxOccurs="1" /&gt;
5367 &lt;xsd:any namespace="##other" minOccurs="0"
5368 maxOccurs="unbounded" processContents="lax" /&gt;
5369
5370
5371
5372 <span class="grey">Boulton, et al. Standards Track [Page 96]</span></pre>
5373 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-97" ></span>
5374 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5375
5376
5377 &lt;/xsd:sequence&gt;
5378 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5379 &lt;/xsd:extension&gt;
5380 &lt;/xsd:complexContent&gt;
5381 &lt;/xsd:complexType&gt;
5382
5383 &lt;xsd:element name="mixing-modes" type="mixing-modesType" /&gt;
5384
5385 &lt;xsd:complexType name="audio-mixing-modesType"&gt;
5386 &lt;xsd:complexContent&gt;
5387 &lt;xsd:extension base="Tcore"&gt;
5388 &lt;xsd:sequence&gt;
5389 &lt;xsd:element ref="audio-mixing-mode"
5390 minOccurs="0" maxOccurs="unbounded" /&gt;
5391 &lt;xsd:any namespace="##other" minOccurs="0"
5392 maxOccurs="unbounded" processContents="lax" /&gt;
5393 &lt;/xsd:sequence&gt;
5394 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5395 &lt;/xsd:extension&gt;
5396 &lt;/xsd:complexContent&gt;
5397 &lt;/xsd:complexType&gt;
5398
5399 &lt;xsd:element name="audio-mixing-modes" type="audio-mixing-modesType" /&gt;
5400
5401 &lt;xsd:complexType name="audio-mixing-modeType" mixed="true"&gt;
5402 &lt;xsd:sequence&gt;
5403 &lt;xsd:any namespace="##other" minOccurs="0"
5404 maxOccurs="unbounded" processContents="lax" /&gt;
5405 &lt;/xsd:sequence&gt;
5406 &lt;xsd:attribute name="package" type="xsd:string" use="required" /&gt;
5407 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5408 &lt;/xsd:complexType&gt;
5409
5410 &lt;xsd:element name="audio-mixing-mode" type="audio-mixing-modeType" /&gt;
5411
5412 &lt;xsd:complexType name="video-mixing-modesType"&gt;
5413 &lt;xsd:complexContent&gt;
5414 &lt;xsd:extension base="Tcore"&gt;
5415 &lt;xsd:sequence&gt;
5416 &lt;xsd:element ref="video-mixing-mode"
5417 minOccurs="0" maxOccurs="unbounded" /&gt;
5418 &lt;xsd:any namespace="##other" minOccurs="0"
5419 maxOccurs="unbounded" processContents="lax" /&gt;
5420 &lt;/xsd:sequence&gt;
5421 &lt;xsd:attribute name="vas" type="boolean.datatype"
5422 default="false" /&gt;
5423 &lt;xsd:attribute name="activespeakermix" type="boolean.datatype"
5424 default="false" /&gt;
5425
5426
5427
5428 <span class="grey">Boulton, et al. Standards Track [Page 97]</span></pre>
5429 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-98" ></span>
5430 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5431
5432
5433 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5434 &lt;/xsd:extension&gt;
5435 &lt;/xsd:complexContent&gt;
5436 &lt;/xsd:complexType&gt;
5437
5438 &lt;xsd:element name="video-mixing-modes" type="video-mixing-modesType" /&gt;
5439
5440 &lt;xsd:complexType name="video-mixing-modeType" mixed="true"&gt;
5441 &lt;xsd:sequence&gt;
5442 &lt;xsd:any namespace="##other" minOccurs="0"
5443 maxOccurs="unbounded" processContents="lax" /&gt;
5444 &lt;/xsd:sequence&gt;
5445 &lt;xsd:attribute name="package" type="xsd:string" use="required" /&gt;
5446 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5447 &lt;/xsd:complexType&gt;
5448
5449 &lt;xsd:element name="video-mixing-mode" type="video-mixing-modeType" /&gt;
5450
5451
5452 &lt;!-- supported-tones --&gt;
5453
5454 &lt;xsd:complexType name="supported-tonesType"&gt;
5455 &lt;xsd:complexContent&gt;
5456 &lt;xsd:extension base="Tcore"&gt;
5457 &lt;xsd:sequence&gt;
5458 &lt;xsd:element ref="supported-country-codes"
5459 minOccurs="0" maxOccurs="1" /&gt;
5460 &lt;xsd:element ref="supported-h248-codes"
5461 minOccurs="0" maxOccurs="1" /&gt;
5462 &lt;xsd:any namespace="##other" minOccurs="0"
5463 maxOccurs="unbounded" processContents="lax" /&gt;
5464 &lt;/xsd:sequence&gt;
5465 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5466 &lt;/xsd:extension&gt;
5467 &lt;/xsd:complexContent&gt;
5468 &lt;/xsd:complexType&gt;
5469
5470 &lt;xsd:element name="supported-tones" type="supported-tonesType" /&gt;
5471
5472 &lt;xsd:complexType name="supported-country-codesType"&gt;
5473 &lt;xsd:complexContent&gt;
5474 &lt;xsd:extension base="Tcore"&gt;
5475 &lt;xsd:sequence&gt;
5476 &lt;xsd:element ref="country-code"
5477 minOccurs="0" maxOccurs="unbounded" /&gt;
5478 &lt;xsd:any namespace="##other" minOccurs="0"
5479 maxOccurs="unbounded" processContents="lax" /&gt;
5480 &lt;/xsd:sequence&gt;
5481
5482
5483
5484 <span class="grey">Boulton, et al. Standards Track [Page 98]</span></pre>
5485 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-99" ></span>
5486 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5487
5488
5489 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5490 &lt;/xsd:extension&gt;
5491 &lt;/xsd:complexContent&gt;
5492 &lt;/xsd:complexType&gt;
5493
5494 &lt;xsd:element name="supported-country-codes"
5495 type="supported-country-codesType" /&gt;
5496
5497 &lt;xsd:complexType name="country-codeType" mixed="true"&gt;
5498 &lt;xsd:sequence&gt;
5499 &lt;xsd:any namespace="##other" minOccurs="0"
5500 maxOccurs="unbounded" processContents="lax" /&gt;
5501 &lt;/xsd:sequence&gt;
5502 &lt;xsd:attribute name="package" type="xsd:string" use="required" /&gt;
5503 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5504 &lt;/xsd:complexType&gt;
5505
5506 &lt;xsd:element name="country-code" type="country-codeType" /&gt;
5507
5508 &lt;xsd:complexType name="supported-h248-codesType"&gt;
5509 &lt;xsd:complexContent&gt;
5510 &lt;xsd:extension base="Tcore"&gt;
5511 &lt;xsd:sequence&gt;
5512 &lt;xsd:element ref="h248-code"
5513 minOccurs="0" maxOccurs="unbounded" /&gt;
5514 &lt;xsd:any namespace="##other" minOccurs="0"
5515 maxOccurs="unbounded" processContents="lax" /&gt;
5516 &lt;/xsd:sequence&gt;
5517 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5518 &lt;/xsd:extension&gt;
5519 &lt;/xsd:complexContent&gt;
5520 &lt;/xsd:complexType&gt;
5521
5522 &lt;xsd:element name="supported-h248-codes"
5523 type="supported-h248-codesType" /&gt;
5524
5525 &lt;xsd:complexType name="h248-codeType" mixed="true"&gt;
5526 &lt;xsd:sequence&gt;
5527 &lt;xsd:any namespace="##other" minOccurs="0"
5528 maxOccurs="unbounded" processContents="lax" /&gt;
5529 &lt;/xsd:sequence&gt;
5530 &lt;xsd:attribute name="package" type="xsd:string" use="required" /&gt;
5531 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5532 &lt;/xsd:complexType&gt;
5533
5534 &lt;xsd:element name="h248-code" type="h248-codeType" /&gt;
5535
5536
5537
5538
5539
5540 <span class="grey">Boulton, et al. Standards Track [Page 99]</span></pre>
5541 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-100" ></span>
5542 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5543
5544
5545 &lt;!-- file-transfer-modes --&gt;
5546
5547 &lt;xsd:complexType name="file-transfer-modesType"&gt;
5548 &lt;xsd:complexContent&gt;
5549 &lt;xsd:extension base="Tcore"&gt;
5550 &lt;xsd:sequence&gt;
5551 &lt;xsd:element ref="file-transfer-mode"
5552 minOccurs="0" maxOccurs="unbounded" /&gt;
5553 &lt;xsd:any namespace="##other" minOccurs="0"
5554 maxOccurs="unbounded" processContents="lax" /&gt;
5555 &lt;/xsd:sequence&gt;
5556 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5557 &lt;/xsd:extension&gt;
5558 &lt;/xsd:complexContent&gt;
5559 &lt;/xsd:complexType&gt;
5560
5561 &lt;xsd:element name="file-transfer-modes"
5562 type="file-transfer-modesType" /&gt;
5563
5564 &lt;xsd:complexType name="file-transfer-modeType"&gt;
5565 &lt;xsd:complexContent&gt;
5566 &lt;xsd:extension base="Tcore"&gt;
5567 &lt;xsd:sequence&gt;
5568 &lt;xsd:any namespace="##other" minOccurs="0"
5569 maxOccurs="unbounded" processContents="lax" /&gt;
5570 &lt;/xsd:sequence&gt;
5571 &lt;xsd:attribute name="name" type="transfermode.datatype"
5572 use="required" /&gt;
5573 &lt;xsd:attribute name="package" type="xsd:string" use="required" /&gt;
5574 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5575 &lt;/xsd:extension&gt;
5576 &lt;/xsd:complexContent&gt;
5577 &lt;/xsd:complexType&gt;
5578 &lt;xsd:element name="file-transfer-mode" type="file-transfer-modeType" /&gt;
5579
5580
5581 &lt;!-- asr-tts-support --&gt;
5582
5583 &lt;xsd:complexType name="asr-tts-supportType"&gt;
5584 &lt;xsd:complexContent&gt;
5585 &lt;xsd:extension base="Tcore"&gt;
5586 &lt;xsd:sequence&gt;
5587 &lt;xsd:element ref="asr-support"
5588 minOccurs="0" maxOccurs="1" /&gt;
5589 &lt;xsd:element ref="tts-support"
5590 minOccurs="0" maxOccurs="1" /&gt;
5591 &lt;xsd:any namespace="##other" minOccurs="0"
5592 maxOccurs="unbounded" processContents="lax" /&gt;
5593
5594
5595
5596 <span class="grey">Boulton, et al. Standards Track [Page 100]</span></pre>
5597 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-101" ></span>
5598 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5599
5600
5601 &lt;/xsd:sequence&gt;
5602 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5603 &lt;/xsd:extension&gt;
5604 &lt;/xsd:complexContent&gt;
5605 &lt;/xsd:complexType&gt;
5606
5607 &lt;xsd:element name="asr-tts-support" type="asr-tts-supportType" /&gt;
5608
5609 &lt;xsd:complexType name="asr-supportType"&gt;
5610 &lt;xsd:complexContent&gt;
5611 &lt;xsd:extension base="Tcore"&gt;
5612 &lt;xsd:sequence&gt;
5613 &lt;xsd:element ref="language"
5614 minOccurs="0" maxOccurs="unbounded" /&gt;
5615 &lt;xsd:any namespace="##other" minOccurs="0"
5616 maxOccurs="unbounded" processContents="lax" /&gt;
5617 &lt;/xsd:sequence&gt;
5618 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5619 &lt;/xsd:extension&gt;
5620 &lt;/xsd:complexContent&gt;
5621 &lt;/xsd:complexType&gt;
5622
5623 &lt;xsd:element name="asr-support" type="asr-supportType" /&gt;
5624
5625 &lt;xsd:complexType name="tts-supportType"&gt;
5626 &lt;xsd:complexContent&gt;
5627 &lt;xsd:extension base="Tcore"&gt;
5628 &lt;xsd:sequence&gt;
5629 &lt;xsd:element ref="language"
5630 minOccurs="0" maxOccurs="unbounded" /&gt;
5631 &lt;xsd:any namespace="##other" minOccurs="0"
5632 maxOccurs="unbounded" processContents="lax" /&gt;
5633 &lt;/xsd:sequence&gt;
5634 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5635 &lt;/xsd:extension&gt;
5636 &lt;/xsd:complexContent&gt;
5637 &lt;/xsd:complexType&gt;
5638
5639 &lt;xsd:element name="tts-support" type="tts-supportType" /&gt;
5640
5641 &lt;xsd:complexType name="languageType"&gt;
5642 &lt;xsd:complexContent&gt;
5643 &lt;xsd:extension base="Tcore"&gt;
5644 &lt;xsd:sequence&gt;
5645 &lt;xsd:any namespace="##other" minOccurs="0"
5646 maxOccurs="unbounded" processContents="lax" /&gt;
5647 &lt;/xsd:sequence&gt;
5648 &lt;xsd:attribute ref="xml:lang" /&gt;
5649
5650
5651
5652 <span class="grey">Boulton, et al. Standards Track [Page 101]</span></pre>
5653 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-102" ></span>
5654 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5655
5656
5657 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5658 &lt;/xsd:extension&gt;
5659 &lt;/xsd:complexContent&gt;
5660 &lt;/xsd:complexType&gt;
5661
5662 &lt;xsd:element name="language" type="languageType" /&gt;
5663
5664
5665 &lt;!-- media-server-location --&gt;
5666
5667 &lt;xsd:complexType name="media-server-locationType"&gt;
5668 &lt;xsd:complexContent&gt;
5669 &lt;xsd:extension base="Tcore"&gt;
5670 &lt;xsd:sequence&gt;
5671 &lt;xsd:element name="civicAddress" type="ca:civicAddress"
5672 minOccurs="1" maxOccurs="1" /&gt;
5673 &lt;xsd:any namespace="##other" minOccurs="0"
5674 maxOccurs="unbounded" processContents="lax" /&gt;
5675 &lt;/xsd:sequence&gt;
5676 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5677 &lt;/xsd:extension&gt;
5678 &lt;/xsd:complexContent&gt;
5679 &lt;/xsd:complexType&gt;
5680
5681 &lt;xsd:element name="media-server-location"
5682 type="media-server-locationType" /&gt;
5683
5684
5685 &lt;!-- vxml-support --&gt;
5686
5687 &lt;xsd:complexType name="vxml-supportType"&gt;
5688 &lt;xsd:complexContent&gt;
5689 &lt;xsd:extension base="Tcore"&gt;
5690 &lt;xsd:sequence&gt;
5691 &lt;xsd:element ref="vxml-mode"
5692 minOccurs="0" maxOccurs="unbounded" /&gt;
5693 &lt;xsd:any namespace="##other" minOccurs="0"
5694 maxOccurs="unbounded" processContents="lax" /&gt;
5695 &lt;/xsd:sequence&gt;
5696 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5697 &lt;/xsd:extension&gt;
5698 &lt;/xsd:complexContent&gt;
5699 &lt;/xsd:complexType&gt;
5700
5701 &lt;xsd:element name="vxml-support" type="vxml-supportType" /&gt;
5702
5703
5704
5705
5706
5707
5708 <span class="grey">Boulton, et al. Standards Track [Page 102]</span></pre>
5709 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-103" ></span>
5710 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5711
5712
5713 &lt;xsd:complexType name="vxml-modeType"&gt;
5714 &lt;xsd:complexContent&gt;
5715 &lt;xsd:extension base="Tcore"&gt;
5716 &lt;xsd:sequence&gt;
5717 &lt;xsd:any namespace="##other" minOccurs="0"
5718 maxOccurs="unbounded" processContents="lax" /&gt;
5719 &lt;/xsd:sequence&gt;
5720 &lt;xsd:attribute name="package" type="xsd:string" use="required" /&gt;
5721 &lt;xsd:attribute name="support" type="vxml.datatype" use="required" /&gt;
5722 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5723 &lt;/xsd:extension&gt;
5724 &lt;/xsd:complexContent&gt;
5725 &lt;/xsd:complexType&gt;
5726
5727 &lt;xsd:element name="vxml-mode" type="vxml-modeType" /&gt;
5728
5729
5730 &lt;!-- label --&gt;
5731
5732 &lt;xsd:element name="label" type="label.datatype" /&gt;
5733
5734
5735 &lt;!-- media-server-address --&gt;
5736
5737 &lt;xsd:element name="media-server-address" type="xsd:anyURI" /&gt;
5738
5739 &lt;!-- encryption --&gt;
5740
5741 &lt;xsd:complexType name="encryptionType"&gt;
5742 &lt;xsd:complexContent&gt;
5743 &lt;xsd:extension base="Tcore"&gt;
5744 &lt;xsd:sequence&gt;
5745 &lt;xsd:any namespace="##other" minOccurs="0"
5746 maxOccurs="unbounded" processContents="lax" /&gt;
5747 &lt;/xsd:sequence&gt;
5748 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5749 &lt;/xsd:extension&gt;
5750 &lt;/xsd:complexContent&gt;
5751 &lt;/xsd:complexType&gt;
5752
5753 &lt;xsd:element name="encryption" type="encryptionType" /&gt;
5754
5755
5756
5757
5758
5759
5760
5761
5762
5763
5764 <span class="grey">Boulton, et al. Standards Track [Page 103]</span></pre>
5765 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-104" ></span>
5766 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5767
5768
5769 &lt;!--
5770 ####################################################
5771
5772 DATATYPES
5773
5774 ####################################################
5775 --&gt;
5776
5777 &lt;xsd:simpleType name="version.datatype"&gt;
5778 &lt;xsd:restriction base="xsd:NMTOKEN"&gt;
5779 &lt;xsd:enumeration value="1.0" /&gt;
5780 &lt;/xsd:restriction&gt;
5781 &lt;/xsd:simpleType&gt;
5782
5783 &lt;xsd:simpleType name="id.datatype"&gt;
5784 &lt;xsd:restriction base="xsd:NMTOKEN" /&gt;
5785 &lt;/xsd:simpleType&gt;
5786
5787 &lt;xsd:simpleType name="status.datatype"&gt;
5788 &lt;xsd:restriction base="xsd:positiveInteger"&gt;
5789 &lt;xsd:pattern value="[0-9][0-9][0-9]" /&gt;
5790 &lt;/xsd:restriction&gt;
5791 &lt;/xsd:simpleType&gt;
5792
5793 &lt;xsd:simpleType name="msstatus.datatype"&gt;
5794 &lt;xsd:restriction base="xsd:NMTOKEN"&gt;
5795 &lt;xsd:enumeration value="active" /&gt;
5796 &lt;xsd:enumeration value="deactivated" /&gt;
5797 &lt;xsd:enumeration value="unavailable" /&gt;
5798 &lt;/xsd:restriction&gt;
5799 &lt;/xsd:simpleType&gt;
5800
5801 &lt;xsd:simpleType name="action.datatype"&gt;
5802 &lt;xsd:restriction base="xsd:NMTOKEN"&gt;
5803 &lt;xsd:enumeration value="create" /&gt;
5804 &lt;xsd:enumeration value="update" /&gt;
5805 &lt;xsd:enumeration value="remove" /&gt;
5806 &lt;/xsd:restriction&gt;
5807 &lt;/xsd:simpleType&gt;
5808
5809 &lt;xsd:simpleType name="actions.datatype"&gt;
5810 &lt;xsd:restriction base="xsd:NMTOKEN"&gt;
5811 &lt;xsd:enumeration value="encoding" /&gt;
5812 &lt;xsd:enumeration value="decoding" /&gt;
5813 &lt;xsd:enumeration value="passthrough" /&gt;
5814 &lt;/xsd:restriction&gt;
5815 &lt;/xsd:simpleType&gt;
5816
5817
5818
5819
5820 <span class="grey">Boulton, et al. Standards Track [Page 104]</span></pre>
5821 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-105" ></span>
5822 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5823
5824
5825 &lt;xsd:simpleType name="appdata.datatype"&gt;
5826 &lt;xsd:restriction base="xsd:string" /&gt;
5827 &lt;/xsd:simpleType&gt;
5828
5829 &lt;xsd:simpleType name="dtmf.datatype"&gt;
5830 &lt;xsd:restriction base="xsd:NMTOKEN"/&gt;
5831 &lt;/xsd:simpleType&gt;
5832
5833 &lt;xsd:simpleType name="transfermode.datatype"&gt;
5834 &lt;xsd:restriction base="xsd:NMTOKEN" /&gt;
5835 &lt;/xsd:simpleType&gt;
5836
5837 &lt;xsd:simpleType name="boolean.datatype"&gt;
5838 &lt;xsd:restriction base="xsd:NMTOKEN"&gt;
5839 &lt;xsd:enumeration value="true" /&gt;
5840 &lt;xsd:enumeration value="false" /&gt;
5841 &lt;/xsd:restriction&gt;
5842 &lt;/xsd:simpleType&gt;
5843
5844 &lt;xsd:simpleType name="vxml.datatype"&gt;
5845 &lt;xsd:restriction base="xsd:NMTOKEN"/&gt;
5846 &lt;/xsd:simpleType&gt;
5847
5848 &lt;xsd:simpleType name="label.datatype"&gt;
5849 &lt;xsd:restriction base="xsd:NMTOKEN" /&gt;
5850 &lt;/xsd:simpleType&gt;
5851
5852 &lt;xsd:simpleType name="subscriptionid.datatype"&gt;
5853 &lt;xsd:restriction base="xsd:NMTOKEN" /&gt;
5854 &lt;/xsd:simpleType&gt;
5855
5856 &lt;/xsd:schema&gt;
5857
5858
5859
5860
5861
5862
5863
5864
5865
5866
5867
5868
5869
5870
5871
5872
5873
5874
5875
5876 <span class="grey">Boulton, et al. Standards Track [Page 105]</span></pre>
5877 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-106" ></span>
5878 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5879
5880
5881 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Media Service Resource Consumer Interface XML Schema</span>
5882
5883 This section gives the XML Schema Definition
5884 [<a href="#ref-W3C.REC-xmlschema-1-20041028">W3C.REC-xmlschema-1-20041028</a>] [<a href="#ref-W3C.REC-xmlschema-2-20041028">W3C.REC-xmlschema-2-20041028</a>] of the
5885 "application/mrb-consumer+xml" format.
5886
5887 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
5888 &lt;xsd:schema targetNamespace="urn:ietf:params:xml:ns:mrb-consumer"
5889 elementFormDefault="qualified" blockDefault="#all"
5890 xmlns="urn:ietf:params:xml:ns:mrb-consumer"
5891 xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
5892 xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt;
5893
5894 &lt;xsd:annotation&gt;
5895 &lt;xsd:documentation&gt;
5896 IETF MediaCtrl MRB 1.0
5897
5898 This is the schema of the IETF MediaCtrl MRB Consumer interface.
5899
5900 The schema namespace is urn:ietf:params:xml:ns:mrb-consumer
5901
5902 &lt;/xsd:documentation&gt;
5903 &lt;/xsd:annotation&gt;
5904
5905
5906 &lt;!--
5907 #############################################################
5908
5909 SCHEMA IMPORTS
5910
5911 #############################################################
5912 --&gt;
5913
5914 &lt;xsd:import namespace="http://www.w3.org/XML/1998/namespace"
5915 schemaLocation="http://www.w3.org/2001/xml.xsd"&gt;
5916 &lt;xsd:annotation&gt;
5917 &lt;xsd:documentation&gt;
5918 This import brings in the XML attributes for
5919 xml:base, xml:lang, etc.
5920 &lt;/xsd:documentation&gt;
5921 &lt;/xsd:annotation&gt;
5922 &lt;/xsd:import&gt;
5923
5924 &lt;xsd:import
5925 namespace="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
5926 schemaLocation="civicAddress.xsd"&gt;
5927 &lt;xsd:annotation&gt;
5928 &lt;xsd:documentation&gt;
5929
5930
5931
5932 <span class="grey">Boulton, et al. Standards Track [Page 106]</span></pre>
5933 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-107" ></span>
5934 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5935
5936
5937 This import brings in the civicAddress specification
5938 from <a href="./rfc5139">RFC 5139</a>.
5939 &lt;/xsd:documentation&gt;
5940 &lt;/xsd:annotation&gt;
5941 &lt;/xsd:import&gt;
5942
5943 &lt;!--
5944 #####################################################
5945
5946 Extensible core type
5947
5948 #####################################################
5949 --&gt;
5950
5951 &lt;xsd:complexType name="Tcore"&gt;
5952 &lt;xsd:annotation&gt;
5953 &lt;xsd:documentation&gt;
5954 This type is extended by other (non-mixed) component types to
5955 allow attributes from other namespaces.
5956 &lt;/xsd:documentation&gt;
5957 &lt;/xsd:annotation&gt;
5958 &lt;xsd:sequence/&gt;
5959 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5960 &lt;/xsd:complexType&gt;
5961
5962
5963 &lt;!--
5964 #####################################################
5965
5966 TOP-LEVEL ELEMENT: mrbconsumer
5967
5968 #####################################################
5969 --&gt;
5970
5971 &lt;xsd:complexType name="mrbconsumerType"&gt;
5972 &lt;xsd:complexContent&gt;
5973 &lt;xsd:extension base="Tcore"&gt;
5974 &lt;xsd:sequence&gt;
5975 &lt;xsd:choice&gt;
5976 &lt;xsd:element ref="mediaResourceRequest" /&gt;
5977 &lt;xsd:element ref="mediaResourceResponse" /&gt;
5978 &lt;xsd:any namespace="##other" minOccurs="0"
5979 maxOccurs="unbounded" processContents="lax" /&gt;
5980 &lt;/xsd:choice&gt;
5981 &lt;/xsd:sequence&gt;
5982 &lt;xsd:attribute name="version" type="version.datatype"
5983 use="required" /&gt;
5984 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
5985
5986
5987
5988 <span class="grey">Boulton, et al. Standards Track [Page 107]</span></pre>
5989 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-108" ></span>
5990 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
5991
5992
5993 &lt;/xsd:extension&gt;
5994 &lt;/xsd:complexContent&gt;
5995 &lt;/xsd:complexType&gt;
5996
5997 &lt;xsd:element name="mrbconsumer" type="mrbconsumerType" /&gt;
5998
5999
6000 &lt;!--
6001 #####################################################
6002
6003 mediaResourceRequest TYPE
6004
6005 #####################################################
6006 --&gt;
6007
6008 &lt;!-- mediaResourceRequest --&gt;
6009
6010 &lt;xsd:complexType name="mediaResourceRequestType"&gt;
6011 &lt;xsd:complexContent&gt;
6012 &lt;xsd:extension base="Tcore"&gt;
6013 &lt;xsd:sequence&gt;
6014 &lt;xsd:element ref="generalInfo" minOccurs="0" /&gt;
6015 &lt;xsd:element ref="ivrInfo" minOccurs="0" /&gt;
6016 &lt;xsd:element ref="mixerInfo" minOccurs="0" /&gt;
6017 &lt;xsd:any namespace="##other" minOccurs="0"
6018 maxOccurs="unbounded" processContents="lax" /&gt;
6019 &lt;/xsd:sequence&gt;
6020 &lt;xsd:attribute name="id" type="xsd:string"
6021 use="required" /&gt;
6022 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6023 &lt;/xsd:extension&gt;
6024 &lt;/xsd:complexContent&gt;
6025 &lt;/xsd:complexType&gt;
6026
6027 &lt;xsd:element name="mediaResourceRequest"
6028 type="mediaResourceRequestType" /&gt;
6029
6030
6031
6032
6033
6034
6035
6036
6037
6038
6039
6040
6041
6042
6043
6044 <span class="grey">Boulton, et al. Standards Track [Page 108]</span></pre>
6045 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-109" ></span>
6046 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6047
6048
6049 &lt;!--
6050 #####################################################
6051
6052 generalInfo TYPE
6053
6054 #####################################################
6055 --&gt;
6056
6057 &lt;!-- generalInfo --&gt;
6058
6059 &lt;xsd:complexType name="generalInfoType"&gt;
6060 &lt;xsd:complexContent&gt;
6061 &lt;xsd:extension base="Tcore"&gt;
6062 &lt;xsd:sequence&gt;
6063 &lt;xsd:element ref="session-info" minOccurs="0" /&gt;
6064 &lt;xsd:element ref="packages" minOccurs="0" /&gt;
6065 &lt;xsd:any namespace="##other" minOccurs="0"
6066 maxOccurs="unbounded" processContents="lax" /&gt;
6067 &lt;/xsd:sequence&gt;
6068 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6069 &lt;/xsd:extension&gt;
6070 &lt;/xsd:complexContent&gt;
6071 &lt;/xsd:complexType&gt;
6072
6073 &lt;xsd:element name="generalInfo" type="generalInfoType" /&gt;
6074
6075
6076 &lt;!-- session-info --&gt;
6077
6078 &lt;xsd:complexType name="session-infoType"&gt;
6079 &lt;xsd:complexContent&gt;
6080 &lt;xsd:extension base="Tcore"&gt;
6081 &lt;xsd:sequence&gt;
6082 &lt;xsd:element name="session-id" type="id.datatype"/&gt;
6083 &lt;xsd:element name="seq" type="xsd:nonNegativeInteger"/&gt;
6084 &lt;xsd:element name="action" type="action.datatype"/&gt;
6085 &lt;xsd:any namespace="##other" minOccurs="0"
6086 maxOccurs="unbounded" processContents="lax" /&gt;
6087 &lt;/xsd:sequence&gt;
6088 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6089 &lt;/xsd:extension&gt;
6090 &lt;/xsd:complexContent&gt;
6091 &lt;/xsd:complexType&gt;
6092
6093 &lt;xsd:element name="session-info" type="session-infoType" /&gt;
6094
6095
6096
6097
6098
6099
6100 <span class="grey">Boulton, et al. Standards Track [Page 109]</span></pre>
6101 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-110" ></span>
6102 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6103
6104
6105 &lt;!-- packages --&gt;
6106
6107 &lt;xsd:complexType name="packagesType"&gt;
6108 &lt;xsd:complexContent&gt;
6109 &lt;xsd:extension base="Tcore"&gt;
6110 &lt;xsd:sequence&gt;
6111 &lt;xsd:element name="package" type="xsd:string" minOccurs="0"
6112 maxOccurs="unbounded" /&gt;
6113 &lt;xsd:any namespace="##other" minOccurs="0"
6114 maxOccurs="unbounded" processContents="lax" /&gt;
6115 &lt;/xsd:sequence&gt;
6116 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6117 &lt;/xsd:extension&gt;
6118 &lt;/xsd:complexContent&gt;
6119 &lt;/xsd:complexType&gt;
6120
6121 &lt;xsd:element name="packages" type="packagesType"/&gt;
6122
6123
6124 &lt;!--
6125 #####################################################
6126
6127 ivrInfo TYPE
6128
6129 #####################################################
6130 --&gt;
6131
6132 &lt;!-- ivrInfo --&gt;
6133
6134 &lt;xsd:complexType name="ivrInfoType"&gt;
6135 &lt;xsd:complexContent&gt;
6136 &lt;xsd:extension base="Tcore"&gt;
6137 &lt;xsd:sequence&gt;
6138 &lt;xsd:element ref="ivr-sessions" minOccurs="0" /&gt;
6139 &lt;xsd:element ref="file-formats" minOccurs="0" /&gt;
6140 &lt;xsd:element ref="dtmf-type" minOccurs="0" /&gt;
6141 &lt;xsd:element ref="tones" minOccurs="0" /&gt;
6142 &lt;xsd:element ref="asr-tts" minOccurs="0" /&gt;
6143 &lt;xsd:element ref="vxml" minOccurs="0" /&gt;
6144 &lt;xsd:element ref="location" minOccurs="0" /&gt;
6145 &lt;xsd:element ref="encryption" minOccurs="0" /&gt;
6146 &lt;xsd:element ref="application-data" minOccurs="0" /&gt;
6147 &lt;xsd:element ref="max-prepared-duration" minOccurs="0" /&gt;
6148 &lt;xsd:element ref="file-transfer-modes" minOccurs="0" /&gt;
6149 &lt;xsd:any namespace="##other" minOccurs="0"
6150 maxOccurs="unbounded" processContents="lax" /&gt;
6151 &lt;/xsd:sequence&gt;
6152 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6153
6154
6155
6156 <span class="grey">Boulton, et al. Standards Track [Page 110]</span></pre>
6157 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-111" ></span>
6158 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6159
6160
6161 &lt;/xsd:extension&gt;
6162 &lt;/xsd:complexContent&gt;
6163 &lt;/xsd:complexType&gt;
6164
6165 &lt;xsd:element name="ivrInfo" type="ivrInfoType" /&gt;
6166
6167
6168 &lt;!--
6169 #####################################################
6170
6171 mixerInfo TYPE
6172
6173 #####################################################
6174 --&gt;
6175
6176 &lt;!-- mixerInfo --&gt;
6177
6178 &lt;xsd:complexType name="mixerInfoType"&gt;
6179 &lt;xsd:complexContent&gt;
6180 &lt;xsd:extension base="Tcore"&gt;
6181 &lt;xsd:sequence&gt;
6182 &lt;xsd:element ref="mixers" minOccurs="0"/&gt;
6183 &lt;xsd:element ref="file-formats" minOccurs="0"/&gt;
6184 &lt;xsd:element ref="dtmf-type" minOccurs="0"/&gt;
6185 &lt;xsd:element ref="tones" minOccurs="0"/&gt;
6186 &lt;xsd:element ref="mixing-modes" minOccurs="0"/&gt;
6187 &lt;xsd:element ref="application-data" minOccurs="0"/&gt;
6188 &lt;xsd:element ref="location" minOccurs="0"/&gt;
6189 &lt;xsd:element ref="encryption" minOccurs="0"/&gt;
6190 &lt;xsd:any namespace="##other" minOccurs="0"
6191 maxOccurs="unbounded" processContents="lax" /&gt;
6192 &lt;/xsd:sequence&gt;
6193 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6194 &lt;/xsd:extension&gt;
6195 &lt;/xsd:complexContent&gt;
6196 &lt;/xsd:complexType&gt;
6197
6198 &lt;xsd:element name="mixerInfo" type="mixerInfoType" /&gt;
6199
6200
6201
6202
6203
6204
6205
6206
6207
6208
6209
6210
6211
6212 <span class="grey">Boulton, et al. Standards Track [Page 111]</span></pre>
6213 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-112" ></span>
6214 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6215
6216
6217 &lt;!--
6218 #####################################################
6219
6220 mediaResourceResponse TYPE
6221
6222 #####################################################
6223 --&gt;
6224
6225 &lt;!-- mediaResourceResponse --&gt;
6226
6227 &lt;xsd:complexType name="mediaResourceResponseType"&gt;
6228 &lt;xsd:complexContent&gt;
6229 &lt;xsd:extension base="Tcore"&gt;
6230 &lt;xsd:sequence&gt;
6231 &lt;xsd:element ref="response-session-info" minOccurs="0" /&gt;
6232 &lt;xsd:any namespace="##other" minOccurs="0"
6233 maxOccurs="unbounded" processContents="lax" /&gt;
6234 &lt;/xsd:sequence&gt;
6235 &lt;xsd:attribute name="id" type="xsd:string"
6236 use="required" /&gt;
6237 &lt;xsd:attribute name="status" type="status.datatype"
6238 use="required" /&gt;
6239 &lt;xsd:attribute name="reason" type="xsd:string" /&gt;
6240 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6241 &lt;/xsd:extension&gt;
6242 &lt;/xsd:complexContent&gt;
6243 &lt;/xsd:complexType&gt;
6244
6245 &lt;xsd:element name="mediaResourceResponse"
6246 type="mediaResourceResponseType" /&gt;
6247
6248
6249 &lt;!--
6250 ####################################################
6251
6252 ELEMENTS
6253
6254 ####################################################
6255 --&gt;
6256
6257 &lt;!-- response-session-info --&gt;
6258
6259 &lt;xsd:complexType name="response-session-infoType"&gt;
6260 &lt;xsd:complexContent&gt;
6261 &lt;xsd:extension base="Tcore"&gt;
6262 &lt;xsd:sequence&gt;
6263 &lt;xsd:element name="session-id" type="id.datatype"/&gt;
6264 &lt;xsd:element name="seq" type="xsd:nonNegativeInteger"/&gt;
6265
6266
6267
6268 <span class="grey">Boulton, et al. Standards Track [Page 112]</span></pre>
6269 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-113" ></span>
6270 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6271
6272
6273 &lt;xsd:element name="expires" type="xsd:nonNegativeInteger"/&gt;
6274 &lt;xsd:element ref="media-server-address"
6275 minOccurs="0" maxOccurs="unbounded" /&gt;
6276 &lt;xsd:any namespace="##other" minOccurs="0"
6277 maxOccurs="unbounded" processContents="lax" /&gt;
6278 &lt;/xsd:sequence&gt;
6279 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6280 &lt;/xsd:extension&gt;
6281 &lt;/xsd:complexContent&gt;
6282 &lt;/xsd:complexType&gt;
6283
6284 &lt;xsd:element name="response-session-info"
6285 type="response-session-infoType" /&gt;
6286
6287 &lt;!-- media-server-address --&gt;
6288
6289 &lt;xsd:complexType name="media-server-addressTYPE"&gt;
6290 &lt;xsd:complexContent&gt;
6291 &lt;xsd:extension base="Tcore"&gt;
6292 &lt;xsd:sequence&gt;
6293 &lt;xsd:element name="connection-id" type="xsd:string"
6294 minOccurs="0" maxOccurs="unbounded" /&gt;
6295 &lt;xsd:element ref="ivr-sessions" minOccurs="0"/&gt;
6296 &lt;xsd:element ref="mixers" minOccurs="0"/&gt;
6297 &lt;xsd:any namespace="##other" minOccurs="0"
6298 maxOccurs="unbounded" processContents="lax" /&gt;
6299 &lt;/xsd:sequence&gt;
6300 &lt;xsd:attribute name="uri" type="xsd:anyURI" use="required" /&gt;
6301 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6302 &lt;/xsd:extension&gt;
6303 &lt;/xsd:complexContent&gt;
6304 &lt;/xsd:complexType&gt;
6305
6306 &lt;xsd:element name="media-server-address"
6307 type="media-server-addressTYPE" /&gt;
6308
6309 &lt;!-- ivr-sessions --&gt;
6310
6311 &lt;xsd:complexType name="ivr-sessionsType"&gt;
6312 &lt;xsd:complexContent&gt;
6313 &lt;xsd:extension base="Tcore"&gt;
6314 &lt;xsd:sequence&gt;
6315 &lt;xsd:element ref="rtp-codec" minOccurs="0"
6316 maxOccurs="unbounded" /&gt;
6317 &lt;xsd:any namespace="##other" minOccurs="0"
6318 maxOccurs="unbounded" processContents="lax" /&gt;
6319 &lt;/xsd:sequence&gt;
6320 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6321
6322
6323
6324 <span class="grey">Boulton, et al. Standards Track [Page 113]</span></pre>
6325 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-114" ></span>
6326 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6327
6328
6329 &lt;/xsd:extension&gt;
6330 &lt;/xsd:complexContent&gt;
6331 &lt;/xsd:complexType&gt;
6332
6333 &lt;xsd:element name="ivr-sessions" type="ivr-sessionsType" /&gt;
6334
6335 &lt;xsd:complexType name="rtp-codecType"&gt;
6336 &lt;xsd:complexContent&gt;
6337 &lt;xsd:extension base="Tcore"&gt;
6338 &lt;xsd:sequence&gt;
6339 &lt;xsd:element name="decoding" type="xsd:nonNegativeInteger" /&gt;
6340 &lt;xsd:element name="encoding" type="xsd:nonNegativeInteger" /&gt;
6341 &lt;xsd:any namespace="##other" minOccurs="0"
6342 maxOccurs="unbounded" processContents="lax" /&gt;
6343 &lt;/xsd:sequence&gt;
6344 &lt;xsd:attribute name="name" type="xsd:string" use="required" /&gt;
6345 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6346 &lt;/xsd:extension&gt;
6347 &lt;/xsd:complexContent&gt;
6348 &lt;/xsd:complexType&gt;
6349
6350 &lt;xsd:element name="rtp-codec" type="rtp-codecType" /&gt;
6351
6352
6353 &lt;!-- file-formats --&gt;
6354
6355 &lt;xsd:complexType name="file-formatsType"&gt;
6356 &lt;xsd:complexContent&gt;
6357 &lt;xsd:extension base="Tcore"&gt;
6358 &lt;xsd:sequence&gt;
6359 &lt;xsd:element ref="required-format"
6360 minOccurs="0" maxOccurs="unbounded" /&gt;
6361 &lt;xsd:any namespace="##other" minOccurs="0"
6362 maxOccurs="unbounded" processContents="lax" /&gt;
6363 &lt;/xsd:sequence&gt;
6364 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6365 &lt;/xsd:extension&gt;
6366 &lt;/xsd:complexContent&gt;
6367 &lt;/xsd:complexType&gt;
6368
6369 &lt;xsd:element name="file-formats" type="file-formatsType" /&gt;
6370
6371 &lt;xsd:complexType name="required-formatType"&gt;
6372 &lt;xsd:complexContent&gt;
6373 &lt;xsd:extension base="Tcore"&gt;
6374 &lt;xsd:sequence&gt;
6375 &lt;xsd:element ref="required-file-package"
6376 minOccurs="0" maxOccurs="unbounded" /&gt;
6377
6378
6379
6380 <span class="grey">Boulton, et al. Standards Track [Page 114]</span></pre>
6381 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-115" ></span>
6382 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6383
6384
6385 &lt;xsd:any namespace="##other" minOccurs="0"
6386 maxOccurs="unbounded" processContents="lax" /&gt;
6387 &lt;/xsd:sequence&gt;
6388 &lt;xsd:attribute name="name" type="xsd:string" use="required" /&gt;
6389 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6390 &lt;/xsd:extension&gt;
6391 &lt;/xsd:complexContent&gt;
6392 &lt;/xsd:complexType&gt;
6393
6394 &lt;xsd:element name="required-format" type="required-formatType" /&gt;
6395
6396 &lt;xsd:complexType name="required-file-packageType"&gt;
6397 &lt;xsd:complexContent&gt;
6398 &lt;xsd:extension base="Tcore"&gt;
6399 &lt;xsd:sequence&gt;
6400 &lt;xsd:element name="required-file-package-name" type="xsd:string"
6401 minOccurs="0" maxOccurs="unbounded" /&gt;
6402 &lt;xsd:any namespace="##other" minOccurs="0"
6403 maxOccurs="unbounded" processContents="lax" /&gt;
6404 &lt;/xsd:sequence&gt;
6405 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6406 &lt;/xsd:extension&gt;
6407 &lt;/xsd:complexContent&gt;
6408 &lt;/xsd:complexType&gt;
6409
6410 &lt;xsd:element name="required-file-package"
6411 type="required-file-packageType" /&gt;
6412
6413 &lt;!-- dtmf-type --&gt;
6414
6415 &lt;xsd:complexType name="dtmfType"&gt;
6416 &lt;xsd:complexContent&gt;
6417 &lt;xsd:extension base="Tcore"&gt;
6418 &lt;xsd:sequence&gt;
6419 &lt;xsd:element ref="detect" /&gt;
6420 &lt;xsd:element ref="generate" /&gt;
6421 &lt;xsd:element ref="passthrough" /&gt;
6422 &lt;xsd:any namespace="##other" minOccurs="0"
6423 maxOccurs="unbounded" processContents="lax" /&gt;
6424 &lt;/xsd:sequence&gt;
6425 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6426 &lt;/xsd:extension&gt;
6427 &lt;/xsd:complexContent&gt;
6428 &lt;/xsd:complexType&gt;
6429
6430 &lt;xsd:element name="dtmf" type="dtmfType" /&gt;
6431
6432 &lt;xsd:complexType name="detectType"&gt;
6433
6434
6435
6436 <span class="grey">Boulton, et al. Standards Track [Page 115]</span></pre>
6437 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-116" ></span>
6438 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6439
6440
6441 &lt;xsd:complexContent&gt;
6442 &lt;xsd:extension base="Tcore"&gt;
6443 &lt;xsd:sequence&gt;
6444 &lt;xsd:element ref="dtmf-type"
6445 minOccurs="0" maxOccurs="unbounded" /&gt;
6446 &lt;xsd:any namespace="##other" minOccurs="0"
6447 maxOccurs="unbounded" processContents="lax" /&gt;
6448 &lt;/xsd:sequence&gt;
6449 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6450 &lt;/xsd:extension&gt;
6451 &lt;/xsd:complexContent&gt;
6452 &lt;/xsd:complexType&gt;
6453
6454 &lt;xsd:element name="detect" type="detectType" /&gt;
6455
6456 &lt;xsd:complexType name="generateType"&gt;
6457 &lt;xsd:complexContent&gt;
6458 &lt;xsd:extension base="Tcore"&gt;
6459 &lt;xsd:sequence&gt;
6460 &lt;xsd:element ref="dtmf-type"
6461 minOccurs="0" maxOccurs="unbounded" /&gt;
6462 &lt;xsd:any namespace="##other" minOccurs="0"
6463 maxOccurs="unbounded" processContents="lax" /&gt;
6464 &lt;/xsd:sequence&gt;
6465 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6466 &lt;/xsd:extension&gt;
6467 &lt;/xsd:complexContent&gt;
6468 &lt;/xsd:complexType&gt;
6469
6470 &lt;xsd:element name="generate" type="generateType" /&gt;
6471
6472 &lt;xsd:complexType name="passthroughType"&gt;
6473 &lt;xsd:complexContent&gt;
6474 &lt;xsd:extension base="Tcore"&gt;
6475 &lt;xsd:sequence&gt;
6476 &lt;xsd:element ref="dtmf-type"
6477 minOccurs="0" maxOccurs="unbounded" /&gt;
6478 &lt;xsd:any namespace="##other" minOccurs="0"
6479 maxOccurs="unbounded" processContents="lax" /&gt;
6480 &lt;/xsd:sequence&gt;
6481 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6482 &lt;/xsd:extension&gt;
6483 &lt;/xsd:complexContent&gt;
6484 &lt;/xsd:complexType&gt;
6485
6486 &lt;xsd:element name="passthrough" type="passthroughType" /&gt;
6487
6488 &lt;xsd:complexType name="dtmf-typeType"&gt;
6489
6490
6491
6492 <span class="grey">Boulton, et al. Standards Track [Page 116]</span></pre>
6493 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-117" ></span>
6494 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6495
6496
6497 &lt;xsd:complexContent&gt;
6498 &lt;xsd:extension base="Tcore"&gt;
6499 &lt;xsd:sequence&gt;
6500 &lt;xsd:any namespace="##other" minOccurs="0"
6501 maxOccurs="unbounded" processContents="lax" /&gt;
6502 &lt;/xsd:sequence&gt;
6503 &lt;xsd:attribute name="name" type="dtmf.datatype" use="required" /&gt;
6504 &lt;xsd:attribute name="package" type="xsd:string" use="required" /&gt;
6505 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6506 &lt;/xsd:extension&gt;
6507 &lt;/xsd:complexContent&gt;
6508 &lt;/xsd:complexType&gt;
6509
6510 &lt;xsd:element name="dtmf-type" type="dtmf-typeType" /&gt;
6511
6512 &lt;!-- tones --&gt;
6513
6514 &lt;xsd:complexType name="required-tonesType"&gt;
6515 &lt;xsd:complexContent&gt;
6516 &lt;xsd:extension base="Tcore"&gt;
6517 &lt;xsd:sequence&gt;
6518 &lt;xsd:element ref="country-codes"
6519 minOccurs="0" maxOccurs="1" /&gt;
6520 &lt;xsd:element ref="h248-codes"
6521 minOccurs="0" maxOccurs="1" /&gt;
6522 &lt;xsd:any namespace="##other" minOccurs="0"
6523 maxOccurs="unbounded" processContents="lax" /&gt;
6524 &lt;/xsd:sequence&gt;
6525 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6526 &lt;/xsd:extension&gt;
6527 &lt;/xsd:complexContent&gt;
6528 &lt;/xsd:complexType&gt;
6529
6530 &lt;xsd:element name="tones" type="required-tonesType" /&gt;
6531
6532 &lt;xsd:complexType name="required-country-codesType"&gt;
6533 &lt;xsd:complexContent&gt;
6534 &lt;xsd:extension base="Tcore"&gt;
6535 &lt;xsd:sequence&gt;
6536 &lt;xsd:element ref="country-code"
6537 minOccurs="0" maxOccurs="unbounded" /&gt;
6538 &lt;xsd:any namespace="##other" minOccurs="0"
6539 maxOccurs="unbounded" processContents="lax" /&gt;
6540 &lt;/xsd:sequence&gt;
6541 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6542 &lt;/xsd:extension&gt;
6543 &lt;/xsd:complexContent&gt;
6544 &lt;/xsd:complexType&gt;
6545
6546
6547
6548 <span class="grey">Boulton, et al. Standards Track [Page 117]</span></pre>
6549 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-118" ></span>
6550 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6551
6552
6553 &lt;xsd:element name="country-codes"
6554 type="required-country-codesType" /&gt;
6555
6556 &lt;xsd:complexType name="country-codeType" mixed="true"&gt;
6557 &lt;xsd:sequence&gt;
6558 &lt;xsd:any namespace="##other" minOccurs="0"
6559 maxOccurs="unbounded" processContents="lax" /&gt;
6560 &lt;/xsd:sequence&gt;
6561 &lt;xsd:attribute name="package" type="xsd:string" use="required" /&gt;
6562 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6563 &lt;/xsd:complexType&gt;
6564
6565 &lt;xsd:element name="country-code" type="country-codeType" /&gt;
6566
6567 &lt;xsd:complexType name="required-h248-codesType"&gt;
6568 &lt;xsd:complexContent&gt;
6569 &lt;xsd:extension base="Tcore"&gt;
6570 &lt;xsd:sequence&gt;
6571 &lt;xsd:element ref="h248-code"
6572 minOccurs="0" maxOccurs="unbounded" /&gt;
6573 &lt;xsd:any namespace="##other" minOccurs="0"
6574 maxOccurs="unbounded" processContents="lax" /&gt;
6575 &lt;/xsd:sequence&gt;
6576 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6577 &lt;/xsd:extension&gt;
6578 &lt;/xsd:complexContent&gt;
6579 &lt;/xsd:complexType&gt;
6580
6581 &lt;xsd:element name="h248-codes"
6582 type="required-h248-codesType" /&gt;
6583
6584 &lt;xsd:complexType name="h248-codeType" mixed="true"&gt;
6585 &lt;xsd:sequence&gt;
6586 &lt;xsd:any namespace="##other" minOccurs="0"
6587 maxOccurs="unbounded" processContents="lax" /&gt;
6588 &lt;/xsd:sequence&gt;
6589 &lt;xsd:attribute name="package" type="xsd:string" use="required" /&gt;
6590 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6591 &lt;/xsd:complexType&gt;
6592
6593 &lt;xsd:element name="h248-code" type="h248-codeType" /&gt;
6594
6595 &lt;!-- asr-tts --&gt;
6596
6597 &lt;xsd:complexType name="asr-ttsType"&gt;
6598 &lt;xsd:complexContent&gt;
6599 &lt;xsd:extension base="Tcore"&gt;
6600 &lt;xsd:sequence&gt;
6601
6602
6603
6604 <span class="grey">Boulton, et al. Standards Track [Page 118]</span></pre>
6605 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-119" ></span>
6606 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6607
6608
6609 &lt;xsd:element ref="asr-support"
6610 minOccurs="0" maxOccurs="1" /&gt;
6611 &lt;xsd:element ref="tts-support"
6612 minOccurs="0" maxOccurs="1" /&gt;
6613 &lt;xsd:any namespace="##other" minOccurs="0"
6614 maxOccurs="unbounded" processContents="lax" /&gt;
6615 &lt;/xsd:sequence&gt;
6616 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6617 &lt;/xsd:extension&gt;
6618 &lt;/xsd:complexContent&gt;
6619 &lt;/xsd:complexType&gt;
6620
6621 &lt;xsd:element name="asr-tts" type="asr-ttsType" /&gt;
6622
6623 &lt;xsd:complexType name="asr-supportType"&gt;
6624 &lt;xsd:complexContent&gt;
6625 &lt;xsd:extension base="Tcore"&gt;
6626 &lt;xsd:sequence&gt;
6627 &lt;xsd:element ref="language"
6628 minOccurs="0" maxOccurs="unbounded" /&gt;
6629 &lt;xsd:any namespace="##other" minOccurs="0"
6630 maxOccurs="unbounded" processContents="lax" /&gt;
6631 &lt;/xsd:sequence&gt;
6632 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6633 &lt;/xsd:extension&gt;
6634 &lt;/xsd:complexContent&gt;
6635 &lt;/xsd:complexType&gt;
6636
6637 &lt;xsd:element name="asr-support" type="asr-supportType" /&gt;
6638
6639 &lt;xsd:complexType name="tts-supportType"&gt;
6640 &lt;xsd:complexContent&gt;
6641 &lt;xsd:extension base="Tcore"&gt;
6642 &lt;xsd:sequence&gt;
6643 &lt;xsd:element ref="language"
6644 minOccurs="0" maxOccurs="unbounded" /&gt;
6645 &lt;xsd:any namespace="##other" minOccurs="0"
6646 maxOccurs="unbounded" processContents="lax" /&gt;
6647 &lt;/xsd:sequence&gt;
6648 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6649 &lt;/xsd:extension&gt;
6650 &lt;/xsd:complexContent&gt;
6651 &lt;/xsd:complexType&gt;
6652
6653 &lt;xsd:element name="tts-support" type="tts-supportType" /&gt;
6654
6655 &lt;xsd:complexType name="languageType"&gt;
6656 &lt;xsd:complexContent&gt;
6657
6658
6659
6660 <span class="grey">Boulton, et al. Standards Track [Page 119]</span></pre>
6661 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-120" ></span>
6662 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6663
6664
6665 &lt;xsd:extension base="Tcore"&gt;
6666 &lt;xsd:sequence&gt;
6667 &lt;xsd:any namespace="##other" minOccurs="0"
6668 maxOccurs="unbounded" processContents="lax" /&gt;
6669 &lt;/xsd:sequence&gt;
6670 &lt;xsd:attribute ref="xml:lang" /&gt;
6671 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6672 &lt;/xsd:extension&gt;
6673 &lt;/xsd:complexContent&gt;
6674 &lt;/xsd:complexType&gt;
6675
6676 &lt;xsd:element name="language" type="languageType" /&gt;
6677
6678
6679 &lt;!-- vxml --&gt;
6680
6681 &lt;xsd:complexType name="vxmlType"&gt;
6682 &lt;xsd:complexContent&gt;
6683 &lt;xsd:extension base="Tcore"&gt;
6684 &lt;xsd:sequence&gt;
6685 &lt;xsd:element ref="vxml-mode"
6686 minOccurs="0" maxOccurs="unbounded" /&gt;
6687 &lt;xsd:any namespace="##other" minOccurs="0"
6688 maxOccurs="unbounded" processContents="lax" /&gt;
6689 &lt;/xsd:sequence&gt;
6690 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6691 &lt;/xsd:extension&gt;
6692 &lt;/xsd:complexContent&gt;
6693 &lt;/xsd:complexType&gt;
6694
6695 &lt;xsd:element name="vxml" type="vxmlType" /&gt;
6696
6697 &lt;xsd:complexType name="vxml-modeType"&gt;
6698 &lt;xsd:complexContent&gt;
6699 &lt;xsd:extension base="Tcore"&gt;
6700 &lt;xsd:sequence&gt;
6701 &lt;xsd:any namespace="##other" minOccurs="0"
6702 maxOccurs="unbounded" processContents="lax" /&gt;
6703 &lt;/xsd:sequence&gt;
6704 &lt;xsd:attribute name="package" type="xsd:string" use="required" /&gt;
6705 &lt;xsd:attribute name="require" type="vxml.datatype" use="required" /&gt;
6706 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6707 &lt;/xsd:extension&gt;
6708 &lt;/xsd:complexContent&gt;
6709 &lt;/xsd:complexType&gt;
6710
6711 &lt;xsd:element name="vxml-mode" type="vxml-modeType" /&gt;
6712
6713
6714
6715
6716 <span class="grey">Boulton, et al. Standards Track [Page 120]</span></pre>
6717 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-121" ></span>
6718 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6719
6720
6721 &lt;!-- location --&gt;
6722
6723 &lt;xsd:complexType name="locationType"&gt;
6724 &lt;xsd:complexContent&gt;
6725 &lt;xsd:extension base="Tcore"&gt;
6726 &lt;xsd:sequence&gt;
6727 &lt;xsd:element ref="ca:civicAddress"
6728 minOccurs="1" maxOccurs="1" /&gt;
6729 &lt;xsd:any namespace="##other" minOccurs="0"
6730 maxOccurs="unbounded" processContents="lax" /&gt;
6731 &lt;/xsd:sequence&gt;
6732 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6733 &lt;/xsd:extension&gt;
6734 &lt;/xsd:complexContent&gt;
6735 &lt;/xsd:complexType&gt;
6736
6737 &lt;xsd:element name="location" type="locationType" /&gt;
6738
6739
6740 &lt;!-- encryption --&gt;
6741
6742 &lt;xsd:complexType name="encryptionType"&gt;
6743 &lt;xsd:complexContent&gt;
6744 &lt;xsd:extension base="Tcore"&gt;
6745 &lt;xsd:sequence&gt;
6746 &lt;xsd:any namespace="##other" minOccurs="0"
6747 maxOccurs="unbounded" processContents="lax" /&gt;
6748 &lt;/xsd:sequence&gt;
6749 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6750 &lt;/xsd:extension&gt;
6751 &lt;/xsd:complexContent&gt;
6752 &lt;/xsd:complexType&gt;
6753
6754 &lt;xsd:element name="encryption" type="encryptionType" /&gt;
6755
6756 &lt;!-- application-data --&gt;
6757
6758 &lt;xsd:element name="application-data" type="appdata.datatype" /&gt;
6759
6760 &lt;!-- max-prepared-duration --&gt;
6761
6762 &lt;xsd:complexType name="max-prepared-durationType"&gt;
6763 &lt;xsd:complexContent&gt;
6764 &lt;xsd:extension base="Tcore"&gt;
6765 &lt;xsd:sequence&gt;
6766 &lt;xsd:element ref="max-time" /&gt;
6767 &lt;xsd:any namespace="##other" minOccurs="0"
6768 maxOccurs="unbounded" processContents="lax" /&gt;
6769
6770
6771
6772 <span class="grey">Boulton, et al. Standards Track [Page 121]</span></pre>
6773 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-122" ></span>
6774 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6775
6776
6777 &lt;/xsd:sequence&gt;
6778 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6779 &lt;/xsd:extension&gt;
6780 &lt;/xsd:complexContent&gt;
6781 &lt;/xsd:complexType&gt;
6782
6783 &lt;xsd:element name="max-prepared-duration"
6784 type="max-prepared-durationType" /&gt;
6785
6786
6787 &lt;xsd:complexType name="max-timeType"&gt;
6788 &lt;xsd:complexContent&gt;
6789 &lt;xsd:extension base="Tcore"&gt;
6790 &lt;xsd:sequence&gt;
6791 &lt;xsd:element name="max-time-package" type="xsd:string" /&gt;
6792 &lt;xsd:any namespace="##other" minOccurs="0"
6793 maxOccurs="unbounded" processContents="lax" /&gt;
6794 &lt;/xsd:sequence&gt;
6795 &lt;xsd:attribute name="max-time-seconds" type="xsd:nonNegativeInteger"
6796 use="required" /&gt;
6797 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6798 &lt;/xsd:extension&gt;
6799 &lt;/xsd:complexContent&gt;
6800 &lt;/xsd:complexType&gt;
6801
6802 &lt;xsd:element name="max-time" type="max-timeType" /&gt;
6803
6804
6805 &lt;!-- file-transfer-modes --&gt;
6806
6807 &lt;xsd:complexType name="file-transfer-modesType"&gt;
6808 &lt;xsd:complexContent&gt;
6809 &lt;xsd:extension base="Tcore"&gt;
6810 &lt;xsd:sequence&gt;
6811 &lt;xsd:element ref="file-transfer-mode"
6812 minOccurs="0" maxOccurs="unbounded" /&gt;
6813 &lt;xsd:any namespace="##other" minOccurs="0"
6814 maxOccurs="unbounded" processContents="lax" /&gt;
6815 &lt;/xsd:sequence&gt;
6816 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6817 &lt;/xsd:extension&gt;
6818 &lt;/xsd:complexContent&gt;
6819 &lt;/xsd:complexType&gt;
6820
6821 &lt;xsd:element name="file-transfer-modes"
6822 type="file-transfer-modesType" /&gt;
6823
6824 &lt;xsd:complexType name="file-transfer-modeType"&gt;
6825
6826
6827
6828 <span class="grey">Boulton, et al. Standards Track [Page 122]</span></pre>
6829 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-123" ></span>
6830 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6831
6832
6833 &lt;xsd:complexContent&gt;
6834 &lt;xsd:extension base="Tcore"&gt;
6835 &lt;xsd:sequence&gt;
6836 &lt;xsd:any namespace="##other" minOccurs="0"
6837 maxOccurs="unbounded" processContents="lax" /&gt;
6838 &lt;/xsd:sequence&gt;
6839 &lt;xsd:attribute name="name" type="transfermode.datatype"
6840 use="required" /&gt;
6841 &lt;xsd:attribute name="package" type="xsd:string" use="required" /&gt;
6842 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6843 &lt;/xsd:extension&gt;
6844 &lt;/xsd:complexContent&gt;
6845 &lt;/xsd:complexType&gt;
6846
6847 &lt;xsd:element name="file-transfer-mode" type="file-transfer-modeType" /&gt;
6848
6849 &lt;!-- mixers --&gt;
6850
6851 &lt;xsd:complexType name="mixerssessionsType"&gt;
6852 &lt;xsd:complexContent&gt;
6853 &lt;xsd:extension base="Tcore"&gt;
6854 &lt;xsd:sequence&gt;
6855 &lt;xsd:element ref="mix" minOccurs="0"
6856 maxOccurs="unbounded" /&gt;
6857 &lt;xsd:any namespace="##other" minOccurs="0"
6858 maxOccurs="unbounded" processContents="lax" /&gt;
6859 &lt;/xsd:sequence&gt;
6860 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6861 &lt;/xsd:extension&gt;
6862 &lt;/xsd:complexContent&gt;
6863 &lt;/xsd:complexType&gt;
6864
6865 &lt;xsd:element name="mixers" type="mixerssessionsType" /&gt;
6866
6867 &lt;xsd:complexType name="mixType"&gt;
6868 &lt;xsd:complexContent&gt;
6869 &lt;xsd:extension base="Tcore"&gt;
6870 &lt;xsd:sequence&gt;
6871 &lt;xsd:element ref="rtp-codec" minOccurs="0"
6872 maxOccurs="unbounded" /&gt;
6873 &lt;xsd:any namespace="##other" minOccurs="0"
6874 maxOccurs="unbounded" processContents="lax" /&gt;
6875 &lt;/xsd:sequence&gt;
6876 &lt;xsd:attribute name="users" type="xsd:nonNegativeInteger"
6877 use="required" /&gt;
6878 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6879 &lt;/xsd:extension&gt;
6880 &lt;/xsd:complexContent&gt;
6881
6882
6883
6884 <span class="grey">Boulton, et al. Standards Track [Page 123]</span></pre>
6885 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-124" ></span>
6886 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6887
6888
6889 &lt;/xsd:complexType&gt;
6890
6891 &lt;xsd:element name="mix" type="mixType" /&gt;
6892
6893 &lt;!-- mixing-modes --&gt;
6894
6895 &lt;xsd:complexType name="mixing-modesType"&gt;
6896 &lt;xsd:complexContent&gt;
6897 &lt;xsd:extension base="Tcore"&gt;
6898 &lt;xsd:sequence&gt;
6899 &lt;xsd:element ref="audio-mixing-modes"
6900 minOccurs="0" maxOccurs="1" /&gt;
6901 &lt;xsd:element ref="video-mixing-modes"
6902 minOccurs="0" maxOccurs="1" /&gt;
6903 &lt;xsd:any namespace="##other" minOccurs="0"
6904 maxOccurs="unbounded" processContents="lax" /&gt;
6905 &lt;/xsd:sequence&gt;
6906 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6907 &lt;/xsd:extension&gt;
6908 &lt;/xsd:complexContent&gt;
6909 &lt;/xsd:complexType&gt;
6910
6911 &lt;xsd:element name="mixing-modes" type="mixing-modesType" /&gt;
6912
6913 &lt;xsd:complexType name="audio-mixing-modesType"&gt;
6914 &lt;xsd:complexContent&gt;
6915 &lt;xsd:extension base="Tcore"&gt;
6916 &lt;xsd:sequence&gt;
6917 &lt;xsd:element ref="audio-mixing-mode"
6918 minOccurs="0" maxOccurs="unbounded" /&gt;
6919 &lt;xsd:any namespace="##other" minOccurs="0"
6920 maxOccurs="unbounded" processContents="lax" /&gt;
6921 &lt;/xsd:sequence&gt;
6922 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6923 &lt;/xsd:extension&gt;
6924 &lt;/xsd:complexContent&gt;
6925 &lt;/xsd:complexType&gt;
6926
6927 &lt;xsd:element name="audio-mixing-modes" type="audio-mixing-modesType" /&gt;
6928
6929 &lt;xsd:complexType name="audio-mixing-modeType" mixed="true"&gt;
6930 &lt;xsd:sequence&gt;
6931 &lt;xsd:any namespace="##other" minOccurs="0"
6932 maxOccurs="unbounded" processContents="lax" /&gt;
6933 &lt;/xsd:sequence&gt;
6934 &lt;xsd:attribute name="package" type="xsd:string" use="required" /&gt;
6935 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6936 &lt;/xsd:complexType&gt;
6937
6938
6939
6940 <span class="grey">Boulton, et al. Standards Track [Page 124]</span></pre>
6941 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-125" ></span>
6942 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6943
6944
6945 &lt;xsd:element name="audio-mixing-mode" type="audio-mixing-modeType" /&gt;
6946
6947 &lt;xsd:complexType name="video-mixing-modesType"&gt;
6948 &lt;xsd:complexContent&gt;
6949 &lt;xsd:extension base="Tcore"&gt;
6950 &lt;xsd:sequence&gt;
6951 &lt;xsd:element ref="video-mixing-mode"
6952 minOccurs="0" maxOccurs="unbounded" /&gt;
6953 &lt;xsd:any namespace="##other" minOccurs="0"
6954 maxOccurs="unbounded" processContents="lax" /&gt;
6955 &lt;/xsd:sequence&gt;
6956 &lt;xsd:attribute name="vas" type="boolean.datatype"
6957 default="false" /&gt;
6958 &lt;xsd:attribute name="activespeakermix" type="boolean.datatype"
6959 default="false" /&gt;
6960 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6961 &lt;/xsd:extension&gt;
6962 &lt;/xsd:complexContent&gt;
6963 &lt;/xsd:complexType&gt;
6964
6965 &lt;xsd:element name="video-mixing-modes" type="video-mixing-modesType" /&gt;
6966
6967 &lt;xsd:complexType name="video-mixing-modeType" mixed="true"&gt;
6968 &lt;xsd:sequence&gt;
6969 &lt;xsd:any namespace="##other" minOccurs="0"
6970 maxOccurs="unbounded" processContents="lax" /&gt;
6971 &lt;/xsd:sequence&gt;
6972 &lt;xsd:attribute name="package" type="xsd:string" use="required" /&gt;
6973 &lt;xsd:anyAttribute namespace="##other" processContents="lax" /&gt;
6974 &lt;/xsd:complexType&gt;
6975
6976 &lt;xsd:element name="video-mixing-mode" type="video-mixing-modeType" /&gt;
6977
6978
6979 &lt;!--
6980 ####################################################
6981
6982 DATATYPES
6983
6984 ####################################################
6985 --&gt;
6986
6987 &lt;xsd:simpleType name="version.datatype"&gt;
6988 &lt;xsd:restriction base="xsd:NMTOKEN"&gt;
6989 &lt;xsd:enumeration value="1.0" /&gt;
6990 &lt;/xsd:restriction&gt;
6991 &lt;/xsd:simpleType&gt;
6992
6993
6994
6995
6996 <span class="grey">Boulton, et al. Standards Track [Page 125]</span></pre>
6997 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-126" ></span>
6998 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
6999
7000
7001 &lt;xsd:simpleType name="id.datatype"&gt;
7002 &lt;xsd:restriction base="xsd:NMTOKEN" /&gt;
7003 &lt;/xsd:simpleType&gt;
7004
7005 &lt;xsd:simpleType name="status.datatype"&gt;
7006 &lt;xsd:restriction base="xsd:positiveInteger"&gt;
7007 &lt;xsd:pattern value="[0-9][0-9][0-9]" /&gt;
7008 &lt;/xsd:restriction&gt;
7009 &lt;/xsd:simpleType&gt;
7010
7011 &lt;xsd:simpleType name="transfermode.datatype"&gt;
7012 &lt;xsd:restriction base="xsd:NMTOKEN"/&gt;
7013 &lt;/xsd:simpleType&gt;
7014
7015 &lt;xsd:simpleType name="action.datatype"&gt;
7016 &lt;xsd:restriction base="xsd:NMTOKEN"&gt;
7017 &lt;xsd:enumeration value="remove" /&gt;
7018 &lt;xsd:enumeration value="update" /&gt;
7019 &lt;/xsd:restriction&gt;
7020 &lt;/xsd:simpleType&gt;
7021
7022 &lt;xsd:simpleType name="dtmf.datatype"&gt;
7023 &lt;xsd:restriction base="xsd:NMTOKEN"/&gt;
7024 &lt;/xsd:simpleType&gt;
7025
7026 &lt;xsd:simpleType name="boolean.datatype"&gt;
7027 &lt;xsd:restriction base="xsd:NMTOKEN"&gt;
7028 &lt;xsd:enumeration value="true" /&gt;
7029 &lt;xsd:enumeration value="false" /&gt;
7030 &lt;/xsd:restriction&gt;
7031 &lt;/xsd:simpleType&gt;
7032
7033 &lt;xsd:simpleType name="vxml.datatype"&gt;
7034 &lt;xsd:restriction base="xsd:NMTOKEN"/&gt;
7035 &lt;/xsd:simpleType&gt;
7036
7037 &lt;xsd:simpleType name="appdata.datatype"&gt;
7038 &lt;xsd:restriction base="xsd:string" /&gt;
7039 &lt;/xsd:simpleType&gt;
7040
7041 &lt;/xsd:schema&gt;
7042
7043
7044
7045
7046
7047
7048
7049
7050
7051
7052 <span class="grey">Boulton, et al. Standards Track [Page 126]</span></pre>
7053 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-127" ></span>
7054 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
7055
7056
7057 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Security Considerations</span>
7058
7059 The MRB network entity has two primary interfaces -- Publish and
7060 Consumer -- that carry sensitive information and must therefore be
7061 appropriately protected and secured.
7062
7063 The Publish interface, as defined in and described in <a href="#section-5.1">Section 5.1</a>,
7064 uses the Media Control Channel Framework [<a href="./rfc6230" title="&quot;Media Control Channel Framework&quot;">RFC6230</a>] as a mechanism to
7065 connect an MRB to a Media Server. It is very important that the
7066 communication between the MRB and the Media Server is secured: a
7067 malicious entity may change or even delete subscriptions to a Media
7068 Server, thus affecting the view the MRB has of the resources actually
7069 available on a Media Server, leading it to incorrect selection when
7070 media resources are being requested by an Application Server. A
7071 malicious entity may even manipulate available resources on a Media
7072 Server, for example, to make the MRB think no resources are available
7073 at all. Considering that the Publish interface is a CFW Control
7074 Package, the same security considerations included in the Media
7075 Control Channel Framework specification apply here to protect
7076 interactions between an MRB and a Media Server.
7077
7078 The Publish interface also allows a Media Server, as explained in
7079 <a href="#section-5.1.5.18">Section 5.1.5.18</a>, to provide more or less accurate information about
7080 its geographic location, should Application Servers be interested in
7081 such details when looking for services at an MRB. While the usage of
7082 this information is entirely optional and the level of detail to be
7083 provided is implementation specific, it is important to draw
7084 attention to the potential security issues that the disclosure of
7085 such addresses may introduce. As such, it is important to make sure
7086 MRB implementations don't disclose this information as is to
7087 interested Application Servers but only exploit those addresses as
7088 part of computation algorithms to pick the most adequate resources
7089 Application Servers may be looking for.
7090
7091 The Consumer interface, as defined in and described in <a href="#section-5.2">Section 5.2</a>,
7092 conceives transactions based on a session ID. These transactions may
7093 be transported either by means of HTTP messages or SIP dialogs. This
7094 means that malicious users could be able to disrupt or manipulate an
7095 MRB session should they have access to the above-mentioned session ID
7096 or replicate it somehow: for instance, a malicious entity could
7097 modify an existing session between an Application Server and the MRB,
7098 e.g., requesting less resources than originally requested to cause
7099 media dialogs to be rejected by the Application Server, or requesting
7100 many more resources instead to try and lock as many of (if not all)
7101 the resources an MRB can provide, thus making them unavailable to
7102 other legitimate Application Servers in subsequent requests. In
7103 order to prevent this, it is strongly advised that MRB
7104 implementations generate session identifiers that are very hard to
7105
7106
7107
7108 <span class="grey">Boulton, et al. Standards Track [Page 127]</span></pre>
7109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-128" ></span>
7110 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
7111
7112
7113 replicate, in order to minimize the chances that malicious users
7114 could gain access to valid identifiers by just guessing or by means
7115 of brute-force attacks. It is very important, of course, to also
7116 secure the way that these identifiers are transported by the involved
7117 parties, in both requests and responses, in order to prevent network
7118 attackers from intercepting Consumer messages and having access to
7119 session IDs. The Consumer interface uses either the Hypertext
7120 Transfer Protocol (HTTP) or the Session Initiation Protocol (SIP) as
7121 the mechanism for clients to connect to an MRB to request media
7122 resources. In the case where HTTP is used, any binding using the
7123 Consumer interface MUST be capable of being transacted over Transport
7124 Layer Security (TLS), as described in <a href="./rfc2818">RFC 2818</a> [<a href="./rfc2818" title="&quot;HTTP Over TLS&quot;">RFC2818</a>]. In the
7125 case where SIP is used, the same security considerations included in
7126 the Media Control Channel Framework specification apply here to
7127 protect interactions between a client requesting media resources and
7128 an MRB.
7129
7130 Should a valid session ID be compromised somehow (that is,
7131 intercepted or just guessed by a malicious user), as a further means
7132 to prevent disruption the Consumer interface also prescribes the use
7133 of a sequence number in its transactions. This sequence number is to
7134 be increased after each successful transaction, starting from a first
7135 value randomly generated by the MRB when the session is first
7136 created, and it must match in every request/response. While this
7137 adds complexity to the protocol (implementations must pay attention
7138 to those sequence numbers, since wrong values will cause "Wrong
7139 sequence number" errors and the failure of the related requests), it
7140 is an important added value for security. In fact, considering that
7141 different transactions related to the same session could be
7142 transported in different, unrelated HTTP messages (or SIP INVITEs in
7143 cases where the In-line mode is being used), this sequence number
7144 protection prevents the chances of session replication or disruption,
7145 especially in cases where the session ID has been compromised: that
7146 is, it should make it harder for malicious users to manipulate or
7147 remove a session for which they have obtained the session ID. It is
7148 strongly advised that the MRB doesn't choose 1 as the first sequence
7149 number for a new session but rather picks a random value to start
7150 from. The reaction to transactions that are out of sequence is left
7151 to MRB implementations: a related error code is available, but
7152 implementations may decide to enforce further limitations or actions
7153 upon the receipt of too many failed attempts in a row or of what
7154 looks like blatant attempts to guess what the current, valid sequence
7155 number is.
7156
7157 It is also worth noting that in In-line mode (both IAMM and IUMM) the
7158 MRB may act as a Back-to-Back User Agent (B2BUA). This means that
7159 when acting as a B2BUA the MRB may modify SIP bodies: it is the case,
7160 for instance, for the IAMM handling multipart/mixed payloads. This
7161
7162
7163
7164 <span class="grey">Boulton, et al. Standards Track [Page 128]</span></pre>
7165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-129" ></span>
7166 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
7167
7168
7169 impacts the ability to use any SIP security feature that protects the
7170 body (e.g., <a href="./rfc4474">RFC 4474</a> [<a href="./rfc4474" title="&quot;Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)&quot;">RFC4474</a>], S/MIME, etc.), unless the MRB acts as
7171 a mediator for the security association. This should be taken into
7172 account when implementing an MRB compliant with this specification.
7173
7174 Both the Publishing interface and Consumer interface may address the
7175 location of a Media Server: the Publishing interface may be used to
7176 inform the MRB where a Media Server is located (approximately or
7177 precisely), and the Consumer interface may be used to ask for a Media
7178 Server located somewhere in a particular region (e.g., a conference
7179 bridge close to San Francisco). Both Media Server and MRB
7180 implementers need to take this into account when deciding whether or
7181 not to make this location information available, and if so how many
7182 bits of information really need to be made available for brokering
7183 purposes.
7184
7185 It is worthwhile to cover authorization issues related to this
7186 specification. Neither the Publishing interface nor the Consumer
7187 interface provides an explicit means for implementing authentication,
7188 i.e., they do not contain specific protocol interactions to ensure
7189 that authorized Application Servers can make use of the services
7190 provided by an MRB instance. Considering that both interfaces are
7191 transported using well-established protocols (HTTP, SIP, CFW),
7192 support for such functionality can be expressed by means of the
7193 authentication mechanisms provided by the protocols themselves.
7194 Therefore, any MRB-aware entity (Application Servers, Media Servers,
7195 MRBs themselves) MUST support HTTP and SIP Digest access
7196 authentication. The usage of such Digest access authentications is
7197 recommended and not mandatory, which means MRB-aware entities MAY
7198 exploit it in deployment.
7199
7200 An MRB may want to enforce further constraints on the interactions
7201 between an Application Server/Media Server and an MRB. For example,
7202 it may choose to only accept requests associated with a specific
7203 session ID from the IP address that originated the first request or
7204 may just make use of pre-shared certificates to assess the identity
7205 of legitimate Application Servers and/or Media Servers.
7206
7207
7208
7209
7210
7211
7212
7213
7214
7215
7216
7217
7218
7219
7220 <span class="grey">Boulton, et al. Standards Track [Page 129]</span></pre>
7221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-130" ></span>
7222 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
7223
7224
7225 <span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. IANA Considerations</span>
7226
7227 There are several IANA considerations associated with this
7228 specification.
7229
7230 <span class="h3"><a class="selflink" id="section-13.1" href="#section-13.1">13.1</a>. Media Control Channel Framework Package Registration</span>
7231
7232 This section registers a new Media Control Channel Framework package,
7233 per the instructions in <a href="./rfc6230#section-13.1">Section&nbsp;13.1 of [RFC6230]</a>.
7234
7235 Package Name: mrb-publish/1.0
7236
7237 Published Specification(s): <a href="./rfc6917">RFC 6917</a>
7238
7239 Person and email address to contact for further information: IETF
7240 MediaCtrl working group ([email protected]), Chris Boulton
7241 ([email protected]).
7242
7243 <span class="h3"><a class="selflink" id="section-13.2" href="#section-13.2">13.2</a>. application/mrb-publish+xml Media Type</span>
7244
7245 To: application
7246
7247 Subject: Registration of media type application/mrb-publish+xml
7248
7249 Type name: application
7250
7251 Subtype name: mrb-publish+xml
7252
7253 Required parameters: none
7254
7255 Optional parameters: Same as charset parameter of application/xml as
7256 specified in <a href="./rfc3023">RFC 3023</a> [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>].
7257
7258 Encoding considerations: Same as encoding considerations of
7259 application/xml as specified in <a href="./rfc3023">RFC 3023</a> [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>].
7260
7261 Security considerations: See <a href="./rfc3023#section-10">Section&nbsp;10 of RFC 3023</a> [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>] and
7262 <a href="./rfc6917#section-12">Section&nbsp;12 of RFC 6917</a>.
7263
7264 Interoperability considerations: none.
7265
7266 Published specification: <a href="./rfc6917#section-10">Section&nbsp;10 of RFC 6917</a>.
7267
7268 Applications that use this media type: This media type is used to
7269 support a Media Resource Broker (MRB) entity.
7270
7271
7272
7273
7274
7275
7276 <span class="grey">Boulton, et al. Standards Track [Page 130]</span></pre>
7277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-131" ></span>
7278 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
7279
7280
7281 Additional Information:
7282
7283 Magic Number: None
7284
7285 File Extension: .xdf
7286
7287 Macintosh file type code: "TEXT"
7288
7289 Person and email address to contact for further information: Chris
7290 Boulton ([email protected]).
7291
7292 Intended usage: COMMON
7293
7294 Author/Change controller: The IETF.
7295
7296 <span class="h3"><a class="selflink" id="section-13.3" href="#section-13.3">13.3</a>. application/mrb-consumer+xml Media Type</span>
7297
7298 To: application
7299
7300 Subject: Registration of media type application/mrb-consumer+xml
7301
7302 Type name: application
7303
7304 Subtype name: mrb-consumer+xml
7305
7306 Mandatory parameters: none
7307
7308 Optional parameters: Same as charset parameter of application/xml as
7309 specified in <a href="./rfc3023">RFC 3023</a> [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>].
7310
7311 Encoding considerations: Same as encoding considerations of
7312 application/xml as specified in <a href="./rfc3023">RFC 3023</a> [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>].
7313
7314 Security considerations: See <a href="./rfc3023#section-10">Section&nbsp;10 of RFC 3023</a> [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>] and
7315 <a href="./rfc6917#section-12">Section&nbsp;12 of RFC 6917</a>.
7316
7317 Interoperability considerations: none.
7318
7319 Published specification: <a href="./rfc6917#section-11">Section&nbsp;11 of RFC 6917</a>.
7320
7321 Applications that use this media type: This media type is used to
7322 support a Media Resource Broker (MRB) entity.
7323
7324
7325
7326
7327
7328
7329
7330
7331
7332 <span class="grey">Boulton, et al. Standards Track [Page 131]</span></pre>
7333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-132" ></span>
7334 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
7335
7336
7337 Additional Information:
7338
7339 Magic Number: None
7340
7341 File Extension: .xdf
7342
7343 Macintosh file type code: "TEXT"
7344
7345 Person and email address to contact for further information: Chris
7346 Boulton ([email protected]).
7347
7348 Intended usage: COMMON
7349
7350 Author/Change controller: The IETF.
7351
7352 <span class="h3"><a class="selflink" id="section-13.4" href="#section-13.4">13.4</a>. URN Sub-Namespace Registration for mrb-publish</span>
7353
7354 IANA has registered the URN "urn:ietf:params:xml:ns:mrb-publish",
7355 with the ID of "mrb-publish". The schema of the XML namespace named
7356 urn:ietf:params:xml:ns:mrb-publish is in <a href="#section-10">Section 10</a>.
7357
7358 <span class="h3"><a class="selflink" id="section-13.5" href="#section-13.5">13.5</a>. URN Sub-Namespace Registration for mrb-consumer</span>
7359
7360 IANA has registered the URN "urn:ietf:params:xml:ns:mrb-consumer",
7361 with the ID of "mrb-consumer". The schema of the XML namespace named
7362 urn:ietf:params:xml:ns:mrb-consumer is in <a href="#section-11">Section 11</a>.
7363
7364 <span class="h3"><a class="selflink" id="section-13.6" href="#section-13.6">13.6</a>. XML Schema Registration for mrb-publish</span>
7365
7366 IANA has registered the schema for mrb-publish:
7367
7368 URI: urn:ietf:params:xml:schema:mrb-publish
7369
7370 ID: mrb-publish
7371
7372 Filename: mrb-publish
7373
7374 Registrant Contact: IETF MediaCtrl working group
7375 ([email protected])
7376
7377 Schema: The XML for the schema is in <a href="#section-10">Section 10</a> of this document.
7378
7379
7380
7381
7382
7383
7384
7385
7386
7387
7388 <span class="grey">Boulton, et al. Standards Track [Page 132]</span></pre>
7389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-133" ></span>
7390 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
7391
7392
7393 <span class="h3"><a class="selflink" id="section-13.7" href="#section-13.7">13.7</a>. XML Schema Registration for mrb-consumer</span>
7394
7395 Please register the schema for mrb-consumer:
7396
7397 URI: urn:ietf:params:xml:schema:mrb-consumer
7398
7399 ID: mrb-consumer
7400
7401 Filename: mrb-consumer
7402
7403 Registrant Contact: IETF MediaCtrl working group
7404 ([email protected])
7405
7406 Schema: The XML for the schema is in <a href="#section-11">Section 11</a> of this document.
7407
7408 <span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. Acknowledgements</span>
7409
7410 The authors would like to thank the members of the Publish Interface
7411 design team, who provided valuable input into this document. The
7412 design team consisted of Adnan Saleem, Michael Trank, Victor
7413 Paulsamy, Martin Dolly, and Scott McGlashan. The authors would also
7414 like to thank John Dally, Bob Epley, Simon Romano, Henry Lum,
7415 Christian Groves, and Jonathan Lennox for input into this
7416 specification.
7417
7418 Ben Campbell carried out the RAI expert review on an early version of
7419 this specification and provided a great deal of invaluable input.
7420
7421 <span class="h2"><a class="selflink" id="section-15" href="#section-15">15</a>. References</span>
7422
7423 <span class="h3"><a class="selflink" id="section-15.1" href="#section-15.1">15.1</a>. Normative References</span>
7424
7425 [<a id="ref-ISO.10646.2012">ISO.10646.2012</a>]
7426 International Organization for Standardization,
7427 "Information technology -- Universal Coded Character Set
7428 (UCS)", ISO Standard 10646, 2012.
7429
7430 [<a id="ref-ISO.3166-1">ISO.3166-1</a>]
7431 International Organization for Standardization, "Codes for
7432 the representation of names of countries and their
7433 subdivisions - Part 1: Country codes", ISO Standard
7434 3166-1:2006, 2006.
7435
7436 [<a id="ref-ISO.639.2002">ISO.639.2002</a>]
7437 International Organization for Standardization, "Codes for
7438 the representation of names of languages -- Part 1:
7439 Alpha-2 code", ISO Standard 639, 2002.
7440
7441
7442
7443
7444 <span class="grey">Boulton, et al. Standards Track [Page 133]</span></pre>
7445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-134" ></span>
7446 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
7447
7448
7449 [<a id="ref-ITU-T.Q.1950">ITU-T.Q.1950</a>]
7450 International Telecommunication Union, "Bearer independent
7451 call bearer control protocol", ITU-T Recommendation
7452 Q.1950, December 2002.
7453
7454 [<a id="ref-RFC2046">RFC2046</a>] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
7455 Extensions (MIME) Part Two: Media Types", <a href="./rfc2046">RFC 2046</a>,
7456 November 1996.
7457
7458 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
7459 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
7460
7461 [<a id="ref-RFC2616">RFC2616</a>] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
7462 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
7463 Transfer Protocol -- HTTP/1.1", <a href="./rfc2616">RFC 2616</a>, June 1999.
7464
7465 [<a id="ref-RFC3023">RFC3023</a>] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
7466 Types", <a href="./rfc3023">RFC 3023</a>, January 2001.
7467
7468 [<a id="ref-RFC3261">RFC3261</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
7469 A., Peterson, J., Sparks, R., Handley, M., and E.
7470 Schooler, "SIP: Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>,
7471 June 2002.
7472
7473 [<a id="ref-RFC3311">RFC3311</a>] Rosenberg, J., "The Session Initiation Protocol (SIP)
7474 UPDATE Method", <a href="./rfc3311">RFC 3311</a>, October 2002.
7475
7476 [<a id="ref-RFC3711">RFC3711</a>] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
7477 Norrman, "The Secure Real-time Transport Protocol (SRTP)",
7478 <a href="./rfc3711">RFC 3711</a>, March 2004.
7479
7480 [<a id="ref-RFC5139">RFC5139</a>] Thomson, M. and J. Winterbottom, "Revised Civic Location
7481 Format for Presence Information Data Format Location
7482 Object (PIDF-LO)", <a href="./rfc5139">RFC 5139</a>, February 2008.
7483
7484 [<a id="ref-RFC5763">RFC5763</a>] Fischl, J., Tschofenig, H., and E. Rescorla, "Framework
7485 for Establishing a Secure Real-time Transport Protocol
7486 (SRTP) Security Context Using Datagram Transport Layer
7487 Security (DTLS)", <a href="./rfc5763">RFC 5763</a>, May 2010.
7488
7489 [<a id="ref-W3C.REC-xmlschema-1-20041028">W3C.REC-xmlschema-1-20041028</a>]
7490 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn,
7491 "XML Schema Part 1: Structures Second Edition", World Wide
7492 Web Consortium Recommendation REC-xmlschema-1-20041028,
7493 October 2004,
7494 &lt;<a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028">http://www.w3.org/TR/2004/REC-xmlschema-1-20041028</a>&gt;.
7495
7496
7497
7498
7499
7500 <span class="grey">Boulton, et al. Standards Track [Page 134]</span></pre>
7501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-135" ></span>
7502 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
7503
7504
7505 [<a id="ref-W3C.REC-xmlschema-2-20041028">W3C.REC-xmlschema-2-20041028</a>]
7506 Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes
7507 Second Edition", World Wide Web Consortium
7508 Recommendation REC-xmlschema-2-20041028, October 2004,
7509 &lt;<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028">http://www.w3.org/TR/2004/REC-xmlschema-2-20041028</a>&gt;.
7510
7511 <span class="h3"><a class="selflink" id="section-15.2" href="#section-15.2">15.2</a>. Informative References</span>
7512
7513 [<a id="ref-RFC2818">RFC2818</a>] Rescorla, E., "HTTP Over TLS", <a href="./rfc2818">RFC 2818</a>, May 2000.
7514
7515 [<a id="ref-RFC4240">RFC4240</a>] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network
7516 Media Services with SIP", <a href="./rfc4240">RFC 4240</a>, December 2005.
7517
7518 [<a id="ref-RFC4474">RFC4474</a>] Peterson, J. and C. Jennings, "Enhancements for
7519 Authenticated Identity Management in the Session
7520 Initiation Protocol (SIP)", <a href="./rfc4474">RFC 4474</a>, August 2006.
7521
7522 [<a id="ref-RFC4733">RFC4733</a>] Schulzrinne, H. and T. Taylor, "RTP Payload for DTMF
7523 Digits, Telephony Tones, and Telephony Signals", <a href="./rfc4733">RFC 4733</a>,
7524 December 2006.
7525
7526 [<a id="ref-RFC5022">RFC5022</a>] Van Dyke, J., Burger, E., and A. Spitzer, "Media Server
7527 Control Markup Language (MSCML) and Protocol", <a href="./rfc5022">RFC 5022</a>,
7528 September 2007.
7529
7530 [<a id="ref-RFC5167">RFC5167</a>] Dolly, M. and R. Even, "Media Server Control Protocol
7531 Requirements", <a href="./rfc5167">RFC 5167</a>, March 2008.
7532
7533 [<a id="ref-RFC5552">RFC5552</a>] Burke, D. and M. Scott, "SIP Interface to VoiceXML Media
7534 Services", <a href="./rfc5552">RFC 5552</a>, May 2009.
7535
7536 [<a id="ref-RFC5567">RFC5567</a>] Melanchuk, T., "An Architectural Framework for Media
7537 Server Control", <a href="./rfc5567">RFC 5567</a>, June 2009.
7538
7539 [<a id="ref-RFC5707">RFC5707</a>] Saleem, A., Xin, Y., and G. Sharratt, "Media Server Markup
7540 Language (MSML)", <a href="./rfc5707">RFC 5707</a>, February 2010.
7541
7542 [<a id="ref-RFC6230">RFC6230</a>] Boulton, C., Melanchuk, T., and S. McGlashan, "Media
7543 Control Channel Framework", <a href="./rfc6230">RFC 6230</a>, May 2011.
7544
7545 [<a id="ref-RFC6231">RFC6231</a>] McGlashan, S., Melanchuk, T., and C. Boulton, "An
7546 Interactive Voice Response (IVR) Control Package for the
7547 Media Control Channel Framework", <a href="./rfc6231">RFC 6231</a>, May 2011.
7548
7549 [<a id="ref-RFC6381">RFC6381</a>] Gellens, R., Singer, D., and P. Frojdh, "The 'Codecs' and
7550 'Profiles' Parameters for "Bucket" Media Types", <a href="./rfc6381">RFC 6381</a>,
7551 August 2011.
7552
7553
7554
7555
7556 <span class="grey">Boulton, et al. Standards Track [Page 135]</span></pre>
7557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-136" ></span>
7558 <span class="grey"><a href="./rfc6917">RFC 6917</a> Media Resource Brokering April 2013</span>
7559
7560
7561 [<a id="ref-RFC6501">RFC6501</a>] Novo, O., Camarillo, G., Morgan, D., and J. Urpalainen,
7562 "Conference Information Data Model for Centralized
7563 Conferencing (XCON)", <a href="./rfc6501">RFC 6501</a>, March 2012.
7564
7565 [<a id="ref-RFC6505">RFC6505</a>] McGlashan, S., Melanchuk, T., and C. Boulton, "A Mixer
7566 Control Package for the Media Control Channel Framework",
7567 <a href="./rfc6505">RFC 6505</a>, March 2012.
7568
7569 Authors' Addresses
7570
7571 Chris Boulton
7572 NS-Technologies
7573
7574 EMail: [email protected]
7575
7576
7577 Lorenzo Miniero
7578 Meetecho
7579 Via Carlo Poerio 89
7580 Napoli 80100
7581 Italy
7582
7583 EMail: [email protected]
7584
7585
7586 Gary Munson
7587 AT&amp;T
7588 200 Laurel Avenue South
7589 Middletown, New Jersey 07748
7590 USA
7591
7592 EMail: [email protected]
7593
7594
7595
7596
7597
7598
7599
7600
7601
7602
7603
7604
7605
7606
7607
7608
7609
7610
7611
7612 Boulton, et al. Standards Track [Page 136]
7613 </pre>