Hotspot Connectivity Manual

Transcription

1 Hotspot Connectivity Manual This document is updated from time to time, please ensure you are reading the latest version by refreshing the following link: Version 1.7 November BATS Global Markets, Inc. serves the institutional spot foreign exchange market through BATS Hotspot LLC and BATS Hotspot Europe Limited (collectively, Hotspot ). This document has been established for informational purposes only and none of the products or services described herein constitute advice or the recommendation of any product or service. This document is only intended for use by persons that qualify as Eligible Contract Participants under the U.S. Commodity Exchange Act or as Professional Clients or Eligible Counterparties under the Financial Services and Markets Act of 2000, as applicable. Persons that do not qualify should not act or rely upon it.

2 Change Log Version Description of change 1.3 Change Log added Definition of terms added Connectivity Order process added Updated Appendix B 1.4 List of Port s and IP s updated for London LD4 Port and IP list added for NY5 Connectivity Order process updated 1.5 More detail on internet migration options in NY5 Trans-Atlantic WAN availability Clarification of NY5 demarcation 1.6 NY5 certification requirement removed 1.7 Hotspot Link port ranges added for NY5 and LD4 Prod and Cert BATS Global Markets 2015 Page 2 of 12

3 Introduction This document explains the connectivity options available to both the US & UK Hotspot matching engines. This document will be updated regularly as further information becomes available. In summary: The London matching engine is a new instance at Equinix LD4 The New York matching engine is migrating to Equinix NY5 Participants are responsible for choosing their connectivity provider, arranging for connectivity to the data centre and paying all associated communications charges including cross-connects within the data center. It is not possible to access Hotspot using existing connectivity into the BATS equities markets. This applies to both LD4 & NY5 matching engines. Contacts Connectivity Inquiries prodsupport@hotspotfx.com New York & London Sales Inquiries Hotspotfxsales@bats.com London New York London Matching Engine Key Dates The schedule for go live of the London matching engine at LD4 is published at: New York Matching Engine Key Dates The schedule for the migration of the New York matching engine to NY5 is published at: See Appendix B for further detail regarding this migration. BATS Global Markets 2015 Page 3 of 12

4 Definition of terms For the purpose of this document please note the following terms: Existing Connectivity This refers to connectivity that participants currently have into the existing New Jersey Hotspot environment. Existing Connectivity is in the following locations: NY4 545 Washington (New Jersey) LD4 TY3 Existing Connectivity will not give access to the matching engine in LD4 New Connectivity This refers to new cross connects that participants request to access the new LD4 & NY5 environments. New Connectivity does not allow access to the New Jersey hotspot environment. New Connectivity options The following New Connectivity options only are supported. Data centre cross-connect Directly connected via metro ethernet circuit Extranet LD4 to NY5 connectivity Post migration of the NY matching engine to Equinix NY5, Hotspot will offer access to the NY5 matching engine from LD4 and vice-versa via a Hotspot provided trans-atlantic wide area network. Hotspot plans to offer all access protocols for market data, order entry & drop copy. This connectivity will be available from January 1, Further details, including pricing will be published after the NY matching engine migration to NY5. See Appendix A for connectivity protocols, IP addressing & TCP ports. Both certification and production services are available as per the table in Appendix A. Hotspot does not require participants to establish a VPN however all services apart from the Java GUI (available in NY5 only) will be restricted and require participants to provide their registered source IP address to access those services. BATS Global Markets 2015 Page 4 of 12

5 Data centre cross-connect London: Participants may cross connect from any of the Equinix Slough campus data centres ie LD4, LD5 or LD6 New York: Participants may cross connect from any of the Equinix Secaucus campus data centres ie NY4 & NY5 The technical and commercial relationship is between Equinix and the participant, Hotspot is not involved. Participant orders and pays for the cross connect Directly connected via metro ethernet Participants may connect via a metro ethernet circuit. No co-location space is required. Hotspot does not host telco equipment. The cross-connect from telco demarcation point can be ordered by Hotspot and recharged to the participant. Extranet Participants may connect using an extranet. Extranet supplier provisions high-speed up links for multiple participants. The technical and commercial relationship is between the extranet provider and the participant. Extranets must be approved by Hotspot. Physical Interfaces Only the following physical interface specifications are supported. Location Speed Media 10G LR (single-mode) Equinix NY5 / NY4 - US 1G LX (single-mode) 100Meg 100BaseT (copper) Equinix LD4 - UK 10G 1G 100Meg LR (single-mode) & SR (multi-mode) LX (single-mode), SX (multi-mode) & 1000BaseT 100BaseT (copper) Equinix LD5, LD6 - UK 10G 1G LR (single-mode) LX (single-mode) BATS Global Markets 2015 Page 5 of 12

