draft-ietf-mediactrl-mixer-control-package-04.txt   draft-ietf-mediactrl-mixer-control-package-05.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 31, 2009 Rain Willow Communications Expires: August 24, 2009 Rain Willow Communications
C. Boulton C. Boulton
Avaya NS-Technologies
January 27, 2009 February 20, 2009
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-04 draft-ietf-mediactrl-mixer-control-package-05
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 31, 2009. This Internet-Draft will expire on August 24, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 57, line 30 skipping to change at page 57, line 30
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="urn:ietf:params:xml:ns:msc-mixer" <xsd:schema targetNamespace="urn:ietf:params:xml:ns:msc-mixer"
xmlns:fw="urn:ietf:params:xml:ns:control:framework-attributes" xmlns:fw="urn:ietf:params:xml:ns:control:framework-attributes"
elementFormDefault="qualified" elementFormDefault="qualified"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="urn:ietf:params:xml:ns:msc-mixer" xmlns="urn:ietf:params:xml:ns:msc-mixer"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:annotation> <xsd:annotation>
<xsd:documentation> <xsd:documentation>
IETF MediaCtrl Mixer 1.0 (20081103) IETF MediaCtrl Mixer 1.0 (20090220)
This is the schema of the Mixer control package. It This is the schema of the Mixer control package. It
defines request, response and notification elements for defines request, response and notification elements for
mixing. mixing.
The schema namespace is urn:ietf:params:xml:ns:msc-mixer The schema namespace is urn:ietf:params:xml:ns:msc-mixer
</xsd:documentation> </xsd:documentation>
</xsd:annotation> </xsd:annotation>
skipping to change at page 58, line 24 skipping to change at page 58, line 24
##################################################### #####################################################
Extensible core type Extensible core type
##################################################### #####################################################
--> -->
<xsd:complexType name="Tcore"> <xsd:complexType name="Tcore">
<xsd:annotation> <xsd:annotation>
<xsd:documentation> <xsd:documentation>
This type is extended by other component types to This type is extended by other (non-mixed) component types to
allow elements and attributes from other namespaces allow attributes from other namespaces.
to be added.
</xsd:documentation> </xsd:documentation>
</xsd:annotation> </xsd:annotation>
<xsd:sequence> <xsd:sequence/>
<xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" />
</xsd:sequence>
<xsd:anyAttribute namespace="##other" processContents="lax" /> <xsd:anyAttribute namespace="##other" processContents="lax" />
</xsd:complexType> </xsd:complexType>
<!-- <!--
##################################################### #####################################################
TOP LEVEL ELEMENT: mscmixer TOP LEVEL ELEMENT: mscmixer
##################################################### #####################################################
--> -->
skipping to change at page 60, line 46 skipping to change at page 60, line 42
use="required" /> use="required" />
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="modifyconference" type="modifyconferenceType" /> <xsd:element name="modifyconference" type="modifyconferenceType" />
<!-- destroyconference --> <!-- destroyconference -->
<xsd:complexType name="destroyconferenceType"> <xsd:complexType name="destroyconferenceType">
<xsd:complexContent>
<xsd:extension base="Tcore">
<xsd:sequence>
<xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" />
</xsd:sequence>
<xsd:attribute name="conferenceid" type="xsd:string" <xsd:attribute name="conferenceid" type="xsd:string"
use="required" /> use="required" />
</xsd:extension>
</xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="destroyconference" <xsd:element name="destroyconference"
type="destroyconferenceType" /> type="destroyconferenceType" />
<!-- <!--
##################################################### #####################################################
JOIN TYPES JOIN TYPES
skipping to change at page 64, line 35 skipping to change at page 64, line 41
<xsd:attribute name="reason" type="xsd:string" /> <xsd:attribute name="reason" type="xsd:string" />
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="conferenceexit" type="conferenceexitType" /> <xsd:element name="conferenceexit" type="conferenceexitType" />
<xsd:complexType name="responseType"> <xsd:complexType name="responseType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence>
<xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" />
</xsd:sequence>
<xsd:attribute name="status" type="status.datatype" <xsd:attribute name="status" type="status.datatype"
use="required" /> use="required" />
<xsd:attribute name="reason" type="xsd:string" /> <xsd:attribute name="reason" type="xsd:string" />
<xsd:attributeGroup ref="fw:framework-attributes" /> <xsd:attributeGroup ref="fw:framework-attributes" />
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="response" type="responseType" /> <xsd:element name="response" type="responseType" />
<xsd:complexType name="subscribeType"> <xsd:complexType name="subscribeType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence> <xsd:sequence>
<xsd:element ref="active-talkers-sub" <xsd:element ref="active-talkers-sub"
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:extension> </xsd:extension>
skipping to change at page 67, line 16 skipping to change at page 67, line 25
<!-- priority --> <!-- priority -->
<xsd:simpleType name="priorityType"> <xsd:simpleType name="priorityType">
<xsd:restriction base="xsd:positiveInteger" /> <xsd:restriction base="xsd:positiveInteger" />
</xsd:simpleType> </xsd:simpleType>
<xsd:element name="priority" type="priorityType" /> <xsd:element name="priority" type="priorityType" />
<xsd:complexType name="audiomixingType"> <xsd:complexType name="audiomixingType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence>
<xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" />
</xsd:sequence>
<xsd:attribute name="type" type="audiomix.datatype" <xsd:attribute name="type" type="audiomix.datatype"
default="nbest" /> default="nbest" />
<xsd:attribute name="n" type="xsd:nonNegativeInteger" <xsd:attribute name="n" type="xsd:nonNegativeInteger"
default="0" /> default="0" />
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="audio-mixing" type="audiomixingType" /> <xsd:element name="audio-mixing" type="audiomixingType" />
skipping to change at page 68, line 27 skipping to change at page 68, line 41
<!-- video-layout --> <!-- video-layout -->
<!-- doesn't extend tCore since its content model is mixed --> <!-- doesn't extend tCore since its content model is mixed -->
<xsd:complexType name="videolayoutType" mixed="true"> <xsd:complexType name="videolayoutType" mixed="true">
<xsd:sequence> <xsd:sequence>
<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="min-participants" <xsd:attribute name="min-participants"
type="xsd:positiveInteger" default="1" /> type="xsd:positiveInteger" default="1" />
<xsd:anyAttribute namespace="##other" processContents="lax" />
</xsd:complexType> </xsd:complexType>
<xsd:element name="video-layout" type="videolayoutType" /> <xsd:element name="video-layout" type="videolayoutType" />
<xsd:complexType name="auditType"> <xsd:complexType name="auditType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence>
<xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" />
</xsd:sequence>
<xsd:attribute name="capabilities" <xsd:attribute name="capabilities"
type="boolean.datatype" default="true" /> type="boolean.datatype" default="true" />
<xsd:attribute name="mixers" type="boolean.datatype" <xsd:attribute name="mixers" type="boolean.datatype"
default="true" /> default="true" />
<xsd:attribute name="conferenceid" type="xsd:string" /> <xsd:attribute name="conferenceid" type="xsd:string" />
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="audit" type="auditType" /> <xsd:element name="audit" type="auditType" />
skipping to change at page 83, line 16 skipping to change at page 83, line 16
As this control package processes XML markup, implementations MUST As this control package processes XML markup, implementations MUST
address the security considerations of [RFC3023]. address the security considerations of [RFC3023].
As a Control Package of the Media Control Channel Framework, As a Control Package of the Media Control Channel Framework,
security, confidentiality and integrity of messages transported over security, confidentiality and integrity of messages transported over
the control channel MUST be addressed as described in Section 11 of the control channel MUST be addressed as described in Section 11 of
the Media Control channel Framework the Media Control channel Framework
([I-D.ietf-mediactrl-sip-control-framework]), including Transport ([I-D.ietf-mediactrl-sip-control-framework]), including Transport
Level Protection, Control Channel Policy Management and Session Level Protection, Control Channel Policy Management and Session
Establishment. Establishment. In addition, implementations MUST address security,
confidentiality and integrity of User Agent sessions with the MS,
both in terms of SIP signaling and associated RTP media flow; see
[I-D.ietf-mediactrl-sip-control-framework] for further details on
this topic.
Adequate transport protection and authentication are critical, Adequate transport protection and authentication are critical,
especially when the implementation is deployed in open networks. If especially when the implementation is deployed in open networks. If
the implementation fails to correctly address these issues, it risks the implementation fails to correctly address these issues, it risks
exposure to malicious attacks, including (but not limited to): exposure to malicious attacks, including (but not limited to):
Denial of Service: An attacker could insert a request message into Denial of Service: An attacker could insert a request message into
the transport stream causing specific conferences or join mixers the transport stream causing specific conferences or join mixers
on the MS to be destroyed. For example, <destroyconference on the MS to be destroyed. For example, <destroyconference
conferenceid="XXXX">, where the value of "XXXX" could be guessed conferenceid="XXXX">, where the value of "XXXX" could be guessed
skipping to change at page 87, line 9 skipping to change at page 87, line 9
XML namspace: urn:ietf:params:xml:ns:msc-mixer XML namspace: urn:ietf:params:xml:ns:msc-mixer
8.3. MIME Registration 8.3. MIME Registration
Mime type: application/msc-mixer+xml Mime type: application/msc-mixer+xml
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 -05 and -05 versions.
o Schema: Fixed problem with non-deterministic content models.
o 7. Security Considerations: Added requirement that
implementations need to secure SIP and RTP sessions with User
Agents.
The following are the changes between the -04 and -03 versions. The following are the changes between the -04 and -03 versions.
o 4.2.1.4.3: corrected typo o 4.2.1.4.3: corrected typo
o 4.2.2.3: Clarified the behavior of <modifyjoin> for cases where o 4.2.2.3: Clarified the behavior of <modifyjoin> for cases where
each direction of a stream is independently controlled. each direction of a stream is independently controlled.
o 4.2.2.5: Corrected syntax error in examples. o 4.2.2.5: Corrected syntax error in examples.
o 4.2.2.5.1: Clarified that when an audio stream is in the muted o 4.2.2.5.1: Clarified that when an audio stream is in the muted
skipping to change at page 95, line 12 skipping to change at page 95, line 12
Shawn Emery carried out a thorough security review. Shawn Emery carried out a thorough security review.
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-08 (work in draft-ietf-mediactrl-sip-control-framework-09 (work in
progress), December 2008. progress), February 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.
[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.
skipping to change at page 95, line 45 skipping to change at page 95, line 45
October 2008. October 2008.
[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-07 (work in Markup Language (MSML)", draft-saleem-msml-08 (work in
progress), August 2008. progress), February 2009.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. June 2002.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, July 2003. Applications", STD 64, RFC 3550, July 2003.
skipping to change at page 97, line 20 skipping to change at page 97, line 20
SE-16985 Stockholm, Sweden SE-16985 Stockholm, Sweden
Email: scott.mcglashan@hp.com Email: scott.mcglashan@hp.com
Tim Melanchuk Tim Melanchuk
Rain Willow Communications Rain Willow Communications
Email: tim.melanchuk@gmail.com Email: tim.melanchuk@gmail.com
Chris Boulton Chris Boulton
Avaya NS-Technologies
Building 3
Wern Fawr Lane
St Mellons
Cardiff, South Wales CF3 5EA
Email: cboulton@avaya.com Email: chris@ns-technologies.com
 End of changes. 21 change blocks. 
24 lines changed or deleted 49 lines changed or added

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