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 - Client / Server Correlation Value uploaded


Hi Anthony

 

I support effective logging, but the existing protocol specification provides all that is needed in the form of the Unique Batch Item ID. This field supports the unique identification of each and every Batch Item originated by a client or by a server:

 

REQUEST:

<RequestMessage>

  <RequestHeader>

    <ProtocolVersion>

      <ProtocolVersionMajor type="Integer" value="1"/>

      <ProtocolVersionMinor type="Integer" value="1"/>

    </ProtocolVersion>

    <BatchCount type="Integer" value="3"/>

  </RequestHeader>

  <BatchItem>

    <Operation type="Enumeration" value="Create"/>

    <UniqueBatchItemID type="ByteString" value="75e8bdb337aec40e"/>

    <RequestPayload>

      <ObjectType type="Enumeration" value="SymmetricKey"/>

      o o o

    </RequestPayload>

  </BatchItem>

  <BatchItem>

    <Operation type="Enumeration" value="Create"/>

    <UniqueBatchItemID type="ByteString" value="ac0e6e56e8d99f66"/>

    <RequestPayload>

      <ObjectType type="Enumeration" value="SymmetricKey"/>

      o o o

    </RequestPayload>

  </BatchItem>

  <BatchItem>

    <Operation type="Enumeration" value="Create"/>

    <UniqueBatchItemID type="ByteString" value="77e87d356ba09da1"/>

    <RequestPayload>

      <ObjectType type="Enumeration" value="SymmetricKey"/>

      o o o

    </RequestPayload>

  </BatchItem>

</RequestMessage>

 

RESPONSE:

<ResponseMessage>

  <ResponseHeader>

    <ProtocolVersion>

      <ProtocolVersionMajor type="Integer" value="1"/>

      <ProtocolVersionMinor type="Integer" value="1"/>

    </ProtocolVersion>

    <TimeStamp type="DateTime" value="2012-04-27T08:14:44+00:00"/>

    <BatchCount type="Integer" value="3"/>

  </ResponseHeader>

  <BatchItem>

    <Operation type="Enumeration" value="Create"/>

    <UniqueBatchItemID type="ByteString" value="75e8bdb337aec40e"/>

    o o o

  </BatchItem>

  <BatchItem>

    <Operation type="Enumeration" value="Create"/>

    <UniqueBatchItemID type="ByteString" value="ac0e6e56e8d99f66"/>

    o o o

  </BatchItem>

  <BatchItem>

    <Operation type="Enumeration" value="Create"/>

    <UniqueBatchItemID type="ByteString" value="77e87d356ba09da1"/>

    o o o

  </BatchItem>

</ResponseMessage>

 

The Unique Batch Item ID is superior to a message identifier because it identifies individual operations within a message. This same identifier is returned to the client in the server’s response. The proposed Client/Server Correlation IDs provide no value beyond what the Unique Batch Item ID already provides.

 

I would suggest that the KMIP Usage Guide be amended to say that every Batch Item SHOULD include a Unique Batch Item ID – even if the message contains just a single Batch Item (if only to facilitate problem analysis) – and both clients and servers SHOULD include the Unique Batch Item ID in any logs. The Usage Guide should further state that a Unique Batch Item ID SHOULD be globally unique [and not merely unique within a message] so as to preclude logging ambiguities.

 

Cheers,

… Dave

 

 

 

From: kmip@lists.oasis-open.org [mailto:kmip@lists.oasis-open.org] On Behalf Of Anthony Berglas
Sent: Tuesday, December 15, 2015 2:59 AM
To: kmip@lists.oasis-open.org
Subject: [kmip] Groups - Client / Server Correlation Value uploaded

 

Submitter's message
We have a request to provide closer coordination between client and server logs. This very simple proposal provides a text field that enables the client to provide extra information for the server to log. The server can also pass back a string to the client which can be used to identify server log values.

I would like to present this at the next call. All feedback in advance most welcome.
-- Anthony Berglas

Document Name: Client / Server Correlation Value


Description
Proposal to enhance communication between the client and server.
Download Latest Revision
Public Download Link


Submitter: Anthony Berglas
Group: OASIS Key Management Interoperability Protocol (KMIP) TC
Folder: Proposals
Date submitted: 2015-12-14 23:58:43

 


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]