https://www.w3.org/Bugs/Public/show_bug.cgi?id=23572
Bug ID: 23572
Summary: Documented format with which to specify ICE servers
does not match implementation and contains typos
Product: WebRTC Working Group
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: minor
Priority: P2
Component: WebRTC API
Assignee: public-webrtc@w3.org
Reporter: matthewrobertson03@gmail.com
CC: public-webrtc@w3.org
The WebRTC W3C working draft states that multiple ICE server urls can be
specified for a single set of credentials using the "urls" dictionary key:
http://www.w3.org/TR/webrtc/#idl-def-RTCIceServer
This does not match the current Chromium or Firefox implementations in which
only single url can be specified under the "url" key:
https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/modules/mediastream/RTCPeerConnection.cpp&l=97
Currently in the spec there is no mention of the "url" key (only "urls") and
there is no example that demonstrates specifying multiple urls for a single
IceServer object. This would be a useful feature for situations in which one
server is capable of providing several TURN protocols (TURNS, transport=tcp,
transport=udp etc) but it is not strictly necessary, as it can currently be
accomplished by passing in multiple IceServer objects each with a single URL.
Also, there is a small typo in the example JSON at the bottom of this section
of the spec (4.2.2.1):
http://www.w3.org/TR/webrtc/#idl-def-RTCIceServer
[ { urls: "stun:stun1.example.net } , { urls:"turn:turn.example.org", username:
"user", credential:"myPassword"} ]
should be (missing "):
[ { urls: "stun:stun1.example.net" } , { urls:"turn:turn.example.org",
username: "user", credential:"myPassword"} ]
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.