[kmip] KMIP v1.2 TestCases: Inconsistency w.r.t. Register of Split Keys?

["Featherstone, David" <David.Featherstone@safenet-inc.com>]

(Re-sending due to alleged problems with the reflector, last week. Comments appreciated.)

 

Greetings

 

I wonder whether there’s an inconsistency with Register of a Split Key as exemplified in the KMIP v1.2 Test Cases document [beginning p.858]:

 

2.3.48 TC-SJ-3-12 - Join Split Keys

<RequestMessage>

<RequestHeader>

<ProtocolVersion>

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

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

</ProtocolVersion>

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

</RequestHeader>

<BatchItem>

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

<RequestPayload>

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

<TemplateAttribute>

<Attribute>

<AttributeName type="TextString" value="x-ID"/>

<AttributeValue type="TextString" value="TC-SJ-3-12-split1"/>

</Attribute>

</TemplateAttribute>

<SplitKey>

<SplitKeyParts type="Integer" value="4"/>

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

<SplitKeyThreshold type="Integer" value="2"/>

<SplitKeyMethod type="Enumeration" value="PolynomialSharingGF2_8"/>

<KeyBlock>

<KeyFormatType type="Enumeration" value="Raw"/>

<KeyValue>

<KeyMaterial type="ByteString" value="66C46A7754F94DE420C7B1A7FFF5EC56"/>

</KeyValue>

</KeyBlock>

</SplitKey>

</RequestPayload>

</BatchItem>

</RequestMessage>

 

Notice the absence of both a Cryptographic Algorithm and a Cryptographic Length from the above request.

 

The KMIP v1.2 specification’s Table 144-Register Attribute Requirements, however, clearly states that both Cryptographic Algorithm and a Cryptographic Length are in fact required to be present – only Secret Data being exempt.

 

QUESTION: Must Cryptographic Algorithm and Cryptographic Length be present in the Register of a Split Key object type?

 

Regards,

… Dave

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.