Closed Bug 888640 Opened 12 years ago Closed 12 years ago

ICE candidates for data channel has two components

Categories

(Core :: WebRTC, defect)

Product:
Core
Component:
WebRTC
Version:
25 Branch
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 901560

People

(Reporter: kahmyong.moon, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0) Gecko/20130629 Firefox/25.0 (Nightly/Aurora) Build ID: 20130629031116 Steps to reproduce: 1. Created an RTCPeerConnection. 2. Created an RTCDataChannel. 3. Created an offer. Actual results: The offered SDP includes four ICE candidates with two foundations and two components: m=application 55480 SCTP/DTLS 5000 c=IN IP4 192.168.1.70 a=fmtp:5000 protocol=webrtc-datachannel;streams=16 a=sendrecv a=candidate:0 1 UDP 2111832319 192.168.1.70 55480 typ host a=candidate:1 1 UDP 2111766783 192.168.56.1 55481 typ host a=candidate:0 2 UDP 2111832318 192.168.1.70 55482 typ host a=candidate:1 2 UDP 2111766782 192.168.56.1 55483 typ host While both components are checked (and required for ICE to complete, as far as I can tell), only component 1 is ever used to transport data. With media streams, these two components would be RTP and RTCP, but that doesn't make sense for SCTP carried over DTLS, does it? Expected results: I would expect only one component to be used by data channels. I could just be misunderstanding how this is supposed to all work, though.
Component: Untriaged → WebRTC
Product: Firefox → Core
I think bug 901560 has better information about this issue.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.