6 Demarcation London: The demarcation between Hotspot and participant at Equinix LD4 is the patch frame within the Hotspot suite. New York: The demarcation between Hotspot and participant at Equinix NY4 & NY5 are the satellite patching cabinets in NY4 & NY5. All cross connects between participants and Hotspot are equal length in both NY4 & NY5. Bandwidth Guidance London: As the Hotspot London market is new, then it is not possible to provide a reliable estimate of required bandwidth, however participants are strongly advised to provision enough spare bandwidth to cope with growth and exceptional market conditions. Hotspot suggest a minimum of 1G. Insufficient bandwidth will cause dropped packets and TCP Retransmissions IP Addressing The details below apply to all New Connectivity methods Hotspot hosts use registered addresses for all data flows. Hotspot supports publicly registered participant addresses. If required, Hotspot can allocate a 10.x.y.z address block. This subnet can be split to provide transit P2P and host/nat subnets if needed. Hotspot supports static routing and dynamic routing via BGP. BATS Global Markets 2015 Page 6 of 12

7 Connectivity Ordering Process There are two options as outlined below: Hotspot encourages participants to organise New Connectivity and move away from the Existing Connectivity. Option 1 - New Connectivity Participants requesting New Connectivity are required to: Sign the Hotspot Connectivity Order Form The signed document should be returned to your account manager or prodsupport@hotspotfx.com Option 2 - Existing Connectivity NOTE: Existing Connectivity will not provide access to the new LD4 matching engine. New connectivity is required to access the LD4 matching engine (see Option 1 above). Participants with Existing Connectivity from NY4, LD4, 545 Washington, TY3 and the do not need to complete any further connectivity documentation if they plan to continue to utilize their Existing Connectivity to access the NY5 matching engine. Connectivity order process summary NY5: The following table summarises the options available and the documentation requirements for the NY5 migration, Do I need to sign the "Hotspot Connectivity Order Form" for the NY5 migration? Connecting From To Legacy HS To New NY5 Existing Physical Connectivity New Physical Connectivity Other Connectivity NY4 No No 545 No No TY3 No No LD4 No No NY4 n/a Yes NY5 n/a Yes No No Extranet No No Vendor No No BATS Global Markets 2015 Page 7 of 12

8 LD4: The following table summarises the options available and the documentation requirements for the new London LD4 matching engine. Do I need to sign the "Hotspot Connectivity Order Form" for the new LD4 London Matching Engine? Existing Physical Connectivity Connecting From To New LD4 NY4 n/a 545 n/a TY3 n/a LD4 n/a New Physical Connectivity LD4 Yes Other Connectivity Extranet Vendor No No No Certification Existing participants connecting to the existing New Jersey matching engine are not required to re-certify as part of the migration to NY5. Connectivity Testing Participants planning to use Existing Connectivity to access the NY5 matching engine can only test NY5 connectivity using the weekend tests, dates as below: 17 October 2015 Weekend test, all pairs 7 November 2015 Go-live weekend Hotspot strongly encourages all participants to use all available test opportunities. See hotspotfx.com/ny5 for details. BATS Global Markets 2015 Page 8 of 12

