Re: [MMUSIC] The rtp-duplication related drafts

On Jan 3, 2013, at 10:41 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> On 1/3/13 9:47 PM, Ali C. Begen (abegen) wrote:
>> Thanks for the review.
>> 
>> On Jan 3, 2013, at 9:29 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>> 
>>> Ali,
>>> 
>>> On 1/3/13 5:31 PM, Ali C. Begen (abegen) wrote:
>>>> Hi everyone,
>>>> 
>>>> The following two drafts have been adopted by MMUSIC a while ago and the main draft discussing the RTP duplication issues is being finalized in AVTEXT (this was also adopted as a WG item a while ago). It is simply waiting for the WG to make a decision on the srcname proposal.
>>>> 
>>>> http://datatracker.ietf.org/doc/draft-ietf-mmusic-delayed-duplication/
>>>> http://datatracker.ietf.org/doc/draft-ietf-mmusic-duplication-grouping/
>>> 
>>> I have a question about these:
>>> 
>>> Each example shows only one group. But couldn't there be multiple duplication groups?
>>> 
>> There could be.
>> 
>>> If so, the current proposal has no mechanism for specifying separate duplication-delay for each group.
>>> 
>> 
>> a=duplication-delay:X could be specified in each media session. For example:
>> 
>> 	a=rtpmap:100 MP2T/90000
>>         a=ssrc:1000 cname:ch1@example.com
>>         a=ssrc:1010 cname:ch1@example.com
>>         a=ssrc-group:DUP 1000 1010
>>         a=duplication-delay:100
>>         a=mid:Group1
>> 	a=rtpmap:101 MP2T/90000
>>         a=ssrc:2000 cname:ch2@example.com
>>         a=ssrc:2010 cname:ch2@example.com
>>         a=ssrc-group:DUP 2000 2010
>>         a=duplication-delay:150
>>         a=mid:Group2
> 
> This makes the attributes very order dependent. If this is intended, then I think you need more words to say that. Currently it says:
> 
>   If used as a media-level
>   attribute, it MUST be used with the 'ssrc-group' attribute and "DUP"
>   grouping semantics...

My mistake, did not copy/paste the whole thing.

	m=video 30000 RTP/AVP 100
        c=IN IP4 233.252.0.1/127
        a=source-filter:incl IN IP4 233.252.0.1 198.51.100.1
        a=rtpmap:100 MP2T/90000
        a=ssrc:1000 cname:ch1@example.com
        a=ssrc:1010 cname:ch1@example.com
        a=ssrc-group:DUP 1000 1010
        a=duplication-delay:100
        a=mid:Group1
	m=video 40000 RTP/AVP 101
        c=IN IP4 233.252.0.2/127
        a=source-filter:incl IN IP4 233.252.0.2 198.51.100.1
        a=rtpmap:101 MP2T/90000
        a=ssrc:2000 cname:ch2@example.com
        a=ssrc:2010 cname:ch2@example.com
        a=ssrc-group:DUP 2000 2010
        a=duplication-delay:150
        a=mid:Group2

so there is one duplication-delay attribute in each media session (specified by a m= line). It does not matter whether it is before or after the ssrc-group line. It is OK as long as it is somewhere before the next m line.

> 
> What does "used with" mean? I assumed it simply meant that both attributes had to be present in the media section. But what you are saying now says that there is some very specific ordering required. E.g. that the a=duplicaation-delay must follow the a=ssrc-group:DUP to which it applies, and precede any other a=ssrc-group:DUP. This is possible, but ugly to specify.

I hope it is clear now?

> 
>> (The SSRC need not be different as SSRC only need to be unique within each media session)
>> 
>> For the non-ssrc grouping, your comment holds. It does not support specifying different delay values for different groups. Do you think we should support distinct delay values for different groups (which probably means duplication-delay attribute has to be media-level only)?
> 
> I don't know. Nothing seems appealing.
> 
> 	Thanks,
> 	Paul
> 
>> -acbegen
>> 
>>> 	Thanks,
>>> 	Paul
>>> 
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>> 
>> 
> 