roap中 ds:SignatureType 和 xenc:EncryptedKeyType 的总结

      roap中的 ds:SignatureType，<signature>.<ds:SignedInfo>.<ds:Reference>.<ds:Transforms> must contains a single <ds:Transform> element that signals the use of the exclusive canonicalization algorithm without comments

1、ROAP trigger中的 ds:SignatureType 和 xenc:EncryptedKeyType
      1、这两者在trigger type为"LeaveDomain"时shall出现，相应element的名字为<signature>和<encKey>；
      2、<encKey> contain a MAC key wrapped with the current Domain key，此MAC key就是<signature>中签名所用的key；
      3、<signature>.<ds:SignedInfo>.<ds:Reference>.URI == <leaveDomain>.id，这说明此signature是对leaveDomain的签名；
      4、<signature>.<ds:KeyInfo>.<ds:RetrievalMethod>.URI == <encKey>.id，这说明encKey中的key是用于签名所用的key；
      5、、<signature>.<ds:SignedInfo>.<ds:SignatureMethod>.Algorithm  must be http://www.w3.org/2000/09/xmldsig#hmac-sha1。

2、RO type 中的两个 ds:SignatureType 和一个 xenc:EncryptedKeyType
      1、RO schema<complexType name="ProtectedRO"> <sequence> <element name="ro" type="roap:ROPayload" form="qualified"/> <element name="mac" type="ds:SignatureType"/> </sequence> </complexType> <complexType name="ROPayload"> <sequence> <element name="riID" type="roap:Identifier"/> <element name="rights" type="o-ex:rightsType"/> <element name="signature" type="ds:SignatureType" minOccurs="0"/> <element name="timeStamp" type="dateTime" minOccurs="0"/> <element name="encKey" type="xenc:EncryptedKeyType"/> <element ref="roap:roPayloadAliases" minOccurs="0"/> <any processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute name="version" type="roap:Version" use="required" /> <attribute name="id" type="ID" use="required" /> <attribute name="stateful" type="boolean"/> <attribute name="domainRO" type="boolean"/> <attribute name="riURL" type="anyURI"/> </complexType>
      2、第一个signature <mac>，其是对上面<ro>的签名，其签名密码存在于<ro>.<encKey>中，这些可以通过下面的关系得知：
           <mac>.<ds:SignedInfo>.<ds:Reference>.URI == <ro>.id；
           <mac>.<ds:KeyInfo>.<ds:RetrievalMethod>.URI == <ro>.<encKey>.id;
      3、第二个signature <ro>.<signature>，其是对<rights>的签名；
           <signature> MUST be present when the RO is a Domain RO，and SHOULD NOT be present when the RO is a Device RO and it is delivered using the RO Acquisition protocol；
           <signature>.<ds:SignedInfo>.<ds:Reference>.URI == <rights>.o-ex:id；
           The <ds:KeyInfo> child element of the <signature> element SHALL identify the signing key，但signing key到底是什么，不清楚；
      4、<ro>.<encKey>，其包含的key有Kmac 和 Krek，分别是<mac>和<ro>.<rights>的key，其被打包的key为hash of clients public key 或 domain key;
           <enckey>.id == <rights>.<ds:KeyInfo>.<ds:RetrievalMethod>.URI;
           If intended for a Device, the child of the <ds:KeyInfo> element SHALL be the <roap:X509SPKIHash> element, identifying a particular DRM Agent's public key; if intended for a Domain, it will be of the type <roap:domainID> element, identifying the correct Domain key.

3、<roap:ProtectedDomainKey> 中的 <xenc:EncryptedKeyType>
      1、schema <complexType name="ProtectedDomainKey"> <sequence> <element name="encKey" type="xenc:EncryptedKeyType"/> <element name="riID" type="roap:Identifier"/> <element name="mac" type="base64Binary"/> </sequence> </complexType>
      2、<encKey>包含的key有Kmac 和 Kd。Kmac我猜是用来验证的，这个值应该等于<mac>，Kd是domain key；
      3、<encKey>.Id == ROAP-JoinDomainRequest.<domainID>;
      4、<encKey>.<ds:KeyInfo>.<roap:X509SPKIHash>  is for identifying a particular DRM Agent's public key through the hash of the subjectPublicKeyInfo value in its certificate.

4、<meteringReportSubmit> 中的 <xenc:EncryptedKeyType>
      1、schema... <element name="meteringReport"> <complexType> <sequence> <element name="encryptedMeteringReport" type="xenc:EncryptedDataType”/> <element name="encKey" type="xenc:EncryptedKeyType"/> <element name="mac" type="base64Binary"/> <sequence> </complexType> </element> ...
      2、<encKey>包含的key有Kmac 和 Kmek。Kmac我猜是用来验证的，这个值应该等于<mac>，Kmek是<encryptedMeteringReport>的key；
      3、<encKey>.Id == <encryptedMeteringReport>.<ds:KeyInfo>.<ds:RetrievalMethod>.URI;
      4、<encKey>.<ds:KeyInfo>.<roap:X509SPKIHash>  is for identifying the RIs Public Key through the (SHA-1) hash of the DER-encoded subjectPublicKeyInfo value in the RIs Certificate.