kmip-interop-tech — archive

[Tim Hudson]

The interop call is on again this week 30 minutes before the main call and we have a larger than usual number of items to cover off on. 1) Update from Jane Harnad on the latest OASIS information pack 2) Request for a change in interop handling a) one vendor has another server product they would like to make available in addition to the current product under test b) one vendor has a significantly updated server product they would like to make available for interop replacing the product that was originally proposed for the interop and used in informal testing 3) Feedback on interop process so far 4) Issues raised already: a) error in 11.2 step 2 as reported by Michael Stevens (see end of email) b) the operations list in the spreadsheets isn't complete c) the algorithms and key sizes are not in the spreadsheets d) other interop issues? 5) Status updates from each vendor on testing to date 6) Other items We have three ways to handle item 2 in the agenda: 1) remain with the current agreed approach and only those products that were available at the start of formal interop are permitted and must be used on the interop network at the RSA show [with only minor updates for reported issues during the formal interop] 2) agree unanimously to allow a new product and a significantly updated release into formal interop 3) take a special majority vote to allow a new product and a significantly updated release into formal interop If the group decision is to allow a variation of the rules we are operating under then I suggest that we stick with the current time frame and allow updates for the server test target spreadsheets until Monday morning at 9am GMT+10 (Australia/Queensland). We should also keep in mind that Bob Lockhart had additional profiles with tests which he held off distributing. Those could also be incorporated if we are restarting interop. I've discussed with a number of vendors this evening and the consensus so far appears to be that we should take a special majority vote (which we will interpret as 5 out of the 7 vendors must agree) to change from the originally agreed plan at the commencement of interop. This will mean updated claims spreadsheets and re-testing for all those vendors who have already tested where the client or server claims are different given if we do update we will fix the missing items in the spreadsheets. Please all have a clear view on which approach your organisation wants to take to resolving the issues raised. Thanks, Tim. ---8<--- Issue for a KMIP 1.0 test for 11.2 Step 2 (this is not an issue in the KMIP 1.1 test document) Document has: Tag: BATCH_ORDER_OPTION (0x420010), Type: BOOLEAN (0x06), Data: 0x0000000000000001 Tag: BATCH_ERROR_CONTINUATION_OPTION (0x42000e), Type: ENUMERATION (0x05), Data: 0x00000001 (CONTINUE) Tag: BATCH_COUNT (0x42000d), Type: INTEGER (0x02), Data: 0x00000002 It should be: Tag: BATCH_ORDER_OPTION (0x420010), Type: BOOLEAN (0x06), Data: 0x0000000000000001 Tag: BATCH_ERROR_CONTINUATION_OPTION (0x42000e), Type: ENUMERATION (0x05), Data: 0x00000001 (CONTINUE) Tag: BATCH_COUNT (0x42000d), Type: INTEGER (0x02), Data: 0x00000002 Please check your test programs and update to ensure they have the order of the fields in conformance with the specification.