rfc8845.txt		rfc8845-bordersminimal.txt
	skipping to change at line 1005 ¶		skipping to change at line 1005 ¶
	Advertiser to indicate that several MCC captures are used to		Advertiser to indicate that several MCC captures are used to
	represent a capture scene. Table 14 provides an example of this		represent a capture scene. Table 14 provides an example of this
	case.		case.
	As outlined in Section 7.1, each instance of the MCC has its own		As outlined in Section 7.1, each instance of the MCC has its own
	Capture identity, i.e., MCC1. It allows all the individual captures		Capture identity, i.e., MCC1. It allows all the individual captures
	contained in the MCC to be referenced by a single MCC identity.		contained in the MCC to be referenced by a single MCC identity.
	The example below shows the use of a Multiple Content Capture:		The example below shows the use of a Multiple Content Capture:
	+===================+=========================+		------------------- -------------------------
	| Capture Scene #1 | |		Capture Scene #1
	+===================+=========================+		VC1 {MC attributes}
	| VC1 | {MC attributes} |		VC2 {MC attributes}
	+-------------------+-------------------------+		VC3 {MC attributes}
	| VC2 | {MC attributes} |		MCC1(VC1,VC2,VC3) {MC and MCC attributes}
	+-------------------+-------------------------+		CSV(MCC1)
	| VC3 | {MC attributes} |		------------------- -------------------------
	+-------------------+-------------------------+
	| MCC1(VC1,VC2,VC3) | {MC and MCC attributes} |
	+-------------------+-------------------------+
	| CSV(MCC1) | |
	+-------------------+-------------------------+
	Table 1: Multiple Content Capture Concept		Table 1: Multiple Content Capture Concept
	This indicates that MCC1 is a single capture that contains the		This indicates that MCC1 is a single capture that contains the
	Captures VC1, VC2, and VC3, according to any MCC1 attributes.		Captures VC1, VC2, and VC3, according to any MCC1 attributes.
	7.2.1. MCC Attributes		7.2.1. MCC Attributes
	Media Capture Attributes may be associated with the MCC instance and		Media Capture Attributes may be associated with the MCC instance and
	the Single Media Captures that the MCC references. A Provider should		the Single Media Captures that the MCC references. A Provider should
	skipping to change at line 1055 ¶		skipping to change at line 1050 ¶
	For example: a virtual scene could be constructed for the MCC capture		For example: a virtual scene could be constructed for the MCC capture
	with two Video Captures with a "MaxCaptures" attribute set to 2 and		with two Video Captures with a "MaxCaptures" attribute set to 2 and
	an "Area of Capture" attribute provided with an overall area. Each		an "Area of Capture" attribute provided with an overall area. Each
	of the individual Captures could then also include an "Area of		of the individual Captures could then also include an "Area of
	Capture" attribute with a subset of the overall area. The Consumer		Capture" attribute with a subset of the overall area. The Consumer
	would then know how each capture is related to others within the		would then know how each capture is related to others within the
	scene, but not the relative position of the individual captures		scene, but not the relative position of the individual captures
	within the composed capture.		within the composed capture.
	+===============+===================================+		--------------- -----------------------------------
	| Capture Scene | |		Capture Scene
	| #1 | |		#1
	+===============+===================================+		VC1 AreaofCapture=(0,0,0)(9,0,0)
	| VC1 | AreaofCapture=(0,0,0)(9,0,0) |		(0,0,9)(9,0,9)
	| | (0,0,9)(9,0,9) |		VC2 AreaofCapture=(10,0,0)(19,0,0)
	+---------------+-----------------------------------+		(10,0,9)(19,0,9)
	| VC2 | AreaofCapture=(10,0,0)(19,0,0) |		MCC1(VC1,VC2) MaxCaptures=2
	| | (10,0,9)(19,0,9) |		AreaofCapture=(0,0,0)(19,0,0)
	+---------------+-----------------------------------+		(0,0,9)(19,0,9)
	| MCC1(VC1,VC2) | MaxCaptures=2 |		CSV(MCC1)
	| | AreaofCapture=(0,0,0)(19,0,0) |		--------------- -----------------------------------
	| | (0,0,9)(19,0,9) |
	+---------------+-----------------------------------+
	| CSV(MCC1) | |
	+---------------+-----------------------------------+
	Table 2: Example of MCC and Single Media Capture		Table 2: Example of MCC and Single Media Capture
	Attributes		Attributes
	The subsections below describe the MCC-only attributes.		The subsections below describe the MCC-only attributes.
	7.2.1.1. Maximum Number of Captures within an MCC		7.2.1.1. Maximum Number of Captures within an MCC
	The Maximum Number of Captures MCC attribute indicates the maximum		The Maximum Number of Captures MCC attribute indicates the maximum
	number of individual Captures that may appear in a Capture Encoding		number of individual Captures that may appear in a Capture Encoding
	skipping to change at line 1174 ¶		skipping to change at line 1165 ¶
	An index is used to represent an instance in the policy setting. An		An index is used to represent an instance in the policy setting. An
	index of 0 represents the most current instance of the policy, i.e.,		index of 0 represents the most current instance of the policy, i.e.,
	the active speaker, 1 represents the previous instance, i.e., the		the active speaker, 1 represents the previous instance, i.e., the
	previous active speaker, and so on.		previous active speaker, and so on.
	The following example shows a case where the Provider provides two		The following example shows a case where the Provider provides two
	media streams, one showing the active speaker and a second stream		media streams, one showing the active speaker and a second stream
	showing the previous speaker.		showing the previous speaker.
	+==================+=====================+		------------------ ---------------------
	| Capture Scene #1 | |		Capture Scene #1
	+==================+=====================+		VC1
	| VC1 | |		VC2
	+------------------+---------------------+		MCC1(VC1,VC2) Policy=SoundLevel:0
	| VC2 | |		MaxCaptures=1
	+------------------+---------------------+		MCC2(VC1,VC2) Policy=SoundLevel:1
	| MCC1(VC1,VC2) | Policy=SoundLevel:0 |		MaxCaptures=1
	| | MaxCaptures=1 |		CSV(MCC1,MCC2)
	+------------------+---------------------+		------------------ ---------------------
	| MCC2(VC1,VC2) | Policy=SoundLevel:1 |
	| | MaxCaptures=1 |
	+------------------+---------------------+
	| CSV(MCC1,MCC2) | |
	+------------------+---------------------+
	Table 3: Example Policy MCC Attribute		Table 3: Example Policy MCC Attribute
	Usage		Usage
	7.2.1.3. Synchronization Identity		7.2.1.3. Synchronization Identity
	The Synchronization Identity MCC attribute indicates how the		The Synchronization Identity MCC attribute indicates how the
	individual Captures in multiple MCC Captures are synchronized. To		individual Captures in multiple MCC Captures are synchronized. To
	indicate that the Capture Encodings associated with MCCs contain		indicate that the Capture Encodings associated with MCCs contain
	Captures from the same source at the same time, a Provider should set		Captures from the same source at the same time, a Provider should set
	skipping to change at line 1214 ¶		skipping to change at line 1200 ¶
	attribute. For example, when the Provider is in an MCU, it may		attribute. For example, when the Provider is in an MCU, it may
	determine that each separate CLUE Endpoint is a remote source of		determine that each separate CLUE Endpoint is a remote source of
	media. The Synchronization Identity may be used across media types,		media. The Synchronization Identity may be used across media types,
	i.e., to synchronize audio- and video-related MCCs.		i.e., to synchronize audio- and video-related MCCs.
	Without this attribute it is assumed that multiple MCCs may provide		Without this attribute it is assumed that multiple MCCs may provide
	content from different sources at any particular point in time.		content from different sources at any particular point in time.
	For example:		For example:
	+=======================+=====================+		----------------------- ---------------------
	| Capture Scene #1 | |		Capture Scene #1
	+=======================+=====================+		VC1 Description=Left
	| VC1 | Description=Left |		VC2 Description=Center
	+-----------------------+---------------------+		VC3 Description=Right
	| VC2 | Description=Center |		AC1 Description=Room
	+-----------------------+---------------------+		CSV(VC1,VC2,VC3)
	| VC3 | Description=Right |		CSV(AC1)
	+-----------------------+---------------------+		----------------------- ---------------------
	| AC1 | Description=Room |		Capture Scene #2
	+-----------------------+---------------------+		VC4 Description=Left
	| CSV(VC1,VC2,VC3) | |		VC5 Description=Center
	+-----------------------+---------------------+		VC6 Description=Right
	| CSV(AC1) | |		AC2 Description=Room
	+=======================+=====================+		CSV(VC4,VC5,VC6)
	| Capture Scene #2 | |		CSV(AC2)
	+=======================+=====================+		----------------------- ---------------------
	| VC4 | Description=Left |		Capture Scene #3
	+-----------------------+---------------------+		VC7
	| VC5 | Description=Center |		AC3
	+-----------------------+---------------------+		----------------------- ---------------------
	| VC6 | Description=Right |		Capture Scene #4
	+-----------------------+---------------------+		VC8
	| AC2 | Description=Room |		AC4
	+-----------------------+---------------------+		----------------------- ---------------------
	| CSV(VC4,VC5,VC6) | |		Capture Scene #5
	+-----------------------+---------------------+		MCC1(VC1,VC4,VC7) SynchronizationID=1
	| CSV(AC2) | |		MaxCaptures=1
	+=======================+=====================+		MCC2(VC2,VC5,VC8) SynchronizationID=1
	| Capture Scene #3 | |		MaxCaptures=1
	+=======================+=====================+		MCC3(VC3,VC6) MaxCaptures=1
	| VC7 | |		MCC4(AC1,AC2,AC3,AC4) SynchronizationID=1
	+-----------------------+---------------------+		MaxCaptures=1
	| AC3 | |		CSV(MCC1,MCC2,MCC3)
	+=======================+=====================+		CSV(MCC4)
	| Capture Scene #4 | |		----------------------- ---------------------
	+=======================+=====================+
	| VC8 | |
	+-----------------------+---------------------+
	| AC4 | |
	+=======================+=====================+
	| Capture Scene #5 | |
	+=======================+=====================+
	| MCC1(VC1,VC4,VC7) | SynchronizationID=1 |
	| | MaxCaptures=1 |
	+-----------------------+---------------------+
	| MCC2(VC2,VC5,VC8) | SynchronizationID=1 |
	| | MaxCaptures=1 |
	+-----------------------+---------------------+
	| MCC3(VC3,VC6) | MaxCaptures=1 |
	+-----------------------+---------------------+
	| MCC4(AC1,AC2,AC3,AC4) | SynchronizationID=1 |
	| | MaxCaptures=1 |
	+-----------------------+---------------------+
	| CSV(MCC1,MCC2,MCC3) | |
	+-----------------------+---------------------+
	| CSV(MCC4) | |
	+-----------------------+---------------------+
	Table 4: Example Synchronization Identity		Table 4: Example Synchronization Identity
	MCC Attribute Usage		MCC Attribute Usage
	The above Advertisement would indicate that MCC1, MCC2, MCC3, and		The above Advertisement would indicate that MCC1, MCC2, MCC3, and
	MCC4 make up a Capture Scene. There would be four Capture Encodings		MCC4 make up a Capture Scene. There would be four Capture Encodings
	(one for each MCC). Because MCC1 and MCC2 have the same		(one for each MCC). Because MCC1 and MCC2 have the same
	SynchronizationID, each Encoding from MCC1 and MCC2, respectively,		SynchronizationID, each Encoding from MCC1 and MCC2, respectively,
	would together have content from only Capture Scene 1 or only Capture		would together have content from only Capture Scene 1 or only Capture
	Scene 2 or the combination of VC7 and VC8 at a particular point in		Scene 2 or the combination of VC7 and VC8 at a particular point in
	skipping to change at line 1574 ¶		skipping to change at line 1538 ¶
	Transmission Set. It does not imply that the Single Media Captures		Transmission Set. It does not imply that the Single Media Captures
	contained in the Multiple Content Capture could all be transmitted at		contained in the Multiple Content Capture could all be transmitted at
	the same time.		the same time.
	In this example, the two Simultaneous Transmission Sets are shown in		In this example, the two Simultaneous Transmission Sets are shown in
	Table 5. If a Provider advertises one or more mutually exclusive		Table 5. If a Provider advertises one or more mutually exclusive
	Simultaneous Transmission Sets, then, for each media type, the		Simultaneous Transmission Sets, then, for each media type, the
	Consumer MUST ensure that it chooses Media Captures that lie wholly		Consumer MUST ensure that it chooses Media Captures that lie wholly
	within one of those Simultaneous Transmission Sets.		within one of those Simultaneous Transmission Sets.
	+===================+		-------------------
	| Simultaneous Sets |		Simultaneous Sets
	+===================+		{VC0, VC1, VC2}
	| {VC0, VC1, VC2} |		{VC0, VC3, VC2}
	+-------------------+		-------------------
	| {VC0, VC3, VC2} |
	+-------------------+
	Table 5: Two		Table 5: Two
	Simultaneous		Simultaneous
	Transmission Sets		Transmission Sets
	A Provider OPTIONALLY can include the Simultaneous Transmission Sets		A Provider OPTIONALLY can include the Simultaneous Transmission Sets
	in its Advertisement. These constraints apply across all the Capture		in its Advertisement. These constraints apply across all the Capture
	Scenes in the Advertisement. It is a syntax-conformance requirement		Scenes in the Advertisement. It is a syntax-conformance requirement
	that the Simultaneous Transmission Sets MUST allow all the media		that the Simultaneous Transmission Sets MUST allow all the media
	Captures in any particular Capture Scene View to be used		Captures in any particular Capture Scene View to be used
	skipping to change at line 1729 ¶		skipping to change at line 1691 ¶
	encoding of the MCC. This allows an Advertiser to specify encoding		encoding of the MCC. This allows an Advertiser to specify encoding
	attributes associated with the Media Captures without the need to		attributes associated with the Media Captures without the need to
	provide an individual Capture Encoding for each of the inputs.		provide an individual Capture Encoding for each of the inputs.
	If an Encoding Group is assigned to a Media Capture referenced by the		If an Encoding Group is assigned to a Media Capture referenced by the
	MCC, it indicates that this Capture may also have an individual		MCC, it indicates that this Capture may also have an individual
	Capture Encoding.		Capture Encoding.
	For example:		For example:
	+==================+=================+		------------------ -----------------
	| Capture Scene #1 | |		Capture Scene #1
	+==================+=================+		VC1 EncodeGroupID=1
	| VC1 | EncodeGroupID=1 |		VC2
	+------------------+-----------------+		MCC1(VC1,VC2) EncodeGroupID=2
	| VC2 | |		CSV(VC1)
	+------------------+-----------------+		CSV(MCC1)
	| MCC1(VC1,VC2) | EncodeGroupID=2 |		------------------ -----------------
	+------------------+-----------------+
	| CSV(VC1) | |
	+------------------+-----------------+
	| CSV(MCC1) | |
	+------------------+-----------------+
	Table 6: Example Usage of Encoding		Table 6: Example Usage of Encoding
	with MCC and Source Captures		with MCC and Source Captures
	This would indicate that VC1 may be sent as its own Capture Encoding		This would indicate that VC1 may be sent as its own Capture Encoding
	from EncodeGroupID=1 or that it may be sent as part of a Capture		from EncodeGroupID=1 or that it may be sent as part of a Capture
	Encoding from EncodeGroupID=2 along with VC2.		Encoding from EncodeGroupID=2 along with VC2.
	More than one Capture MAY use the same Encoding Group.		More than one Capture MAY use the same Encoding Group.
	skipping to change at line 2152 ¶		skipping to change at line 2109 ¶
	Capture Scenes:		Capture Scenes:
	The following table represents the Capture Scenes for this Provider.		The following table represents the Capture Scenes for this Provider.
	Recall that a Capture Scene is composed of alternative Capture Scene		Recall that a Capture Scene is composed of alternative Capture Scene
	Views covering the same spatial region. Capture Scene #1 is for the		Views covering the same spatial region. Capture Scene #1 is for the
	main people captures, and Capture Scene #2 is for presentation.		main people captures, and Capture Scene #2 is for presentation.
	Each row in the table is a separate Capture Scene View.		Each row in the table is a separate Capture Scene View.
	+==================+		------------------
	| Capture Scene #1 |		Capture Scene #1
	+==================+		VC0, VC1, VC2
	| VC0, VC1, VC2 |		MCC3
	+------------------+		MCC4
	| MCC3 |		VC5
	+------------------+		AC0, AC1, AC2
	| MCC4 |		AC3
	+------------------+		------------------
	| VC5 |		Capture Scene #2
	+------------------+		VC6
	| AC0, AC1, AC2 |		AC4
	+------------------+		------------------
	| AC3 |
	+==================+
	| Capture Scene #2 |
	+==================+
	| VC6 |
	+------------------+
	| AC4 |
	+------------------+
	Table 7: Example		Table 7: Example
	Capture Scene Views		Capture Scene Views
	Different Capture Scenes are distinct from each other and do not		Different Capture Scenes are distinct from each other and do not
	overlap. A Consumer can choose a view from each Capture Scene. In		overlap. A Consumer can choose a view from each Capture Scene. In
	this case, the three Captures, VC0, VC1, and VC2, are one way of		this case, the three Captures, VC0, VC1, and VC2, are one way of
	representing the video from the Endpoint. These three Captures		representing the video from the Endpoint. These three Captures
	should appear adjacent to each other. Alternatively, another way of		should appear adjacent to each other. Alternatively, another way of
	representing the Capture Scene is with the capture MCC3, which		representing the Capture Scene is with the capture MCC3, which
	skipping to change at line 2257 ¶		skipping to change at line 2206 ¶
	12.1.3. The MCU Case		12.1.3. The MCU Case
	This section shows how an MCU might express its Capture Scenes,		This section shows how an MCU might express its Capture Scenes,
	intending to offer different choices for consumers that can handle		intending to offer different choices for consumers that can handle
	different numbers of streams. Each MCC is for video. A single Audio		different numbers of streams. Each MCC is for video. A single Audio
	Capture is provided for all single and multi-screen configurations		Capture is provided for all single and multi-screen configurations
	that can be associated (e.g., lip-synced) with any combination of		that can be associated (e.g., lip-synced) with any combination of
	Video Captures (the MCCs) at the consumer.		Video Captures (the MCCs) at the consumer.
	+==========================+==================================+		-------------------------- ----------------------------------
	| Capture Scene #1 | |		Capture Scene #1
	+==========================+==================================+		MCC for a single-screen consumer
	| MCC | for a single-screen consumer |		MCC1, MCC2 for a two-screen consumer
	+--------------------------+----------------------------------+		MCC3, MCC4, MCC5 for a three-screen consumer
	| MCC1, MCC2 | for a two-screen consumer |		MCC6, MCC7, MCC8, MCC9 for a four-screen consumer
	+--------------------------+----------------------------------+		AC0 AC representing all participants
	| MCC3, MCC4, MCC5 | for a three-screen consumer |		CSV(MCC0)
	+--------------------------+----------------------------------+		CSV(MCC1,MCC2)
	| MCC6, MCC7, MCC8, MCC9 | for a four-screen consumer |		CSV(MCC3,MCC4,MCC5)
	+--------------------------+----------------------------------+		CSV(MCC6,MCC7,MCC8,MCC9)
	| AC0 | AC representing all participants |		CSV(AC0)
	+--------------------------+----------------------------------+		-------------------------- ----------------------------------
	| CSV(MCC0) | |
	+--------------------------+----------------------------------+
	| CSV(MCC1,MCC2) | |
	+--------------------------+----------------------------------+
	| CSV(MCC3,MCC4,MCC5) | |
	+--------------------------+----------------------------------+
	| CSV(MCC6,MCC7,MCC8,MCC9) | |
	+--------------------------+----------------------------------+
	| CSV(AC0) | |
	+--------------------------+----------------------------------+
	Table 8: MCU Main Capture Scenes		Table 8: MCU Main Capture Scenes
	If/when a presentation stream becomes active within the conference,		If/when a presentation stream becomes active within the conference,
	the MCU might re-advertise the available media as:		the MCU might re-advertise the available media as:
	+==================+======================================+		------------------ --------------------------------------
	| Capture Scene #2 | Note |		Capture Scene #2 Note
	+==================+======================================+		VC10 Video capture for presentation
	| VC10 | Video capture for presentation |		AC1 Presentation audio to accompany VC10
	+------------------+--------------------------------------+		CSV(VC10)
	| AC1 | Presentation audio to accompany VC10 |		CSV(AC1)
	+------------------+--------------------------------------+		------------------ --------------------------------------
	| CSV(VC10) | |
	+------------------+--------------------------------------+
	| CSV(AC1) | |
	+------------------+--------------------------------------+
	Table 9: MCU Presentation Capture Scene		Table 9: MCU Presentation Capture Scene
	12.2. Media Consumer Behavior		12.2. Media Consumer Behavior
	This section gives an example of how a Media Consumer might behave		This section gives an example of how a Media Consumer might behave
	when deciding how to request streams from the three-screen endpoint		when deciding how to request streams from the three-screen endpoint
	described in the previous section.		described in the previous section.
	The receive side of a call needs to balance its requirements (based		The receive side of a call needs to balance its requirements (based
	skipping to change at line 2404 ¶		skipping to change at line 2339 ¶
	MCU is responsible for making these unique in the outgoing		MCU is responsible for making these unique in the outgoing
	advertisement.		advertisement.
	12.3.1. Single Media Captures and MCC in the Same Advertisement		12.3.1. Single Media Captures and MCC in the Same Advertisement
	Four endpoints are involved in a Conference where CLUE is used. An		Four endpoints are involved in a Conference where CLUE is used. An
	MCU acts as a middlebox between the endpoints with a CLUE channel		MCU acts as a middlebox between the endpoints with a CLUE channel
	between each endpoint and the MCU. The MCU receives the following		between each endpoint and the MCU. The MCU receives the following
	Advertisements.		Advertisements.
	+==================+================================+		------------------ --------------------------------
	| Capture Scene #1 | Description=AustralianConfRoom |		Capture Scene #1 Description=AustralianConfRoom
	+==================+================================+		VC1 Description=Audience
	| VC1 | Description=Audience |		EncodeGroupID=1
	| | EncodeGroupID=1 |		CSV(VC1)
	+------------------+--------------------------------+		------------------ --------------------------------
	| CSV(VC1) | |
	+------------------+--------------------------------+
	Table 10: Advertisement Received from Endpoint A		Table 10: Advertisement Received from Endpoint A
	+==================+===========================+		------------------ ---------------------------
	| Capture Scene #1 | Description=ChinaConfRoom |		Capture Scene #1 Description=ChinaConfRoom
	+==================+===========================+		VC1 Description=Speaker
	| VC1 | Description=Speaker |		EncodeGroupID=1
	| | EncodeGroupID=1 |		VC2 Description=Audience
	+------------------+---------------------------+		EncodeGroupID=1
	| VC2 | Description=Audience |		CSV(VC1, VC2)
	| | EncodeGroupID=1 |		------------------ ---------------------------
	+------------------+---------------------------+
	| CSV(VC1, VC2) | |
	+------------------+---------------------------+
	Table 11: Advertisement Received from Endpoint B		Table 11: Advertisement Received from Endpoint B
	Note: Endpoint B indicates that it sends two streams.		Note: Endpoint B indicates that it sends two streams.
	+==================+=========================+		------------------ -------------------------
	| Capture Scene #1 | Description=USAConfRoom |		Capture Scene #1 Description=USAConfRoom
	+==================+=========================+		VC1 Description=Audience
	| VC1 | Description=Audience |		EncodeGroupID=1
	| | EncodeGroupID=1 |		CSV(VC1)
	+------------------+-------------------------+		------------------ -------------------------
	| CSV(VC1) | |
	+------------------+-------------------------+
	Table 12: Advertisement Received from		Table 12: Advertisement Received from
	Endpoint C		Endpoint C
	If the MCU wanted to provide a Multiple Content Captures containing a		If the MCU wanted to provide a Multiple Content Captures containing a
	round-robin switched view of the audience from the three endpoints		round-robin switched view of the audience from the three endpoints
	and the speaker, it could construct the following advertisement:		and the speaker, it could construct the following advertisement:
	+=======================+====================================+		----------------------- ------------------------------------
	| Capture Scene #1 | Description=AustralianConfRoom |		Capture Scene #1 Description=AustralianConfRoom
	+=======================+====================================+		VC1 Description=Audience
	| VC1 | Description=Audience |		CSV(VC1)
	+-----------------------+------------------------------------+		----------------------- ------------------------------------
	| CSV(VC1) | |		Capture Scene #2 Description=ChinaConfRoom
	+=======================+====================================+		VC2 Description=Speaker
	| Capture Scene #2 | Description=ChinaConfRoom |		VC3 Description=Audience
	+=======================+====================================+		CSV(VC2, VC3)
	| VC2 | Description=Speaker |		----------------------- ------------------------------------
	+-----------------------+------------------------------------+		Capture Scene #3 Description=USAConfRoom
	| VC3 | Description=Audience |		VC4 Description=Audience
	+-----------------------+------------------------------------+		CSV(VC4)
	| CSV(VC2, VC3) | |		----------------------- ------------------------------------
	+=======================+====================================+		Capture Scene #4
	| Capture Scene #3 | Description=USAConfRoom |		MCC1(VC1,VC2,VC3,VC4) Policy=RoundRobin:1
	+=======================+====================================+		MaxCaptures=1
	| VC4 | Description=Audience |		EncodingGroup=1
	+-----------------------+------------------------------------+		CSV(MCC1)
	| CSV(VC4) | |		----------------------- ------------------------------------
	+=======================+====================================+
	| Capture Scene #4 | |
	+=======================+====================================+
	| MCC1(VC1,VC2,VC3,VC4) | Policy=RoundRobin:1 |
	| | MaxCaptures=1 |
	| | EncodingGroup=1 |
	+-----------------------+------------------------------------+
	| CSV(MCC1) | |
	+-----------------------+------------------------------------+
	Table 13: Advertisement Sent to Endpoint F - One Encoding		Table 13: Advertisement Sent to Endpoint F - One Encoding
	Alternatively, if the MCU wanted to provide the speaker as one media		Alternatively, if the MCU wanted to provide the speaker as one media
	stream and the audiences as another, it could assign an encoding		stream and the audiences as another, it could assign an encoding
	group to VC2 in Capture Scene 2 and provide a CSV in Capture Scene #4		group to VC2 in Capture Scene 2 and provide a CSV in Capture Scene #4
	as per the example below.		as per the example below.
	+===================+======================================+		------------------- --------------------------------------
	| Capture Scene #1 | Description=AustralianConfRoom |		Capture Scene #1 Description=AustralianConfRoom
	+===================+======================================+		VC1 Description=Audience
	| VC1 | Description=Audience |		CSV(VC1)
	+-------------------+--------------------------------------+		------------------- --------------------------------------
	| CSV(VC1) | |		Capture Scene #2 Description=ChinaConfRoom
	+===================+======================================+		VC2 Description=Speaker
	| Capture Scene #2 | Description=ChinaConfRoom |		EncodingGroup=1
	+===================+======================================+		VC3 Description=Audience
	| VC2 | Description=Speaker |		CSV(VC2, VC3)
	| | EncodingGroup=1 |		------------------- --------------------------------------
	+-------------------+--------------------------------------+		Capture Scene #3 Description=USAConfRoom
	| VC3 | Description=Audience |		VC4 Description=Audience
	+-------------------+--------------------------------------+		CSV(VC4)
	| CSV(VC2, VC3) | |		------------------- --------------------------------------
	+===================+======================================+		Capture Scene #4
	| Capture Scene #3 | Description=USAConfRoom |		MCC1(VC1,VC3,VC4) Policy=RoundRobin:1
	+===================+======================================+		MaxCaptures=1
	| VC4 | Description=Audience |		EncodingGroup=1
	+-------------------+--------------------------------------+		AllowSubset=True
	| CSV(VC4) | |		MCC2(VC2) MaxCaptures=1
	+===================+======================================+		EncodingGroup=1
	| Capture Scene #4 | |		CSV2(MCC1,MCC2)
	+===================+======================================+		------------------- --------------------------------------
	| MCC1(VC1,VC3,VC4) | Policy=RoundRobin:1 |
	| | MaxCaptures=1 |
	| | EncodingGroup=1 |
	| | AllowSubset=True |
	+-------------------+--------------------------------------+
	| MCC2(VC2) | MaxCaptures=1 |
	| | EncodingGroup=1 |
	+-------------------+--------------------------------------+
	| CSV2(MCC1,MCC2) | |
	+-------------------+--------------------------------------+
	Table 14: Advertisement Sent to Endpoint F - Two Encodings		Table 14: Advertisement Sent to Endpoint F - Two Encodings
	Therefore, a Consumer could choose whether or not to have a separate		Therefore, a Consumer could choose whether or not to have a separate
	speaker-related stream and could choose which endpoints to see. If		speaker-related stream and could choose which endpoints to see. If
	it wanted the second stream but not the Australian conference room,		it wanted the second stream but not the Australian conference room,
	it could indicate the following captures in the Configure message:		it could indicate the following captures in the Configure message:
	+---------------+----------+		--------------- ----------
	| MCC1(VC3,VC4) | Encoding |		MCC1(VC3,VC4) Encoding
	+---------------+----------+		VC2 Encoding
	| VC2 | Encoding |		--------------- ----------
	+---------------+----------+
	Table 15: MCU Case:		Table 15: MCU Case:
	Consumer Response		Consumer Response
	12.3.2. Several MCCs in the Same Advertisement		12.3.2. Several MCCs in the Same Advertisement
	Multiple MCCs can be used where multiple streams are used to carry		Multiple MCCs can be used where multiple streams are used to carry
	media from multiple endpoints. For example:		media from multiple endpoints. For example:
	A conference has three endpoints D, E, and F. Each endpoint has		A conference has three endpoints D, E, and F. Each endpoint has
	three video captures covering the left, middle, and right regions of		three video captures covering the left, middle, and right regions of
	each conference room. The MCU receives the following advertisements		each conference room. The MCU receives the following advertisements
	from D and E.		from D and E.
	+==================+================================+		------------------ --------------------------------
	| Capture Scene #1 | Description=AustralianConfRoom |		Capture Scene #1 Description=AustralianConfRoom
	+==================+================================+		VC1 CaptureArea=Left
	| VC1 | CaptureArea=Left |		EncodingGroup=1
	+------------------+--------------------------------+		VC2 CaptureArea=Center
	| | EncodingGroup=1 |		EncodingGroup=1
	+------------------+--------------------------------+		VC3 CaptureArea=Right
	| VC2 | CaptureArea=Center |		EncodingGroup=1
	+------------------+--------------------------------+		CSV(VC1,VC2,VC3)
	| | EncodingGroup=1 |		------------------ --------------------------------
	+------------------+--------------------------------+
	| VC3 | CaptureArea=Right |
	+------------------+--------------------------------+
	| | EncodingGroup=1 |
	+------------------+--------------------------------+
	| CSV(VC1,VC2,VC3) | |
	+------------------+--------------------------------+
	Table 16: Advertisement Received from Endpoint D		Table 16: Advertisement Received from Endpoint D
	+==================+===========================+		------------------ ---------------------------
	| Capture Scene #1 | Description=ChinaConfRoom |		Capture Scene #1 Description=ChinaConfRoom
	+==================+===========================+		VC1 CaptureArea=Left
	| VC1 | CaptureArea=Left |		EncodingGroup=1
	+------------------+---------------------------+		VC2 CaptureArea=Center
	| | EncodingGroup=1 |		EncodingGroup=1
	+------------------+---------------------------+		VC3 CaptureArea=Right
	| VC2 | CaptureArea=Center |		EncodingGroup=1
	+------------------+---------------------------+		CSV(VC1,VC2,VC3)
	| | EncodingGroup=1 |		------------------ ---------------------------
	+------------------+---------------------------+
	| VC3 | CaptureArea=Right |
	+------------------+---------------------------+
	| | EncodingGroup=1 |
	+------------------+---------------------------+
	| CSV(VC1,VC2,VC3) | |
	+------------------+---------------------------+
	Table 17: Advertisement Received from Endpoint E		Table 17: Advertisement Received from Endpoint E
	The MCU wants to offer Endpoint F three Capture Encodings. Each		The MCU wants to offer Endpoint F three Capture Encodings. Each
	Capture Encoding would contain all the Captures from either Endpoint		Capture Encoding would contain all the Captures from either Endpoint
	D or Endpoint E, depending on the active speaker. The MCU sends the		D or Endpoint E, depending on the active speaker. The MCU sends the
	following Advertisement:		following Advertisement:
	+=====================+==========================================+		--------------------- ------------------------------------------
	| Capture Scene #1 | Description=AustralianConfRoom |		Capture Scene #1 Description=AustralianConfRoom
	+=====================+==========================================+		VC1
	| VC1 | |		VC2
	+---------------------+------------------------------------------+		VC3
	| VC2 | |		CSV(VC1,VC2,VC3)
	+---------------------+------------------------------------------+		--------------------- ------------------------------------------
	| VC3 | |		Capture Scene #2 Description=ChinaConfRoom
	+---------------------+------------------------------------------+		VC4
	| CSV(VC1,VC2,VC3) | |		VC5
	+=====================+==========================================+		VC6
	| Capture Scene #2 | Description=ChinaConfRoom |		CSV(VC4,VC5,VC6)
	+=====================+==========================================+		--------------------- ------------------------------------------
	| VC4 | |		Capture Scene #3
	+---------------------+------------------------------------------+		MCC1(VC1,VC4) CaptureArea=Left
	| VC5 | |		MaxCaptures=1
	+---------------------+------------------------------------------+		SynchronizationID=1
	| VC6 | |		EncodingGroup=1
	+---------------------+------------------------------------------+		MCC2(VC2,VC5) CaptureArea=Center
	| CSV(VC4,VC5,VC6) | |		MaxCaptures=1
	+=====================+==========================================+		SynchronizationID=1
	| Capture Scene #3 | |		EncodingGroup=1
	+=====================+==========================================+		MCC3(VC3,VC6) CaptureArea=Right
	| MCC1(VC1,VC4) | CaptureArea=Left |		MaxCaptures=1
	| | MaxCaptures=1 |		SynchronizationID=1
	| | SynchronizationID=1 |		EncodingGroup=1
	| | EncodingGroup=1 |		CSV(MCC1,MCC2,MCC3)
	+---------------------+------------------------------------------+		--------------------- ------------------------------------------
	| MCC2(VC2,VC5) | CaptureArea=Center |
	| | MaxCaptures=1 |
	| | SynchronizationID=1 |
	| | EncodingGroup=1 |
	+---------------------+------------------------------------------+
	| MCC3(VC3,VC6) | CaptureArea=Right |
	| | MaxCaptures=1 |
	| | SynchronizationID=1 |
	| | EncodingGroup=1 |
	+---------------------+------------------------------------------+
	| CSV(MCC1,MCC2,MCC3) | |
	+---------------------+------------------------------------------+
	Table 18: Advertisement Sent to Endpoint F		Table 18: Advertisement Sent to Endpoint F
	12.3.3. Heterogeneous Conference with Switching and Composition		12.3.3. Heterogeneous Conference with Switching and Composition
	Consider a conference between endpoints with the following		Consider a conference between endpoints with the following
	characteristics:		characteristics:
	Endpoint A - 4 screens, 3 cameras		Endpoint A - 4 screens, 3 cameras
	skipping to change at line 2715 ¶		skipping to change at line 2597 ¶
	One of the points of this example is that endpoints A and B each want		One of the points of this example is that endpoints A and B each want
	to receive three capture encodings for their large display areas, and		to receive three capture encodings for their large display areas, and
	nine encodings for their smaller areas. A and B are be able to each		nine encodings for their smaller areas. A and B are be able to each
	send the same Configure message to the MCU, and each receive the same		send the same Configure message to the MCU, and each receive the same
	conceptual Media Captures from the MCU. The differences are in how		conceptual Media Captures from the MCU. The differences are in how
	they are rendered and are purely a local matter at A and B.		they are rendered and are purely a local matter at A and B.
	The Advertisements for such a scenario are described below.		The Advertisements for such a scenario are described below.
	+=====================+========================+		--------------------- ------------------------
	| Capture Scene #1 | Description=Endpoint x |		Capture Scene #1 Description=Endpoint x
	+=====================+========================+		VC1 EncodingGroup=1
	| VC1 | EncodingGroup=1 |		VC2 EncodingGroup=1
	+---------------------+------------------------+		VC3 EncodingGroup=1
	| VC2 | EncodingGroup=1 |		AC1 EncodingGroup=2
	+---------------------+------------------------+		CSV1(VC1, VC2, VC3)
	| VC3 | EncodingGroup=1 |		CSV2(AC1)
	+---------------------+------------------------+		--------------------- ------------------------
	| AC1 | EncodingGroup=2 |
	+---------------------+------------------------+
	| CSV1(VC1, VC2, VC3) | |
	+---------------------+------------------------+
	| CSV2(AC1) | |
	+---------------------+------------------------+
	Table 19: Advertisement Received at the MCU		Table 19: Advertisement Received at the MCU
	from Endpoints A to D		from Endpoints A to D
	+==================+========================+		------------------ ------------------------
	| Capture Scene #1 | Description=Endpoint y |		Capture Scene #1 Description=Endpoint y
	+==================+========================+		VC1 EncodingGroup=1
	| VC1 | EncodingGroup=1 |		AC1 EncodingGroup=2
	+------------------+------------------------+		CSV1(VC1)
	| AC1 | EncodingGroup=2 |		CSV2(AC1)
	+------------------+------------------------+		------------------ ------------------------
	| CSV1(VC1) | |
	+------------------+------------------------+
	| CSV2(AC1) | |
	+------------------+------------------------+
	Table 20: Advertisement Received at the		Table 20: Advertisement Received at the
	MCU from Endpoints E to G		MCU from Endpoints E to G
	Rather than considering what is displayed, CLUE concentrates more on		Rather than considering what is displayed, CLUE concentrates more on
	what the MCU sends. The MCU doesn't know anything about the number		what the MCU sends. The MCU doesn't know anything about the number
	of screens an endpoint has.		of screens an endpoint has.
	As Endpoints A to D each advertise that three Captures make up a		As Endpoints A to D each advertise that three Captures make up a
	Capture Scene, the MCU offers these in a "site switching" mode. That		Capture Scene, the MCU offers these in a "site switching" mode. That
	is, there are three Multiple Content Captures (and Capture Encodings)		is, there are three Multiple Content Captures (and Capture Encodings)
	each switching between Endpoints. The MCU switches in the applicable		each switching between Endpoints. The MCU switches in the applicable
	media into the stream based on voice activity. Endpoint A will not		media into the stream based on voice activity. Endpoint A will not
	see a capture from itself.		see a capture from itself.
	Using the MCC concept, the MCU would send the following Advertisement		Using the MCC concept, the MCU would send the following Advertisement
	to Endpoint A:		to Endpoint A:
	+=====================+========================+		--------------------- ------------------------
	| Capture Scene #1 | Description=Endpoint B |		Capture Scene #1 Description=Endpoint B
	+=====================+========================+		VC4 CaptureArea=Left
	| VC4 | CaptureArea=Left |		VC5 CaptureArea=Center
	+---------------------+------------------------+		VC6 CaptureArea=Right
	| VC5 | CaptureArea=Center |		AC1
	+---------------------+------------------------+		CSV(VC4,VC5,VC6)
	| VC6 | CaptureArea=Right |		CSV(AC1)
	+---------------------+------------------------+		--------------------- ------------------------
	| AC1 | |		Capture Scene #2 Description=Endpoint C
	+---------------------+------------------------+		VC7 CaptureArea=Left
	| CSV(VC4,VC5,VC6) | |		VC8 CaptureArea=Center
	+---------------------+------------------------+		VC9 CaptureArea=Right
	| CSV(AC1) | |		AC2
	+=====================+========================+		CSV(VC7,VC8,VC9)
	| Capture Scene #2 | Description=Endpoint C |		CSV(AC2)
	+=====================+========================+		--------------------- ------------------------
	| VC7 | CaptureArea=Left |		Capture Scene #3 Description=Endpoint D
	+---------------------+------------------------+		VC10 CaptureArea=Left
	| VC8 | CaptureArea=Center |		VC11 CaptureArea=Center
	+---------------------+------------------------+		VC12 CaptureArea=Right
	| VC9 | CaptureArea=Right |		AC3
	+---------------------+------------------------+		CSV(VC10,VC11,VC12)
	| AC2 | |		CSV(AC3)
	+---------------------+------------------------+		--------------------- ------------------------
	| CSV(VC7,VC8,VC9) | |		Capture Scene #4 Description=Endpoint E
	+---------------------+------------------------+		VC13
	| CSV(AC2) | |		AC4
	+=====================+========================+		CSV(VC13)
	| Capture Scene #3 | Description=Endpoint D |		CSV(AC4)
	+=====================+========================+		--------------------- ------------------------
	| VC10 | CaptureArea=Left |		Capture Scene #5 Description=Endpoint F
	+---------------------+------------------------+		VC14
	| VC11 | CaptureArea=Center |		AC5
	+---------------------+------------------------+		CSV(VC14)
	| VC12 | CaptureArea=Right |		CSV(AC5)
	+---------------------+------------------------+		--------------------- ------------------------
	| AC3 | |		Capture Scene #6 Description=Endpoint G
	+---------------------+------------------------+		VC15
	| CSV(VC10,VC11,VC12) | |		AC6
	+---------------------+------------------------+		CSV(VC15)
	| CSV(AC3) | |		CSV(AC6)
	+=====================+========================+		--------------------- ------------------------
	| Capture Scene #4 | Description=Endpoint E |
	+=====================+========================+
	| VC13 | |
	+---------------------+------------------------+
	| AC4 | |
	+---------------------+------------------------+
	| CSV(VC13) | |
	+---------------------+------------------------+
	| CSV(AC4) | |
	+=====================+========================+
	| Capture Scene #5 | Description=Endpoint F |
	+=====================+========================+
	| VC14 | |
	+---------------------+------------------------+
	| AC5 | |
	+---------------------+------------------------+
	| CSV(VC14) | |
	+---------------------+------------------------+
	| CSV(AC5) | |
	+=====================+========================+
	| Capture Scene #6 | Description=Endpoint G |
	+=====================+========================+
	| VC15 | |
	+---------------------+------------------------+
	| AC6 | |
	+---------------------+------------------------+
	| CSV(VC15) | |
	+---------------------+------------------------+
	| CSV(AC6) | |
	+---------------------+------------------------+
	Table 21: Advertisement Sent to Endpoint A -		Table 21: Advertisement Sent to Endpoint A -
	Source Part		Source Part
	The above part of the Advertisement presents information about the		The above part of the Advertisement presents information about the
	sources to the MCC. The information is effectively the same as the		sources to the MCC. The information is effectively the same as the
	received Advertisements, except that there are no Capture Encodings		received Advertisements, except that there are no Capture Encodings
	associated with them and the identities have been renumbered.		associated with them and the identities have been renumbered.
	In addition to the source Capture information, the MCU advertises		In addition to the source Capture information, the MCU advertises
	site switching of Endpoints B to G in three streams.		site switching of Endpoints B to G in three streams.
	+===================+===============================================+		------------------- -----------------------------------------------
	| Capture Scene #7 | Description=Output3streammix |		Capture Scene #7 Description=Output3streammix
	+===================+===============================================+		MCC1(VC4,VC7,VC10, CaptureArea=Left
	|MCC1(VC4,VC7,VC10, | CaptureArea=Left |		VC13) MaxCaptures=1
	| VC13) | MaxCaptures=1 |		SynchronizationID=1
	| | SynchronizationID=1 |		Policy=SoundLevel:0
	| | Policy=SoundLevel:0 |		EncodingGroup=1
	| | EncodingGroup=1 |		MCC2(VC5,VC8,VC11, CaptureArea=Center
	+-------------------+-----------------------------------------------+		VC14) MaxCaptures=1
	|MCC2(VC5,VC8,VC11, | CaptureArea=Center |		SynchronizationID=1
	| VC14) | MaxCaptures=1 |		Policy=SoundLevel:0
	| | SynchronizationID=1 |		EncodingGroup=1
	| | Policy=SoundLevel:0 |		MCC3(VC6,VC9,VC12, CaptureArea=Right
	| | EncodingGroup=1 |		VC15) MaxCaptures=1
	+-------------------+-----------------------------------------------+		SynchronizationID=1
	|MCC3(VC6,VC9,VC12, | CaptureArea=Right |		Policy=SoundLevel:0
	| VC15) | MaxCaptures=1 |		EncodingGroup=1
	| | SynchronizationID=1 |		MCC4() (for audio) CaptureArea=whole scene
	| | Policy=SoundLevel:0 |		MaxCaptures=1
	| | EncodingGroup=1 |		Policy=SoundLevel:0
	+-------------------+-----------------------------------------------+		EncodingGroup=2
	|MCC4() (for audio) | CaptureArea=whole scene |		MCC5() (for audio) CaptureArea=whole scene
	| | MaxCaptures=1 |		MaxCaptures=1
	| | Policy=SoundLevel:0 |		Policy=SoundLevel:1
	| | EncodingGroup=2 |		EncodingGroup=2
	+-------------------+-----------------------------------------------+		MCC6() (for audio) CaptureArea=whole scene
	|MCC5() (for audio) | CaptureArea=whole scene |		MaxCaptures=1
	| | MaxCaptures=1 |		Policy=SoundLevel:2
	| | Policy=SoundLevel:1 |		EncodingGroup=2
	| | EncodingGroup=2 |		MCC7() (for audio) CaptureArea=whole scene
	+-------------------+-----------------------------------------------+		MaxCaptures=1
	|MCC6() (for audio) | CaptureArea=whole scene |		Policy=SoundLevel:3
	| | MaxCaptures=1 |		EncodingGroup=2
	| | Policy=SoundLevel:2 |		CSV(MCC1,MCC2,MCC3)
	| | EncodingGroup=2 |		CSV(MCC4,MCC5,MCC6,
	+-------------------+-----------------------------------------------+		MCC7)
	|MCC7() (for audio) | CaptureArea=whole scene |		------------------- -----------------------------------------------
	| | MaxCaptures=1 |
	| | Policy=SoundLevel:3 |
	| | EncodingGroup=2 |
	+-------------------+-----------------------------------------------+
	|CSV(MCC1,MCC2,MCC3)| |
	+-------------------+-----------------------------------------------+
	|CSV(MCC4,MCC5,MCC6,| |
	| MCC7) | |
	+-------------------+-----------------------------------------------+
	Table 22: Advertisement Sent to Endpoint A - Switching Part		Table 22: Advertisement Sent to Endpoint A - Switching Part
	The above part describes the three main switched streams that relate		The above part describes the three main switched streams that relate
	to site switching. MaxCaptures=1 indicates that only one Capture		to site switching. MaxCaptures=1 indicates that only one Capture
	from the MCC is sent at a particular time. SynchronizationID=1		from the MCC is sent at a particular time. SynchronizationID=1
	indicates that the source sending is synchronized. The provider can		indicates that the source sending is synchronized. The provider can
	choose to group together VC13, VC14, and VC15 for the purpose of		choose to group together VC13, VC14, and VC15 for the purpose of
	switching according to the SynchronizationID. Therefore, when the		switching according to the SynchronizationID. Therefore, when the
	provider switches one of them into an MCC, it can also switch the		provider switches one of them into an MCC, it can also switch the
	skipping to change at line 2916 ¶		skipping to change at line 2749 ¶
	All the audio for the conference is included in Scene #7. There		All the audio for the conference is included in Scene #7. There
	isn't necessarily a one-to-one relation between any audio capture and		isn't necessarily a one-to-one relation between any audio capture and
	video capture in this scene. Typically, a change in the loudest		video capture in this scene. Typically, a change in the loudest
	talker will cause the MCU to switch the audio streams more quickly		talker will cause the MCU to switch the audio streams more quickly
	than switching video streams.		than switching video streams.
	The MCU can also supply nine media streams showing the active and		The MCU can also supply nine media streams showing the active and
	previous eight speakers. It includes the following in the		previous eight speakers. It includes the following in the
	Advertisement:		Advertisement:
	+========================+===========================+		------------------------ ---------------------------
	| Capture Scene #8 | Description=Output9stream |		Capture Scene #8 Description=Output9stream
	+========================+===========================+		MCC8(VC4,VC5,VC6,VC7, MaxCaptures=1
	| MCC8(VC4,VC5,VC6,VC7, | MaxCaptures=1 |		VC8,VC9,VC10,VC11, Policy=SoundLevel:0
	| VC8,VC9,VC10,VC11, | Policy=SoundLevel:0 |		VC12,VC13,VC14,VC15) EncodingGroup=1
	| VC12,VC13,VC14,VC15) | EncodingGroup=1 |		MCC9(VC4,VC5,VC6,VC7, MaxCaptures=1
	+------------------------+---------------------------+		VC8,VC9,VC10,VC11, Policy=SoundLevel:1
	| MCC9(VC4,VC5,VC6,VC7, | MaxCaptures=1 |		VC12,VC13,VC14,VC15) EncodingGroup=1
	| VC8,VC9,VC10,VC11, | Policy=SoundLevel:1 |		------------------------ ---------------------------
	| VC12,VC13,VC14,VC15) | EncodingGroup=1 |		to to
	+========================+===========================+		MCC16(VC4,VC5,VC6,VC7, MaxCaptures=1
	| to | to |		VC8,VC9,VC10,VC11, Policy=SoundLevel:8
	+========================+===========================+		VC12,VC13,VC14,VC15) EncodingGroup=1
	| MCC16(VC4,VC5,VC6,VC7, | MaxCaptures=1 |		CSV(MCC8,MCC9,MCC10,
	| VC8,VC9,VC10,VC11, | Policy=SoundLevel:8 |		MCC11,MCC12,MCC13,
	| VC12,VC13,VC14,VC15) | EncodingGroup=1 |		MCC14,MCC15,MCC16)
	+------------------------+---------------------------+		------------------------ ---------------------------
	| CSV(MCC8,MCC9,MCC10, | |
	| MCC11,MCC12,MCC13, | |
	| MCC14,MCC15,MCC16) | |
	+------------------------+---------------------------+
	Table 23: Advertisement Sent to Endpoint A -		Table 23: Advertisement Sent to Endpoint A -
	9 Switched Part		9 Switched Part
	The above part indicates that there are nine capture encodings. Each		The above part indicates that there are nine capture encodings. Each
	of the Capture Encodings may contain any captures from any source		of the Capture Encodings may contain any captures from any source
	site with a maximum of one Capture at a time. Which Capture is		site with a maximum of one Capture at a time. Which Capture is
	present is determined by the policy. The MCCs in this scene do not		present is determined by the policy. The MCCs in this scene do not
	have any spatial attributes.		have any spatial attributes.
	Note: The Provider alternatively could provide each of the MCCs above		Note: The Provider alternatively could provide each of the MCCs above
	in its own Capture Scene.		in its own Capture Scene.
	If the MCU wanted to provide a composed Capture Encoding containing		If the MCU wanted to provide a composed Capture Encoding containing
	all of the nine captures, it could advertise in addition:		all of the nine captures, it could advertise in addition:
	+========================+=======================+		------------------------ -----------------------
	| Capture Scene #9 | Description=NineTiles |		Capture Scene #9 Description=NineTiles
	+========================+=======================+		MCC13(MCC8,MCC9,MCC10, MaxCaptures=9
	| MCC13(MCC8,MCC9,MCC10, | MaxCaptures=9 |		MCC11,MCC12,MCC13, EncodingGroup=1
	| MCC11,MCC12,MCC13, | EncodingGroup=1 |		MCC14,MCC15,MCC16)
	| MCC14,MCC15,MCC16) | |		CSV(MCC13)
	+------------------------+-----------------------+		------------------------ -----------------------
	| CSV(MCC13) | |
	+------------------------+-----------------------+
	Table 24: Advertisement Sent to Endpoint A -		Table 24: Advertisement Sent to Endpoint A -
	9 Composed Part		9 Composed Part
	As MaxCaptures is 9, it indicates that the capture encoding contains		As MaxCaptures is 9, it indicates that the capture encoding contains
	information from nine sources at a time.		information from nine sources at a time.
	The Advertisement to Endpoint B is identical to the above, other than		The Advertisement to Endpoint B is identical to the above, other than
	the fact that captures from Endpoint A would be added and the		the fact that captures from Endpoint A would be added and the
	captures from Endpoint B would be removed. Whether the Captures are		captures from Endpoint B would be removed. Whether the Captures are
	skipping to change at line 3008 ¶		skipping to change at line 2835 ¶
	Endpoint C - 1 screen, 1 camera		Endpoint C - 1 screen, 1 camera
	This example focuses on what the user at Endpoint C sees. The user		This example focuses on what the user at Endpoint C sees. The user
	would like to see the video capture of the current talker, without		would like to see the video capture of the current talker, without
	composing it with any other video capture. In this example, Endpoint		composing it with any other video capture. In this example, Endpoint
	C is capable of receiving only a single video stream. The following		C is capable of receiving only a single video stream. The following
	tables describe advertisements from Endpoints A and B to the MCU, and		tables describe advertisements from Endpoints A and B to the MCU, and
	from the MCU to Endpoint C, that can be used to accomplish this.		from the MCU to Endpoint C, that can be used to accomplish this.
	+===================+===================================+		------------------- -----------------------------------
	| Capture Scene #1 | Description=Endpoint x |		Capture Scene #1 Description=Endpoint x
	+===================+===================================+		VC1 CaptureArea=Left
	| VC1 | CaptureArea=Left |		EncodingGroup=1
	| | EncodingGroup=1 |		VC2 CaptureArea=Center
	+-------------------+-----------------------------------+		EncodingGroup=1
	| VC2 | CaptureArea=Center |		VC3 CaptureArea=Right
	| | EncodingGroup=1 |		EncodingGroup=1
	+-------------------+-----------------------------------+		MCC1(VC1,VC2,VC3) MaxCaptures=1
	| VC3 | CaptureArea=Right |		CaptureArea=whole scene
	| | EncodingGroup=1 |		Policy=SoundLevel:0
	+-------------------+-----------------------------------+		EncodingGroup=1
	| MCC1(VC1,VC2,VC3) | MaxCaptures=1 |		AC1 CaptureArea=whole scene
	| | CaptureArea=whole scene |		EncodingGroup=2
	| | Policy=SoundLevel:0 |		CSV1(VC1, VC2,
	| | EncodingGroup=1 |		VC3)
	+-------------------+-----------------------------------+		CSV2(MCC1)
	| AC1 | CaptureArea=whole scene |		CSV3(AC1)
	| | EncodingGroup=2 |		------------------- -----------------------------------
	+-------------------+-----------------------------------+
	| CSV1(VC1, VC2, | |
	| VC3) | |
	+-------------------+-----------------------------------+
	| CSV2(MCC1) | |
	+-------------------+-----------------------------------+
	| CSV3(AC1) | |
	+-------------------+-----------------------------------+
	Table 25: Advertisement Received at the MCU from		Table 25: Advertisement Received at the MCU from
	Endpoints A and B		Endpoints A and B
	Endpoints A and B are advertising each individual video capture, and		Endpoints A and B are advertising each individual video capture, and
	also a switched capture MCC1 that switches between the other three		also a switched capture MCC1 that switches between the other three
	based on who is the active talker. These endpoints do not advertise		based on who is the active talker. These endpoints do not advertise
	distinct audio captures associated with each individual video		distinct audio captures associated with each individual video
	capture, so it would be impossible for the MCU (as a media consumer)		capture, so it would be impossible for the MCU (as a media consumer)
	to make its own determination of which video capture is the active		to make its own determination of which video capture is the active
	talker based just on information in the audio streams.		talker based just on information in the audio streams.
	+======================+==========================================+		---------------------- ------------------------------------------
	| Capture Scene #1 | Description=conference |		Capture Scene #1 Description=conference
	+======================+==========================================+		MCC1() CaptureArea=Left
	| MCC1() | CaptureArea=Left |		MaxCaptures=1
	| | MaxCaptures=1 |		SynchronizationID=1
	| | SynchronizationID=1 |		Policy=SoundLevel:0
	| | Policy=SoundLevel:0 |		EncodingGroup=1
	| | EncodingGroup=1 |		MCC2() CaptureArea=Center
	+----------------------+------------------------------------------+		MaxCaptures=1
	| MCC2() | CaptureArea=Center |		SynchronizationID=1
	| | MaxCaptures=1 |		Policy=SoundLevel:0
	| | SynchronizationID=1 |		EncodingGroup=1
	| | Policy=SoundLevel:0 |		MCC3() CaptureArea=Right
	| | EncodingGroup=1 |		MaxCaptures=1
	+----------------------+------------------------------------------+		SynchronizationID=1
	| MCC3() | CaptureArea=Right |		Policy=SoundLevel:0
	| | MaxCaptures=1 |		EncodingGroup=1
	| | SynchronizationID=1 |		MCC4() CaptureArea=whole scene
	| | Policy=SoundLevel:0 |		MaxCaptures=1
	| | EncodingGroup=1 |		Policy=SoundLevel:0
	+----------------------+------------------------------------------+		EncodingGroup=1
	| MCC4() | CaptureArea=whole scene |		MCC5() (for audio) CaptureArea=whole scene
	| | MaxCaptures=1 |		MaxCaptures=1
	| | Policy=SoundLevel:0 |		Policy=SoundLevel:0
	| | EncodingGroup=1 |		EncodingGroup=2
	+----------------------+------------------------------------------+		MCC6() (for audio) CaptureArea=whole scene
	| MCC5() (for audio) | CaptureArea=whole scene |		MaxCaptures=1
	| | MaxCaptures=1 |		Policy=SoundLevel:1
	| | Policy=SoundLevel:0 |		EncodingGroup=2
	| | EncodingGroup=2 |		CSV1(MCC1,MCC2,MCC3)
	+----------------------+------------------------------------------+		CSV2(MCC4)
	| MCC6() (for audio) | CaptureArea=whole scene |		CSV3(MCC5,MCC6)
	| | MaxCaptures=1 |		---------------------- ------------------------------------------
	| | Policy=SoundLevel:1 |
	| | EncodingGroup=2 |
	+----------------------+------------------------------------------+
	| CSV1(MCC1,MCC2,MCC3) | |
	+----------------------+------------------------------------------+
	| CSV2(MCC4) | |
	+----------------------+------------------------------------------+
	| CSV3(MCC5,MCC6) | |
	+----------------------+------------------------------------------+
	Table 26: Advertisement Sent from the MCU to Endpoint C		Table 26: Advertisement Sent from the MCU to Endpoint C
	The MCU advertises one scene, with four video MCCs. Three of them in		The MCU advertises one scene, with four video MCCs. Three of them in
	CSV1 give a left, center, and right view of the conference, with site		CSV1 give a left, center, and right view of the conference, with site
	switching. MCC4 provides a single video capture representing a view		switching. MCC4 provides a single video capture representing a view
	of the whole conference. The MCU intends for MCC4 to be switched		of the whole conference. The MCU intends for MCC4 to be switched
	between all the other original source captures. In this example,		between all the other original source captures. In this example,
	advertisement of the MCU is not giving all the information about all		advertisement of the MCU is not giving all the information about all
	the other endpoints' scenes and which of those captures are included		the other endpoints' scenes and which of those captures are included
End of changes. 26 change blocks.
	590 lines changed or deleted		400 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/