This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22347 - RTCIceServer should have multiple URLs
Summary: RTCIceServer should have multiple URLs
Status: RESOLVED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Web RTC Working Group
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-13 07:42 UTC by Harald Alvestrand
Modified: 2014-10-29 18:39 UTC (History)
1 user (show)

See Also:


Attachments

Description Harald Alvestrand 2013-06-13 07:42:59 UTC
Discussion on the mailing list in early June 2013 led to this proposal for a change, which seems to be acceptable:

Current:


dictionary RTCIceServer {
    DOMString  url;
    DOMString? credential;
};


Proposed:


dictionary RTCIceServer {
    sequence<DOMString> urls;  // for backwards compatibility, implementations
                        // should also handle |url|
    DOMString?  username;  // previously agreed upon
    DOMString? credential;
};

4.2.2.1 Dictionary RTCIceServer Members


username of type DOMString, nullable

If the url element of the internal array is a TURN URI, then this is the username to use with that TURN server.

credential of type DOMString, nullable

    If the url element of the internal array is a TURN URI, then this is the password to use with that TURN server.
urls of type DOMString[]

    A list of STUN or TURN URIs as defined in [STUN-URI] and [TURN-URI]. If multiple URIs are present, they represent alternate ways to contact the STUN/TURN server, listed in order of preference.

Link to original proposal: http://lists.w3.org/Archives/Public/public-webrtc/2013Jun/0075.html
Comment 1 Harald Alvestrand 2014-10-29 18:39:53 UTC
As of the June 1 2014 version, this is fixed.