TC-IMPEXP-3-20

From
Mark Joseph <>
Date
2019-02-04T00:54:00+00:00
ID
Thread
TC-IMPEXP-3-20
Hi Martin,
   We just changed this test so that for Export we expect the Fresh attribute to be True, and on Import we pass that same value of True.  I thought the purpose of the Import is to preserve the state of the managed object being given to the new server, thus Fresh would have the same value it was given from the Export.
Best,  Mark
From:
Martin Shannon <>
To:
  <>
Sent:
2/3/2019 4:27 PM
Subject:
[kmip-interop-tech] TC-IMPEXP-3-20
Hi All,

We have detected a few servers failing this test due to the value of the Fresh attribute in the Export response. So, I thought  d pose a few questions to the group.
Since we are exporting a newly registered object, it makes sense that the Fresh attribute should be True when exported. And several vendors  servers exhibit this behaviour. But TC-IMPEXP-3-20.xml, the reference, has the Fresh attribute  set to False in the export response.
Which is correct?
What is the use case for Export?

Furthermore, should the Import operation really be allowed to specify a value for Fresh? Fresh is supposed to be set by the server, not the client.

Martin



Martin Shannon
Software Developer   QuintessenceLabs
W:
quintessencelabs.com


 Unit 1 Lower Ground  15 Denison St
Deakin ACT 2600
P: +61 2 6260 4922


 Delivering quantum enhanced cyber-security for over ten years

 Find out more at   quintessencelabs.com