< draft-ietf-mediactrl-mixer-control-package-13.txt		draft-ietf-mediactrl-mixer-control-package-14.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 8, 2011 Rain Willow Communications		Expires: July 10, 2011 Rain Willow Communications
	C. Boulton		C. Boulton
	NS-Technologies		NS-Technologies
	January 4, 2011		January 6, 2011
	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-13		draft-ietf-mediactrl-mixer-control-package-14
	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 38 ¶		skipping to change at page 1, line 38 ¶
	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 July 8, 2011.		This Internet-Draft will expire on July 10, 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 4, line 33 ¶		skipping to change at page 4, line 33 ¶
	6.2.2. Bridging connections . . . . . . . . . . . . . . . . 82		6.2.2. Bridging connections . . . . . . . . . . . . . . . . 82
	6.2.3. Video conferencing . . . . . . . . . . . . . . . . . 83		6.2.3. Video conferencing . . . . . . . . . . . . . . . . . 83
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 85		7. Security Considerations . . . . . . . . . . . . . . . . . . . 85
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 88		8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 88
	8.1. Control Package Registration . . . . . . . . . . . . . . 88		8.1. Control Package Registration . . . . . . . . . . . . . . 88
	8.2. URN Sub-Namespace Registration . . . . . . . . . . . . . 88		8.2. URN Sub-Namespace Registration . . . . . . . . . . . . . 88
	8.3. XML Schema Registration . . . . . . . . . . . . . . . . . 89		8.3. XML Schema Registration . . . . . . . . . . . . . . . . . 89
	8.4. MIME Media Type Registration for		8.4. MIME Media Type Registration for
	'application/msc-mixer+xml' . . . . . . . . . . . . . . . 89		'application/msc-mixer+xml' . . . . . . . . . . . . . . . 89
	9. Change Summary . . . . . . . . . . . . . . . . . . . . . . . 91		9. Change Summary . . . . . . . . . . . . . . . . . . . . . . . 91
	10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 100		10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 101
	11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 101		11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 102
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . 102		12. References . . . . . . . . . . . . . . . . . . . . . . . . . 103
	12.1. Normative References . . . . . . . . . . . . . . . . . . 102		12.1. Normative References . . . . . . . . . . . . . . . . . . 103
	12.2. Informative References . . . . . . . . . . . . . . . . . 103		12.2. Informative References . . . . . . . . . . . . . . . . . 104
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 104		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 105
	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 Control Framework - an equivalent term for		initiated commands. The Control Framework - an equivalent term for
	the Media Control Channel Framework - utilizes many functions		the Media Control Channel Framework - utilizes many functions
	provided by the Session Initiation Protocol [RFC3261] (SIP) for the		provided by the Session Initiation Protocol [RFC3261] (SIP) for the
	rendezvous and establishment of a reliable channel for control		rendezvous and establishment of a reliable channel for control
	skipping to change at page 58, line 42 ¶		skipping to change at page 58, line 42 ¶
	where "type-name" and "subtype-name" are defined in Section 4.2 of		where "type-name" and "subtype-name" are defined in Section 4.2 of
	[RFC4288], "parameter-name" is defined in Section 4.3 of [RFC4288]		[RFC4288], "parameter-name" is defined in Section 4.3 of [RFC4288]
	and "value" is defined in Section 5.1 of [RFC2045].		and "value" is defined in Section 5.1 of [RFC2045].
	4.7.7. Language Identifier		4.7.7. Language Identifier
	A language identifier labels information content as being of a		A language identifier labels information content as being of a
	particular human language variant. Following the XML specification		particular human language variant. Following the XML specification
	for language identification [XML], a legal language identifier is		for language identification [XML], a legal language identifier is
	identified by a RFC5646 ([RFC5646]) and RFC4647 ([RFC4647]) code		identified by a RFC5646 code ([RFC5646]) and matched according to
	where the language code is required and a country code or other		RFC4647 ([RFC4647]).
	subtag identifier is optional.
	5. Formal Syntax		5. Formal Syntax
	This section defines the XML schema for the Mixer Control Package.		This section defines the XML schema for the Mixer Control Package.
	The schema is normative.		The schema is normative.
	The schema defines datatypes, attributes, and mixer elements in the		The schema defines datatypes, attributes, and mixer elements in the
	urn:ietf:params:xml:ns:msc-mixer namespace. In most elements the		urn:ietf:params:xml:ns:msc-mixer namespace. In most elements the
	order of child elements is significant. The schema is extensible:		order of child elements is significant. The schema is extensible:
	elements allow attributes and child elements from other namespaces.		elements allow attributes and child elements from other namespaces.
	skipping to change at page 91, line 9 ¶		skipping to change at page 91, 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 -14 and -13 versions
			(addressing remaining IESG DISCUSS):
			o 4.7.7 Language Identifier: deleted statement "where the language
			code is required and a country code or other subtag identifier is
			optional" and clarified that RFC 4647 specifies the matching
			procedure.
	The following are the changes between the -13 and -12 versions		The following are the changes between the -13 and -12 versions
	(addressing remaining IESG DISCUSS):		(addressing remaining IESG DISCUSS):
	o 4.0, 4.1, etc: Added language tags to identify the language of		o 4.0, 4.1, etc: Added language tags to identify the language of
	descriptive text attributes. A desclang attribute is added to the		descriptive text attributes. A desclang attribute is added to the
	root element and has a default value of i-default. Subordinate		root element and has a default value of i-default. Subordinate
	elements with descriptive text attributes also have this attribute		elements with descriptive text attributes also have this attribute
	defined - if it is not specified on the subordinate element, then		defined - if it is not specified on the subordinate element, then
	the desclang value on the root element applies. Added example of		the desclang value on the root element applies. Added example of
	desclang in 4.1.		desclang in 4.1.
End of changes. 7 change blocks.
	13 lines changed or deleted		20 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/