Specify configuration parameters

[ZmGorynych]

We need to specify configuration parameters for each mode so that they can be clearly referenced from other specs. The purpose is to avoid explaining CMCD functionality in different specs. E.g., the DASH spec should say "request

For example:

Mode #1 - the client attaches CMCD data to each media object request, using one of the Data Transmission Modes defined in Section 3. This mode matches the default delivery mode in v1 of CMCD.

Configuration parameters: data transmission mode (query/header/json)
Client functionality: send CMCD data with each GET request for the requested type of objects

Mode #2 - This mode reports data to an alternate destination after either the full response or an error has been received to a media object request, using one of the Data Transmission Modes defined in Section 3. This reporting MAY be batched if using the JSON data transmission mode. Each report MUST include a ‘url’ and a ‘ts’ key.

Configuration parameters: data transmission mode, URL of alternative destination, reporting interval in units of time (optional)
Client functionality: send CMCD information after each GET request is completed or (if reporting interval is used) every T seconds send a batch of requests completed in the last T seconds.

Mode #3 - the client reports a subset of CMCD data to a data collector by making an HTTP/S request to a beacon end-point and passing the data via one of the Data Transmission Modes defined in Section 3. These reports are made on state changes and optionally at regular fixed intervals.
[...]

Configuration parameters: data transmission mode, reporting interval in units of time, a flag whether to enable reporting on state changes
Client functionality: send batched CMCD information every T seconds or on state change.