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 25545 - Initialization of of RTCConfiguration while invoking RTCPeerConnection.getConfiguration should be updated.
Summary: Initialization of of RTCConfiguration while invoking RTCPeerConnection.getCon...
Status: RESOLVED INVALID
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Web RTC Working Group
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-05 11:34 UTC by Kiran
Modified: 2014-10-31 16:52 UTC (History)
2 users (show)

See Also:

Attachments

Description Kiran 2014-05-05 11:34:52 UTC 
When RTCPeerConnection.getConfiguration is invoked [1], a new RTCConfiguration object is created and initialized. While initializing this newly created object, spec is missing to specify, initialization of requestIdentity attribute.

This may be fixed by modifying the following line 

When this method is call, the user agent MUST construct new RTCConfiguration object to be returned, and initialize it using the ICE Agent's ICE transports setting and ICE servers list.

to

When this method is called, the user agent MUST construct new RTCConfiguration object to be returned, and initialize it using the ICE Agent's ICE transports setting and ICE servers list and requestIdentity.

[1] http://dev.w3.org/2011/webrtc/editor/webrtc.html#widl-RTCPeerConnection-getConfiguration-RTCConfiguration
Comment 1 Harald Alvestrand 2014-10-31 16:52:50 UTC 
RequestIdentity is gone, so this is OBE.