How are certificate policies used in Marlin?
They are used throughout Marlin. Here are some examples: • A DRM Object Provider that issues Link objects must sign them. Links are evaluated for trust independent of their acquisition. The fact that a system entity with the role “DRM Object Provider” was engaged in the acquisition of the Link may be lost when the Link is used to build the Node/Link topology. Therefore, an additional mechanism must be in place to evaluate the Link for trustworthiness. This information is conveyed via the certificate policy of “id-cp-octopus-marlin-signing-link”. Before a Link is relied upon to form the Node-Link topology, the signature over a given Link object must be validated. One step in the validation process is to see if the intended policy terms are in the end entity certificate. • When a License is issued, a Controller object (and the Control it refers to) must be signed by a key that adheres to a specific certificate policy (see the Trust Management section of Marlin Core, 9.1.3.6). When a Lice
