FDO spec explicitly states:
3.9.1. Mapping Messages to ServiceInfo
A ServiceInfo module MAY have an arbitrary number of messages. There are no arrays, but numbered message names can be used to simulate their effect (mod:key1, mod:key2).
Since ServiceInfo messages are separated into one or more FDO messages, it is possible to use the same message over and over again. Whether this is has a cumulative or repetitive effect is up to the module that interprets the messages (e.g., file:part might be repeated for successive parts, but tpm:certificate might be individual certificates).
The order of interpretation of ServiceInfo messages MUST be the same as the order they are received in the message. All ServiceInfo elements in a message MUST BE interpreted before the next message is transmitted.
This is a mechanism that inherently embeds a "sequence number" into payloads to disambiguate any reordering, omission, duplication of payload massages.
Should we use this as part of the chunking mechanism in upload (and other?) FSIMS?
FDO spec explicitly states:
This is a mechanism that inherently embeds a "sequence number" into payloads to disambiguate any reordering, omission, duplication of payload massages.
Should we use this as part of the chunking mechanism in upload (and other?) FSIMS?