2.1.18 c-playerid

This field specifies a unique identifier for the client application that originated the request. The identifier MUST be a GUID. The GUID is expressed in registry format and is not enclosed in quotation marks, as shown by the following ABNF syntax.

If the client is configured to remain anonymous (that is, not send private information), the client MUST set the c-playerid field as indicated by the ABNF syntax for the playid_priv syntax element as shown in the following code example. Otherwise, c-playerid MUST use the syntax for playid_pub as shown in the following code example. The client MUST choose a value for playid_pub randomly, and the same value MUST be used for playid_pub in all logging messages created by the client application, regardless of which content is streamed.

 Furthermore, multiple instances, or incarnations, of the client application MUST use the same value for the playid_pub syntax element. However, if the client application is shared by multiple users, and it is possible to determine a user identity or account name of the user launching the client application, then the value for playid_pub SHOULD be different for each user identity or account name. For example, multi-user operating systems typically have separate accounts with a distinct account name for each user, but cellular telephones do not.

If the client uses the playid_priv syntax element, the client SHOULD choose the value for the playid syntax element randomly; however, the client MUST use the same playid value for all logging messages sent for the same session.

The syntax of the c-playerid field is defined as follows.

 playid= 12HEXDIG
 playid_pub = "{" 8HEXDIG "-" 4HEXDIG "-" 4HEXDIG "-" 
               4HEXDIG "-" 12HEXDIG "}"
 playid_priv= "{3300AD50-2C39-46c0-AE0A-" playid "}"
  
 c-playerid= playid_pub / playid_priv
  

Example:

  
 {c579d042-cecc-11d1-bb31-00a0c9603954}

Example (client is anonymous):

  
 {3300AD50-2C39-46c0-AE0A-70b64f321a80}