kmip-interop-tech — archive

[Bruce Rich]

I have a couple of things in the current set of interop testcases that I think need more discussion. TC-152-11 and TC-152-12 (assuming wd02a is most current) The testcases are described as         "Register two symmetric keys, both with the same (non-default) Object Group name specified and the Fresh attribute set to true.         Get the Fresh attribute from both keys to make sure it was set. Perform three batched Locate and Get requests to get a fresh key from the group..."         However none of the Locate/Get pairs actually specify that they are looking for FRESH objects in that ObjectGroup, so there is no reason why the second Locate/Get would return anything other than the key that the first one did.  And thusly there is no reason that the third Locate/Get would fail to find a key.         If we add to the attributes passed on all the Locates that we are looking for a FRESH object, then I agree with the validity of that test (and that would change results/scores for those two tests). MSGENC-JSON-1-10, 11, 12 (assuming wd03 is most current) MSGENC-XML-1.10, 11, 12 At TIME 0, the client is telling the server that the maximum message size it can tolerate in the response is 256 bytes, which would be tolerable for a TTLV-encoded response. Neither XML nor JSON can even return an error message in that amount of space.  (For example, the JSON error response in shown the profile is 775 bytes, a clear violation of the client's ability to handle.  So the only thing a server can do is close the connection.  If we want to make these tests valid for more verbose encodings, then we need to adjust the max size up a bit.  And this is going to change some results/scores for these tests. Bruce A Rich brich at-sign us dot ibm dot com