The next step wraps the content key and the initialization vector according to the FPS specification. The integrity
verification is optional, but it is part of the best practice requirements. Next, the server creates a content key
context (CKC) in response to the application that contains the content key and the initialization vector. The
client application then provides CKC to FPS to request a play context.