Opened 8 years ago

Last modified 8 years ago

#29 new defect

Section 12.2 Multiple Sources

Reported by: bernard_aboba@… Owned by: draft-ietf-rtcweb-rtp-usage@…
Priority: critical Milestone: milestone1
Component: rtp-usage Version: 1.0
Severity: Active WG Document Keywords:
Cc:

Description

tbd: there needs to be a way of indicating how RTP stream relate when
there are multiple sources, possibly with simulcast or layered
coding, and different types of mixer or other middlebox. It is
possible that the various BUNDLE/Plan-X proposals will solve this,
but it might also need RTP-level stream identification. To be
resolved once the outcome of the BUNDLE and plan-X discussions is
known.

[BA] Suggest that the application token extension be considered as a potential solution to this.

Change History (2)

comment:1 Changed 8 years ago by bernard_aboba@…

tbd: Are any mechanism needed to signal limitations in the number of
active SSRC that an end-point can handle?

[BA] I'd suggest that "signal limitations in the number of active SSRC" not be an objective.

comment:2 Changed 8 years ago by bernard_aboba@…

[Magnus Westerlund]

Yes, it is one potential solution. From my perspective the goal must be
to resolve the use cases discussed in
https://datatracker.ietf.org/doc/draft-westerlund-avtext-rtcp-sdes-srcname/

[BA] Section 3 of the above document is relevant, certainly.

Note: See TracTickets for help on using tickets.