[Bug 17682] Clear Key: Document how keys and key IDs are associated

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17682

--- Comment #9 from johnsim@microsoft.com ---
1. Change to EME section 6.1, Clear Key, last paragraph.
________________________________________

The key parameter of addKey() should be a JSON Web Key (JWK) representation of
the symmetric key to be used for decryption, as defined in the IETF
Internet-draft JSON Private Key specification
(http://tools.ietf.org/html/draft-jones-jose-json-private-and-symmetric-key). 

When the JWK ‘key type’ ("kty") member value is 'octet sequence' ("oct"), the
'key value' ("k") member will be a base64 encoding of the octet sequencing
containing the symmetric key value. 

For example, the following contains a single symmetric key represented as a
JWK, designated as being for use with the AES Key Wrap algorithm (line breaks
for readability, only).

{ "keys": 
   {"kty":"oct",
    "alg":"AES128KW",
    "kid":""67ef0gd8pvfd0=",
    "k":" GawgguFyGrWKav7AX4VKUg"
   }
}

________________________________________
2. Change to Examples, Example 8.1, to pass this Clear Key JWK instead of Key
to addKey().

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 14 January 2013 21:46:16 UTC