906998 - Support RTP header extension for webrtc stream demux

Status: RESOLVED WONTFIX

(Core :: WebRTC: Networking, defect, P4)

Comment 1

[Maire Reavy [:mreavy]]

Targeting this for Gecko 32.  I'm setting a target deadline of March 7.  It's approximately 2 man-weeks (de-rated by 50% due to work on other projects).

Comment 2

[Maire Reavy [:mreavy]]

Spec link?  Is this still relevant?  At least a better description of what and why would help.

Comment 3

[Ethan Hugg [:ehugg]]

The RTP Header extension mechanism is defined in RFC 5285:
https://tools.ietf.org/html/rfc5285

It uses the SDP line a=extmap to negotiate the use of them.  For example, our SDP currently shows this one for audio:
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level

Chrome uses that one plus this for audio:
a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time

And three more lines for video:
a=extmap:2 urn:ietf:params:rtp-hdrext:toffset
a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=extmap:4 urn:3gpp:video-orientation

As far as header extensions for demux, I didn't see where a consensus was reached on this.  I did see these two examples from the CLUE WG: 

http://tools.ietf.org/html/draft-romanow-clue-call-flow-02
a=extmap:1 urn:ietf:params:clue:demux

https://tools.ietf.org/html/draft-lennox-clue-rtp-usage-04
a=extmap:1 urn:ietf:params:rtp-hdrex:clue-capture-id

Perhaps there's another draft that I missed that details something we should implement.

Comment 4

[Bulk Bug Changes for mreavy's org]

Mass change P3->P4 to align with new Mozilla triage process.

Comment 5

[Nils Ohlmeier [:drno]]

In general we do support RTP header extension parsing and negotiating now.
The one relevant these days for demxuing is MID which is worked on other bugs.

Comment 6

[Nils Ohlmeier [:drno]]

Bug 1405495 is the one which covers MID in the demuxer.