23098 2013-08-30 02:44:25 +0000 Specify algorithm normalization when reflected to key.algorithm (are generation parameters dropped?) 2014-02-13 13:05:46 +0000 1 1 1 Unclassified Web Cryptography Web Cryptography API Document unspecified PC Linux RESOLVED FIXED P2 normal --- 1 ericroman sleevi ap oldest_to_newest 92728 0 ericroman 2013-08-30 02:44:25 +0000 Let's say you call generateKey() with an HmacKeyParams. There are several possibilities for what the resulting key.algorithm looks like. (1) It is simplified to a HmacParams (i.e. the optional "length" field is dropped) (2) It is mirrored as the exact same HmacKeyParams (3) It is mirrored as a HmacKeyParams, where the optional "length" parameter is filled in with the default length that was inferred. From an implementation standpoint my preference is to (1), since it means we don't need to define interfaces to reflect back the generation parameters. Option (2) by comparison is redundant since the caller already knows what parameters they passed in. 95705 1 ap 2013-11-01 17:58:46 +0000 Isn't key.algorithm the only way to observe the normalized algorithm anyway? If the spec goes with (1), then it seems like algorithm normalizing rules can be removed. 100526 2 sleevi 2014-02-13 13:05:46 +0000 This should be resolved with https://dvcs.w3.org/hg/webcrypto-api/rev/2fa3494f0179