Lifetime of pc.PeerIdentity

[dontcallmedom]

Initially raised by @fluffy at w3c/webrtc-pc#1262

The text seem to say that if the promise successfully resolve, the value will not change. I'm not sure this is correct. Imagine the case where A sets up a connection to B and gets the identity of B. Now the web servers side wants to do a transfer by using a re-offer to A that moves the media to C. A will get a re-Offer, with new ice, new DTLS-SRTP, new fingerprint, and a new identity from C. the PC on the A sides needs to be able to process that and display it.

[dontcallmedom]

Comment by @martinthomson

This is not permitted. Switching the identity of a peer isn't supported. Configuring a connection for a particular identity or successfully authenticating a peer identity both cause the connection to be locked to that identity. Changing the identity is thereafter blocked. This is necessary to ensure that identity-locked media can be safely sent to the peer.

If you want to talk to C, then you need a new RTCPeerConnection instance. Because you need new signaling and DTLS connections, that doesn't seem like a real problem to me.