Open Bug 1210147 Opened 9 years ago Updated 2 years ago

Inspect WebRTC Data Channels (@Transport level) in a tab

Categories

(DevTools :: Netmonitor, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: akratel, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

Developers should be able to inspect network traffic going over webRTC data channels within a given tab. They should be able to have access to transport protocol level (Stream Control Transmission Protocol (SCTP)).

This is the sister bug to WebSocket frame inspection Bug 927481. We should be able to reuse many of the UI components for webRTC. 

Still need to determine the frame equivalency - what level of details do we try to obtain, and what level of filtering we apply.
See Bug 1210127 for overall feature priority.
Depends on: 1210160
Out of curiosity: why is this interest limited to WebRTC data channels? Why are you not interested to "look" into the media streams for audio and video as well?
(In reply to Nils Ohlmeier [:drno] from comment #2)
> Out of curiosity: why is this interest limited to WebRTC data channels? Why
> are you not interested to "look" into the media streams for audio and video
> as well?
We could visualize e.g. bitrate, but otherwise, what would you expect to "see" in the media streams?

Honza
(In reply to Jan Honza Odvarko [:Honza] from comment #4)
> (In reply to Nils Ohlmeier [:drno] from comment #2)
> We could visualize e.g. bitrate, but otherwise, what would you expect to
> "see" in the media streams?

On the same level where a data channel uses SCTP the media streams use RTP packets. If you are interested in looking SCTP packets arriving I would assume you would/coule be interested in looking at the details of RTP packets arriving.
Product: Firefox → DevTools
Type: defect → enhancement
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.