Should MarketID and MarketSegmentID be available on order routing messages?

, ,
1

Imported from previous forum

2

FIX.5.0SP1 introduced new entities to identify markets. MarketID and MarketSegmentID were added. MarketSegmentID essentially replaced TradingSessionID as the method to identify a board or segment of the market. TradingSessionID was then enumerated to identify portions of a trading session occurring within a MarketID and MarketSegmentID.
At the time FIX.5.0SP1 was defined the decision was made to not include MarketID and MarketSegmentID into the order routing transactional messages. In examining the new intent for TradingSessionID as an enumeration and the adoption of MarketID and MarketSegmentID to identify what was previously identified by TradingSessionID, I think we need to add MarketID and MarketSegmentID into the order routing messages as soon as possible.

3

I agree with the assessment and support the addition of these fields to the order messages. I volunteer to prepare a gap analysis for the FIX Global Exchanges & Markets Committee as there are more requirements we need to cover for order messages in the near future.

FIX.5.0SP1 introduced new entities to identify markets. MarketID and
MarketSegmentID were added. MarketSegmentID essentially replaced
TradingSessionID as the method to identify a board or segment of the
market. TradingSessionID was then enumerated to identify portions of a
trading session occurring within a MarketID and MarketSegmentID. At the
time FIX.5.0SP1 was defined the decision was made to not include
MarketID and MarketSegmentID into the order routing transactional
messages. In examining the new intent for TradingSessionID as an
enumeration and the adoption of MarketID and MarketSegmentID to identify
what was previously identified by TradingSessionID, I think we need to
add MarketID and MarketSegmentID into the order routing messages as soon
as possible.

4

[ original email was from sonitta peeler - sonitta.peeler@bofasecurities.com ]
I agree with you totaly.

FIX.5.0SP1 introduced new entities to identify markets. MarketID and
MarketSegmentID were added. MarketSegmentID essentially replaced
TradingSessionID as the method to identify a board or segment of the
market. TradingSessionID was then enumerated to identify portions of a
trading session occurring within a MarketID and MarketSegmentID. At the
time FIX.5.0SP1 was defined the decision was made to not include
MarketID and MarketSegmentID into the order routing transactional
messages. In examining the new intent for TradingSessionID as an
enumeration and the adoption of MarketID and MarketSegmentID to identify
what was previously identified by TradingSessionID, I think we need to
add MarketID and MarketSegmentID into the order routing messages as soon
as possible.