See David F's email - proposing we change wording to make it clear that the compromise occurrence date is optional.
Tim H - this date is required for noting when revocation occurred - there isn't a separate date for when revoke occurred.
Judy F - from CRLs - should be noted that you note dates at suspend etc - so this is meant to be include
David F - separately should we make it clear that CA compromise also covers key compromise - not exactly clear in the specification.
Tony C - should we discuss this further. David - yes. Judy - good topic. KMIP 1.4 topic? Yes.
AI - David to produce material - Tim and Judy will review.
Application Specific Information
See David F's other email - proposing we change wording to make it clear that the compromise occurrence date is optional.
Usage Guide - empty string verse not present - is this indicated there or not.
Tim - would prefer to just see the REQUIRED changed to NO rather than YES and not explicitly note empty string as usable.
AI David to check usage guide to see whether or not there is something there in the UG that indicates empty string should be used to discuss on next call.
Anthony B - is there any confusion on NULL / Empty in the specification. Tim - don't think so - but worth checking.
Other items
Tony - brief update on SDC and DSSS
Some folks at the summit were not aware of just how widely deployed KMIP already is - lots of comments on that.
SSIF increased interest in terms of KMIP after that call
Tim - there is a video link to the session and the SNIA/OASIS presentation will be uploaded to the KMIP document area.