< draft-boulton-conference-control-package-03.txt		draft-boulton-conference-control-package-04.txt >
	Network Working Group C. Boulton		Network Working Group C. Boulton
	Internet-Draft Ubiquity Software Corporation		Internet-Draft Avaya
	Intended status: Standards Track T. Melanchuk		Intended status: Standards Track T. Melanchuk
	Expires: May 5, 2008 BlankSpace		Expires: August 26, 2008 Rain Willow Communications
	S. McGlashan		S. McGlashan
	Hewlett-Packard		Hewlett-Packard
	A. Shiratzky		A. Shiratzky
	Radvision		Radvision
	November 2, 2007		February 23, 2008
	A Conference Control Package for the Session Initiation Protocol (SIP)		A Conference Control Package for the Media Control Channel Framework
	draft-boulton-conference-control-package-03		draft-boulton-conference-control-package-04
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of 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
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	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 May 5, 2008.		This Internet-Draft will expire on August 26, 2008.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2008).
	Abstract		Abstract
	This document defines a Session Initiation (SIP) Control Package for		This document defines a Conference Control Package for the Media
	Conference Control. The control of Media Servers and their related		Control Channel Framework. This Control Package aims to fulfill
	resources in decomposed network architectures plays an important role		Conferencing requirements using the SIP Control Framework.
	in various Next Generation Networks. This Control Package aims to
	fulfill Conferencing requirements using the SIP Control Framework.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
	2. Conventions and Terminology . . . . . . . . . . . . . . . . . 5		2. Conventions and Terminology . . . . . . . . . . . . . . . . . 5
	3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 6		3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	4. Control Package Definition . . . . . . . . . . . . . . . . . . 7		4. Control Package Definition . . . . . . . . . . . . . . . . . . 7
	4.1. Control Package Name . . . . . . . . . . . . . . . . . . . 7		4.1. Control Package Name . . . . . . . . . . . . . . . . . . . 7
	4.2. Framework Message Usage . . . . . . . . . . . . . . . . . 7		4.2. Framework Message Usage . . . . . . . . . . . . . . . . . 7
	4.3. Common XML Support . . . . . . . . . . . . . . . . . . . . 8		4.3. Common XML Support . . . . . . . . . . . . . . . . . . . . 8
	skipping to change at page 3, line 33 ¶		skipping to change at page 3, line 33 ¶
	5.6. <modifyjoin> . . . . . . . . . . . . . . . . . . . . . . . 16		5.6. <modifyjoin> . . . . . . . . . . . . . . . . . . . . . . . 16
	5.7. <unjoin> . . . . . . . . . . . . . . . . . . . . . . . . . 16		5.7. <unjoin> . . . . . . . . . . . . . . . . . . . . . . . . . 16
	5.8. Notifications . . . . . . . . . . . . . . . . . . . . . . 17		5.8. Notifications . . . . . . . . . . . . . . . . . . . . . . 17
	5.8.1. <event> . . . . . . . . . . . . . . . . . . . . . . . 17		5.8.1. <event> . . . . . . . . . . . . . . . . . . . . . . . 17
	5.9. <data> . . . . . . . . . . . . . . . . . . . . . . . . . . 18		5.9. <data> . . . . . . . . . . . . . . . . . . . . . . . . . . 18
	5.10. <subscribe> . . . . . . . . . . . . . . . . . . . . . . . 18		5.10. <subscribe> . . . . . . . . . . . . . . . . . . . . . . . 18
	5.11. Conference Configuration . . . . . . . . . . . . . . . . . 19		5.11. Conference Configuration . . . . . . . . . . . . . . . . . 19
	5.11.1. <audio-mixing> . . . . . . . . . . . . . . . . . . . . 19		5.11.1. <audio-mixing> . . . . . . . . . . . . . . . . . . . . 19
	5.12. Media Streams . . . . . . . . . . . . . . . . . . . . . . 19		5.12. Media Streams . . . . . . . . . . . . . . . . . . . . . . 19
	5.12.1. Configuring Volume . . . . . . . . . . . . . . . . . . 20		5.12.1. Configuring Volume . . . . . . . . . . . . . . . . . . 20
	5.12.2. Configuring Tone Removal . . . . . . . . . . . . . . . 20		5.12.2. Configuring Tone Removal . . . . . . . . . . . . . . . 21
	5.13. Responses . . . . . . . . . . . . . . . . . . . . . . . . 21		5.13. Responses . . . . . . . . . . . . . . . . . . . . . . . . 21
	5.13.1. <response> . . . . . . . . . . . . . . . . . . . . . . 21		5.13.1. <response> . . . . . . . . . . . . . . . . . . . . . . 21
	6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 24		6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
	7. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 25		7. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 25
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 30		8. Security Considerations . . . . . . . . . . . . . . . . . . . 30
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31
	9.1. Control Package Registration . . . . . . . . . . . . . . . 31		9.1. Control Package Registration . . . . . . . . . . . . . . . 31
	9.2. MIME Registration . . . . . . . . . . . . . . . . . . . . 31		9.2. MIME Registration . . . . . . . . . . . . . . . . . . . . 31
	9.3. URN Sub-Namespace Registration . . . . . . . . . . . . . . 31		9.3. URN Sub-Namespace Registration . . . . . . . . . . . . . . 31
	10. Change Summary . . . . . . . . . . . . . . . . . . . . . . . . 32		10. Change Summary . . . . . . . . . . . . . . . . . . . . . . . . 32
	11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 33		11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 33
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 34		12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 34
	12.1. Normative References . . . . . . . . . . . . . . . . . . . 34		12.1. Normative References . . . . . . . . . . . . . . . . . . . 34
	12.2. Informative References . . . . . . . . . . . . . . . . . . 34		12.2. Informative References . . . . . . . . . . . . . . . . . . 34
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36
	Intellectual Property and Copyright Statements . . . . . . . . . . 37		Intellectual Property and Copyright Statements . . . . . . . . . . 37
	1. Introduction		1. Introduction
	The SIP Control Framework [I-D.boulton-sip-control-framework]		The Media Control Channel Framework
	provides a generic template for establishment and reporting		[I-D.ietf-mediactrl-sip-control-framework] provides a generic
	capabilities of remotely initiated commands. The Framework utilizes		template for establishment and reporting capabilities of remotely
	many functions provided by the Session Initiation Protocol [RFC3261]		initiated commands. The Control Framework also introduces the
	(SIP) for the rendezvous and establishment of a reliable channel for
	control interactions. The Control Framework also introduces the
	concept of a Control Package. A Control Package is an explicit usage		concept of a Control Package. A Control Package is an explicit usage
	of the Control Framework for a particular interaction set. This		of the Control Framework for a particular interaction set. This
	specification defines a package for control of conference instances.		specification defines a package for control of conference instances.
	2. Conventions and Terminology		2. Conventions and Terminology
	In this document, BCP 14/RFC 2119 [RFC2119] defines the key words		In this document, BCP 14/RFC 2119 [RFC2119] defines the key words
	"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",		"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
	"SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL". In addition, BCP 15 indicates requirement levels for		"OPTIONAL". In addition, BCP 15 indicates requirement levels for
	skipping to change at page 6, line 7 ¶		skipping to change at page 6, line 7 ¶
	from the output(s) of a connection and it transmits media on the		from the output(s) of a connection and it transmits media on the
	input(s) of a connection.		input(s) of a connection.
	Media Stream: A media stream on a media server represents a media		Media Stream: A media stream on a media server represents a media
	flow between either a connection and a conference, between two		flow between either a connection and a conference, between two
	connections, or between two conferences. Streams may be audio or		connections, or between two conferences. Streams may be audio or
	video and may be bi-directional or uni-directional.		video and may be bi-directional or uni-directional.
	3. Overview		3. Overview
	The SIP Control Framework [I-D.boulton-sip-control-framework]		The SIP Control Framework [I-D.ietf-mediactrl-sip-control-framework]
	provides a generic approach for establishment and reporting		provides a generic approach for establishment and reporting
	capabilities of remotely initiated commands. The Framework utilizes		capabilities of remotely initiated commands. The Framework utilizes
	many functions provided by the Session Initiation Protocol [RFC3261]		many functions provided by the Session Initiation Protocol [RFC3261]
	(SIP) for the rendezvous and establishment of a reliable channel for		(SIP) for the rendezvous and establishment of a reliable channel for
	control interactions. The Control Framework also introduces the		control interactions. The Control Framework also introduces the
	concept of a Control Package. A Control Package is an explicit usage		concept of a Control Package. A Control Package is an explicit usage
	of the Control Framework for a particular interaction set. This		of the Control Framework for a particular interaction set. This
	specification defines a package for basic conferencing.		specification defines a package for basic conferencing.
	The scope of the package is control of media server functions for		The scope of the package is control of media server functions for
	skipping to change at page 7, line 10 ¶		skipping to change at page 7, line 10 ¶
	functions. Although dialog services such as announcements,		functions. Although dialog services such as announcements,
	recordings, and prompts are generally needed for a complete		recordings, and prompts are generally needed for a complete
	conference service, those functions are defined in complementary		conference service, those functions are defined in complementary
	packages.		packages.
	4. Control Package Definition		4. Control Package Definition
	This section fulfils the mandatory requirement for information that		This section fulfils the mandatory requirement for information that
	MUST be specified during the definition of a Control Framework		MUST be specified during the definition of a Control Framework
	Package, as detailed in Section 9 of		Package, as detailed in Section 9 of
	[I-D.boulton-sip-control-framework].		[I-D.ietf-mediactrl-sip-control-framework].
	4.1. Control Package Name		4.1. Control Package Name
	The Control Framework requires a Control Package definition to		The Control Framework requires a Control Package definition to
	specify and register a unique name. The name and version of this		specify and register a unique name. The name and version of this
	Control Package is "msc-conf-audio/1.0" (Media Server Control -		Control Package is "msc-conf-audio/1.0" (Media Server Control -
	Conferencing - Audio - version 1.0).		Conferencing - Audio - version 1.0).
	4.2. Framework Message Usage		4.2. Framework Message Usage
	The intent for the Conference Control package is for the creation,		The intent for the Conference Control package is for the creation,
	manipulation and deletion of conferences as well as joining,		manipulation and deletion of conferences as well as joining,
	manipulation and unjoining of participants to conferences. The		manipulation and unjoining of participants to conferences. The
	Conference Control package is intended for use in an architecture		Conference Control package is intended for use in an architecture
	where application logic and media mixing are distributed. For this		where application logic and media mixing are distributed. For this
	reason the Control Framework will operate in a manner where CONTROL		reason the Control Framework will operate in a manner where CONTROL
	messages, as defined in the Conference Framework		messages, as defined in the Conference Framework
	[I-D.boulton-sip-control-framework], MUST only be sent from the		[I-D.ietf-mediactrl-sip-control-framework], MUST only be sent from
	network entity providing the application logic.		the network entity providing the application logic.
	This package defines XML elements in Section 5 and provides an XML		This package defines XML elements in Section 5 and provides an XML
	Schema in Section 7.		Schema in Section 7.
	The XML elements in this package are split into requests, responses		The XML elements in this package are split into requests, responses
	and event notifications. Requests are carried in CONTROL message		and event notifications. Requests are carried in CONTROL message
	bodies; <createconference> and <join> are examples of package		bodies; <createconference> and <join> are examples of package
	requests. See Section 5.1 for a complete enumeration of requests.		requests. See Section 5.1 for a complete enumeration of requests.
	Responses are carried either in REPORT messages or Control Framework		Responses are carried either in REPORT messages or Control Framework
	200 response bodies; the <response> element is defined as a package		200 response bodies; the <response> element is defined as a package
	response. Event notifications are also carried in REPORT message		response. Event notifications are also carried in REPORT message
	bodies; the <event> element is defined for package event		bodies; the <event> element is defined for package event
	notifications.		notifications.
	Note that package responses are different from framework response		Note that package responses are different from framework response
	codes. Framework error response codes (see Section 8 of		codes. Framework error response codes (see Section 8 of
	[I-D.boulton-sip-control-framework]) are used when the request or		[I-D.ietf-mediactrl-sip-control-framework]) are used when the request
	notification is invalid; for example, a request with invalid XML		or notification is invalid; for example, a request with invalid XML
	(400), or not understood (500). Package responses are carried in 200		(400), or not understood (500). Package responses are carried in 200
	response or REPORT message bodies. This package's response codes are		response or REPORT message bodies. This package's response codes are
	defined in Section 5.13.1.		defined in Section 5.13.1.
	The schema uses "connection-id" and "conf-id" attributes which are		The schema uses "connection-id" and "conf-id" attributes which are
	imported from schema defined in core Control Framework		imported from schema defined in core Control Framework
	[I-D.boulton-sip-control-framework].		[I-D.ietf-mediactrl-sip-control-framework].
	4.3. Common XML Support		4.3. Common XML Support
	The Control Framework requires a Control Package definition to		The Control Framework requires a Control Package definition to
	specify if the attributes for media dialog or conference references		specify if the attributes for media dialog or conference references
	are required.		are required.
	This package requires that the XML Schema in Section 16.1 of		This package requires that the XML Schema in Section 16.1 of
	[I-D.boulton-sip-control-framework] MUST be supported for media		[I-D.ietf-mediactrl-sip-control-framework] MUST be supported for
	dialogs and conferences.		media dialogs and conferences.
	4.4. CONTROL Message Body		4.4. CONTROL Message Body
	A valid CONTROL body message MUST conform to the schema defined in		A valid CONTROL body message MUST conform to the schema defined in
	Section 7 and described in Section 5. XML messages appearing in		Section 7 and described in Section 5. XML messages appearing in
	CONTROL messages MUST contain <createconference>, <modifyconference>,		CONTROL messages MUST contain <createconference>, <modifyconference>,
	<destroyconference>, <join>, <modifyjoin> or <unjoin> request		<destroyconference>, <join>, <modifyjoin> or <unjoin> request
	elements (Section 5.1).		elements (Section 5.1).
	4.5. REPORT Message Body		4.5. REPORT Message Body
	skipping to change at page 11, line 35 ¶		skipping to change at page 11, line 35 ¶
	+-------------+-----------------------------------------------------+		+-------------+-----------------------------------------------------+
	| Name | Speaker |		| Name | Speaker |
	+-------------+-----------------------------------------------------+		+-------------+-----------------------------------------------------+
	| Description | The connection identifier of a speaker that has |		| Description | The connection identifier of a speaker that has |
	| | been active during the preceding interval. |		| | been active during the preceding interval. |
	| | |		| | |
	| Direction | output |		| Direction | output |
	| | |		| | |
	| Type | a connection identifier: see Section 16.1 of |		| Type | a connection identifier: see Section 16.1 of |
	| | [I-D.boulton-sip-control-framework] |		| | [I-D.ietf-mediactrl-sip-control-framework] |
	| | |		| | |
	| Optional | No |		| Optional | No |
	| | |		| | |
	| Possible | Any connection identifier that is currently a |		| Possible | Any connection identifier that is currently a |
	| Values | member of the conference |		| Values | member of the conference |
	| | |		| | |
	| Default | none |		| Default | none |
	+-------------+-----------------------------------------------------+		+-------------+-----------------------------------------------------+
	Table 3: Speaker		Table 3: Speaker
	skipping to change at page 14, line 8 ¶		skipping to change at page 14, line 8 ¶
	then the default is the media configuration of the connection or		then the default is the media configuration of the connection or
	conference.		conference.
	One or more <stream> elements may be specified so that individual		One or more <stream> elements may be specified so that individual
	media streams can be controlled independently; for example, audio		media streams can be controlled independently; for example, audio
	only for transmission, but video only for reception. It is an error		only for transmission, but video only for reception. It is an error
	if a <stream> element is in conflict with (a) another <stream>		if a <stream> element is in conflict with (a) another <stream>
	element, (b) with dialog, connection or conference media		element, (b) with dialog, connection or conference media
	capabilities, or (c) with a SDP label value as part of the		capabilities, or (c) with a SDP label value as part of the
	connection-id (see Section 16.1 of		connection-id (see Section 16.1 of
	[I-D.boulton-sip-control-framework]).		[I-D.ietf-mediactrl-sip-control-framework]).
	The two entities to join are specified by the attributes of <join>.		The two entities to join are specified by the attributes of <join>.
	The <join> element has the following attributes:		The <join> element has the following attributes:
	id1: an identifier for either a connection or a conference. The		id1: an identifier for either a connection or a conference. The
	identifier MUST conform to the syntax defined in Section 16.1 of		identifier MUST conform to the syntax defined in Section 16.1 of
	[I-D.boulton-sip-control-framework] The attribute is mandatory.		[I-D.ietf-mediactrl-sip-control-framework] The attribute is
			mandatory.
	id2: an identifier for either a connection or a conference. The		id2: an identifier for either a connection or a conference. The
	identifier MUST conform to the syntax defined in Section 16.1 of		identifier MUST conform to the syntax defined in Section 16.1 of
	[I-D.boulton-sip-control-framework] The attribute is mandatory.		[I-D.ietf-mediactrl-sip-control-framework] The attribute is
			mandatory.
	Note: Section 16.1 of [I-D.boulton-sip-control-framework] defines the		Note: Section 16.1 of [I-D.ietf-mediactrl-sip-control-framework]
	semantics for a conference identifier but not its syntax. Media		defines the semantics for a conference identifier but not its syntax.
	server implementations need to distinguish between conferences and		Media server implementations need to distinguish between conferences
	connections based upon the values of the "id1" and "id2" attributes.		and connections based upon the values of the "id1" and "id2"
			attributes.
	When an controlling client has finished processing a <join> request,		When an controlling client has finished processing a <join> request,
	it MUST reply with an <response> element (Section 5.13). If the		it MUST reply with an <response> element (Section 5.13). If the
	participant is already a member of the conference instance, a xxx		participant is already a member of the conference instance, a xxx
	package level response should be generated.		package level response should be generated.
	5.5.1. Joining Model		5.5.1. Joining Model
	The <join> operation creates a media stream between a connection and		The <join> operation creates a media stream between a connection and
	a conference, between connections, or between conferences. This sub-		a conference, between connections, or between conferences. This sub-
	skipping to change at page 16, line 30 ¶		skipping to change at page 16, line 32 ¶
	The <modifyjoin> element has the following child elements defined:		The <modifyjoin> element has the following child elements defined:
	<stream>: an element that both identifies the media streams to		<stream>: an element that both identifies the media streams to
	modify and defines the way that each stream should now be		modify and defines the way that each stream should now be
	configured (see Section 5.12). The element is mandatory.		configured (see Section 5.12). The element is mandatory.
	The <modifyjoin> element has the following attributes:		The <modifyjoin> element has the following attributes:
	id1: an identifier for either a connection or a conference. The		id1: an identifier for either a connection or a conference. The
	identifier MUST conform to the syntax defined in Section 16.1 of		identifier MUST conform to the syntax defined in Section 16.1 of
	[I-D.boulton-sip-control-framework] The attribute is mandatory.		[I-D.ietf-mediactrl-sip-control-framework] The attribute is
			mandatory.
	id2: an identifier for either a connection or a conference. The		id2: an identifier for either a connection or a conference. The
	identifier MUST conform to the syntax defined in Section 16.1 of		identifier MUST conform to the syntax defined in Section 16.1 of
	[I-D.boulton-sip-control-framework] The attribute is mandatory.		[I-D.ietf-mediactrl-sip-control-framework] The attribute is
			mandatory.
	The media server MUST configure the streams that are included within		The media server MUST configure the streams that are included within
	<modifyjoin> to that stated by the child elements. It MUST NOT		<modifyjoin> to that stated by the child elements. It MUST NOT
	change the configuration of any streams not included as child		change the configuration of any streams not included as child
	elements.		elements.
	When an MS has finished processing a <modifyjoin> request, it MUST		When an MS has finished processing a <modifyjoin> request, it MUST
	reply with an appropriate <response> element (Section 5.13).		reply with an appropriate <response> element (Section 5.13).
	5.7. <unjoin>		5.7. <unjoin>
	skipping to change at page 17, line 15 ¶		skipping to change at page 17, line 19 ¶
	The <unjoin> element has the following child elements defined:		The <unjoin> element has the following child elements defined:
	<stream>: an element that identifies the media stream(s) to remove		<stream>: an element that identifies the media stream(s) to remove
	(see Section 5.12). The element is optional. When not present,		(see Section 5.12). The element is optional. When not present,
	all streams between "id1" and "id2" are removed.		all streams between "id1" and "id2" are removed.
	The <unjoin> element has the following attributes:		The <unjoin> element has the following attributes:
	id1: an identifier for either a connection or a conference. The		id1: an identifier for either a connection or a conference. The
	identifier MUST conform to the syntax defined in Section 16.1 of		identifier MUST conform to the syntax defined in Section 16.1 of
	[I-D.boulton-sip-control-framework] The attribute is mandatory.		[I-D.ietf-mediactrl-sip-control-framework] The attribute is
			mandatory.
	id2: an identifier for either a connection or a conference. The		id2: an identifier for either a connection or a conference. The
	identifier MUST conform to the syntax defined in Section 16.1 of		identifier MUST conform to the syntax defined in Section 16.1 of
	[I-D.boulton-sip-control-framework] The attribute is mandatory.		[I-D.ietf-mediactrl-sip-control-framework] The attribute is
			mandatory.
	When an MS has successfully received a <unjoin> request, it MUST		When an MS has successfully received a <unjoin> request, it MUST
	reply with a successful <response> element (Section 5.13). If the		reply with a successful <response> element (Section 5.13). If the
	participant is not identified as a member of the conference instance,		participant is not identified as a member of the conference instance,
	a xxx package level response should be generated.		a xxx package level response should be generated.
	5.8. Notifications		5.8. Notifications
	Event notifications are specified in an <event> element.		Event notifications are specified in an <event> element.
	skipping to change at page 21, line 24 ¶		skipping to change at page 21, line 32 ¶
	The <response> element has following attributes:		The <response> element has following attributes:
	status: numeric code indicating the response status. The attribute		status: numeric code indicating the response status. The attribute
	is mandatory.		is mandatory.
	reason: string specifying a reason for the response status. The		reason: string specifying a reason for the response status. The
	attribute is optional.		attribute is optional.
	conf-id: string identifying the conference (see Section 16.1 of		conf-id: string identifying the conference (see Section 16.1 of
	[I-D.boulton-sip-control-framework]). The attribute is optional.		[I-D.ietf-mediactrl-sip-control-framework]). The attribute is
			optional.
	connection-id: string identifying the SIP dialog connection (see		connection-id: string identifying the SIP dialog connection (see
	Section 16.1 of [I-D.boulton-sip-control-framework]). The		Section 16.1 of [I-D.ietf-mediactrl-sip-control-framework]). The
	attribute is optional.		attribute is optional.
	The following status codes are defined:		The following status codes are defined:
	+-----------+-------------------------------------------------------+		+-----------+-------------------------------------------------------+
	| code | description |		| code | description |
	+-----------+-------------------------------------------------------+		+-----------+-------------------------------------------------------+
	| 200 | OK |		| 200 | OK |
	| | |		| | |
	| 401 | Dialog already exists |		| 401 | Dialog already exists |
	skipping to change at page 32, line 7 ¶		skipping to change at page 32, line 7 ¶
	9.2. MIME Registration		9.2. MIME Registration
	TODO: application/msc-conf+xml		TODO: application/msc-conf+xml
	9.3. URN Sub-Namespace Registration		9.3. URN Sub-Namespace Registration
	TODO: urn:ietf:params:xml:ns:msc-conf		TODO: urn:ietf:params:xml:ns:msc-conf
	10. Change Summary		10. Change Summary
			The following are the major changes between the -04 of the draft and
			the -03 version.
			o Updated reference for Media Control Channel Framework
	The following are the major changes between the -03 of the draft and		The following are the major changes between the -03 of the draft and
	the -02 version.		the -02 version.
	o None		o None
	The following are the major changes between the -02 of the draft and		The following are the major changes between the -02 of the draft and
	the -01 version.		the -01 version.
	o clarified the model for join operations and introduced several new		o clarified the model for join operations and introduced several new
	package error codes		package error codes
	skipping to change at page 34, line 14 ¶		skipping to change at page 34, line 14 ¶
	12. References		12. References
	12.1. Normative References		12.1. Normative References
	[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.
	12.2. Informative References		12.2. Informative References
	[I-D.boulton-sip-control-framework]		[I-D.ietf-mediactrl-sip-control-framework]
	Boulton, C., "A Control Framework for the Session		Boulton, C., Melanchuk, T., and S. McGlashan, "Media
	Initiation Protocol (SIP)",		Control Channel Framework",
	draft-boulton-sip-control-framework-05 (work in progress),		draft-ietf-mediactrl-sip-control-framework-01 (work in
	February 2007.		progress), February 2008.
	[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,		[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
	Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext		Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
	Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.		Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
	[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.
	skipping to change at page 36, line 8 ¶		skipping to change at page 36, line 8 ¶
	[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.
	Authors' Addresses		Authors' Addresses
	Chris Boulton		Chris Boulton
	Ubiquity Software Corporation		Avaya
	Building 3		Building 3
	Wern Fawr Lane		Wern Fawr Lane
	St Mellons		St Mellons
	Cardiff, South Wales CF3 5EA		Cardiff, South Wales CF3 5EA
	Email: cboulton@ubiquitysoftware.com		Email: cboulton@avaya.com
	Tim Melanchuk		Tim Melanchuk
	BlankSpace		Rain Willow Communications
	Email: tim.melanchuk@gmail.com		Email: tim.melanchuk@gmail.com
	Scott McGlashan		Scott McGlashan
	Hewlett-Packard		Hewlett-Packard
	Gustav III:s boulevard 36		Gustav III:s boulevard 36
	SE-16985 Stockholm, Sweden		SE-16985 Stockholm, Sweden
	Email: scott.mcglashan@hp.com		Email: scott.mcglashan@hp.com
	Asher Shiratzky		Asher Shiratzky
	Radvision		Radvision
	24 Raoul Wallenberg st		24 Raoul Wallenberg st
	Tel-Aviv, Israel		Tel-Aviv, Israel
	Email: ashers@radvision.com		Email: ashers@radvision.com
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2008).
	This document is subject to the rights, licenses and restrictions		This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors		contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.		retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF		OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
End of changes. 32 change blocks.
	51 lines changed or deleted		60 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/