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 - kmip-tape-lib-profile-v1 0-wd01-review.doc uploaded


Bruce, Tim,

The tape profile is intended to harden the requirements for client-generated identifiers stored in ASI data.  Since the spec also allows server-generated ASI data, I thought it was important to mention server-generated names in the profile, but that portion may still be weak.         

Regardless, I don't think servers should be required to create identifiers in ASI data for the LIBRARY-LTO namespace.  The server MAY do that, but SHALL is too strong.  Yet, the Query response in 3.1.8 does make that requirement.    I didn't catch that, and I'm glad you pointed it out.

To fix that, we can modify that line in the 3.1.8 test case, easily enough.   It's also possible to change Query and ASI in the spec to better define ASI.   I'm not sure spec changes are necessary, but I'll help with whatever the group believes is necessary to achieve the clarity we need.

Stan


-----Original Message-----
From: Tim Hudson [mailto:tjh@cryptsoft.com] 
Sent: Tuesday, July 02, 2013 2:19 PM
To: kmip@lists.oasis-open.org
Cc: Bruce Rich; Feather, Stan S
Subject: Re: [kmip] Groups - kmip-tape-lib-profile-v1 0-wd01-review.doc uploaded

Excellent discussion - and it is indeed hitting the point - that server provided values for ASI is very much underspecified.
How about removing it? Is anyone using it? Does anyone plan to use it?

The point I'm making is that query response does not state you cannot return values in the query response for application name spaces which are client-side only. It states you must include the ones which support the (underspecified) server-side, but it does not state you cannot include others.

There is also a specific error code returned when an application name space isn't supported - allowing for clients to ignore checking the query response.
The usage guide talks about "recognized" rather than "supported".

On removing the requirement for the name spaces to be listed in the Query response - I'll defer to Stan and Rod (there are three editors on the profile) for how to handle that.

Thanks,
Tim.



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