OASIS Key Management Interoperability Protocol (KMIP) TC

 View Only

  • 1.  Enhancement to Get Attributes message

    Posted 06-10-2009 17:52 
    In order for a client to retrieve the full list of attributes for an
object, he must do so in two separate batch requests.  The first request
is the Get Attribute List message to retrieve the list of attribute
names associated with the object, then a separate batch request with the
Get Attributes message with each attribute name listed explicitly.  This
design requires two round trips and extra processing at the client and
the server.  

In addition to having a simpler method to retrieve all attributes of an
object, I can foresee a client wanting to quickly get the list of all
custom attributes (those starting with x- and y-).

I propose adding a tag to the Get Attributes request called Attribute
Selection with five possible values:

0x00  Specified Attributes (requires named list of Attributes)
0x01  All Attributes
0x02  All Client Custom Attributes
0x03  All Server Custom Attributes
0x04  All Custom Attributes

I'm interested in discussing whether the tag should be optional, and if
so what the default value should be.  I think it might be easier to have
'All Attributes' be the default, rather than the named attribute method
already present in the spec.


-Alan Frindell
SafeNet, Inc.
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.


  • 2.  Re: [kmip] Enhancement to Get Attributes message

    Posted 06-11-2009 13:53 

    Alan,

    It would indeed be good to hear from the members if
the usage of such an extended Get Attributes operation is frequent enough.
If yes, using a bitmask to specify (All non-custom attributes | All client-custom
attributes | All server-custom attributes) would be more flexible.

    Regards
    -Robert

    "Frindell,Alan" <Alan.Frindell@safenet-inc.com>
wrote on 06/10/2009 07:46:43 PM:

    
> In order for a client to retrieve the full list of attributes for
an
    
> object, he must do so in two separate batch requests.  The first
request
    
> is the Get Attribute List message to retrieve the list of attribute
    
> names associated with the object, then a separate batch request with
the
    
> Get Attributes message with each attribute name listed explicitly.
 This
    
> design requires two round trips and extra processing at the client
and
    
> the server.  
    
>
    
> In addition to having a simpler method to retrieve all attributes
of an
    
> object, I can foresee a client wanting to quickly get the list of
all
    
> custom attributes (those starting with x- and y-).
    
>
    
> I propose adding a tag to the Get Attributes request called Attribute
    
> Selection with five possible values:
    
>
    
> 0x00  Specified Attributes (requires named list of Attributes)
    
> 0x01  All Attributes
    
> 0x02  All Client Custom Attributes
    
> 0x03  All Server Custom Attributes
    
> 0x04  All Custom Attributes
    
>
    
> I'm interested in discussing whether the tag should be optional, and
if
    
> so what the default value should be.  I think it might be easier
to have
    
> 'All Attributes' be the default, rather than the named attribute method
    
> already present in the spec.
    
>
    
>





Related Content