Opened 8 years ago

Last modified 8 years ago

#26 new defect

Section 5.2.4 Application Token Header Extension

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

Description

If the extension defined in draft-even-mmusic-application-token goes forward, it should be considered whether implementation is OPTIONAL or RECOMMENDED for WebRTC.

Change History (1)

comment:1 Changed 8 years ago by bernard_aboba@…

[Magnus Westerlund]

Yes, we currently do have a open issue of how one is to accomplish
bindings and relations for multiple different purposes around the RTP
media streams. Clearly the different cases discussed in the following
drafts that applies to RTCWEB needs to be taken into account and we need
to reach some consensus on how to resolve their overlap and get
specifications finished:

https://datatracker.ietf.org/doc/draft-westerlund-avtext-rtcp-sdes-srcname/

https://datatracker.ietf.org/doc/draft-ietf-mmusic-msid/

https://datatracker.ietf.org/doc/draft-even-mmusic-application-token/

Note: See TracTickets for help on using tickets.