Hi Philippe, Thanks for the review. Below I try to answer your questions. philippe.gentric@philips.com wrote:
I can agree that at least the following bullet:AVTers, authors, I have found this draft pretty advanced, I have a few questions there is the text related to parameter sets that I do not fully understand, it is distributed across 1.2 (which is fine) and 6.1 at 8.4 and I suspect section 6.1 needs to be revisited/merged due to the new dedicated section 8.4 ?
Yes, that is what we try to express in section 8.4. Plus a few things other in regards to how to add parameter sets to avoid problems, and the usage of reliable protocols. I will take your input that it is hard to read and try to structure the section better.
both in section 6.1 and section 8.4 there is the concept of:
"an RTP session whose parameter sets were already changed by control protocol messages during the lifetime of the RTP session"
Now apart from the fact that there seem to be a duplication here between 6.1 and 8.4,
I have to admit this got me a headache to understand (and actually I am not sure I got it ?)
Can we strcuture this a bit by explaining that there are 3 ways to send parameters sets:
(1) out of band before RTP session starts
(2) out of band during RTP session
(3) in band (of course, during RTP session)
If yes , Would it be possible that what you want to express is that:
(A) parameter sets are transmitted using either (1) or (3) or (1+2) or (1+3),
(B) (1) and (1+2) are the RECOMMENDED way to do it
(C) (3) and (1+3) are only for some specific applications and are NOT RECOMMENDED
(D) in all cases (2) and (3) MUST NOT be used together in the same session
Is this is what you wanted to express ?
I will take care of this.regards, PS: in section 8.4 there is a typo in the word "specificaion"