In Q1 2024, CME Group will be launching iLink 3 Convenience Gateway for trading futures and options on futures on CME Globex. iLink 2 and iLink 3 for CGW will run in parallel until Q4, 2024. All customers connected via Convenience Gateway (CGW) are encouraged to migrate to iLink 3 as early as possible prior to the iLink 2 decommission.

The iLink 3 order entry protocol on CME Globex provides:

  • Simple Binary Encoding (SBE) for faster message encoding and decoding
  • A simple, lightweight, point-to-point session layer protocol using FIX Performance (FIXP)
  • More efficient iLink FIX messaging
  • Standard message size, fixed positions, and fixed-length fields
  • A consistent encoding method for order entry and market data
  • XML schema and templates for order entry as with MDP 3
  • Lean messages move administrative information out of order entry business message

All newly created iLink 3 CGW sessions will be created with Cancel on Disconnect (COD) enabled. To disable COD, Clearing Firm Administrators must enter the change request via Firm Admin Dashboard (FADB). 

Contents

Revision History

DateDescription
March 27, 2024Updated first paragraph under iLink 3 CGW Front-End Audit Trail Requirements: The required audit trail specifications apply to all systems implementing  iLink 3 CGW. All client systems must be certified for Audit Trail for iLink 3 CGW prior to using the production environment.
March 20, 2024Updated <marketsegment id="6" label="Globex OESGW for all CGWs">.
Edited Key Events description for January 31, 2025.
February 12, 2024Updated diagrams in iLink 3 Binary Order Entry Protocol for CGW - Business Layer for "On Demand - Accepted" and "On-Demand Party Details Request Accepted, New Order Rejected"
January 17, 2024Added note to the iLink 3 on CGW Availability section.
November 27, 2023Added Key Event of February 15, 2024, for Certification parallel for futures and options.
September 27, 2023Changes to Key Events and Dates for Mock trading sessions and Production parallel for futures and options.
June 21, 2023Effective 10/31/2024 iLink 2 sessions can no longer be created.
Effective 1/1/2025 CGW will be decommissioned.
All newly created iLink 3 CGW sessions will be created with Cancel on Disconnect (COD) enabled.
April 19, 2023Initial content release

Key Events and Dates

DateMilestone

May 8, 2023

Phase 1 New Release for futures and options

  • New Release CME Request Center for self-service session migration
  • iLink 3 on CGW available in New Release environment for core functionality for on-demand administrative information 
  • A new iLink certification suite will be available in AutoCert+ for on-demand orders

September 25, 2023

Phase 2 New Release for futures and option

  • iLink 3 on CGW available in New Release environment for core functionality for pre-registered administrative information
  • A new iLink certification suite will be available in AutoCert+ for pre-registered orders

October 23, 2023

Production CME Request Center for self-service session creation

January 20, 2024

January 27, 2024

Mock trading sessions

January 28 , 2024

Production parallel for futures and options

February 15, 2024

Certification parallel for futures and options

October 31, 2024

iLink 2 sessions can no longer be created

December 31, 2024

Deadline for customer migration 

January 31, 2025

iLink 2 on CGW Decommission 

  • Drop Copy for iLink 2 source sessions are no longer supported.

Session Management

CME Group requires customers to obtain new iLink 3 CGW sessions. Customers will not be able to migrate their existing iLink sessions from iLink 2 to 3. Customers can create their new iLink 3 CGW sessions through CME Request Center following standard sessions creation practice. New session IP address and port details will be presented to the user in CME Request Center at the time of creation.  

  • During the parallel period, any CGW sessions configured for iLink 3 must send iLink 3 messages.
    • iLink 3 sessions sending iLink 2 messages will be terminated immediately.
  • All CGW sessions must be migrated to iLink 3 by the end of the parallel period.

See iLink 3 for CGW Session Guidelines for more information.

New Release customers will have the ability to obtain new iLink 3 CGW sessions or migrate their existing iLink sessions from iLink 2 to 3 within CME Request Center NR/CERT. 

  • Existing iLink 2 CGW sessions will be converted to iLink 3 over the proceeding weekend to be ready for the next business week.
  • New iLink 3 CGW sessions will be created daily at 4am CT. 


Testing and Certification

A new iLink certification suite will be available in AutoCert+.

  • Certification is required for all client systems on CGWs.
  • All customer systems must be certified for iLink 3 prior to going to the production environment.


Mock Trading Sessions

CME Group will offer customer mock trading sessions to support the customer experience with the iLink 3 on CGW in the CME Globex production environment. Customers are required to register in advance in order to participate in mock trading sessions. Further information on the mock trading sessions will be published in future CME Globex Notices. 

