W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > February 2018

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

From: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Mon, 19 Feb 2018 15:48:55 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-366731541-1519055334-sysbot+gh@w3.org>
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

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:01 UTC