kmip-interop-tech — archive

[Mathias Bjorkqvist]

All,


Here are my summary notes from today's interop call. Please let me know
of any additions/corrections you might have.


Regards,

Mathias



KMIP interop 2010-10-14
Attending: Bruce, Tim, Bob, Mathias

First item(s) in list of possible use
cases to work on related to untested v1.0 items. Asymmetric profiles not
in v1.0, also some items still open (e.g., Subject Alt. Name just defined
as a String - need to spec change or add encoding rule). Storage Client
profile not a proof-of-concept item. Although many of the v2.0 proposals
are far from ready, we also need to decide whether to start working on
use cases with what is available, or whether to wait for the proposals
to mature. For targeting March/April for v2.0, it would be good to have
as much as possible done before the end of the year.

Discussion on how the use cases document
should look like in the future: The decision whether to continue with the
current document and add new use cases, or to rather move to a new document
e.g., with unit tests needs to be a conscious one. Resource requirements
a hurdle to implementing lots of new unit tests. Use cases initially a
way to validate what we were specifying in the spec, and that we could
use the protocol for what we were trying to accomplish. For interop, makes
more sense to segment use cases according to profiles, and refer to relevant
sections in the Use Cases document from the profiles. Statements of use
were given and interop tests were done on a rather small subset of the
specification. For the next specification release, we need to decide what
to test, and what will be included in the statements of use.

For next steps, we can start working
on use cases for v1.0 functionality that is currently not tested. Beyond
that still needs to be decided. We will continue the discussion on how
to proceed on next week's call.