draft-ietf-mediactrl-mrb-08.txt   draft-ietf-mediactrl-mrb-09.txt 
Network Working Group C. Boulton Network Working Group C. Boulton
Internet-Draft NS-Technologies Internet-Draft NS-Technologies
Intended status: Standards Track L. Miniero Intended status: Standards Track L. Miniero
Expires: October 15, 2011 Meetecho Expires: November 24, 2011 Meetecho
G. Munson G. Munson
AT&T AT&T
April 13, 2011 May 23, 2011
Media Resource Brokering Media Resource Brokering
draft-ietf-mediactrl-mrb-08 draft-ietf-mediactrl-mrb-09
Abstract Abstract
The MediaCtrl work group in the IETF has proposed an architecture for The MediaCtrl work group in the IETF has proposed an architecture for
controlling media services. The Session Initiation Protocol (SIP) is controlling media services. The Session Initiation Protocol (SIP) is
used as the signalling protocol which provides many inherent used as the signalling protocol which provides many inherent
capabilities for message routing. In addition to such signalling capabilities for message routing. In addition to such signalling
properties, a need exists for intelligent, application level media properties, a need exists for intelligent, application level media
service selection based on non-static signalling properties. This is service selection based on non-static signalling properties. This is
especially true when considered in conjunction with deployment especially true when considered in conjunction with deployment
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 15, 2011. This Internet-Draft will expire on November 24, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 31 skipping to change at page 2, line 31
4. Deployment Scenario Options . . . . . . . . . . . . . . . . . 9 4. Deployment Scenario Options . . . . . . . . . . . . . . . . . 9
4.1. Query MRB . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1. Query MRB . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.1. Hybrid Query MRB . . . . . . . . . . . . . . . . . . 10 4.1.1. Hybrid Query MRB . . . . . . . . . . . . . . . . . . 10
4.2. In-Line MRB . . . . . . . . . . . . . . . . . . . . . . . 11 4.2. In-Line MRB . . . . . . . . . . . . . . . . . . . . . . . 11
5. MRB Interface Definitions . . . . . . . . . . . . . . . . . . 14 5. MRB Interface Definitions . . . . . . . . . . . . . . . . . . 14
5.1. Media Server Resource Publish Interface . . . . . . . . . 14 5.1. Media Server Resource Publish Interface . . . . . . . . . 14
5.1.1. Control Package Definition . . . . . . . . . . . . . 15 5.1.1. Control Package Definition . . . . . . . . . . . . . 15
5.1.2. Element Definitions . . . . . . . . . . . . . . . . . 17 5.1.2. Element Definitions . . . . . . . . . . . . . . . . . 17
5.1.3. <mrbrequest> . . . . . . . . . . . . . . . . . . . . 17 5.1.3. <mrbrequest> . . . . . . . . . . . . . . . . . . . . 17
5.1.4. <mrbnotification> . . . . . . . . . . . . . . . . . . 19 5.1.4. <mrbnotification> . . . . . . . . . . . . . . . . . . 19
5.1.5. <mrbresponse> . . . . . . . . . . . . . . . . . . . . 28 5.1.5. <mrbresponse> . . . . . . . . . . . . . . . . . . . . 29
5.2. Media Service Resource Consumer Interface . . . . . . . . 30 5.2. Media Service Resource Consumer Interface . . . . . . . . 30
5.2.1. Query Mode / HTTP Consumer Interface Usage . . . . . 30 5.2.1. Query Mode / HTTP Consumer Interface Usage . . . . . 31
5.2.2. In-Line Aware Mode / SIP Consumer Interface Usage . . 31 5.2.2. In-Line Aware Mode / SIP Consumer Interface Usage . . 32
5.2.3. Consumer Interface Lease Mechanism . . . . . . . . . 33 5.2.3. Consumer Interface Lease Mechanism . . . . . . . . . 34
5.2.4. Media Service Resource Request . . . . . . . . . . . 36 5.2.4. Media Service Resource Request . . . . . . . . . . . 36
5.2.5. Media Service Resource Response . . . . . . . . . . . 48 5.2.5. Media Service Resource Response . . . . . . . . . . . 48
5.3. In-Line Unaware MRB Interface . . . . . . . . . . . . . . 50 5.3. In-Line Unaware MRB Interface . . . . . . . . . . . . . . 50
6. MRB acting as a B2BUA . . . . . . . . . . . . . . . . . . . . 52 6. MRB acting as a B2BUA . . . . . . . . . . . . . . . . . . . . 52
7. Multi-modal MRB Implementations . . . . . . . . . . . . . . . 53 7. Multi-modal MRB Implementations . . . . . . . . . . . . . . . 53
8. Relative Merits of Query Mode, IAMM, and IUMM . . . . . . . . 54 8. Relative Merits of Query Mode, IAMM, and IUMM . . . . . . . . 54
9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 56 9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 56
9.1. Publish Example . . . . . . . . . . . . . . . . . . . . . 56 9.1. Publish Example . . . . . . . . . . . . . . . . . . . . . 56
9.2. Consumer Example . . . . . . . . . . . . . . . . . . . . 62 9.2. Consumer Example . . . . . . . . . . . . . . . . . . . . 62
9.2.1. Query Example . . . . . . . . . . . . . . . . . . . . 62 9.2.1. Query Example . . . . . . . . . . . . . . . . . . . . 62
9.2.2. IAMM Example . . . . . . . . . . . . . . . . . . . . 65 9.2.2. IAMM Example . . . . . . . . . . . . . . . . . . . . 65
10. Media Service Resource Publisher Interface XML Schema . . . . 80 10. Media Service Resource Publisher Interface XML Schema . . . . 81
11. Media Service Resource Consumer Interface XML Schema . . . . 102 11. Media Service Resource Consumer Interface XML Schema . . . . 103
12. Security Considerations . . . . . . . . . . . . . . . . . . . 123 12. Security Considerations . . . . . . . . . . . . . . . . . . . 124
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 124 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 125
13.1. Control Package Registration . . . . . . . . . . . . . . 124 13.1. Control Package Registration . . . . . . . . . . . . . . 125
13.2. application/mrb-publish+xml MIME Type . . . . . . . . . . 124 13.2. application/mrb-publish+xml MIME Type . . . . . . . . . . 125
13.3. application/mrb-consumer+xml MIME Type . . . . . . . . . 125 13.3. application/mrb-consumer+xml MIME Type . . . . . . . . . 126
13.4. URN Sub-Namespace Registration for mrb-publish . . . . . 126 13.4. URN Sub-Namespace Registration for mrb-publish . . . . . 127
13.5. URN Sub-Namespace Registration for mrb-consumer . . . . . 126 13.5. URN Sub-Namespace Registration for mrb-consumer . . . . . 127
13.6. XML Schema Registration for mrb-publish . . . . . . . . . 126 13.6. XML Schema Registration for mrb-publish . . . . . . . . . 127
13.7. XML Schema Registration for mrb-consumer . . . . . . . . 126 13.7. XML Schema Registration for mrb-consumer . . . . . . . . 127
14. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 14. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
14.1. Changes from 07 Version . . . . . . . . . . . . . . . . . 128 14.1. Changes from 08 Version . . . . . . . . . . . . . . . . . 129
14.2. Changes from 06 Version . . . . . . . . . . . . . . . . . 128 14.2. Changes from 07 Version . . . . . . . . . . . . . . . . . 129
14.3. Changes from 05 Version . . . . . . . . . . . . . . . . . 128 14.3. Changes from 06 Version . . . . . . . . . . . . . . . . . 129
14.4. Changes from 04 Version . . . . . . . . . . . . . . . . . 129 14.4. Changes from 05 Version . . . . . . . . . . . . . . . . . 129
14.5. Changes from 03 Version . . . . . . . . . . . . . . . . . 129 14.5. Changes from 04 Version . . . . . . . . . . . . . . . . . 130
14.6. Changes from 02 Version . . . . . . . . . . . . . . . . . 129 14.6. Changes from 03 Version . . . . . . . . . . . . . . . . . 130
14.7. Changes from 01 Version . . . . . . . . . . . . . . . . . 130 14.7. Changes from 02 Version . . . . . . . . . . . . . . . . . 130
14.8. Changes from 00 Version . . . . . . . . . . . . . . . . . 130 14.8. Changes from 01 Version . . . . . . . . . . . . . . . . . 131
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 131 14.9. Changes from 00 Version . . . . . . . . . . . . . . . . . 131
16. References . . . . . . . . . . . . . . . . . . . . . . . . . 132 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 132
16.1. Normative References . . . . . . . . . . . . . . . . . . 132 16. References . . . . . . . . . . . . . . . . . . . . . . . . . 133
16.2. Informative References . . . . . . . . . . . . . . . . . 133 16.1. Normative References . . . . . . . . . . . . . . . . . . 133
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 135 16.2. Informative References . . . . . . . . . . . . . . . . . 134
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 136
1. Introduction 1. Introduction
The topic of Media Resource management has been in discussion for a The topic of Media Resource management has been in discussion for a
number of years with varying proprietary solutions being used today. number of years with varying proprietary solutions being used today.
It is clear that, as we move towards a consistent architecture and It is clear that, as we move towards a consistent architecture and
protocol for Media Server Control, a standard mechanism is required protocol for Media Server Control, a standard mechanism is required
for accurate media resource selection. for accurate media resource selection.
As IP based multimedia infrastructures mature, the complexity and As IP based multimedia infrastructures mature, the complexity and
skipping to change at page 18, line 46 skipping to change at page 18, line 46
The attribute MUST be present. The attribute MUST be present.
The <subscription> element has the following child elements: The <subscription> element has the following child elements:
expires: Provides the amount of time in seconds that a subscription expires: Provides the amount of time in seconds that a subscription
should be installed for notifications at the Media Server. Once should be installed for notifications at the Media Server. Once
the amount of time has passed, the subscription expires and the the amount of time has passed, the subscription expires and the
MRB has to subscribe again in case it is still interested in MRB has to subscribe again in case it is still interested in
receiving notifications from the MS. The element MAY be present. receiving notifications from the MS. The element MAY be present.
frequency: Provides the frequency in seconds that the MRB wishes to minfrequency: Provides the minimum frequency in seconds that the
receive notifications from the MS. The element MAY be present. MRB wishes to receive notifications from the MS. The element MAY
be present.
Please note that these two optional pieces of information provided by maxfrequency: Provides the maximum frequency in seconds that the
the MRB only act as a suggestion: the MS MAY change the proposed MRB wishes to receive notifications from the MS. The element MAY
be present.
Please note that these three optional pieces of information provided
by the MRB only act as a suggestion: the MS MAY change the proposed
values if it considers the suggestions unacceptable (e.g., if the MRB values if it considers the suggestions unacceptable (e.g., if the MRB
has requested a too high notification frequency). In such case, the has requested a too high notification frequency). In such case, the
request would not fail, but the updated, acceptable values would be request would not fail, but the updated, acceptable values would be
reported in the <mrbresponse> accordingly. reported in the <mrbresponse> accordingly.
5.1.4. <mrbnotification> 5.1.4. <mrbnotification>
The <mrbnotification> element is included in a request from a Media The <mrbnotification> element is included in a request from a Media
Server to an MRB to provide the details relating current status. The Server to an MRB to provide the details relating current status. The
Media Server will inform the MRB of its current status as defined by Media Server will inform the MRB of its current status as defined by
skipping to change at page 30, line 19 skipping to change at page 30, line 38
<mrbresponse> with status code 401/402/403, depending on the action <mrbresponse> with status code 401/402/403, depending on the action
the MRB provided in its request: the MRB provided in its request:
o action='create' --> 401; o action='create' --> 401;
o action='update' --> 402; o action='update' --> 402;
o action='remove' --> 403; o action='remove' --> 403;
As explained in Section 5.1.3.1, even in case of an accepted As explained in Section 5.1.3.1, even in case of an accepted
subscription request the MS might change the suggested 'expires' and subscription request the MS might change the suggested 'expires',
'frequency' values provided by the MRB in its <mrbrequest>, if it 'minfrequency' and 'maxfrequency' values provided by the MRB in its
considers them unacceptable (e.g., the requested frequency is too <mrbrequest>, if it considers them unacceptable (e.g., the requested
high). In such a case, the MS MUST add an additional <subscription> frequency range is too high). In such a case, the MS MUST add an
element to the response, including the updated values, to inform the additional <subscription> element to the response, including the
MRB about the change. The MS MAY include such element if the values updated values, to inform the MRB about the change. The MS MAY
have been accepted or were omitted in the request. include such element if the values have been accepted or were omitted
in the request.
5.2. Media Service Resource Consumer Interface 5.2. Media Service Resource Consumer Interface
The Media Server Consumer interface provides the ability for clients The Media Server Consumer interface provides the ability for clients
of an MRB, such as Application Servers, to request an appropriate of an MRB, such as Application Servers, to request an appropriate
Media Server to satisfy specific criteria. The interface allows a Media Server to satisfy specific criteria. The interface allows a
client to pass detailed meta-information to the MRB to help select an client to pass detailed meta-information to the MRB to help select an
appropriate Media Server. The MRB is then able to make an informed appropriate Media Server. The MRB is then able to make an informed
decision and provide the client with an appropriate media server decision and provide the client with an appropriate media server
resource. The MRB Consumer interface includes both 1) In-Line Aware resource. The MRB Consumer interface includes both 1) In-Line Aware
skipping to change at page 58, line 7 skipping to change at page 58, line 7
CFW lidc30BZObiC CONTROL CFW lidc30BZObiC CONTROL
Control-Package: mrb-publish/1.0 Control-Package: mrb-publish/1.0
Content-Type: application/mrb-publish+xml Content-Type: application/mrb-publish+xml
Content-Length: 337 Content-Length: 337
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<mrbpublish version="1.0" xmlns="urn:ietf:params:xml:ns:mrb-publish"> <mrbpublish version="1.0" xmlns="urn:ietf:params:xml:ns:mrb-publish">
<mrbrequest> <mrbrequest>
<subscription action="create" seqnumber="1" id="p0T65U"> <subscription action="create" seqnumber="1" id="p0T65U">
<expires>600</expires> <expires>600</expires>
<frequency>20</frequency> <minfrequency>20</minfrequency>
<maxfrequency>20</maxfrequency>
</subscription> </subscription>
</mrbrequest> </mrbrequest>
</mrbpublish> </mrbpublish>
A2. MRB <- MS (200 to CONTROL, request accepted) A2. MRB <- MS (200 to CONTROL, request accepted)
------------------------------------------------ ------------------------------------------------
CFW lidc30BZObiC 200 CFW lidc30BZObiC 200
Timeout: 10 Timeout: 10
Content-Type: application/mrb-publish+xml Content-Type: application/mrb-publish+xml
Content-Length: 139 Content-Length: 139
skipping to change at page 60, line 51 skipping to change at page 61, line 4
</video-mixing-mode> </video-mixing-mode>
<video-mixing-mode package="msc-mixer/1.0"> <video-mixing-mode package="msc-mixer/1.0">
multiple-5x1 multiple-5x1
</video-mixing-mode> </video-mixing-mode>
<video-mixing-mode package="msc-mixer/1.0"> <video-mixing-mode package="msc-mixer/1.0">
multiple-3x3 multiple-3x3
</video-mixing-mode> </video-mixing-mode>
<video-mixing-mode package="msc-mixer/1.0"> <video-mixing-mode package="msc-mixer/1.0">
multiple-4x4 multiple-4x4
</video-mixing-mode> </video-mixing-mode>
</video-mixing-modes>
</video-mixing-modes>
</mixing-modes> </mixing-modes>
<supported-tones> <supported-tones>
<supported-country-codes> <supported-country-codes>
<country-code package="msc-ivr/1.0">GB</country-code> <country-code package="msc-ivr/1.0">GB</country-code>
<country-code package="msc-ivr/1.0">IT</country-code> <country-code package="msc-ivr/1.0">IT</country-code>
<country-code package="msc-ivr/1.0">US</country-code> <country-code package="msc-ivr/1.0">US</country-code>
</supported-country-codes> </supported-country-codes>
<supported-h248-codes> <supported-h248-codes>
<h248-code package="msc-ivr/1.0">cg/*</h248-code> <h248-code package="msc-ivr/1.0">cg/*</h248-code>
<h248-code package="msc-ivr/1.0">biztn/ofque</h248-code> <h248-code package="msc-ivr/1.0">biztn/ofque</h248-code>
skipping to change at page 67, line 15 skipping to change at page 67, line 15
AS MRB MS AS MRB MS
| | | | | |
| 1. INVITE | | | 1. INVITE | |
| (multipart/mixed) | | | (multipart/mixed) | |
|---------------------->| | |---------------------->| |
| 2. 100 (Trying) | | | 2. 100 (Trying) | |
|<----------------------| | |<----------------------| |
| |--+ Extract SDP and | | |--+ Extract SDP and |
| | | MRB payloads; handle | | | | MRB payloads; handle |
| |<-+ Consumer request to | | |<-+ Consumer request to |
| | know MS to use | | | pick MS |
| | | | | |
| | 3. INVITE | | | 3. INVITE |
| | (only copy SDP from 1.) | | | (only copy SDP from 1.) |
| |-------------------------->| | |-------------------------->|
| | 4. 100 (Trying) | | | 4. 100 (Trying) |
| |<--------------------------| | |<--------------------------|
| | |--+ Negotiate | | |--+ Negotiate
| | | | CFW Control | | | | CFW Control
| | |<-+ Channel | | |<-+ Channel
| | 5. 200 OK | | | 5. 200 OK |
skipping to change at page 72, line 23 skipping to change at page 72, line 23
the same as before (e.g. for what concerns the multipart body) but the same as before (e.g. for what concerns the multipart body) but
considering a new party is involved in the communication, the diagram considering a new party is involved in the communication, the diagram
is slightly more complex than before. As before, the MRB acts as a is slightly more complex than before. As before, the MRB acts as a
B2BUA. A UAC sends a SIP INVITE to a SIP URI handled by the AS, B2BUA. A UAC sends a SIP INVITE to a SIP URI handled by the AS,
since it is interested to its services (1.). The AS sends a since it is interested to its services (1.). The AS sends a
provisional response (2.) and, since it doesn't have the resources provisional response (2.) and, since it doesn't have the resources
yet, sends to the MRB a new SIP INVITE (3.), containing both the UAC yet, sends to the MRB a new SIP INVITE (3.), containing both the UAC
media-related SDP and a Consumer request (multipart body). The MRB media-related SDP and a Consumer request (multipart body). The MRB
sends a provisional response to the AS (4.) and starts working on the sends a provisional response to the AS (4.) and starts working on the
request. First of all, it makes use of the Consumer request from the request. First of all, it makes use of the Consumer request from the
AS to determine which MS should be exploited. Once the right MS have AS to determine which MS should be chosen. Once the right MS have
been chosen, the MRB sends a new SIP INVITE to one of the MS by just been chosen, the MRB sends a new SIP INVITE to one of the MS by just
including the SDP part of the original request (5.). The MS including the SDP part of the original request (5.). The MS
negotiates this INVITE as specified in negotiates this INVITE as specified in
[I-D.ietf-mediactrl-sip-control-framework] (6., 7., 8.) to allocate [I-D.ietf-mediactrl-sip-control-framework] (6., 7., 8.) to allocate
the needed media resources to handle the new call leg, eventually the needed media resources to handle the new call leg, eventually
providing the MRB with its own media-related SDP. The MRB replies to providing the MRB with its own media-related SDP. The MRB replies to
the original AS INVITE preparing a SIP 200 OK with another multipart the original AS INVITE preparing a SIP 200 OK with another multipart
body (9.): this multipart body includes the Consumer response used by body (9.): this multipart body includes the Consumer response from
the MRB to determine the right MS and the SDP returned by the MS in the MRB indicating the chosen MS and the SDP returned by the MS in 7.
7. The AS finally acknowledges the 200 OK (10.), and ends the The AS finally acknowledges the 200 OK (10.), and ends the scenario
scenario by eventually providing the UAC with the SDP it needs to by eventually providing the UAC with the SDP it needs to setup the
setup the RTP channels with the chosen MS: a separate direct SIP RTP channels with the chosen MS: a separate direct SIP control dialog
control dialog may be initiated by the AS to the same MS in order to may be initiated by the AS to the same MS in order to set up a
set up a control channel to manipulate the call leg media. control channel to manipulate the call leg media.
As with the IAMM - CFW example in the prior section, this example has
the MRB selecting MS resources across two MS instances. And here
again the convention can be that the MRB sent the SIP INVITE to the
first MS in the list provided to the AS in the Consumer response
information.
Please note that, to ease the reading of the protocol contents, a Please note that, to ease the reading of the protocol contents, a
simple '=_Part' is used whenever a boundary for a 'multipart/mixed' simple '=_Part' is used whenever a boundary for a 'multipart/mixed'
payload is provided, instead of the actual boundary that would be payload is provided, instead of the actual boundary that would be
inserted in the SIP messages. inserted in the SIP messages.
UAC AS MRB MS UAC AS MRB MS
| | | | | | | |
| 1. INVITE | | | | 1. INVITE | | |
| (media SDP) | | | | (media SDP) | | |
skipping to change at page 83, line 10 skipping to change at page 84, line 10
<xsd:element name="mrbrequest" type="mrbrequestType" /> <xsd:element name="mrbrequest" type="mrbrequestType" />
<!-- subscription --> <!-- subscription -->
<xsd:complexType name="subscriptionType"> <xsd:complexType name="subscriptionType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence> <xsd:sequence>
<xsd:element name="expires" type="xsd:nonNegativeInteger" <xsd:element name="expires" type="xsd:nonNegativeInteger"
minOccurs="0" maxOccurs="1" /> minOccurs="0" maxOccurs="1" />
<xsd:element name="frequency" type="xsd:nonNegativeInteger" <xsd:element name="minfrequency" type="xsd:nonNegativeInteger"
minOccurs="0" maxOccurs="1" />
<xsd:element name="maxfrequency" type="xsd:nonNegativeInteger"
minOccurs="0" maxOccurs="1" /> minOccurs="0" maxOccurs="1" />
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="id" type="id.datatype" use="required" /> <xsd:attribute name="id" type="id.datatype" use="required" />
<xsd:attribute name="seqnumber" type="xsd:nonNegativeInteger" <xsd:attribute name="seqnumber" type="xsd:nonNegativeInteger"
use="required" /> use="required" />
<xsd:attribute name="action" type="action.datatype" <xsd:attribute name="action" type="action.datatype"
use="required" /> use="required" />
<xsd:anyAttribute namespace="##other" processContents="lax" /> <xsd:anyAttribute namespace="##other" processContents="lax" />
skipping to change at page 128, line 9 skipping to change at page 129, line 9
Filename: mbr-consumer Filename: mbr-consumer
Registrant Contact: IETF, MEDIACTRL working group Registrant Contact: IETF, MEDIACTRL working group
(mediactrl@ietf.org) (mediactrl@ietf.org)
Schema: The XML for the schema is in Section 11 of this document. Schema: The XML for the schema is in Section 11 of this document.
14. Changes 14. Changes
Note to RFC Editor: Please remove this whole section. Note to RFC Editor: Please remove this whole section.
14.1. Changes from 07 Version 14.1. Changes from 08 Version
o Fixed Nits.
o Added range for reporting period - as per mailing list.
14.2. Changes from 07 Version
o Corrected some errors in the Consumer schema: a few elements were o Corrected some errors in the Consumer schema: a few elements were
not declared optional as they should have been, and some were not declared optional as they should have been, and some were
incorrectly defined as choices instead of sequences; incorrectly defined as choices instead of sequences;
o Corrected examples after validation tests; o Corrected examples after validation tests;
o Fixed a few typos in the text. o Fixed a few typos in the text.
o Clarified language in various places. o Clarified language in various places.
skipping to change at page 128, line 34 skipping to change at page 129, line 40
o Clarifying text related to IAMM and IUMM. o Clarifying text related to IAMM and IUMM.
o Expanded media-server-address for extra information and to allow o Expanded media-server-address for extra information and to allow
multiples. multiples.
o New B2BUA section. o New B2BUA section.
o Updated Examples. o Updated Examples.
14.2. Changes from 06 Version 14.3. Changes from 06 Version
o Added the missing <encoding> and <decoding> elements to the <rtp- o Added the missing <encoding> and <decoding> elements to the <rtp-
codec> instances, where needed. codec> instances, where needed.
o Fixed a few typos in the text. o Fixed a few typos in the text.
14.3. Changes from 05 Version 14.4. Changes from 05 Version
o Clarifier that video layouts may refer to either XCON-defined o Clarifier that video layouts may refer to either XCON-defined
layouts or others. layouts or others.
o Added RFC4240 as an option for VXML support. o Added RFC4240 as an option for VXML support.
o Fixed a few typos in the text and in the schemas. o Fixed a few typos in the text and in the schemas.
14.4. Changes from 04 Version 14.5. Changes from 04 Version
o Corrected some typos and leftovers in both 'session-info' and o Corrected some typos and leftovers in both 'session-info' and
'response-session-info' definitions. 'response-session-info' definitions.
o Clarified that 'response-session-info' is not only included in o Clarified that 'response-session-info' is not only included in
reply to updates, but also to new requests; besides, clarified reply to updates, but also to new requests; besides, clarified
that it is an optional element, in the sense that it is mandatory that it is an optional element, in the sense that it is mandatory
in successful responses (200), while not needed otherwise (any in successful responses (200), while not needed otherwise (any
error). error).
o Corrected the Query example flow which included a 'session'info' o Corrected the Query example flow which included a 'session'info'
in a new request. in a new request.
14.5. Changes from 03 Version 14.6. Changes from 03 Version
o Addressed comments per the Expert RAI Review by Ben Campbell. o Addressed comments per the Expert RAI Review by Ben Campbell.
o Several editorial changes (fixes, typos, nits). o Several editorial changes (fixes, typos, nits).
o Removed the 3xx class responses for the IAMM, per discussion in o Removed the 3xx class responses for the IAMM, per discussion in
Anaheim (feature had been added in the -02 version). Anaheim (feature had been added in the -02 version).
o Clarified that backslashes and XML indentation in the Examples are o Clarified that backslashes and XML indentation in the Examples are
only provided for readability. only provided for readability.
skipping to change at page 129, line 44 skipping to change at page 130, line 48
responses, in order to clarify when they are involved. responses, in order to clarify when they are involved.
o Added some text to better clarify the role of leasing in the o Added some text to better clarify the role of leasing in the
Consumer interface. Consumer interface.
o Added additional IANA considerations, that were missing in the o Added additional IANA considerations, that were missing in the
previous versions of the document. previous versions of the document.
o Added text to the security considerations. o Added text to the security considerations.
14.6. Changes from 02 Version 14.7. Changes from 02 Version
o Added examples in Section 9. o Added examples in Section 9.
o Fixed some nits in the schemas (encryption and required mixed=true o Fixed some nits in the schemas (encryption and required mixed=true
elements). elements).
o Completed review nit review comments from Gary Munson. o Completed review nit review comments from Gary Munson.
14.7. Changes from 01 Version 14.8. Changes from 01 Version
o Added description of lease mechanism. o Added description of lease mechanism.
o Added specific HTTP and SIP usage of Consumer interface. o Added specific HTTP and SIP usage of Consumer interface.
o Completed Publish interface schema + associated text. o Completed Publish interface schema + associated text.
o Included Consumer interface schema + associated text. o Included Consumer interface schema + associated text.
o Included supported-packages element. o Included supported-packages element.
skipping to change at page 130, line 27 skipping to change at page 131, line 32
o Removed announce-var element from doc. o Removed announce-var element from doc.
o Expanded Abstract. o Expanded Abstract.
o General scrub of text - input from Simon Romano. o General scrub of text - input from Simon Romano.
o Added IANA Considerations section. o Added IANA Considerations section.
o Added Security Considerations section. o Added Security Considerations section.
14.8. Changes from 00 Version 14.9. Changes from 00 Version
o Included In-line text based on strawman proposal. o Included In-line text based on strawman proposal.
o Included first attempt at publish interface based on design team o Included first attempt at publish interface based on design team
work. work.
15. Acknowledgments 15. Acknowledgments
The authors would like to thank the members of the Publish Interface The authors would like to thank the members of the Publish Interface
design team who provided valuable input into this document. The design team who provided valuable input into this document. The
skipping to change at page 133, line 23 skipping to change at page 134, line 23
[RFC5705] Rescorla, E., "Keying Material Exporters for Transport [RFC5705] Rescorla, E., "Keying Material Exporters for Transport
Layer Security (TLS)", RFC 5705, March 2010. Layer Security (TLS)", RFC 5705, March 2010.
[W3C.CR-wsdl20-20051215] [W3C.CR-wsdl20-20051215]
Chinnici, R., Moreau, J., Ryman, A., and S. Weerawarana, Chinnici, R., Moreau, J., Ryman, A., and S. Weerawarana,
"Web Services Description Language (WSDL) Version 2.0 Part "Web Services Description Language (WSDL) Version 2.0 Part
1: Core Language", W3C CR CR-wsdl20-20051215, 1: Core Language", W3C CR CR-wsdl20-20051215,
December 2005. December 2005.
[W3C.REC-soap12-part1-20030624] [W3C.REC-soap12-part1-20030624]
Gudgin, M., Nielsen, H., Hadley, M., Moreau, J., and N. Mendelsohn, N., Gudgin, M., Nielsen, H., Moreau, J., and
Mendelsohn, "SOAP Version 1.2 Part 1: Messaging M. Hadley, "SOAP Version 1.2 Part 1: Messaging Framework",
Framework", World Wide Web Consortium FirstEdition REC- World Wide Web Consortium FirstEdition REC-soap12-part1-
soap12-part1-20030624, June 2003, 20030624, June 2003,
<http://www.w3.org/TR/2003/REC-soap12-part1-20030624>. <http://www.w3.org/TR/2003/REC-soap12-part1-20030624>.
[W3C.REC-soap12-part2-20030624] [W3C.REC-soap12-part2-20030624]
Mendelsohn, N., Nielsen, H., Moreau, J., Hadley, M., and Mendelsohn, N., Gudgin, M., Moreau, J., Hadley, M., and H.
M. Gudgin, "SOAP Version 1.2 Part 2: Adjuncts", World Wide Nielsen, "SOAP Version 1.2 Part 2: Adjuncts", World Wide
Web Consortium FirstEdition REC-soap12-part2-20030624, Web Consortium FirstEdition REC-soap12-part2-20030624,
June 2003, June 2003,
<http://www.w3.org/TR/2003/REC-soap12-part2-20030624>. <http://www.w3.org/TR/2003/REC-soap12-part2-20030624>.
16.2. Informative References 16.2. Informative References
[I-D.ietf-mediactrl-ivr-control-package] [I-D.ietf-mediactrl-ivr-control-package]
McGlashan, S., Melanchuk, T., and C. Boulton, "An McGlashan, S., Melanchuk, T., and C. Boulton, "An
Interactive Voice Response (IVR) Control Package for the Interactive Voice Response (IVR) Control Package for the
Media Control Channel Framework", Media Control Channel Framework",
 End of changes. 27 change blocks. 
70 lines changed or deleted 92 lines changed or added

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