Re: [clue] Capture ID scope in a Configure

Yes, can we have Roberta's text (or similar) in the framework so its 
100% clear?

Christian

On 4/04/2013 5:49 AM, Duckworth, Mark wrote:
> +1
>
>> -----Original Message-----
>> From: clue-bounces@ietf.org [mailto:clue-bounces@ietf.org] On Behalf Of
>> Paul Kyzivat
>> Sent: Wednesday, April 03, 2013 2:46 PM
>> To: clue@ietf.org
>> Subject: Re: [clue] Capture ID scope in a Configure
>>
>> On 4/4/13 1:22 AM, Roberta Presta wrote:
>>> Hi all,
>>>
>>> it seems to me that capture scenes and capture scene entries are
>>> semantical abstractions that are useful only to make a media provider
>>> able to show the organization of the available media captures to the
>>> media consumer via an advertisement message.
>>> I don't believe they should be used within a configure message.
>>> The media consumer should specify only *capture encodings*, i.e., the
>>> associations of a media capture with an individual encoding with the
>>> desired parameters.
>>> If the media consumer wants both VC1 encoded with ENC0 and VC1
>> encoded
>>> with ENC1, he should put in the configure message the specification of
>>> two capture encodings.
>>> <captureEncoding id=...>
>>>    <mediaCaptureID>VC1...
>>>    <encodingID>ENC1...
>>>    <encodingParameters>...
>>> If he wants all the captures within a capture scene, he should specify
>>> in the configure a capture encoding for each capture of the scene,
>>> since he should be forced to associate a desired encoding to each
>>> desired capture.
>>> Do you think this interpretation is correct?
>> Yes, this is exactly what I am thinking!
>>
>> 	Thanks,
>> 	Paul
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>