Tuesday, May 24, 2016

UTP Vendor Alert #2016 - 4
Initial Bandwidth Recommendations For The Enhanced INET Platform Migration

Markets Impacted:

Products Impacted:

Contact Information:

What you need to know:

  • As announced in UTP Vendor Alert 2016-01, the Unlisted Trading Privileges (UTP) Operating Committee, comprised of all exchange participants and FINRA, announced its approval of the migration plan for the Securities Information Processor (SIP) to Nasdaq’s INET technology for the UTP data services.
  • UPDATE:
    • Based on the new INET SIP design and requirements of the UTP Committee to support increased capacity, upon launch, this distributed system will handle a minimum peak rate of two million messages per second, per data feed.
    • While it is not anticipated that the actual message rates currently being experienced to dramatically change, with regards to migration, the system is designed to accommodate a significant increase in throughput.
    • As required by the UTP Committee, the SIP will publish the system capability related to bandwidth. The initial recommendation per multicast group is 3.4 Gigabits.
  • The migration is scheduled to be completed in the fourth quarter of 2016. The production-ready environment is scheduled to launch October 10, 2016.

Overview:

The UTP Operating Committee (UTPOC) has contracted with Nasdaq to serve as the SIP. Nasdaq will migrate the legacy SIP technology to INET technology for the UTP data services. Nasdaq plans to launch the new INET technology for the SIP in the fourth quarter of 2016. The production-ready environment is scheduled for October 10, 2016.

What are the initial bandwidth recommendations for the new INET SIP data services?

As announced in UTP Vendor Alert 2016-01, the new data feeds will be designed to support an increase in the throughput and bandwidth. “Increased Capacity – Upon launch, this distributed system will handle a minimum peak rate of two million messages per second, per data feed.”

Based on initial findings of the system capabilities, we are providing a bandwidth recommendation of 3.4 Gigabits (Gb) per multicast group per data service. In order to optimize network resiliency, the A and B groups will not be received across the same connection within the same data center.

Depending on the downstream data recipients business and client requirements a network configuration could look as follows:

Data Service New York "A" New York "B" Chicago "A" Chicago "B"
UQDF Binary 3.4 Gb 3.4 Gb 3.4 Gb 3.4 Gb
UTDF Binary 3.4 Gb 3.4 Gb 3.4 Gb 3.4 Gb
Data Providers Connect 1st 10 Gb 2nd 10 Gb 1st 10 Gb 2nd 10 Gb

While we do not anticipate the actual message rates that recipients are experiencing to dramatically change with regards to migration we are designing the system to accommodate a significant increase in throughput. As you may be aware the UTP committee requires the SIP to publish to the street what the system is able to accommodate as its bandwidth recommendations. Please refer to the UTP Plan Quarterly Metrics for a historical look and peak message rates.

When can we expect to see activity over the new Binary IP’s??

As is stated in Migration Presentation, the new data feeds will be available for dissemination of test data on select weekends and nightly replay beginning with the first scheduled UAT on July 9th. The SIP and the UTP committee have given significant thought in scheduling the Binary Migration and not conflicting with the industry events that are held in June and the July 4th holiday. Given the importance of the Russell Industry event scheduled for June 24th, and the code freeze leading up to the Russell Rebalance, we do not anticipate being able to provide SIP INET Binary data service dissemination testing prior to the planned July 9th date.

In order to assist data recipients in testing the new message formats, prior to their dissemination on the new multicast groups, we have a test file for direct Data Feed Recipients. The file is intended for format testing only and will not be representative of production data.

This flat file is now available for Data Feed Recipients to download and begin to test the new formats. Please be advised that this file is a PCAP file and would need something like “Wireshark” or similar to open and process.

Who should I contact for additional information?