Monday, February 9, 2015

UTP Vendor Alert #2015 - 2
REVISED:Implementation of new UTP Message Header Formats

What is changing?

To accommodate Timestamp information within the UTP Data Feed outbound messages, the UTP Data Feed Message Headers will be expanded from 24 bytes to 43 bytes and include the following field modifications.

• Modified Session Identifier Field
• Modified SIP Date/Time Field
• New Timestamp 1 Field (microseconds since midnight ASCII base95)
• New Timestamp 2 Field (microseconds since midnight ASCII base95)
• New Transaction ID Field

The revised timeline for the UTP Message Header Format release to include Timestamp1 and Timestamp2 is scheduled for July 27, 2015.

How will these improvements be implemented?

The UTP SIP plans to support the new Message Header Protocol changes July 27, 2015. The revised message header will be as follows:

In order to facilitate these improvements the UTP SIP Back End software will be backward compatible, allowing for rapid fallback from new (revised) message header format to existing (current) message header format. While there is no intention of publishing both new (revised) and existing (current) format on any single channel over the course of the day, data recipients should be prepared to receive both.

The UTP SIP intends to use existing message formats and types in order to minimize the impact on data recipients. To facilitate the improvements a message header change will be made to (a) provide the additional content and (b) indicate whether the message format is new (existing) or old (current).

What changes are being made to the message header format?

The Session Identifier in the message header will be redefined to indicate which version of message header is present for the message:

• 'A': existing (current) format, all sessions
• 'U': existing (current) format, U.S. market session
• '1': new (revised) format (session indication is no longer differentiated)

The message header Time Stamp field will be redefined to provide the SIP Timestamp in terms of the number of microseconds since midnight EST. The value will be revised and reduced in size. Revised timestamp will represent the number of microseconds since midnight EST. The value will be a 6-byte string of ASCII-displayable characters relative to ASCII space (" ") representative of a base95 number.

The existing Reserved field: The three remaining bytes of the existing timestamp filed will be reserved for future use.

Three new additional fields will be added to the message header for the new message format:

• Timestamp1 and Timestamp2: A participant-provided timestamps representing the number of microseconds since midnight EST. The value will be a 6-byte string of ASCII-displayable characters relative to ASCII space (" ") representative of a base95 number. The SIP will simply pass through the value provided by the participant where applicable; for transactions originating from participants not using the new input content and for SIP-generated messages, this field will contain all zeros (six ASCII ' ' characters).
• Transaction ID: A transaction identifier reserved for UTP usage. The transaction identifier will be a single string of 7 ASCII-displayable characters. This is intended for UTP SIP internal use only and Data Vendors may ignore/disregard this field.

How will time fields within existing message formats be changed?

The UTP SIP will make one modification to the LULD Price Band Effective Time Field in order to provide a greater granularity to the microsecond.

• The Price Band Message's (category 'A', type 'P') LULD Price Band Effective Time field will be modified to contain a "wall time" time value precise to the microsecond level for the new (proposed) message format (i.e. Session Identifier = '1') in the format "HMSnnnnnn", where:
  • H: an ASCII-displayable character representing the hours portion of the timestamp; values are defined in Appendix F
  • M: an ASCII-displayable character representing the minutes portion of the timestamp; values are defined in Appendix F
  • S: an ASCII-displayable character representing the seconds portion of the timestamp; values are defined in Appendix F
  • nnnnnn: microsecond portion of timestamp (numeric)

• There are no changes at this time for the various Date/Time fields published on the UTP data feeds; these fields will continue to provide precision to the nearest second. Fields include:
  • Cross SRO Trading Action (category 'A', type 'H'), field Action Date/Time (UQDF/UTDF/OMDF)
  • Market Center Trading Action (category 'A', type 'K'), field Action Date/Time (UQDF/UTDF/OMDF)
  • Prior Day As-Of Trade (category 'T', type 'H'), field Prior Day Trade Date/Time (UTDF)

What are the testing opportunities for the release?

Yes. To ensure that direct data feed subscribers are ready to handle the new Message Header Formats, the UTP SIP will offer evening format testing opportunities. The UTP SIP will replay a sample data file with the new UQDF, UTDF and OMDF formats via the production IP multicast channels from 9:00 p.m. to 10:30 p.m., ET, on weekday evenings.

The UTP SIP is working closely with the UTP Operating committee, and will post additional UTP notices to inform the direct data recipients.

Where can I find additional information?

• Refer to the UQDF, UTDF and/or OMDF specification documents.
• Refer to the FAQ Document.
• For questions regarding the UTP Data Feeds, please contact products@utpplan.com.