Re: [webrtc-pc] RTCPeerConnection lacks identity marker beyond current process

I propose a 32 characters hexadecimal string, all characters uppercase ASCII.
1. When a browser creates a new peer connection, it would theoretically need to ensure that it did not previously randomly choose the same string for a previously created peer connection; in practice, this would be so unlikely, that almost anyone would be able to get away with skipping this check.
2. Following the usual principle, a good implementation would only assign uppercase characters to the ID, but would be lenient in accepting lowercase IDs from other implementations. Or maybe not...?

-- 
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1775#issuecomment-366731541 using your GitHub account

Received on Monday, 19 February 2018 15:49:00 UTC