Re: [AVT] Final edits to RTP spec and A/V profile

> Jonathan Rosenberg <jdrosen@dynamicsoft.com> writes:
>
> I suspect each unicast connection is treated as a separate RTP session.

Sfront currently ships with multi-unicast support, and the  
implementation is a hybrid of both approaches. A sender does
sent the same RTP packet to each receiver, and in this way
everything but the lowest layers of the stack believes a 
true multicast session is underway. Sfront needs to do this,
because it lets a sender create and maintain one recovery
journal system for all receivers, a big efficiency improvement
over N recovery journal systems.

However, a receiver doesn't send RTCP RR packets describing  
a sent stream to all other participants, only to the original
sender. This is for efficiency ...                         

BTW, Appendix B of the MWPP guidelines document:

http://www.ietf.org/internet-drafts/draft-lazzaro-avt-mwpp-coding-guidelines-01.txt

Covers this topic in detail ... 

-------------------------------------------------------------------------
John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
lazzaro [at] cs [dot] berkeley [dot] edu     www.cs.berkeley.edu/~lazzaro
-------------------------------------------------------------------------
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt