BOEv3 Message Format Versioning and Nomenclature

Since BOEv3 uses a more rigidly structured message format than prior versions of BOE, message types may be introduced when new fields cannot be accommodated by utilizing reserve bytes in the existing message specification. In such cases, when a new message type is introduced, it will be documented as a distinct message type in this document. Application layer message types are named using the following pattern:

This allows for ease of distinction between similar message types between markets (for example, US Futures compared to US Options), and the handling of new versions of the message (V1, V2, etc).

When application layer message types are discussed in this document, they are being referred to using their general type name unless their specific version is relevant to the documentation.

During any time when multiple versions of messages from CFE to TPH are supported concurrently, the configuration of the port determines which message version may be sent by CFE.