[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[AVT] Re: draft-ietf-avt-rtp-midi-08.txt: Issues with multiplexing different MIDI spaces
On May 24, 2005, at 1:11 AM, Magnus Westerlund wrote:
I agree with the below interpretation regarding what PT is intended
to be used. However I would suggest that one requires the use of
different SSRCs for different midi spaces but have the PT to
indicate which space it uses. This should resolve all your concerns
below regarding packet losses as each SSRC has its own RTP sequence
number space.
OK, if we start down this path then it probably also makes
sense to add your earlier suggested feature in too:
So what can work is to say that in the case of split transport. For
a split stream the same SSRC should be used in both sessions. This
requirement has some implication on collision detection and
resolution. RTCP Cname would need to be used to confirm that two
different sources really is the same.
Then in addition to simplify things the same RTP TS offset can be
recommended to be used. However the synch information in RTCP must
confirm this view that they are running the same time frame.
So that -09.txt will represent all of the extra features needed
to do more complicated session things. If later on it turns out that
there
isn't consensus on these features, I'll pull them back out and do a
-10.txt ...
---
John Lazzaro
http://www.cs.berkeley.edu/~lazzaro
lazzaro [at] cs [dot] berkeley [dot] edu
---
_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
https://www1.ietf.org/mailman/listinfo/avt