Re: [MMUSIC] Some more APPID questions

Hi Harald,
The current draft is still not mature enough and the presentation will have
some information which is not there and some of the text in the 00 version
that is not in the 01 version may come back.

An SSRC can have multiple appIds example is in a three camera system one
appID for active speaker which is now the left camera having a different
appID

The uniqueness of appID should be per media packet stream.

Roni

> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
> Of Harald Alvestrand
> Sent: 03 November, 2013 8:22 PM
> To: mmusic
> Subject: [MMUSIC] Some more APPID questions
> 
> On reviewing the appid document and some of the mail on it.. some
questions.
> 
> I understand that an appid can serve multiple purposes; FEC binding and
> loudest-speaker selection being two examples.
> 
> Some of these give information that is completely outside the context of
RTP /
> SDP, so they have to be application specified. Others are within the
RTP/SDP
> ecosystem.
> Thus:
> 
> - Can one SSRC have mulitple appids?
> This seems necessary for those multiple functions to work at the same time
> without treading on each other, but isn't stated explicitly in the draft.
> 
> - What's the uniqueness criterion for appids?
> It would seem logical to have them unique at the source, but at least in
one
> case (recv-appid), it is given by the destination. Are we depending on
statistical
> uniqueness, or is the uniqueness governed by some other mechanism?
> 
> I'll send off these 2 questions now, in order to make the thread be
focused....
> 
> 
> --
> Surveillance is pervasive. Go Dark.
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic