kmip message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [kmip] Groups - KMIP Group proposal (kmip-spec-1.GroupUpdates-v1.doc) uploaded
- From: Krishna Yellepeddy <kyellepe@us.ibm.com>
- To: "Fitzgerald, Indra" <indra.fitzgerald@hp.com>
- Date: Wed, 18 May 2011 06:00:01 -0500
Hi Indra,
Thanks for reviewing the spec changes.
Responses below to your questions.
Regards,
Krishna
From:
| "Fitzgerald, Indra" <indra.fitzgerald@hp.com>
|
To:
| Krishna Yellepeddy/Austin/IBM@IBMUS,
"kmip@lists.oasis-open.org" <kmip@lists.oasis-open.org>
|
Date:
| 05/16/2011 07:03 PM
|
Subject:
| RE: [kmip] Groups - KMIP Group proposal
(kmip-spec-1.GroupUpdates-v1.doc) uploaded |
Hi Krishna,
I reviewed the spec changes and have the following comments:
1. I need additional clarification on the Object Group Member attribute.
Can some group members have this attribute set to Group Member Fresh and
others to Group Member Default? Once a client retrieves an object, it will
no longer be fresh and the Group Member Fresh setting will no longer be
useful. Also, you would still need to check the Fresh attribute to determine
whether an object has already been retrieved. We don't actually need the
Object Group Member attribute to determine whether an object is fresh.
All we need is the Object Group and Fresh attributes. To help me understand
why we need this Object Group Member attribute, could you please define
Group Member Default? Also, note that Object Group Member is missing the
Rules table.
Answer:
Object Group Member is specified when a client makes
a Locate call, to indicate to the server whether it wants a fresh or default
object from the group. It is not used by the server to keep track of which
objects in a group are fresh and which are default. How the server defines
'default' is based on server policy and how it keeps track of what the
'default' in a group is up to server implementers. An example definition
of default is the next member in the group, where the server uses a round
robin policy to select members from a group. By using 'Default' as opposed
to say 'next', we give the server the flexibility to define 'Default' in
multiple ways to handle use cases that TC members have. I did complete
the Rules table initially, but realized the Rules table implies the attribute
is stored with an object. Since Object Group Member is used by a client
in a Locate call and is not stored as an attribute of an object, I found
the Rules table does not apply.
2. Can the Fresh attribute be set for an object that is not in an object
group?
Answer:
No, a fresh attribute cannot be set for an object
that is not in an object group. This means when an object is removed from
a group by deleting the 'Object Group' attribute the fresh attribute should
also be deleted.
3. What should the server do when an object is a member of multiple groups
and has these new attributes set?
Answer:
The server defines the policy for whether an object
can belong to multiple groups. TC members specifically said they have use
cases where objects may belong to multiple groups, which is why the proposal
allows it. If server policy allows an object to belong to multiple groups,
and a client does a 'Get' on this object, it is marked as no longer fresh.
Until we have group as a first class object (post 1.1), where we can specify
at group creation time whether a group member can belong to multiple groups,
whether a group is homogeneous etc, the server needs to define these policies
itself.
4. Additional clarification and guidance should be added to the Usage Guide.
Answer: Yes, will do so
Thanks,
Indra
-----Original Message-----
From: kyellepe@us.ibm.com [mailto:kyellepe@us.ibm.com]
Sent: Wednesday, May 11, 2011 7:50 PM
To: kmip@lists.oasis-open.org
Subject: [kmip] Groups - KMIP Group proposal (kmip-spec-1.GroupUpdates-v1.doc)
uploaded
The document revision named KMIP Group proposal
(kmip-spec-1.GroupUpdates-v1.doc) has been submitted by Krishna Yellepeddy
to the OASIS Key Management Interoperability Protocol (KMIP) TC document
repository. This document is revision #2 of
KMIP-GroupProposal-03232011.pdf.
Document Description:
Simplified proposal for managing groups - updates to the specification
document
View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=42116
Download Document:
http://www.oasis-open.org/committees/download.php/42116/kmip-spec-1.GroupUpdates-v1.doc
Revision:
This document is revision #2 of KMIP-GroupProposal-03232011.pdf. The
document details page referenced above will show the complete revision
history.
PLEASE NOTE: If the above links do not work for you, your email application
may be breaking the link into two pieces. You may be able to copy
and paste
the entire link address into the address field of your web browser.
-OASIS Open Administration
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]