Client systems must be certified for iLink 3 CGW tests via AutoCert+ prior to participating in the iLink 3 CGW mock trading sessions.

iLink 3 on CGW Availability

 Convenience Gateway (CGW) and Drop Copy Gateway (DCGW) customers must take the following into consideration for this launch:


CGWDCGW
iLink 3iLink 3 and iLink 2 CGW sessions will be available in parallel until the date specified in the Key Events and Dates table.
  • Drop Copy will support both iLink 3 and iLink 2 source sessions during the parallel period.
  • The encoded payload messages sent on Drop Copy with iLink 3 source sessions will be in ASCII format, but will reflect the changes documented in the Drop Copy for iLink 3 Binary Order Entry topic.

Note

The creation of new iLink 3 CGW source sessions may generate additional Drop Copy target sessions. This is an automated process based on load balancing and therefore cannot be changed. Please check target session and corresponding connectivity details in Request Center, as per the current process.

If an iLink 2 message is received on an iLink 3 session, that given session will be terminated immediately.

iLink 2 on CGW Decommission

iLink 2 on CGW will be decommissioned and all CGW sessions will support iLink 3 only. Following the decommission, client systems will not be able to make a TCP connection to iLink 2 CGWs.

Order Entry Service Gateway (OESGW) - SFTP Site Information

There will be a new Order Entry Service Gateway (OESGW) for customers to register administrative information. Customers will be able to use the same CGW session to connect to the Service Gateway using FIXP protocol and submit Party Details Definition Request messages and Party Details List Request messages. The Service Gateway supports FIXP Party Detail Request messages only; any other messages will be rejected.

The OESGW configuration information (i.e. OESGWs and IPs) for CGWs will be added to the iLink 3 config file via an SFTP site (sftpng.cmegroup.com) and accessed via CME Globex network direct connection. This SFTP site contains the configuration files for all environments. The SFTP site is a secure site that requires a username and password for access.

A new market segment will be defined for OESGW:

<marketsegment id="6" label="Globex OESGW for all CGWs">

System Architecture

The following diagrams provide an overview of the system architecture in support of the iLink 3 on CGW launch: 

Current State

This diagram depicts the current state of iLink CGW architecture.

  • CGW sessions support only iLink 2.

current architecture Copy

Parallel State

This diagram shows the production parallel state of iLink CGW architecture supporting both iLink 2 and iLink 3 on CGW messaging protocols.

For iLink 3 on CGW:

  • Each client system connects and sends messages to its new CGW session using the new configured IP and port. The CGW then routes the messages received to the appropriate matching engine.
    • During the production parallel state, CGW sessions will support both iLink 2 and iLink 3.


parallel cgw


Final State

This diagram shows the final state of iLink 3 on CGW architecture following the complete migration to the iLink 3 messaging protocol.

future state CGW


Developing from iLink 2 to iLink 3

The following table summarizes the impacts for client systems developing to iLink 3 and outlines the changes from iLink 2 to iLink 3.

Layer

Feature

iLink 2

iLink 3 

Presentation

Message encoding

Tag value ASCII encoding

Simple Binary Encoding

Session

Authentication, Recovery

FIX Transport (FIXT)

FIX Performance Session Layer (FIXP)

Application

Business logic

FIX semantics

Improved FIX semantics

Transport

End-to-end delivery

TCP

TCP

Network

Virtual Circuits, Routing

IP

IP

Simple Binary Encoding

iLink 3 uses Simple Binary Encoding (SBE) optimized for low latency encoding and decoding while keeping bandwidth utilization reasonably small. All FIX semantics are supported. This encoding standard describes the wire protocol for iLink 3 messages and is complimentary to other FIX standards for session protocol and application-level behavior.

iLink 3 on CGW will be launched in production using the schema version 8.    

iLink 3 CGW Session Layer

iLink 3 uses the FIX Performance (FIXP) protocol to establish and manage bi-directional sessions. Per the FIXP protocol, a FIX session is defined as a bi-directional stream of ordered messages between two parties within a continuous sequence number series. With this release, the iLink 3 Convenience Gateways (CGW) will support weekly client FIX sessions and also mid-week initialization.

For each customer, the CGW starts the session at the beginning of the week. A FIXP session will be maintained by default on a weekly basis; however, the customer can negotiate, establish, and terminate multiple times. Each FIXP session will also be represented with a Universally Unique ID (UUID), which should be a current timestamp.

The term, FIX connection, has a new connotation in iLink 3. A successful logon consists of a two-step process: negotiation and then establishment.

