draft-ietf-mediactrl-mixer-control-package-09.txt   draft-ietf-mediactrl-mixer-control-package-10.txt 
Network Working Group S. McGlashan Network Working Group S. McGlashan
Internet-Draft Hewlett-Packard Internet-Draft Hewlett-Packard
Intended status: Standards Track T. Melanchuk Intended status: Standards Track T. Melanchuk
Expires: July 15, 2010 Rain Willow Communications Expires: August 1, 2010 Rain Willow Communications
C. Boulton C. Boulton
NS-Technologies NS-Technologies
January 11, 2010 January 28, 2010
A Mixer Control Package for the Media Control Channel Framework A Mixer Control Package for the Media Control Channel Framework
draft-ietf-mediactrl-mixer-control-package-09 draft-ietf-mediactrl-mixer-control-package-10
Abstract Abstract
This document defines a Media Control Channel Framework Package for This document defines a Media Control Channel Framework Package for
managing mixers for media conferences and connections. The package managing mixers for media conferences and connections. The package
defines request elements for managing conference mixers, managing defines request elements for managing conference mixers, managing
mixers between conferences and/or connections, as well as associated mixers between conferences and/or connections, as well as associated
responses and notifications. The package also defines elements for responses and notifications. The package also defines elements for
auditing package capabilities and mixers. auditing package capabilities and mixers.
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 15, 2010. This Internet-Draft will expire on August 1, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 34 skipping to change at page 4, line 34
6.2.2. Bridging connections . . . . . . . . . . . . . . . . 80 6.2.2. Bridging connections . . . . . . . . . . . . . . . . 80
6.2.3. Video conferencing . . . . . . . . . . . . . . . . . 81 6.2.3. Video conferencing . . . . . . . . . . . . . . . . . 81
7. Security Considerations . . . . . . . . . . . . . . . . . . . 83 7. Security Considerations . . . . . . . . . . . . . . . . . . . 83
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 86 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 86
8.1. Control Package Registration . . . . . . . . . . . . . . 86 8.1. Control Package Registration . . . . . . . . . . . . . . 86
8.2. URN Sub-Namespace Registration . . . . . . . . . . . . . 86 8.2. URN Sub-Namespace Registration . . . . . . . . . . . . . 86
8.3. XML Schema Registration . . . . . . . . . . . . . . . . . 87 8.3. XML Schema Registration . . . . . . . . . . . . . . . . . 87
8.4. MIME Media Type Registration for 8.4. MIME Media Type Registration for
'application/msc-mixer+xml' . . . . . . . . . . . . . . . 87 'application/msc-mixer+xml' . . . . . . . . . . . . . . . 87
9. Change Summary . . . . . . . . . . . . . . . . . . . . . . . 89 9. Change Summary . . . . . . . . . . . . . . . . . . . . . . . 89
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 96 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 97
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 97 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 98
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 98 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 99
12.1. Normative References . . . . . . . . . . . . . . . . . . 98 12.1. Normative References . . . . . . . . . . . . . . . . . . 99
12.2. Informative References . . . . . . . . . . . . . . . . . 98 12.2. Informative References . . . . . . . . . . . . . . . . . 99
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 100 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 101
1. Introduction 1. Introduction
The Media Control Channel Framework The Media Control Channel Framework
[I-D.ietf-mediactrl-sip-control-framework] provides a generic [I-D.ietf-mediactrl-sip-control-framework] provides a generic
approach for establishment and reporting capabilities of remotely approach for establishment and reporting capabilities of remotely
initiated commands. The Framework utilizes many functions provided initiated commands. The Framework utilizes many functions provided
by the Session Initiation Protocol [RFC3261] (SIP) for the rendezvous by the Session Initiation Protocol [RFC3261] (SIP) for the rendezvous
and establishment of a reliable channel for control interactions. and establishment of a reliable channel for control interactions.
The Control Framework also introduces the concept of a Control The Control Framework also introduces the concept of a Control
skipping to change at page 13, line 31 skipping to change at page 13, line 31
<unjoin> delete a media stream (for example, remove a participant <unjoin> delete a media stream (for example, remove a participant
from a conference). See Section 4.2.2.4 from a conference). See Section 4.2.2.4
Responses from the MS describe the status of the requested operation. Responses from the MS describe the status of the requested operation.
Responses are specified in a <response> element (Section 4.2.3) which Responses are specified in a <response> element (Section 4.2.3) which
includes a mandatory attribute describing the status in terms of a includes a mandatory attribute describing the status in terms of a
numeric code. Response status codes are defined in Section 4.5. The numeric code. Response status codes are defined in Section 4.5. The
MS MUST respond to a request message with a response message. If the MS MUST respond to a request message with a response message. If the
MS is not able to process the request and carry out the mixer MS is not able to process the request and carry out the mixer
operation, the request has failed and the MS MUST indicate the class operation (in whole or in part), then the request has failed: the MS
of failure using an appropriate 4xx response code. Unless an error MUST ensure that no part of the requested mixer operaton is carried
response code is specified for a class of error within this section, out, and the MS MUST indicate the class of failure using an
implementations follow Section 4.5 in determining the appropriate appropriate 4xx response code. Unless an error response code is
status code for the response. specified for a class of error within this section, implementations
follow Section 4.5 in determining the appropriate status code for the
response.
Notifications are sent from the MS to provide updates on the status Notifications are sent from the MS to provide updates on the status
of a mixer operation or subscription. Notifications are specified in of a mixer operation or subscription. Notifications are specified in
an <event> element (Section 4.2.4). an <event> element (Section 4.2.4).
4.2.1. Conference Elements 4.2.1. Conference Elements
4.2.1.1. <createconference> 4.2.1.1. <createconference>
The <createconference> element is sent to the MS to request creation The <createconference> element is sent to the MS to request creation
skipping to change at page 90, line 9 skipping to change at page 90, line 9
Person & email address to contact for further information: Scott Person & email address to contact for further information: Scott
McGlashan <smcg.stds01@mcglashan.org> McGlashan <smcg.stds01@mcglashan.org>
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author/Change controller: The IETF Author/Change controller: The IETF
Other information: None. Other information: None.
9. Change Summary 9. Change Summary
Note to RFC Editor: Please remove this whole section. Note to RFC Editor: Please remove this whole section.
The following are the changes between the -10 and -09 versions:
o References: Moved the XCON reference to the Normative References
section.
o 4.2: Mixer Elements: clarified that when a requested mixer
operation (partially) fails, the MS carries out no part of the
operation and sends an error response.
The following are the changes between the -09 and -08 versions The following are the changes between the -09 and -08 versions
following shepherd writeup: following shepherd writeup:
o 4.2.4.1.1: <active-talker>: Removed the statement that it is an o 4.2.4.1.1: <active-talker>: Removed the statement that it is an
error if an <active-talker> element has both connectionid and error if an <active-talker> element has both connectionid and
conferenceid attributes specified because the AS always sends a conferenceid attributes specified because the AS always sends a
framework 200 in response to notification events, including active framework 200 in response to notification events, including active
talker events. Instead, clarified that no active talker is talker events. Instead, clarified that no active talker is
described if both attributes are specified or if neither attribute described if both attributes are specified or if neither attribute
is specified. is specified.
skipping to change at page 99, line 15 skipping to change at page 100, line 15
12. References 12. References
12.1. Normative References 12.1. Normative References
[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-11 (work in
progress), October 2009. progress), October 2009.
[I-D.ietf-xcon-common-data-model]
Novo, O., Camarillo, G., Morgan, D., and J. Urpalainen,
"Conference Information Data Model for Centralized
Conferencing (XCON)", draft-ietf-xcon-common-data-model-14
(work in progress), November 2009.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, January 2001. Types", RFC 3023, January 2001.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC4574] Levin, O. and G. Camarillo, "The Session Description [RFC4574] Levin, O. and G. Camarillo, "The Session Description
Protocol (SDP) Label Attribute", RFC 4574, August 2006. Protocol (SDP) Label Attribute", RFC 4574, August 2006.
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C M., Maler, E., [XML] Bray, T., Paoli, J., Sperberg-McQueen, C M., Maler, E.,
and F. Yergeau, "Extensible Markup Language (XML) 1.0 and F. Yergeau, "Extensible Markup Language (XML) 1.0
(Third Edition)", W3C Recommendation, February 2004. (Third Edition)", W3C Recommendation, February 2004.
12.2. Informative References 12.2. Informative References
[I-D.ietf-xcon-common-data-model]
Novo, O., Camarillo, G., Morgan, D., and J. Urpalainen,
"Conference Information Data Model for Centralized
Conferencing (XCON)", draft-ietf-xcon-common-data-model-14
(work in progress), November 2009.
[IANA] "IANA registry for RTP Payload Types", [IANA] "IANA registry for RTP Payload Types",
<http://www.iana.org/assignments/rtp-parameters>. <http://www.iana.org/assignments/rtp-parameters>.
[MIME.mediatypes] [MIME.mediatypes]
"IANA registry for MIME Media Types", "IANA registry for MIME Media Types",
<http://www.iana.org/assignments/media-types/>. <http://www.iana.org/assignments/media-types/>.
[MSML] Saleem, A., Xin, Y., and G. Sharratt, "Media Session [MSML] Saleem, A., Xin, Y., and G. Sharratt, "Media Session
Markup Language (MSML)", draft-saleem-msml-09 (work in Markup Language (MSML)", draft-saleem-msml-09 (work in
progress), July 2009. progress), July 2009.
 End of changes. 9 change blocks. 
21 lines changed or deleted 32 lines changed or added

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