OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

kmip message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [kmip] Groups - Group as a managed object(KMIP-GroupProposal-02182011.ppt) uploaded


Krishna,

I have a few questions regarding the Group proposal.

1. Can the functionality described in the group proposal be accomplished using existing KMIP means?
 - Can [Locate "fresh=true"] be done using a Create operation instead?
 - Can a server-supplied attribute "y-default" be used to designate "default" object in a group?

2. Can an object registered by a client considered "fresh"? It would be according to the current definition of "fresh". On the other hand it seems that a "fresh" object is one that has not been seen by any client.

3. "Replicated" attribute seems to come out of nowhere. I think the attribute itself and the terminology around it (e.g. replication server) would need some definition and broader discussion.

4. There doesn't seem to be an explicit group deletion, and if a group contains many objects, particularly of heterogeneous nature, it would not be straightforward for a client to delete a group.

5. Is it possible to add/modify/delete "fresh" attribute of an object?

6. It seems that [Locate "fresh=true"] operation would always have to be batched with a Get request. Otherwise another client can preempt the first one and issue a Get for the object, whose UUID has been returned by the response to the initial [Locate "fresh=true"]. The picture would get even more complicated if the answer to the previous question (5) is "Yes".

Thank you for considering my feedback.

Regards,
Denis

- - - - - - - - - - - - - - - -
Denis Pochuev
Principal Software Engineer
SafeNet, Inc.
Denis.Pochuev@safenet-inc.com
+1 (650) 261-2429



The information contained in this electronic mail transmission 
may be privileged and confidential, and therefore, protected 
from disclosure. If you have received this communication in 
error, please notify us immediately by replying to this 
message and deleting it from your computer without copying 
or disclosing it.




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]