25763 2014-05-18 11:20:27 +0000 does the ID really have to be exaclty 36 char long? 2014-07-02 16:33:34 +0000 1 1 1 Unclassified WebRTC Working Group Media Capture and Streams unspecified PC All RESOLVED FIXED P2 normal --- 1 fluffy public-media-capture adam.bergkvist harald public-media-capture oldest_to_newest 106256 0 fluffy 2014-05-18 11:20:27 +0000 108559 1 harald 2014-07-01 08:03:50 +0000 This is the MediaStreamID attribute. It is intended to be globally (not just locally) unique, so it's reasonable to push implementors to a high length. It is also good to have an upper bound on it. Still, 36 seems to have no particular reason for it except it being the length of an UUID. (see http://en.wikipedia.org/wiki/Universally_unique_identifier) Suggest removing "MUST be 36 characters long" and adding "A good practice is to use an UUID for this ID, which is 36 characters long in its canonical form". 108655 2 adam.bergkvist 2014-07-02 16:33:34 +0000 Added implementation suggestions to MediaStream.id definition and pointed to that from MediaStreamTrack.id. Proposed fix: https://github.com/fluffy/webrtc-w3c/commit/31743d21ba5f35c41fea0616f00a45aaa8d7fe51