9 Appendix A.1 IP addresses & TCP ports for Hotspot NY5 Hotspot NY5 connectivity via cross connects Environment Service IP Prefix TCP Port Range Production Drop Copy / STP / Production FIX Order Entry / Production FIX Order Entry - Link / Production Java API / Production Java GUI / Production FIX BookFeed / Production FIX BookFeed - Link / Production Hotspot ITCH / Certification Drop Copy / STP / Certification FIX Order Entry / Certification FIX Order Entry - Link / Certification Java API / Certification Java GUI / Certification FIX BookFeed / Certification FIX BookFeed - Link / Certification Hotspot ITCH / Environment Hotspot NY5 connectivity via IP TCP Port Service address Range Open Restricted Production Drop Copy / STP Yes Production Java API Yes Production Java GUI Yes - Production FIX BookFeed Yes Certification Drop Copy / STP Yes Certification FIX Order Entry Yes Certification Java API Yes Certification Java GUI Yes - Certification FIX BookFeed Yes Certification Hotspot ITCH Yes Note New un-encrypted FIX Order Entry connections via the internet are not supported at NY5. Participants with existing FIX Order Entry via the internet have a migration option as detailed in Appendix B. Further details on the protocols above can be found at: BATS Global Markets 2015 Page 9 of 12

10 Appendix A.2 IP addresses & TCP ports for London LD4 Hotspot London LD4 connectivity via cross connects TCP Port Environment Service IP Prefix Range Production Drop Copy / STP / Production FIX Order Entry / Production FIX Order Entry Link / Production Java API / Production FIX BookFeed / Production FIX BookFeed Link / Production Hotspot ITCH / Certification Drop Copy / STP / Certification FIX Order Entry / Certification FIX Order Entry - Link / Certification Java API / Certification FIX BookFeed / Certification FIX BookFeed - Link / Certification Hotspot ITCH / Environment Hotspot London LD4 connectivity via IP TCP Port Service address Range Open Restricted Production Drop Copy / STP Yes Production Java API Yes Production FIX BookFeed Yes Certification Drop Copy / STP Yes Certification FIX Order Entry Yes Certification Java API Yes Certification FIX BookFeed Yes Certification Hotspot ITCH Yes Note Un-encrypted FIX Order Entry connections via the internet are not supported at LD4. There is no Java GUI access to the LD4 matching engine Further details on the protocols above can be found at: BATS Global Markets 2015 Page 10 of 12

11 Appendix B Hotspot New York migration to Equinix NY5 The migration date is November 9, 2015, the migration schedule is published at: There will be both certification and production environments at NY5 New Connectivity in NY5 & NY4 Hotspot encourages participants to install New Connectivity to the new Hotspot matching engine in NY5, this is the lowest latency connectivity option. All new cross connects from NY4 & NY5 will be latency equalized with equal cable length. Hotspot will offer access to the London matching engine in LD4 from January 1, 2016, this access will only be available via New Connectivity. Participants with Existing Connectivity to Hotspot Participants with Existing Connectivity to the current (pre-migration) Hotspot matching engine in New Jersey have the option to continue to use that connectivity to reach the new Hotspot environment in NY5 post-migration, however there are restrictions as detailed below. Existing Connectivity from NY4 Participants using Existing NY4 Connectivity can chose between 1. Connecting by targeting the new IP s 2. Connecting by targeting the existing IP s (ie no change) to a Hotspot provided Network Address Translation (NAT) option. The latency penalty for using Existing NY4 Connectivity is sub 100uS. Existing Connectivity from LD4, 545 Washington, TY3 and the Participants using Existing Connectivity from LD4, 545 Washington, TY3 and the will only be able to connect using the Hotspot provided Network Address Translation (NAT) option (ie no change) The latency penalty for using Existing Connectivity from LD4, 545 Washington, TY3 & internet to the new matching engine in NY5 is estimated to be 500uS. Note that Existing Connectivity in all locations will not give access to the London LD4 matching engine. Hotspot will announce the timetable for the shutdown of Existing Connectivity in due course, participants will be given a minimum of six months notice. BATS Global Markets 2015 Page 11 of 12

12 Extranets Participants with extranet connectivity to the current New Jersey matching engine are encouraged to contact their connectivity provider as soon as possible to discuss connectivity to the NY5 matching engines. The two points above regarding Existing and New Connectivity also apply to extranets. For the avoidance of doubt, extranets cannot use existing equites cross connects to access the Hotspot environment. Summary The above information is summarised below: Existing Connectivity New Connectivity Access to new NY5 ME NY4 545 TY3 LD4 NY4 NY5 New target IP's N/A N/A N/A ** ** Target existing IP's ( NAT Option ) N/A N/A N/A ** New un-encrypted FIX Order Entry connections via the internet in NY5 and LD4 are not available. BATS Global Markets 2015 Page 12 of 12