draft-ietf-mediactrl-mrb-06.txt   draft-ietf-mediactrl-mrb-07.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: December 11, 2010 University of Napoli Expires: April 17, 2011 Meetecho
June 9, 2010 October 14, 2010
Media Resource Brokering Media Resource Brokering
draft-ietf-mediactrl-mrb-06 draft-ietf-mediactrl-mrb-07
Abstract Abstract
The MediaCtrl work group in the IETF has proposed an architecture for The MediaCtrl work group in the IETF has proposed an architecture for
controlling media services. The Session Initiation Protocol (SIP) is controlling media services. The Session Initiation Protocol (SIP) is
used as the signalling protocol which provides many inherent used as the signalling protocol which provides many inherent
capabilities for message routing. In addition to such signalling capabilities for message routing. In addition to such signalling
properties, a need exists for intelligent, application level media properties, a need exists for intelligent, application level media
service selection based on non-static signalling properties. This is service selection based on non-static signalling properties. This is
especially true when considered in conjunction with deployment especially true when considered in conjunction with deployment
skipping to change at page 1, line 43 skipping to change at page 1, line 43
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 11, 2010. This Internet-Draft will expire on April 17, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 9 skipping to change at page 3, line 9
9. Security Considerations . . . . . . . . . . . . . . . . . . . 109 9. Security Considerations . . . . . . . . . . . . . . . . . . . 109
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 110 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 110
10.1. Control Package Registration . . . . . . . . . . . . . . 110 10.1. Control Package Registration . . . . . . . . . . . . . . 110
10.2. application/mrb-publish+xml MIME Type . . . . . . . . . . 110 10.2. application/mrb-publish+xml MIME Type . . . . . . . . . . 110
10.3. application/mrb-consumer+xml MIME Type . . . . . . . . . 111 10.3. application/mrb-consumer+xml MIME Type . . . . . . . . . 111
10.4. URN Sub-Namespace Registration for mrb-publish . . . . . 112 10.4. URN Sub-Namespace Registration for mrb-publish . . . . . 112
10.5. URN Sub-Namespace Registration for mrb-consumer . . . . . 112 10.5. URN Sub-Namespace Registration for mrb-consumer . . . . . 112
10.6. XML Schema Registration for mrb-publish . . . . . . . . . 112 10.6. XML Schema Registration for mrb-publish . . . . . . . . . 112
10.7. XML Schema Registration for mrb-consumer . . . . . . . . 112 10.7. XML Schema Registration for mrb-consumer . . . . . . . . 112
11. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 11. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
11.1. Changes from 04 Version . . . . . . . . . . . . . . . . . 114 11.1. Changes from 06 Version . . . . . . . . . . . . . . . . . 114
11.2. Changes from 03 Version . . . . . . . . . . . . . . . . . 114 11.2. Changes from 05 Version . . . . . . . . . . . . . . . . . 114
11.3. Changes from 02 Version . . . . . . . . . . . . . . . . . 114 11.3. Changes from 04 Version . . . . . . . . . . . . . . . . . 114
11.4. Changes from 01 Version . . . . . . . . . . . . . . . . . 115 11.4. Changes from 03 Version . . . . . . . . . . . . . . . . . 114
11.5. Changes from 00 Version . . . . . . . . . . . . . . . . . 115 11.5. Changes from 02 Version . . . . . . . . . . . . . . . . . 115
11.6. Changes from 01 Version . . . . . . . . . . . . . . . . . 115
11.7. Changes from 00 Version . . . . . . . . . . . . . . . . . 115
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 116 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 116
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 117 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 117
13.1. Normative References . . . . . . . . . . . . . . . . . . 117 13.1. Normative References . . . . . . . . . . . . . . . . . . 117
13.2. Informative References . . . . . . . . . . . . . . . . . 118 13.2. Informative References . . . . . . . . . . . . . . . . . 118
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 120 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 120
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.
skipping to change at page 18, line 47 skipping to change at page 18, line 47
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 frequency: Provides the frequency in seconds that the MRB wishes to
receive notifications from the MRB. The element MAY be present. receive notifications from the MS. The element MAY be present.
Please note that these two optional pieces of information provided by Please note that these two optional pieces of information provided by
the MRB only act as a suggestion: the MS MAY change the proposed 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>
skipping to change at page 54, line 19 skipping to change at page 54, line 19
</active-mix> </active-mix>
</active-mixer-sessions> </active-mixer-sessions>
<non-active-rtp-sessions> <non-active-rtp-sessions>
<rtp-codec name="audio/basic"> <rtp-codec name="audio/basic">
<decoding>50</decoding> <decoding>50</decoding>
<encoding>40</encoding> <encoding>40</encoding>
</rtp-codec> </rtp-codec>
</non-active-rtp-sessions> </non-active-rtp-sessions>
<non-active-mixer-sessions> <non-active-mixer-sessions>
<non-active-mix available="15"> <non-active-mix available="15">
<rtp-codec name="audio/basic"/> <rtp-codec name="audio/basic">
<decoding/>
<encoding/>
</rtp-codec>
</non-active-mix> </non-active-mix>
</non-active-mixer-sessions> </non-active-mixer-sessions>
<media-server-status>active</media-server-status> <media-server-status>active</media-server-status>
<supported-codecs> <supported-codecs>
<supported-codecs name="audio/basic"> <supported-codecs name="audio/basic">
<supported-codec-package name="msc-ivr/1.0"> <supported-codec-package name="msc-ivr/1.0">
<supported-actions>encoding</supported-actions> <supported-actions>encoding</supported-actions>
<supported-actions>decoding</supported-actions> <supported-actions>decoding</supported-actions>
</supported-codec-package> </supported-codec-package>
<supported-codec-package name="msc-mixer/1.0"> <supported-codec-package name="msc-mixer/1.0">
skipping to change at page 114, line 9 skipping to change at page 114, 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 8 of this document. Schema: The XML for the schema is in Section 8 of this document.
11. Changes 11. Changes
Note to RFC Editor: Please remove this whole section. Note to RFC Editor: Please remove this whole section.
11.1. Changes from 04 Version 11.1. Changes from 06 Version
o Added the missing <encoding> and <decoding> elements to the <rtp-
codec> instances, where needed.
o Fixed a few typos in the text.
11.2. Changes from 05 Version
o Clarifier that video layouts may refer to either XCON-defined
layouts or others.
o Added RFC4240 as an option for VXML support.
o Fixed a few typos in the text and in the schemas.
11.3. 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.
11.2. Changes from 03 Version 11.4. 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 114, line 48 skipping to change at page 115, line 16
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.
11.3. Changes from 02 Version 11.5. Changes from 02 Version
o Added examples in Section 6. o Added examples in Section 6.
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.
11.4. Changes from 01 Version 11.6. 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 115, line 32 skipping to change at page 115, line 47
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.
11.5. Changes from 00 Version 11.7. 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.
12. Acknowledgments 12. 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 118, line 16 skipping to change at page 118, line 16
Format for Presence Information Data Format Location Format for Presence Information Data Format Location
Object (PIDF-LO)", RFC 5139, February 2008. Object (PIDF-LO)", RFC 5139, February 2008.
[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]
Nielsen, H., Gudgin, M., Hadley, M., Moreau, J., and N. Gudgin, M., Hadley, M., Moreau, J., Mendelsohn, N., and H.
Mendelsohn, "SOAP Version 1.2 Part 1: Messaging Nielsen, "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., Moreau, J., Hadley, M., Gudgin, M., and H. Hadley, M., Mendelsohn, N., Gudgin, M., Moreau, J., and H.
Nielsen, "SOAP Version 1.2 Part 2: Adjuncts", World Wide Nielsen, "SOAP Version 1.2 Part 2: Adjuncts", World Wide
Web Consortium FirstEdition REC-soap12-part2-20030624, Web Consortium FirstEdition REC-soap12-part2-20030624,
June 2003, June 2003,
<http://www.w3.org/TR/2003/REC-soap12-part2-20030624>. <http://www.w3.org/TR/2003/REC-soap12-part2-20030624>.
13.2. Informative References 13.2. Informative References
[I-D.ietf-mediactrl-ivr-control-package] [I-D.ietf-mediactrl-ivr-control-package]
McGlashan, S., Melanchuk, T., and C. Boulton, "An McGlashan, S., Melanchuk, T., and C. Boulton, "An
Interactive Voice Response (IVR) Control Package for the Interactive Voice Response (IVR) Control Package for the
Media Control Channel Framework", Media Control Channel Framework",
draft-ietf-mediactrl-ivr-control-package-08 (work in draft-ietf-mediactrl-ivr-control-package-08 (work in
progress), February 2010. progress), February 2010.
[I-D.ietf-mediactrl-sip-control-framework] [I-D.ietf-mediactrl-sip-control-framework]
Boulton, C., Melanchuk, T., and S. McGlashan, "Media Boulton, C., Melanchuk, T., and S. McGlashan, "Media
Control Channel Framework", Control Channel Framework",
draft-ietf-mediactrl-sip-control-framework-11 (work in draft-ietf-mediactrl-sip-control-framework-12 (work in
progress), October 2009. progress), September 2010.
[RFC4240] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network [RFC4240] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network
Media Services with SIP", RFC 4240, December 2005. Media Services with SIP", RFC 4240, December 2005.
[RFC4281] Gellens, R., Singer, D., and P. Frojdh, "The Codecs [RFC4281] Gellens, R., Singer, D., and P. Frojdh, "The Codecs
Parameter for "Bucket" Media Types", RFC 4281, Parameter for "Bucket" Media Types", RFC 4281,
November 2005. November 2005.
[RFC4733] Schulzrinne, H. and T. Taylor, "RTP Payload for DTMF [RFC4733] Schulzrinne, H. and T. Taylor, "RTP Payload for DTMF
Digits, Telephony Tones, and Telephony Signals", RFC 4733, Digits, Telephony Tones, and Telephony Signals", RFC 4733,
skipping to change at page 120, line 13 skipping to change at page 120, line 13
Server Control", RFC 5567, June 2009. Server Control", RFC 5567, June 2009.
Authors' Addresses Authors' Addresses
Chris Boulton Chris Boulton
NS-Technologies NS-Technologies
Email: chris@ns-technologies.com Email: chris@ns-technologies.com
Lorenzo Miniero Lorenzo Miniero
University of Napoli Meetecho
Via Carlo Poerio 89
Napoli 80100
Italy
Email: lorenzo.miniero@unina.it Email: lorenzo@meetecho.com
 End of changes. 16 change blocks. 
24 lines changed or deleted 48 lines changed or added

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