Versioning in SIVIC

[ryanthompson591]

In the VAST response add a min and max supported version in the SIVIC tag.

Possible ways to agree on version:

1. Decide at run time initialization. This is similar to VPAID (see handshake).
   • There would be an initial handshake
2. Put supported version in the VAST.
   • This would mean that players can reject versions of SIVIC they don't support before they try to play them.

There was a debate about whether to render the ad if the ads required versions were not supported.

• For: if the ad knows it might not be able to communicate with the player it may still be worth showing the elements it wants to show
• Against: if the ad requires a level of communication with the publisher, better to error out than to charge impressions for something that is not supported. This gives control to the ad as to when it wants to support a version and when it doesn't

[mtumi]

since it is in VAST, it needs to be in the VAST 4.2 spec. We also will need to add an error that says version not supported. Can be reflected in OpenRTB using existing spec (when/if needed). Need to add version to handshake.

[ryanthompson591]

In environment data version is one of the fields. SIMID can error if it is not correct.