The exchange will support a FIXP session created at the beginning of the week all through the end of that week. The customer can then establish and terminate FIX connections multiple times intra-day or at the end of each day, with the same UUID or negotiate the new FIXP session with a new UUID as well.

Additional information on the new FIXP protocol is available in the Session Layer topic.  

iLink 3 CGW Business Layer

iLink 3 allows customers to optimize business message construction by pre-registering administrative information or by submitting administrative information per message (on-demand) as follows.

  • Pre-registered administrative information
    • For the most efficient business messaging (i.e. New Order Single, Mass Quote), customers pre-register administrative information in the new Service Gateway weekly.
  • On-demand administrative information
    • Customers send the administrative information to CGW with every business message.

iLink 3 business messages always include a reference to the pre-registered or on-demand administrative information.

Additional information on the new FIXP protocol is available in the Business Layer topic.  

iLink 3 CGW Messaging Impacts

Order Mass Status Request (35=AF)

Client systems may submit Order Mass Status Request (35=AF) messages to obtain statuses for all working orders with a single request.

To provide a consistent customer experience, a new enum value of 7 (for all orders) will be added to MassStatusReqTyp for the MassStatusRequestType field in the Order Mass Status Request (35=AF) message.

Tag NameBinary TypeBinary LengthReqEnumurationDescription
585MassStatusReqTypeMassStatusReqTyp1Y
  • MassStatusRequestType=1 (Instrument)
  • MassStatusRequestType=3 (Product Group)
  • MassStatusRequestType=7 (All Orders)  *only available for CGW sessions.
  • MassStatusRequestType=100 (Market Segment)

Specifies the scope of the Order Mass Status Request within the context of working orders only. Status will be returned for all orders matching the criteria specified here for Session and Firm.

Order Cancel and Cancel-Replace Requests by ClOrdID

Order Cancel and Cancel-Replace Requests by ClOrdID is a risk management feature that allows clients to cancel and modify resting orders using FIX tag 11-ClOrdID without providing tag 37-OrderID.

As a reminder, CME Group strongly recommends that clients do not change the ClOrdID value on a working order to prevent unexpected results on regulatory, support, and order status tools.

All iLink 3 sessions are enabled for Order Cancel and Cancel/Replace by ClOrdID functionality. 

Rejects for ClOrdID (tag 11) Uniqueness

To support order cancellation and order modification by tag 11-CIOrdID, this value must be unique per SenderComp (Session ID + Firm ID) for all working orders on a single market segment.

For an iLink 3 New Order tag 11-ClOrdID:

  • CME Globex will reject an order having the same ClOrdID and SenderComp as a currently working order on the given market segment. A duplicate ClOrdID will generate an iLink 3 Business Reject (tag 35-MsgType=j) message with tag 380-BusinessRejectReason = 133 and tag 58-Text = Duplicate ClOrdID: X not allowed.

A ClOrdID value can be re-used on the same market segment only when the prior order is no longer resting, for instance:

  • the prior order has been completely filled, or
  • the prior order has been cancelled, or
  • the prior order has been eliminated.

Processing for ClOrdID and OrderID Values

With this release, tag 37-OrderID is an optional tag in iLink 3 Order Cancel Request and iLink 3 Order Cancel/Replace Request messages for CME Group Futures and Options on Futures markets.

  • If an Order Cancel Request or Order Cancel Replace Request contains both CIOrdID and OrderID, then the OrderID will be used to look up the original order.
  • If a ClOrdID in an Order Cancel Request or Order Cancel/Replace Request is changed from what was in the original order:
    • the client should send an Order Cancel Request or Order Cancel/Replace Request with the latest CIOrdID accepted by CME Globex.
    • the client sending an Order Cancel Request or Order Cancel/Replace Request with the previous CIOrdID must provide an OrderID as well; otherwise, the Order Cancel/Replace Request will be rejected as order not found.
  • An Execution Report - Cancel and Execution Report - Modify message will return both ClOrdID and OrderID values.
  • An Order Cancel Reject and Order Cancel Replace Reject message will return both ClOrdID and OrderID values.

Cancel on Behalf (COB)

Currently, Cancel on Behalf (COB) functionality is not available for iLink Convenience Gateway (CGW) sessions. Beginning with this release, COB functionality on CME Globex will allow iLink CGW sessions to cancel resting orders and mass quotes from different iLink 3 sessions under the same CME Globex Firm ID (GFID). This functionality is enabled for all CME Group futures and options on futures on CME Globex. 

Good Till Cancel (GTC) and Good Till Date (GTD) orders

Customers should manage cancellation of GTC and GTD orders on iLink 2 sessions and resubmission of GTC and GTD orders on new iLink 3 sessions.

