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 25763 - does the ID really have to be exaclty 36 char long?
Summary: does the ID really have to be exaclty 36 char long?
Status: RESOLVED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: Media Capture and Streams (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: public-media-capture@w3.org
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-18 11:20 UTC by Cullen Jennings
Modified: 2014-07-02 16:33 UTC (History)
3 users (show)

See Also:

Attachments

Description Cullen Jennings 2014-05-18 11:20:27 UTC 

    


    


      



        
          Comment 1
        

        
          Harald Alvestrand

        

        
        

        
          2014-07-01 08:03:50 UTC
        

      






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".

    


    


      



        
          Comment 2
        

        
          Adam Bergkvist

        

        
        

        
          2014-07-02 16:33:34 UTC
        

      






Added implementation suggestions to MediaStream.id definition and pointed to that from MediaStreamTrack.id.

Proposed fix: https://github.com/fluffy/webrtc-w3c/commit/31743d21ba5f35c41fea0616f00a45aaa8d7fe51