[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [AVT] Comments on draft-versteeg-avt-rapid-synchronization-for-rtp-01
On Nov 10, 2008, at 1:10 PM, Roni Even wrote:
Hi,
I reviewed the draft.
My first impression was that the intention was to have a general
mechanism but when reading the text it looks to me that you are
trying to address only MPEG2-TS based on the first paragraph of
section 6. Do you see it as a general solution or only for MPEG2-TS.
If it intends to be a general mechanism the text about MPEG2-TS can
be an appendix.
In section 6.1 you discuss the information that is not part of the
burst RTP stream (TSRAP). A similar information may be the parameter
sets in H.264. You suggest an RTCP message for sending payload
information which should be in RTP, why not send it as RTP packet
with sequence number that precede the first packet in the burst.
With what payload type? It can't be a retransmission payload, because
it is not a retransmission of a packet of the original stream. It
seems awfully heavy weight to start defining a whole new set of
payload formats for this kind of information, soem of which is payload-
format specific and some which is not.
In section 7 you define new messages but the FMT you specify are
already used in RFC5104.
For the RMS message you have a maximum receive bitrate, you should
say that this number cannot be bigger than the b= SDP parameter.
The document should discuss how this mechanism works with SRTP
What do you think needs to be said that isn't said in the SRTP
specifications. The retransmission session is a normal RTP session
which is protected with SRTP just like any other RTP session. Am I
missing something?
Roni Even
(Not as AVT chair)
_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
https://www.ietf.org/mailman/listinfo/avt
_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
https://www.ietf.org/mailman/listinfo/avt