Scalable spec for client-side verification of ConfigurationInfo

[rbehjati]

We need to define a mechanism for specifying the logic for verifying the server configuration info in a generic and scalable manner.

Originally posted by @tiziano88 in https://github.com/project-oak/oak/pull/2254#r730007293

Also see https://github.com/project-oak/oak/pull/2254#discussion_r731124495 from @ipetr0v.

[rbehjati]

The following are some of the information that the client might want to verify. The actual verification depends on the Client.

• hash of web assembly
• metrics configuration (differential privacy parameters: epsilon/bucket sizes)
• tensor flow configuration
• constant response-time/response-size policy: on/off (needs more discussion)