Market Integrity Controls

Messaging Controls

Messaging Controls prevent violation of the maximum Transactions per Second (TPS) rule. Messaging Controls measure Transactions per Second (TPS) and are enforced at the iLink session level.

iLink 3 for Convenience Gateways will have the same messaging controls as iLink 2 except for the changes described below.

Session Layer Messaging Controls

The thresholds are in place for the following Session Layer message types:

    • Negotiate
    • Establish
    • Terminate
    • Sequence
    • Retransmit Request

Application Messaging Controls

Module

Messaging Controls

Common

New Order (35=D)

Order Cancel Replace Request (35=G)

Order Status Request (35=H)

Security Definition Request (35=c)

Order Mass Status Request (35=AF)

Request for Quote (35=R)

New Order Cross (35=s)

Party Details Definition Request (35=CX)

Party Details List Request (35=CF)

Cancel

Order Cancel Request (35=F)

Order Mass Action Request (35=CA)

Mass Quote

Mass Quote (35=i)

Quote Cancel (35=Z)

Messaging Thresholds and Action Types

Messaging Thresholds

Action Type

Message Type

Error Code

Exceeding Reject Threshold

Reject subsequent messages until the TPS rate falls below the threshold.

Business Reject (tag 35-MsgType=j)

Tag 380-BusinessRejectReason=8

Exceeding Terminate Threshold

Terminate the offending iLink 3 session.

Terminate

Tag 39012-ErrorCodes=9

Party Details Messages 

Party Details messages can be counted in session layer or application layer messaging controls depending on whether the messages are sent to CGWs or OESGWs:

Messages

MSGWs

OESGW

PartyDetailsDefinitionRequest messages with PartyDetailsListRequestID≠0

Administrative Message Controls

Common Module

PartyDetailsDefinitionRequest messages with PartyDetailsListRequestID=0

Common Module

*Regardless of whether the PartyDetailsDefinitionRequest message is sent on-demand directly preceding each New Order-Single, Order Cancel Replace Request, Order Cancel Request, etc.

Administrative Message Controls

PartyDetailsListRequest

Administrative Message Controls

Common Module

Automated Port Closure

CME Globex will automatically terminate and close both the primary and backup ports for any iLink 3 session on the 5th invalid negotiate and establish attempts in 60 seconds.

Negotiate messages may be invalid due to:

  • Invalid or missing UUID
  • Invalid or missing HMAC Signature
  • Invalid or missing RequestTimestamp
  • Invalid or missing AccessKeyID
  • Invalid or missing Session
  • Invalid or missing Firm
  • Sending Negotiate message without waiting for NegotiationResponse/NegotiationReject from previous Negotiate message
  • Sending Negotiate message when session is already negotiated 
  • Sending Negotiate message when session is already established

Establish messages may be invalid due to:

  • Invalid or missing UUID
  • Invalid or missing HMAC Signature
  • Invalid or missing RequestTimestamp
  • Invalid or missing AccessKeyID
  • Invalid or missing Session
  • Invalid or missing Firm
  • Invalid or missing NextSeqNo
  • Sending Establish message without waiting for EstablishmentAck/EstablishmentReject from previous Establish message
  • Sending Establish message when session is already established 
  • Sending Establish message when session is not negotiated
  • Missing ApplicationSystemName
  • Missing TradingSystemVersion
  • Missing ApplicationSystemVendor
  • Invalid or missing KeepAliveInterval

Automated port closure can also be triggered by client systems sending messages other than Negotiate and Establish when the session has not been successfully established.

When triggered, CME Globex will send a Terminate message with tag 39012-ErrorCodes=8 (CMEAdministeredPortClosure: due to invalid number of Negotiate/Establish attempts being exceeded).

  • Sessions with active-active fault tolerance will receive the Terminate message on both the primary and backup instances.
  • Sessions without fault tolerance will only receive the Terminate message on the primary instance, but both the primary and backup ports will be closed.

Primary and secondary clearing firm administrators must contact the Global Command Center directly to have a port re-opened.

iLink 3 CGW Message Specifications

See the following topics for message specifications:

iLink 3 CGW Front-End Audit Trail Requirements 

The required audit trail specifications apply to all systems implementing iLink 3 CGW. All client systems must be certified for Audit Trail for iLink 3 CGW prior to using the production environment.

For additional information, please review the Market Regulation Advisory Notice on order routing and front-end audit trail regulatory requirements.

Contact Information

For technical development support, contact Certification Support for Electronic Trading (CSET).

For production requests, please contact the Global Command Center (GCC).

For all other inquiries, please contact Global Account Management (GAM).

  • No labels