How are Marlin Licenses, Nodes and other objects moved between devices in a domain?
License objects are delivered in License bundles (collections of objects) that are either embedded into the content in structured container formats (such as MP4), or transported as standalone Licenses (e.g., sent from a License Server). Since content is protected by encrypting it with the content key that is in the License, media files (with or without embedded Licenses) can be shared using any mechanism the user has available (e.g., ftp, cifs, nfs, e-mail, USB mass storage, etc.) The public part of an Octopus Node is communicated in the registration protocols defined in the delivery system specifications and in the Marlin Core services of the peer-to-peer framework, e.g., as in the Provide DRM Objects protocol. The Link objects, which are the only objects needed to enforce governance, are communicated in the response of certain peer-to-peer protocols. Link objects are also delivered in profile-specific ways, such as the Broadband Registration protocol. Note that Link objects, being se
