OASIS Key Management Interoperability Protocol (KMIP) TC

Proposal for adding Key Value Type to the Get Request Payload.

 -- Mrs. Indra Fitzgerald

The document named Proposal for Adding Key Value Type to Get.doc has been
submitted by Mrs. Indra Fitzgerald to the OASIS Key Management
Interoperability Protocol (KMIP) TC document repository.

Document Description:
Proposal for adding Key Value Type to the Get Request Payload.

View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=33961

Download Document:  
http://www.oasis-open.org/committees/download.php/33961/Proposal%20for%20Adding%20Key%20Value%20Type%20to%20Get.doc


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

Indra, All,
For clarity, instead of overloading
the Key Value Type field, what about introducing a distinct "Key Compression
Type" field with its own enumeration, both in the Get request and
Key Block object? Also, we should consider renaming "Key Value Type"
to "Key Format Type", to be more precise.

Moreover, if we allow clients to specify
under which format they wish to obtain a key (raw, transparent, etc), then
should the spec state the following too ?

- if a client registers a key in a given
format/compression, the server must be able to provide it (as a response
to Get requests) in at least that same format/compression (that would forbid,
for instance, server implementations that take as input a transparent key
and only store the flattened raw byte format).

- any conversion from the original provided
format/compression (that came through a Register operation from the client,
or from a out-of-band admin operation) to any other format/compression
is optional for the server to support.

Regards,
-Robert


indra.fitzgerald@hp.com wrote on 08/27/2009 05:30:44
PM:


> [image removed] 
>

> [kmip] Groups - Proposal for Adding Key Value Type to Get.doc uploaded
>

> indra.fitzgerald 
>

> to:
>

> kmip
>

> 08/27/2009 05:30 PM
>

> Proposal for adding Key Value Type to the Get Request Payload.


> -- Mrs. Indra Fitzgerald


> The document named Proposal for Adding Key Value
Type to Get.doc has been

> submitted by Mrs. Indra Fitzgerald to the OASIS Key Management

> Interoperability Protocol (KMIP) TC document repository.


> Document Description:

> Proposal for adding Key Value Type to the Get Request Payload.


> View Document Details:

> http://www.oasis-open.org/committees/document.php?document_id=33961


> Download Document:

> http://www.oasis-open.org/committees/download.php/33961/Proposal%

> 20for%20Adding%20Key%20Value%20Type%20to%20Get.doc


>

> 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

Robert Haas wrote:
> Indra, All,
> For clarity, instead of overloading the Key Value Type field, what about 
> introducing a distinct "Key Compression Type" field with its own 
> enumeration, both in the Get request and Key Block object? Also, we should 
> consider renaming "Key Value Type" to "Key Format Type", to be more 
> precise.

I could live with these.

> Moreover, if we allow clients to specify under which format they wish to 
> obtain a key (raw, transparent, etc), then should the spec state the 
> following too ?
> 
> - if a client registers a key in a given format/compression, the server 
> must be able to provide it (as a response to Get requests) in at least 
> that same format/compression (that would forbid, for instance, server 
> implementations that take as input a transparent key and only store the 
> flattened raw byte format).
> 
> - any conversion from the original provided format/compression (that came 
> through a Register operation from the client, or from a out-of-band admin 
> operation) to any other format/compression is optional for the server to 
> support.

Yes we should probably include something like this.

spt

> Regards,
> -Robert
> 
> 
> indra.fitzgerald@hp.com wrote on 08/27/2009 05:30:44 PM:
> 
>> [image removed] 
>>
>> [kmip] Groups - Proposal for Adding Key Value Type to Get.doc uploaded
>>
>> indra.fitzgerald 
>>
>> to:
>>
>> kmip
>>
>> 08/27/2009 05:30 PM
>>
>> Proposal for adding Key Value Type to the Get Request Payload.
> 
>> -- Mrs. Indra Fitzgerald
> 
>> The document named Proposal for Adding Key Value Type to Get.doc has 
> been
>> submitted by Mrs. Indra Fitzgerald to the OASIS Key Management
>> Interoperability Protocol (KMIP) TC document repository.
> 
>> Document Description:
>> Proposal for adding Key Value Type to the Get Request Payload.
> 
>> View Document Details:
>> http://www.oasis-open.org/committees/document.php?document_id=33961
> 
>> Download Document:
>> http://www.oasis-open.org/committees/download.php/33961/Proposal%
>> 20for%20Adding%20Key%20Value%20Type%20to%20Get.doc
> 
>> 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

Hi Robert,
 
My comments are inline.
 
Regards,
Indra




From: Robert Haas [mailto:rha@zurich.ibm.com]
Sent: Wednesday, September 16, 2009 6:06 AM
To: Fitzgerald, 
Indra
Cc: kmip@lists.oasis-open.org
Subject: Re: [kmip] 
Groups - Proposal for Adding Key Value Type to Get.doc 
uploaded




Indra, All,
For clarity, instead of overloading the Key Value Type 
field, what about introducing a distinct "Key Compression Type" field with its 
own enumeration, both in the Get request and Key Block object? Also, we should 
consider renaming "Key Value Type" to "Key Format Type", to be more 
precise. 
 
[IF] I assume you are suggesting for us to avoid allowing 
multiple Key Value Types to be specified. I would be ok with that. I am also ok 
with changing the name to Key Format Type or Key Material 
Format.
 
Moreover, if we allow clients to specify under which format they wish to 
obtain a key (raw, transparent, etc), then should the spec state the following 
too ?

- if a client registers a key 
in a given format/compression, the server must be able to provide it (as a 
response to Get requests) in at least that same format/compression (that would 
forbid, for instance, server implementations that take as input a transparent 
key and only store the flattened raw byte format).   
  
- any conversion from the original provided 
format/compression (that came through a Register operation from the client, or 
from a out-of-band admin operation) to any other format/compression is optional 
for the server to support.  
 
 [IF] Yes, we could include this. 
Note however that it is up to the vendor how the object will be 
stored.  

Regards,
-Robert


indra.fitzgerald@hp.com wrote on 08/27/2009 
05:30:44 PM:

> [image removed] 
>
> [kmip] Groups - Proposal for Adding Key Value Type to Get.doc 
uploaded
>
> indra.fitzgerald 

>
> to:
>
> kmip
>
> 
08/27/2009 05:30 PM
>
> Proposal for 
adding Key Value Type to the Get Request Payload.

> -- Mrs. Indra Fitzgerald

> 
The document named Proposal for Adding Key Value Type to Get.doc has 
been
> submitted by Mrs. Indra Fitzgerald to the OASIS Key 
Management
> Interoperability Protocol (KMIP) TC document 
repository.

> Document 
Description:
> Proposal for adding Key Value Type to the Get Request 
Payload.

> View Document Details:
> 
http://www.oasis-open.org/committees/document.php?document_id=33961

> Download Document:
> 
http://www.oasis-open.org/committees/download.php/33961/Proposal%
> 
20for%20Adding%20Key%20Value%20Type%20to%20Get.doc

>
> 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