Refinitiv FX Trading (FXT) - Refinitiv FXall (AAA users)

Refinitiv FX Trading (FXT) - Refinitiv FXall (AAA users)

Document Version: 6.13

Date of issue: 16 December 2020

Network Summary Guide

Legal Information

Refinitiv FX Trading (FXT) - Refinitiv FXall (AAA users) Network Summary Guide

Document Version: 6.13 2

© Refinitiv 2020. All rights reserved.

Refinitiv does not guarantee that any information contained in this document is and will remain accurate or that use

of the information will ensure correct and faultless operation of the relevant service or equipment. Refinitiv, its

agents and employees, accepts no liability for any loss or damage resulting from reliance on the information

contained in this document.

This document contains information proprietary to Refinitiv and may not be reproduced, disclosed, or used in whole

or part without the express written permission of Refinitiv.

Any software, including but not limited to, the code, screen, structure, sequence, and organization thereof, and

documentation are protected by national copyright laws and international treaty provisions. This document is

subject to U.S. and other national export regulations.

Nothing in this document is intended, nor does it, alter the legal obligations, responsibilities or relationship between

yourself and Refinitiv as set out in the contract existing between us.

DOCUMENT CHANGE HISTORY

Version Date GUI Version

Comments

5.0 July 19 7.4

Renamed Table 12 to 12A, added new table 12B, Changes in Internet IP addresses for APAC FXT services in table 12A and table 12B, and table 22. Added new section on “FXT Changes To Internet IP Addresses For APAC Services” page 23

5.0.1 July 19 7.4 Minor corrections

5.0.2 Oct 19 7.4 Updated IP address for FXT Updater tool on page 29

5.0.3 Nov 2019

7.4

Update internet ip address 159.220.240.17-apac1.dealingws.trading.thomsonreuters.net, 159.220.240.18-apac1.dealingedge.trading.thomsonreuters.net, 159.220.240.19 - apac1.feededge.trading.thomsonreuters.net on pages 22,23 and 30

5.0.4 Nov 2019

7.4 Minor corrections

5.0.5 Dec 2019

7.4 Update to table on page 21, collab.thomsonreuters.com update IP address to 155.46.36.33

5.0.7 Jan 2020 7.5 The FQDN matchingcredit.trading.thomsonreuters.net has been removed on page 33.

5.0.8 Feb 2020

7.5 Update to table on page 21, collab.thomsonreuters.com rollback IP address to 159.220.0.155 and 192.165.211.75, and minor edits

6.0 July 2020

7.7

This document covers a major infrastructure update, adding support for the Refinitiv domain. It is mandatory that all client’s local network support both the Refinitiv domain, and Thomsonreuters domain. All users must upgrade to FXT version 7.7 or above by 31st July 2021.

6.2 Sep 2020

7.7 Updates to fully qualified domain names used by the MCA service on page 38, 39

Legal Information



Version Date GUI Version

Comments

6.3 Oct 2020 7.7 Updates to IP addresses for Refinitiv Remote Support Service (TRRS). Table 18, page 32

6.4 Oct 2020 7.7 Rationalised FQDNs for FX Trade Reporting. Table 19, page 33

6.5 Oct 2020 7.7 Changed IP addresses for apac1-feededge.trading.refinitiv.net, apac1.dealingedge.trading.thomsonreuters.net, apac1.apps.cp.thomsonreuters.com

6.9 Nov 2020

7.7 Update to IP address in table 12a (marked in Red), Updated document with Refinitiv Managed Connection as new name for Delivery Direct.

6.10 Nov 2020

7.7 Date change on page 23.

6.11 Nov 2020

7.7 Added section "SSL inspection is not supported with FXT/FXall” on page 9.

6.12 Dec 20 7.7

Syntax of example in Chapter 4 corrected:

emea1-dealingws.trading.refinitiv.net.

6.13 Dec 20 7.8 Updated tables 23 and 13a, and update to Intended Readership section.

Contents



Contents Document Change History .................................................................................................................. 2

About this document........................................................................................................... 6

Intended Readership ........................................................................................................................... 6

In this document .................................................................................................................................. 6

For further information ......................................................................................................................... 6

Feedback ............................................................................................................................................. 6

Chapter 1 Mandatory migration to the Refinitiv domain for all users......................... 7

FXT/FXall versions .............................................................................................................................. 7

Change of name of Refinitiv Delivery Direct ....................................................................................... 7

Chapter 2 Delivery Channel Selection .......................................................................... 8

General FXT/FXall Delivery Channel Considerations ......................................................................... 8

SSL inspection is not supported with FXT/FXall ................................................................................. 9

Refinitiv Managed Connection and Financial Community Network delivery channel Considerations 9

Internet delivery channel Considerations ............................................................................................ 9

Chapter 3 Bandwidth – Minimum requirements for FXT/FXall GUI ............................12

Circuit Size ........................................................................................................................................ 13

CRL and OCSP ................................................................................................................................. 13

Originating IP Address Validation...................................................................................................... 13

Use of IP Addresses .......................................................................................................................... 14

DNS Suffixes ..................................................................................................................................... 14

IP Subnets ......................................................................................................................................... 15

IP Subnet for Electronic Trading ....................................................................................................... 16

FCN and Refinitiv Managed Connection eDNS – Thomson Reuters ............................................... 16

FCN and Refinitiv Managed Connection eDNS – Refinitiv ............................................................... 16

Chapter 4 FXT/FXall Desktop Installation ....................................................................17

Chapter 5 Typical Connectivity Architecture ..............................................................18

Chapter 6 FXT/FXall Desktop Application ...................................................................19

FQDNs, Ports, Protocols and IPs ...................................................................................................... 19

Refinitiv Domain ................................................................................................................................ 20

Domain support and FXT/FXall versions .......................................................................................... 20

Level One network access ................................................................................................................ 20

FQDNs used for FXT/FXall GUI ........................................................................................................ 21

Geographical Latency Considerations .............................................................................................. 25

Client LAN Latency ............................................................................................................................ 25

Heartbeat and reconnection feature .................................................................................................. 25

Network Resilience and Refinitiv Managed Connection CPE ICRL .................................................. 25

Contents



CRL and OCSP ................................................................................................................................. 29

Refinitiv Remote Support Service (TRRS) ........................................................................................ 29

refinitiv FX trade reporting (previously called Dealing Xtra) .............................................................. 29

FXT Updater ...................................................................................................................................... 30

Features ............................................................................................................................................ 30

Chapter 7 FXT In-Trade Adaptor (DTF) ........................................................................32

FQDNs, Ports, Protocols and IPs xx ................................................................................................. 32


CRL and OCSP ................................................................................................................................. 33

Chapter 8 FXT Post Trade Adaptors (DTFE, TOF, Conversation and Ticket Print) ...34

FQDNs, Ports, Protocols and IPs ...................................................................................................... 34


CRL and OCSP ................................................................................................................................. 34

Bandwidth for FXT adaptors .............................................................................................................. 34

Chapter 9 Refinitiv FX Matching Credit Administration (MCA) ..................................35

FQDN and IP address table .............................................................................................................. 36

Chapter 10 Refinitiv Deal Tracker FIX Archiver .............................................................37

Appendix A FXall (Siteminder) FQDNs ...........................................................................38

About this document



About this document

INTENDED READERSHIP

This document is intended for Refinitiv FX Trading (FXT) and Refinitiv FXall users that log in using their corporate email address. This is referred to as Refinitiv Authentication, Authorization and Accounting (AAA).

This document does not apply to FXall users that log in using their FXall ID. This is known as FXall Siteminder. FXall Siteminder clients should use Refinitiv FXall Siteminder via Refinitiv Managed Connection (Delivery direct).

IN THIS DOCUMENT

The document provides a summary of key network information required for operation of both the Refinitiv FXT/FXall desktop application (including the Configuration Management component) and the suite of In-Trade/Post Trade feed adapters, of which the overall FXT/FXall solution is comprised.

This document does not describe the provision of network delivery channels.

FOR FURTHER INFORMATION

For questions or further information related to FXT/FXall, please contact the global Refinitiv help desk using the link below.

MyRefinitiv – Contact Us

FEEDBACK

If you have any comments on this document, please contact the global Refinitiv help desk using the link below.

MyRefinitiv – Contact Us

https://transactions.refinitiv.com/filebase/documents/components/GAgalS%2BYstLmVJ5k8KER19R8xLncfa68R1WjNoRIgbY

https://my.refinitiv.com/content/mytr/en/helpandsupport.html

https://my.refinitiv.com/content/mytr/en/helpandsupport.html

Chapter 1 Mandatory migration to the Refinitiv domain for all users



Chapter 1 Mandatory migration to the Refinitiv

domain for all users

The Refinitiv FX Trading infrastructure is being updated as we transition our brand, products and technology from Thomson Reuters to Refinitiv. This impacts all FX Trading users and FXall users that login using their corporate email address.

Starting from FXT/FXall version 7.7, FQDNs that currently use the Thomson Reuters domain will be moving to the Refinitiv domain. For example, emea1.dealingws.trading.thomsonreuters.net will be replaced with emea1-dealingws.trading.refinitiv.net.

This document has been updated to reflect the required changes in FQDNs to map to the Refinitiv domain.

NOTES It is mandatory that clients support BOTH the Thomsonreuters.com domain and Refinitiv.com Domain on their Client Network BEFORE installing FXT version 7.7 or above. This includes clients that access FXT/FXall services via Refinitiv Managed Connection, FCN and Internet. An announcement will be made when the Thomson Reuters domain is fully decommissioned for FXT services.

FXall services that have migrated onto the Thomson Reuters/Refinitiv AAA services must support both the Thomsonreuters.com domain and Refinitiv.com Domain on their Client Network BEFORE installing FXT/FXall version 7.7 or above.

Warning: As part of service resilience, services may be switched to other areas/regions. In order to have access to a fully resilient service all FQDNs must be configured and accessible regardless of user’s location and FQDN area.

Warning: Over time Refinitiv will be moving services to cloud based access. This means that IP address listed in this document may change with little or no notice. We strongly recommend that clients do NOT hard code IP addresses into Clients Network security devices and instead use the FQDNs listed.

FXT/FXALL VERSIONS

The domain you connect to is dependent on the FXT/FXall version you are using as per the tables in the following chapters.

FXT version Domain used Example FQDN

FXT/FXall version 7.6.x and below

Thomson Reuters emea1.dealingws.trading.thomsonreuters.net

FXT/FXall version 7.7 and above

Refinitiv

Note Some services will continue to use the Thomson Reuters Domain)

emea1-dealingws.trading.refinitiv.net

CHANGE OF NAME OF REFINITIV DELIVERY DIRECT

Please be aware that Delivery Direct has been renamed Refinitiv Managed Connection. The new name, Refinitiv Managed Connections is used in this document. This is a change to the name only.

Chapter 2 Delivery Channel Selection




All FXT/FXall services are available over the public internet and private network (Refinitiv Managed Connection or Financial Community Network), the FXT/FXall solution is delivery channel agnostic. The delivery channel that is used is determined by the customer infrastructure (customer DNS forwarding and subsequent FQDN resolution) and not by FXT/FXall application or user profile driven preference.

Where a FQDN is shared across multiple customer deployed Refinitiv’ products i.e. products in addition to FXT/FXall, the prevailing resolution and resulting IP address will apply to all consumers of that service when resolution is requested by a consuming application.

GENERAL FXT/FXALL DELIVERY CHANNEL CONSIDERATIONS

MTU (Maximum Transmission Unit)

To function correctly and make full use of network bandwidth the FXT/FXall desktop application requires an IP MTU of 1500 bytes to be set on the client’s system (resulting in a maximum segment size of 1460 bytes). To ensure that this IP MTU is processed correctly any client site network components must have their network interface MTU set to 1518 bytes. This allows for a full size 1500 byte IP frame plus 14 bytes for Ethernet headers and 4 bytes for the FCS (frame Check Sum).

The clients ISP will need to ensure they can accept full size 1518 byte frames. If they are adding any additional headers or tags (e.g. VLAN tag or QOS value) they will need to increase their network device interface MTU accordingly.

MTU diagram

Standard maximum size 1518 byte frame

Destination

MAC 6 bytes

Source MAC

6 bytes

IP Header 20

bytes

TCP Header

20 bytes

FCS

4 bytesTCP Payload (not to scale) Up to 1460 bytes

Ethernet header 14 bytes

Ethernet type

2 bytes

IP or layer three MTU – 1500 bytes

MSS (maximum segment size) – 1460 bytes

Ethernet or layer two MTU – 1514 bytes

Network device interface MTU – 1518 bytes

HTTP(S) Tunnelling

A number of FXT/FXall services consumed by the desktop application and feed adapters make use of the HTTP(S) Tunnelling method HTTP Connect, a number of commercial HTTP Proxy Servers do not have this feature enabled by default, HTTP Connect tunnelling must be available for FXT/FXall Desktop application operation.

Delivery Channel Failover

As already noted, the FXT/FXall solution is delivery channel agnostic, where delivery channel failover is required e.g. from Refinitiv Managed Connection to Public Internet or vice versa, this would be effected by a reconfiguration of DNS resolution precedence in respect of the FXT/FXall FQDNs.

Where a delivery channel failover has taken place, FXT/FXall components may require to be restarted, depending on a client’s DNS TTL, a DNS Flush may also be required to force re-resolution prior to FXT/FXall restart.

For info, the default FXT/FXall Refinitiv Managed Connection DNS TTL is 20 minutes, FXT Post Trade is an exception with a TTL of 5 minutes, the prevailing public internet DNS TTL is 30 seconds.




NOTE A Delivery Channel Failover will result in a change in the Originating IP Address used to access the FXT/FXall application. Clients using Delivery Channel Failover should ensure that both Internet and Refinitiv Managed Connection originating IP addresses are provided to Refinitiv.

Client LAN Latency

FXT/FXall components are hosted on client network nodes and therefore FXT/FXall data must transition through client network infrastructure, competing with non FXT/FXall client network traffic for resource, sufficient consideration must therefore be given to client network incurred latency and bandwidth availability.

SSL INSPECTION IS NOT SUPPORTED WITH FXT/FXALL

Refinitiv does not support FXT/FXall with use of enforce SSL inspection (sometimes called TLS/HTTPS Interception). If clients use SSL inspection they must configure URL filtering profiles to NOT enforce SSL inspection on any domains used by the FXT/FXall GUI. For example, you must trust all FQDNs from *.thomsonreuters.com, *.thomsonreuters.net, *.thomsonreuters.biz and *.refinitiv.com, *.refinitiv.net, *.refinitiv.biz domains.

REFINITIV MANAGED CONNECTION AND FINANCIAL COMMUNITY NETWORK DELIVERY

CHANNEL CONSIDERATIONS

Inter Chassis Redundancy Link (ICRL)

On FCN and Refinitiv Managed Connection sites it is recommended that an ICRL should be installed between FCE or Refinitiv Managed Connection CPE’s. The ICRL will provide uninterrupted access to FXT/FXall services in the event of a single site WAN failure and the failure of a single site PoP.

Sufficient consideration should be given to ICRL latency between CPE’s and the impact on overall RTT, additionally; the ICRL should be capable of carrying all FXT/FXall traffic for a given CPE/site.

Please see Refinitiv Managed Connection documentation for further details on ICRL installation and configuration.

https://my.refinitiv.com/content/mytr/en/policies/private-network-overview.html

Financial Community Network (FCN)

In addition to Refinitiv Managed Connection and Internet, FXT/FXall is also supported on Financial Community Network (FCN). The network requirements for FCN are the same as Refinitiv Managed Connection implementations (for example use the same eDNS and FQDNs).

Further information on FCN is available via the following link:


INTERNET DELIVERY CHANNEL CONSIDERATIONS

Whereas Refinitiv Managed Connection uses comms providers who are under contract to Refinitiv for end to end service provision, internet delivery relies on one or more third-party Internet Service Providers (ISPs) who are under client contract and who Refinitiv has no control over.






Network setup for maximum resilience

The client IT department should confirm that the FXT/FXall users’ connection to the internet is resilient to single component or provider failure. It is recommended that customers using Refinitiv products over the Internet have transit connections to at least two Internet Service Providers (ISPs) and use them in a multi-homed setup. A multi-homed connection architecture ensures that in the event of component failure on the ISP level, such as a circuit breakdown, service disconnection or hardware error, the remaining services will continue to support the service, without user-discernible impact.

When considering multi-homing, i.e. using more than one ISP at the same time, for resilience, it is important that customers do not select two ISPs where one is the sole upstream transit supplier to the other. In such a situation, despite being rare, the failure of the upstream supplier will result in the failure of the other.

Client IT departments should consult the Heartbeat and Reconnection Feature section of this document to be able to provide guidance on whether the client ISP resilience would result in a disconnection of FXT/FXall users.

Connection Capacity

Refinitiv provides bandwidth requirements for FX Trading in this document. Client IT departments should review this and confirm back that this bandwidth level can be supported by the client’s network and ISP partners without packet loss.

Clients should monitor their bandwidth usage to ensure their available Internet access capacity remains appropriate for the robust, uninterrupted and highly resilient operation.

Clients should be aware that lower tier internet offerings may offer a headline bandwidth figure which is not guaranteed. This may cause disconnects or instability in the FXT/FXall product at these times. For clients with the recommended resilient ISP setup, Refinitiv recommends that each ISP access link has enough capacity to carry the entirety of the customer’s Internet traffic, i.e. observed peak traffic demand does not saturate more than 50% of the link’s capacity.

Domain Name System and Resolution

In order to minimise the impact of any issues arising from outages in the customer’s network or global Internet, Refinitiv recommends customers concurrently use DNS servers located in many different locations. This could be e.g. a server inside the customer’s network and one in an ISP system, or one in the customer local network and one in the disaster recovery centre. It will not be possible to access the FXT/FXall service if name resolution is impaired, so the appropriate level of DNS server reach is integral to resilience and quality of experience. DNS resolution (to either internet IP addresses or Refinitiv Managed Connection IP addresses) is also integral to ensuring that all users are using the preferred delivery channel.

Application flow diagnostics

To assist in diagnosing network issues, Refinitiv may require the client to provide packet capture information of the FXT/FXall application flows, taken from the perimeter of the client network.

Service Level

When planning the deployment of FXT/FXall using the Internet, the client IT department should provide clarity about what SLAs the client Internet Service Providers provide, and should relate this to the business impact should the FXT/FXall connection be unavailable. Refinitiv uses backbone (otherwise known as Tier 1) ISPs.

Security

Although the FXT/FXall product offers end to end encryption of data between client hardware and Refinitiv (see the FX Trading Security FAQ for more details), the security of the hardware at the client site which runs the FXT/FXall software can be compromised by unauthorised third parties if the client internet connection is not adequately secured.

https://transactions.thomsonreuters.com/filebase/documents/components/WwDUefhbLiL%2BSH1H04XT%2BwR2RpQOB52ZZuhNqcb5opk




Proxy Support

Basic and NTLM squid and NTLM Bluecoat Proxy authentication is supported via user name and password authentication. Smart card authentication is not supported.

The table below show the different Proxy authentication types and support status.

Authentication Type FXT/FXall 7.x GUI

Treasury Center (FXT 7.x)

Electronic Trading (FXT 7.x)

PTF 1.4

No Proxy / Direct connection

Yes Yes Yes Yes

Basic Authentication Yes Yes Yes Yes

NTLM* Yes Yes Yes No

Kerberos* No No No No

Table 1 – Authentication types

* Tested with Squid and Bluecoat

Chapter 3 Bandwidth – Minimum requirements for FXT/FXall GUI



Chapter 3 Bandwidth – Minimum requirements for

FXT/FXall GUI

The following tables show the minimum bandwidth requirements for FXT GUI. Bandwidth is calculated depending on the services within FXT that the end users utilize. All user must have FXT Basic with addition bandwidth added, for Matching, Quick Trade, and Price stream plus any other services.

All FXT Users must have the following bandwidth to cover Dealing functionality:

Users FXT Basic

First User 160Kbps

Each Subsequent 128Kbps

Table 2 - FXT basic bandwidth for Dealing functionality

On top of the basic bandwidth, user must add additional bandwidth depending on the servicers being used and the usage of the product, as per table below:

Users FXT Matching * Quick Trade/POMS

Price Steam (Low usage up to 5 providers)

Price Steam

Price Steam (Mid usage up to 10 providers)

Price Steam (High usage over 10 providers)

Electronic Trading

First User 256 Kbps 700 Kbps 1000 Kbps 1500 Kbps 2000 Kbps 256 Kbps

Second User 512 Kbps 1300 Kbps 1700 Kbps 2700 Kbps 3700 Kbps 512 Kbps

Five Users 1280 Kbps 3100 Kbps 3800 Kbps 6300 Kbps 8800 Kbps 1280 Kbps

Ten Users 2560 Kbps 5100 Kbps 5100 Kbps 10300 Kbps 15300 Kbps 2560 Kbps

Table 3 - FXT additional bandwidth for trading functionality

*FXT Matching includes Matching Spot, Forward, NDF, Order Book and Treasury Centre are referred to as premier users.

As an example, if the site was a single user of Dealing, Matching forwards, and Price Steam (over 10 providers) the following bandwidth is required:

160 Kbps + 256 Kbps + 2000 Kbps = 2416 Kbps

As second example if the site was a five user of Dealing, Matching forwards, and Price Steam (over 10 providers) the following bandwidth is required

672 Kbps + 1280 Kbps + 8800 Kbps = 10752 Kbps

The Table below shows the minimum bandwidth required for FXall users:

Users

FXall Basic *

Price Stream (Low usage up to 5 providers)

Price Stream

(Mid usage up to 10 providers)

Price Stream (High usage over 10 providers)

First User 256 Kbps 1000 Kbps 1500 Kbps 2000 Kbps

Second User 512 Kbps 1700 Kbps 2700 Kbps 3700 Kbps

Five Users 1280 Kbps 3800 Kbps 6300 Kbps 8800 Kbps

Ten Users 2560 Kbps 5100 Kbps 10300 Kbps 15300 Kbps

Table 4 – Minimum bandwidth for FXall users




CIRCUIT SIZE

In addition to the minimum bandwidth requirements, clients must consider the relationship between total circuit size and the corresponding network insertion delay. As a simple rule the larger the circuit size the smaller the network insertion delay. The following table shows the recommended minimum total circuit size against number of FXT premier users (For example matching users).

Number of Users (up to)

Recommended Minimum Bandwidth for Dealing and Matching

Recommended Minimum Circuit Size

1 416 Kbps 6 Mbps

2 928 Kbps 6 Mbps

3 1312 Kbps 6 Mbps

4 1696 Kbps 10 Mbps

5 2080 Kbps 10 Mbps

6 2464 Kbps 10 Mbps

7 2848 Kbps 10 Mbps

8 3232 Kbps 10 Mbps

9 3616 Kbps 10 Mbps

10 4000 Kbps 20 Mbps

20 7840 Kbps 50 Mbps

30 11680 Kbps 50 Mbps

40 15520 Kbps 100 Mbps

50 19360 Kbps 100 Mbps

60 23200 Kbps 100 Mbps

70 27040 Kbps 100 Mbps

80 30880 Kbps 100 Mbps

90 34720 100 Mbps

100 38560 100 Mbps

Table 5 – Recommended Circuit Size

CRL AND OCSP

CRL and OCSP resources are only available over the Public Internet, revocation checking will fail where a host resides on a private network only i.e. Refinitiv Managed Connection and should therefore be disabled using the method appropriate to FXT component as defined in the following sections.

ORIGINATING IP ADDRESS VALIDATION

Access to FXT service end points are restricted to known originating IP addresses (X-Forwarded-For) associated to a client organisation, these can be individual addresses or where a pool is shared across an organisation, a subnet or subnets.

Originating IP addresses must always be unique to a client organisation, Refinitiv Managed Connection configuration will ensure originating IP addresses will always be unique however where Public Internet is used,




clients must ensure that originating addresses are not drawn from an ISP pool shared outside of their organisation, where this is the case static allocation or a dedicated pool is required.

NOTE All originating IP addresses used to access the FXT service must be added (white-list), this must include any resilient communication solutions clients may use. To allow resiliency of FXT services, all FQDN and any corresponding client originating IP addresses must be configured regardless of user’s location.

Clients can assign originating IP addresses as a single address or as a range. An example is show below:

Single or first Address in range Last Address in Range

86.54.32.16 86.54.32.31

Table 6 – Address range

There is no limit to the number of single IP addresses that can be assigned

NOTE IP validation is via IPv4 only. IPv6 is not supported.

USE OF IP ADDRESSES

While this document lists current FXT IP addresses for information, these are subject to change and no service dependency should be placed on their specification, FXT FQDNs are provided and should be used.

DNS SUFFIXES

The following table outlines the DNS Suffixes used by the overall FXT/FXall solution, please note that in many instances these Suffixes will be common to multiple Refinitiv products and sufficient consideration should be given to FXT/FXall related DNS changes on previously deployed Refinitiv products.

DNS Suffix Authoritative DNS Usage

*.cp.thomsonreuters.net Public Internet

Extranet DNS

FXT/FXall Desktop Application

FXT In-Trade Feed Adapter

*.trading.thomsonreuters.net Public Internet

Extranet DNS



FXT Post-Trade Feed Adapters

*.reuters.com

Note: one host only - “customers”

Public Internet

Extranet DNS FXT/FXall Desktop Application

*.extranet.thomsonreuters.biz Extranet DNS FXT/FXall Desktop Application

*.thomsonreuters.com Public Internet FXT/FXall Desktop Application

*.cp.extranet.thomsonreuters.biz Extranet DNS FXT/FXall Desktop Application

*.cp.thomsonreuters.com Public Internet FXT/FXall Desktop Application

*Refinitiv.net Public Internet

Extranet DNS



FXT Post-Trade Feed Adapters




DNS Suffix Authoritative DNS Usage

*Refinitiv.com Public Internet FXT/FXall Desktop Application


*Refinitiv.biz Extranet DNS FXT/FXall Desktop Application


Table 7 - FXT DNS Suffixes

IP SUBNETS

In order to meet latency and availability requirements, the FXT consumes services from endpoints provisioned across multiple Refinitiv datacentres globally.

The impact of the distribution of FXT service implementation is that there are no large contiguous subnet allocations in use, some sites using one or two IPs only and therefore no reasonable overall aggregation of FXT specific subnets exists.

Refinitiv Managed Connection FXT subnets are listed below, although the largest allocated range is /27, comparison with the Refinitiv Managed Connection IP addresses listed in table 5 will show that in most cases, only one or two IPs are allocated/used from each subnet.

The allocation of public internet addresses is less contiguous when compared to Deliver Direct, for this reason no subnets are shown, /32s can be assumed in most cases.

Refinitiv Managed Connection Subnets

Public Internet Subnets

159.43.2.96/28

N/A – refer to FQDN tables

159.43.5.192/27

159.43.8.0/27

159.43.10.0/25

159.43.16.16/28

159.43.16.32/27

159.43.16.128/27

159.43.16.176/28

159.43.17.128/25

159.43.18.8/29

159.43.20.8/29

159.43.30.0/27

159.43.22.72/32

159.43.31.0/27

159.43.32.32/27

159.43.32.64/27

159.43.32.112/28

159.43.33.64/27

159.43.34.48/28

159.43.13.0/25




Refinitiv Managed Connection Subnets

Public Internet Subnets

192.155.137.64/28

192.155.137.80/28

192.155.137.96/28

192.155.138.64/28

192.155.138.96/28

Table 8 – FXT IP Subnets

IP SUBNET FOR ELECTRONIC TRADING

For Electronic Trading (ET) users the following subnets are required. All use ports 443, 8443, 16000-16010:

Connection to Refinitiv Managed Connection Subnets

Ports

ET RET1 (LD4) 159.43.28.0/24 443, 8443, 16000-16010

ET RET2 (LD4) 159.43.29.0/24 443, 8443, 16000-16010

ET RET(NJ2) 159.43.9.1/24 443, 8443, 16000-16010

ET RET(NJ2) 159.43.168.0/24 443, 8443, 16000-16010

Table 9 – Electronic Trading IP Subnets

FCN AND REFINITIV MANAGED CONNECTION EDNS – THOMSON REUTERS

The Thomson Reuters eDNS details are in the table below:

eDNS Location IP Address FQDN

London 192.152.41.71 edns04.uk.extranet.thomsonreuters.biz

New York 192.152.41.91 edns04.us.extranet.thomsonreuters.biz

Singapore 192.152.41.101 edns04.sg.extranet.thomsonreuters.biz

Table 10 - Refinitiv Managed Connection DNS Servers

FCN AND REFINITIV MANAGED CONNECTION EDNS – REFINITIV

As part of the migration from the Thomson Reuters Domain to the Refinitiv domain the eDNS servers will change. The new Refinitiv FCN and Refinitiv Managed Connection eDNS server details are provided below:

eDNS Location IP Address FQDN

London 192.152.41.71 edns04.uk.extranet.refinitiv.biz

New York 192.152.41.91 edns04.us.extranet.refinitiv.biz

Singapore 192.152.41.101 edns04.sg.extranet.refinitiv.biz

Table 11 - Refinitiv Managed Connection DNS Servers

Chapter 4 FXT/FXall Desktop Installation



Chapter 4 FXT/FXall Desktop Installation

The Fully Qualified Domain Names (FQDN) used by the FXT desktop to connect to the FXT hosts are the same whether the connection is via FCN, Refinitiv Managed Connection or the Internet.

Generally these are:

• *.net FCN, Refinitiv Managed Connection and Internet

• *.biz FCN and Refinitiv Managed Connection

• *.com Internet

For example: emea1-dealingws.trading.refinitiv.net.

The configuration of DNS forwarding for hosts on the refinitiv.net domain will determine if the FXT host resolves to an IP address on FCN/Refinitiv Managed Connection or an IP address on the Internet.

Where Refinitiv Managed Connection is the selected delivery channel, the local client DNS should be configured to selectively forward FXT service FQDN DNS queries to the Refinitiv Managed Connection eDNS server. For Internet delivery, the client DNS should forward queries to the Public DNS. Network traffic will then be routed accordingly.

It is possible for clients to use different delivery methods for different locations. For example, a client could use Refinitiv Managed Connection for FXT on a primary site and the Internet on a business continuity secondary site.

Refinitiv.net

Chapter 5 Typical Connectivity Architecture



Chapter 5 Typical Connectivity Architecture

The diagram below describes the fundamental operational components of an FXT installation.

Refinitiv Datacentre

Client site

FXT desktop

Messaging

& Directory

Delivery Direct

/ Internet

Dealing Services Platform Eikon platform

Authentication,

Preference, and

Profile services

Authentication,

Authorisation &

Administration

Dealing network

Blotters

Order BookDealingMessaging

Roster

Review / Blotter

services

Aggregator

FXT Login MatchingPrice

Stream

Relationship

Trading

POMS

Matching

HostOrder Book

Price

Stream

Client

Compliance

Engine

AUTEX

Client Fix

Engine

Post Trade

Feeds

Conversation

printer

Ticket printer

Ticket Output

Feed

Client Fix

Engine

DTFE

Post Trade

RTN

DTF

Conversation

service and

analysis

Blotter

Chapter 6 FXT/FXall Desktop Application




FQDNS, PORTS, PROTOCOLS AND IPS

The FXT/FXall Desktop application consumes services exposed over protocols/ports HTTPS/443. As previously stated, all FXT/FXall Desktop application services are available through both supported delivery channels (Refinitiv Managed Connection and Internet), client DNS forwarding and resolution determining the (single) channel used by an FXT/FXall Desktop instance.

FXT/FXall and Eikon share some DNS FDQNs and so it is recommended that customers should use the same Refinitiv access network for FXT/FXall and Eikon.

For example:

• If a customer is using the Internet to consume Eikon content then the customer should use the Internet to connect to and consume FXT/FXall.

• If a customer is using FCN to consume Eikon content then the customer should use the same FCN set to connect to and consume FXT/FXall

• If a customer is using Refinitiv Managed Connection to consume Eikon content then the customer should use the same Refinitiv Managed Connection set to connect to and consume FXT/FXall

For legacy FXall users, please refer to Appendix A FXall (Siteminder) FQDNs on page 38.

Table 7 lists the FDQNs and IPs used by the FXT/FXall desktop.

Warning: In order to have access to a fully resilient service all FQDNs must be configured and accessible

regardless of user’s location and FQDN area.

To aide in the interpretation of FQDNs, FXT/FXall utilises the following naming standard:

Top Level Domain (TLD)

Delivery Channel

Description

.biz

Refinitiv Managed Connection and FCN

Service FQDN accessible via Refinitiv Managed Connection and FCN, identifiable by the 3rd level domain of “extranet” and a TLD of .biz

Example: emea1-apps.platform.refinitiv.biz

There will always be a corresponding Internet only service FQDN, identifiable by a TLD of .com and the absence of a third level domain of “extranet”

.com Internet

Service FQDN accessible via Internet only, identifiable by the TLD of .com

Example: emea1-apps.platform.refinitiv.com

There will always be a corresponding Refinitiv Managed Connection only service FQDN, identifiable by a TLD of .biz and a 3rd level domain of “extranet”

.net

FCN and Refinitiv Managed Connection

and

Internet

Single service FQDN accessible via either FCN, Refinitiv Managed Connection and Internet.

Example: emea1-dealingedge.trading.refinitiv.net

Table 12 - FQDN Naming Standard




REFINITIV DOMAIN

As part of the migration from Thomson Reuters to Refinitiv, Starting from FXT/FXall version 7.7 FQDNs that currently use the Thomson Reuters domain will be moving to the Refinitiv domain. For example, emea1.dealingws.trading.thomsonreuters.net will be replaced with emea1-dealingws.trading.refinitiv.net.

This document has been updated to reflect the required changes in FQDNs to map to the Refinitiv domain.

NOTES It is mandatory that clients support BOTH the Thomsonreuters.com domain and Refinitiv.com Domain on their Client Network BEFORE installing FXT/FXall version 7.7 or above. This includes clients that access FXT services via Refinitiv Managed Connection, FCN and Internet. An announcement will be made when the Thomson Reuters domain is fully decommissioned for FXT/FXall services.

FXall services that have migrated onto the Thomson Reuters/Refinitiv AAA services must support both the Thomsonreuters.com domain and Refinitiv.com Domain on their Client Network BEFORE installing FXT/FXall version 7.7 or above.

Warning: As part of service resilience, services may be switched to other areas/regions. In order to have access to a fully resilient service all FQDNs must be configured and accessible regardless of user’s location and FQDN area.

Warning: Over time Refinitiv will be moving services to cloud based access. This means that IP address listed in this document may change with little or no notice. We strongly recommend that clients do NOT hard code IP addresses into Clients Network security devices and instead use the FQDNs listed.

DOMAIN SUPPORT AND FXT/FXALL VERSIONS

The domain you connect to is dependent on the FXT/FXall version you are using as per the tables in the following chapters.

FXT/FXall version Domain used Example FQDN

FXT/FXall version 7.6.x and below

Thomson Reuters emea1.dealingws.trading.thomsonreuters.net

FXT/FXall version 7.7 and above

Refinitiv (Note That some services will continue to use the Thomson Reuters Domain)

emea1-dealingws.trading.refinitiv.net

LEVEL ONE NETWORK ACCESS

To simplify network access to Refinitiv FXall servers the following level one FQDNs can be added to your LAN security devices:

*.refinitiv.com,

*.refinitiv.net,

*.refinitiv.biz,

*.fxall.com,

*.thomsonreuters.com,

*.thomsonreuters.net,

*.thomsonreuters.biz




FQDNS USED FOR FXT/FXALL GUI

As noted above for FXT/FXall version 7.7 and above we require both Thomson Reuters and Refinitiv Domain FQDN to be supported on the client network.

customers.reuters.com is replaced by my.refinitiv.com. my.refinitiv.com is a public cloud hosted service and so no dedicated IP address is assigned, and can change at any time.

Items highlighted in YELLOW are Not Live as of date of document. These are due to go live in Q1 2021.

Items listed in RED text have changed value since version 6.5 document revision

FQDN for Thomson Reuters Domain (FXT/FXall 7.6 and below)

FQDN for Refinitiv Domain (FXT/FXall 7.7 and above)

Internet

Updated Internet IP address for Refinitiv domain

Refinitiv Managed Connection/FCN

amers3.fxtcreditadmin.trading.thomsonreuters.net amers3-fxtcreditadmin.trading.refinitiv.net 209.191.134.210 159.43.8.24

amers1.apps.cp.extranet.thomsonreuters.biz amers1-apps.platform.refinitiv.biz N/A 192.155.137.19

amers1.apps.cp.thomsonreuters.com amers1-apps.platform.refinitiv.com 159.220.40.41 164.57.211.134 N/A

amers1.dealingedge.trading.thomsonreuters.net amers1-dealingedge.trading.refinitiv.net 159.220.41.130 159.43.2.98

amers1.dealingws.trading.thomsonreuters.net* amers1-dealingws.trading.refinitiv.net 159.220.41.129 159.43.2.97

amers1.fxt.cp.extranet.thomsonreuters.biz amers1-fxt.trading.refinitiv.biz N/A 192.155.137.22

amers1.fxt.cp.thomsonreuters.com amers1-fxt.trading.refinitiv.com 159.220.40.40 164.57.211.138 N/A

amers1.heartbeat.cp.thomsonreuters.net amers1.heartbeat.ciam.refinitiv.net 159.220.40.126 192.155.137.73

amers1.login.cp.thomsonreuters.net amers1.identity.ciam.refinitiv.net 159.220.40.98 192.155.137.66

amers1.test.cp.extranet.thomsonreuters.biz** amers1-test.platform.refinitiv.biz N/A 192.155.137.19

amers1.test.cp.thomsonreuters.com** amers1-test.platform.refinitiv.com 159.220.40.110 164.57.211.134 N/A

amers1.views.cp.extranet.thomsonreuters.biz amers1-views.platform.refinitiv.biz N/A 192.155.137.19

amers1.views.cp.thomsonreuters.com amers1-views.platform.refinitiv.com 159.220.40.105 164.57.211.134 N/A






Internet



amers2.apps.cp.extranet.thomsonreuters.biz amers2-apps.platform.refinitiv.biz N/A 192.155.138.22

amers2.apps.cp.thomsonreuters.com amers2-apps.platform.refinitiv.com 159.220.54.3 159.220.53.111 N/A

amers2.fxt.cp.extranet.thomsonreuters.biz amers2-fxt.trading.refinitiv.biz N/A 192.155.138.23

amers2.fxt.cp.thomsonreuters.com amers2-fxt.trading.refinitiv.com 159.220.54.23 159.220.53.116 N/A

amers2.heartbeat.cp.thomsonreuters.net amers2.heartbeat.ciam.refinitiv.net 192.165.219.171 192.155.138.73


amers2.views.cp.extranet.thomsonreuters.biz amers2-views.platform.refinitiv.biz N/A 192.155.138.22

amers2.views.cp.thomsonreuters.com amers2-views.platform.refinitiv.com 192.165.219.184 159.220.53.111 N/A

amers3.fxtaggie.trading.thomsonreuters.net amers3-fxtaggie.trading.refinitiv.net 209.191.134.203 159.43.8.10

amers3.fxtblotter.trading.thomsonreuters.net amers3-fxtblotter.trading.refinitiv.net 209.191.134.205 159.43.8.25

amers3.fxtdiagnostics.trading.thomsonreuters.net amers3-fxtdiagnostics.trading.refinitiv.net 209.191.134.207 159.43.8.27

amers3.fxtfb.trading.thomsonreuters.net amers3-fxtfb.trading.refinitiv.net 209.191.134.202 159.43.8.9

amers3.fxtpoms.trading.thomsonreuters.net amers3-fxtpoms.trading.refinitiv.net 209.191.134.204 159.43.8.11

amers3.fxtqt.trading.thomsonreuters.net amers3-fxtqt.trading.refinitiv.net 209.191.134.201 159.43.8.8

amers3.fxttc.trading.thomsonreuters.net amers3-fxttc.trading.refinitiv.net 209.191.134.211 159.43.8.28

amers3.fxttcoptions.trading.thomsonreuters.net amers3-fxttcoptions.trading.refinitiv.net 209.191.134.212 159.43.8.29

apac1.apps.cp.extranet.thomsonreuters.biz apac1-apps.platform.refinitiv.biz N/A 159.43.32.80

apac1.apps.cp.thomsonreuters.com apac1-apps.platform.refinitiv.com 155.46.33.16 155.46.33.75 N/A

apac1.dealingedge.trading.thomsonreuters.net apac1-dealingedge.trading.refinitiv.net 159.220.240.18 159.43.32.114

apac1.dealingws.trading.thomsonreuters.net* apac1-dealingws.trading.refinitiv.net 159.220.240.17 159.43.32.113

apac1.fxt.cp.extranet.thomsonreuters.biz apac1-fxt.trading.refinitiv.biz N/A 159.43.32.65






Internet



apac1.fxt.cp.thomsonreuters.com apac1-fxt.trading.refinitiv.com 155.46.33.21 155.46.33.80 N/A

apac1.heartbeat.cp.thomsonreuters.net apac1.heartbeat.ciam.refinitiv.net 155.46.33.20 159.43.32.50

apac1.login.cp.thomsonreuters.net apac1.identity.ciam.refinitiv.net 155.46.33.15 159.43.32.41

apac1.test.cp.extranet.thomsonreuters.biz apac1-test.platform.refinitiv.biz N/A 159.43.32.80

apac1.test.cp.thomsonreuters.com** apac1-test.platform.refinitiv.com 155.46.33.19 155.46.33.75 N/A

apac1.views.cp.extranet.thomsonreuters.biz apac1-views.platform.refinitiv.biz N/A 159.43.32.80

apac1.views.cp.thomsonreuters.com apac1-views.platform.refinitiv.com 155.46.33.22 155.46.33.75 N/A

apac2.dealingedge.trading.thomsonreuters.net apac2-dealingedge.trading.refinitiv.net 159.220.20.210 159.43.34.50

apac2.dealingws.trading.thomsonreuters.net apac2-dealingws.trading.refinitiv.net 159.220.20.209 159.43.34.49

apac3.fxtaggie.trading.thomsonreuters.net apac3-fxtaggie.trading.refinitiv.net 159.220.240.3 159.43.33.67

collab.extranet.thomsonreuters.biz Collab.platform.refinitiv.biz 159.43.30.7

collab.thomsonreuters.com Collab.platform.refinitiv.com 159.220.0.155 N/A

collab.thomsonreuters.com (DR?) Collab.platform.refinitiv.com 192.165.211.75

emea1.apps.cp.extranet.thomsonreuters.biz emea1-apps.platform.refinitiv.biz N/A 159.43.16.135

emea1.apps.cp.thomsonreuters.com emea1-apps.platform.refinitiv.com 159.220.1.19 155.46.25.65 N/A

emea1.dealingedge.trading.thomsonreuters.net emea1-dealingedge.trading.refinitiv.net 159.220.2.162 159.43.16.178

emea1.fxt.cp.extranet.thomsonreuters.biz emea1-fxt.trading.refinitiv.biz N/A 159.43.16.142

emea1.fxt.cp.thomsonreuters.com emea1-fxt.trading.refinitiv.com 159.220.1.18 155.46.25.64 N/A

emea1.heartbeat.cp.thomsonreuters.net emea1.heartbeat.ciam.refinitiv.net 159.220.1.73 159.43.16.51

emea1.login.cp.thomsonreuters.net emea1.identity.ciam.refinitiv.net 159.220.1.64 159.43.16.41

emea1.test.cp.extranet.thomsonreuters.biz** emea1-test.platform.refinitiv.biz N/A 159.43.16.135






Internet



emea1.test.cp.thomsonreuters.com** emea1-test.platform.refinitiv.com 159.220.1.98 155.46.25.65 N/A

emea1.views.cp.extranet.thomsonreuters.biz emea1-views.platform.refinitiv.biz N/A 159.43.16.135

emea1.views.cp.thomsonreuters.com emea1-views.platform.refinitiv.com 159.220.1.49 155.46.25.65 N/A

emea3.fxtaggie.trading.thomsonreuters.net emea3-fxtaggie.trading.refinitiv.net 159.220.63.3 159.43.31.3

emea1.dealingws.trading.thomsonreuters.net emea1-dealingws.trading.refinitiv.net 159.220.2.161 159.43.16.177

amers2.test.cp.extranet.thomsonreuters.biz amers2-test.platform.refinitiv.biz 192.155.138.22

amers2.test.cp.thomsonreuters.com amers2-test.platform.refinitiv.com 159.220.53.111

Table 13A - FXT Desktop Application FQDNs

Customers.reuters.com is replace by my.refinitiv.com. my.refinitiv.com is a public cloud hosted service and so no dedicated IP address is assigned, and can change at any time.




GEOGRAPHICAL LATENCY CONSIDERATIONS

Global organisations may face the choice as to where they offer connection points (to Refinitiv Managed Connection or the Internet) for their users. Customers should be aware that FXT/FXall is designed to ensure that users connect to the Refinitiv point of presence in their local region (either AMERS, APAC or EMEA). This local region is defined at the time of setting up the user for Eikon or FXT/FXall access.

To take a concrete example, a user who is based in Hong Kong would access the aggregation service via the IP address defined in the table above for “apac3.fxtaggie.trading.thomsonreuters.net”. This is a site in Asia. Even if that user uses a Refinitiv Managed Connection or ISP connection which is based in London, they would still be directed to the Point of Presence in Asia.

Warning: As part of service resilience, services may be switched to other areas. In order to have access to a fully resilient service all FQDNs must be configured and accessible regardless of user’s location and

FQDN area.

CLIENT LAN LATENCY

Given the latency sensitive nature of the FXT/FXall desktop application, it is recommended that the customer ensures that the total round trip time for FXT/FXall users is under 250ms by ensuring that FXT/FXall traffic takes the shortest path over the customer's internal network to the relevant FXT/FXall services

Where the customer’s internal network increases the total round trip time beyond 250ms, user perception of product performance may be affected, and functionality may be compromised.

Clients have a responsibility to ensure that latency introduced by networks under their control or contract, i.e. LAN, WAN or ISP, is kept to an absolute minimum.

HEARTBEAT AND RECONNECTION FEATURE

The FXT application has a reconnect feature which detects broken connections. Following a disconnect the application automatically reconnects users to disconnected sessions. The UI attempts to reconnect every five seconds up to 12 times. During the auto reconnect period user re-authentication is not required. If network is down for over 60 seconds, then the application must be restarted.

The AAA application time to live is set to 18 hours, Users must re-logon to the GUI once every 18 hours. The AAA token is validated by the FXT application every 30 seconds

NOTE Any change in user Originating IP Address, while users are connected to the service, may require an application restart.

Individual application Heartbeat timings

Product Function Frequency Timeout

FXT GUI Matching 4 seconds 12 seconds

FXT GUI DSP/Dealing 5 seconds 15 seconds

Table 14 – Heartbeat timings

NETWORK RESILIENCE AND REFINITIV MANAGED CONNECTION CPE ICRL

To reduce the possible impact of service disruption, Refinitiv strongly recommends to clients that an ICRL is installed at FCN and Refinitiv Managed Connection (including split site configurations).




The inclusion of an ICRL between FCN/Refinitiv Managed Connection CPEs (client-site router) ensures continuation of FXT desktop service in the event of certain network outage events, the FXT Desktop will function where an ICRL is not present however there will be no protection from transient network issues, resulting in FXT desktop session termination with the associated cancellation of open orders.

The following outlines a number of failure scenarios and the impact to the FXT Desktop service from both an ICRL/No ICRL perspective; applying to both single and split customer site configuration.

Secondary WAN Circuit Failure

Client Network

TRAgg RouterSecondary


TRAgg Router

Primary

TRAgg Router

Primary

CPE 2CPE 2CPE 1CPE 1

Client NetworkInfrastructure




ICRL

Figure 1 - Secondary WAN Circuit Failure

ICRL No ICRL

Impact to end user: No loss of service, only loss of resilience since no active TRFXT connections are on CPE2

No Loss of service

No service resilience

What happens when circuit is restored?

Service resilience is restored No service resilience

Is manual intervention required No, the secondary WAN is restored automatically.

No, the secondary WAN is restored automatically.

Table 15 - Secondary WAN Circuit Failure Impact

Primary WAN Circuit Failure

Client Network



TRAgg Router

Primary

TRAgg Router

Primary






ICRL




Figure 2 - Primary WAN Circuit Failure

ICRL No ICRL

Impact to end user:

No loss of service, only loss of service resilience.

CPE1 will maintain existing source NAT tables and route all traffic via the ICRL cable to CPE2 & secondary WAN.

The failover is about 1 second, so there will be no service loss, but potentially latencies.

FXT users will be disconnected from trade venues and all open orders will be cancelled.

This is due to the source NAT table residing within CPE1, The FXT TCP sessions are therefore not transferrable to CPE2 via the ICRL.

When the CPE2 is designated as Primary the FXT application will reconnect to trade venues.

FXT application will automatically reconnect if network is restored within 60 Seconds.

What happens when Primary WAN circuit is restored?

BGP will re-converge and it will start using the restored circuit.

No application restart or login is required.

User session is disconnected. Matching prices removed.


This is because the source NAT table will die with the CPE2 so the TCP sessions are not transferrable to CPE1 on the ICRL

Is manual intervention required?

No No

Table 16 – Primary WAN Circuit Failure Impact

Secondary CPE (2) Failure

Client Network



TRAgg Router

Primary

TRAgg Router

Primary






ICRL

Figure 3 – Secondary CPE (2) Failure




ICRL No ICRL

Impact to end user:

No loss of service, only loss of resilience since no active TRFXT connections are on CPE2

No Loss of service

No service resilience

What happens when circuit is restored?

Service resilience is restored No service resilience

Is manual intervention required? Possibly – depends on failure scenario.

Possibly – depends on failure scenario.

Table 17 – Secondary CPE (2) Failure Impact

Primary CPE (1) Failure

Client Network



TRAgg Router

Primary

TRAgg Router

Primary






ICRL

Figure 4 – Primary CPE (1) Failure

ICRL No ICRL

Impact to end user:

FXT users will be disconnected from trade venues and all open orders will be cancelled, this is due to the source NAT table residing within CPE1, TCP sessions are therefore not transferrable to CPE2 on the ICRL. When the CPE2 is designated as Primary the FXT application will reconnect to trade venues.

FXT application will automatically reconnect if network is restored within 60 Seconds

FXT users will be disconnected from trade venues and all open orders will be cancelled, this is due to the source NAT table residing within CPE1, TCP sessions are therefore not transferrable to CPE2 as there is no ICRL. When the CPE2 is designated as Primary the FXT application will reconnect to trade venues.





ICRL No ICRL

What happens when Primary CPE is restored?

Resilience is restored.

If the CPE1 restore is undertaken outside of trading hours there will be no user impact.

if CPE1 restore takes places during trading hours user session is disconnected. Matching prices removed.


No service Resilience.

If the CPE1 restore is undertaken outside of trading hours there will be no user impact.

If CPE1 restore takes places during trading hours user session is disconnected. Matching prices removed.


Is manual intervention required Depends on specific failure scenario

Depends on specific failure scenario.

Table 18 – Primary CPE (1) Failure Impact

CRL AND OCSP

CRL responder resources are specified in most PKI certificates associated to the FXT Desktop Application, CRL checking is however disabled by default.

No OCSP responder resources are specified.

REFINITIV REMOTE SUPPORT SERVICE (TRRS)

Refinitiv offers a remote desktop access (called Refinitiv Remote Support Service - TRRS) between clients’ desktop and Refinitiv support/help desk. TRRS is only available if clients give permission and request remote access. When using TRRS via Refinitiv Managed Connection or FCN the following FQDN must be configured on the clients EDNS.

NOTE The FQDNs listed in the table below uses Port HTPPS: 443

FQDN Thomson Reuters Domain FQDN Refinitiv Domain FCN and Refinitiv Managed Connection IP address

rs.cp.extranet.thomsonreuters.biz rs.platform.refinitiv.biz 159.43.5.19

LON-ECOM-BGTN01.rs.cp.thomsonreuters.com #EMEA

LON-ECOM-BGTN01-rs.platform.refinitiv.com

159.43.17.140

SNG-ECOM-BGTN01.rs.cp.thomsonreuters.com #ASIA

SNG-ECOM-BGTN01-rs.platform.refinitiv.com

159.43.40.131

Table 19 – FQDN for TRRS

REFINITIV FX TRADE REPORTING (PREVIOUSLY CALLED DEALING XTRA)

Refinitiv FX Trade Reporting is a web service that contains information about Matching and Dealing services, for example access to the Matching trade data or details of a Credit Replication. The tables below show the URLS to access the original Dealing Xtra service and new Refinitiv FX Trade Reporting. All User must upgrade to the new Refinitiv URLs by end Q3.




NOTE The FQDNs listed in the table below use 80 (HTTP_REDIRECT to HTTPS/443), 443

dxdxtrapub.markets.reuters.com & fxreportingpub.trading.refinitiv.net are no longer used by FX Trade Reporting

Delivery Method

FQDN Thomson Reuters Domain

FQDN Refinitiv Domain Live Standby

Internet dxtra.markets.reuters.com fxreporting.trading.refinitiv.net 159.220.24.15 146.242.30.28

Refinitiv Managed Connection

dxtra.markets.reuters.com fxreporting.trading.refinitiv.net 159.43.17.156 159.43.10.14

Table 20 – FQDN for Dealing Xtra

FXT UPDATER

FXT 7.1 and all subsequent versions of FXT have an optional update mechanism to allow FX Trading clients to upgrade their current version to a newer or latest supported version of FXT. The FXT Updater is an integrated software update feature that does not require the user to perform a download of software and full installation of the FXT GUI in order to upgrade. See FXT Updater Quick Start Guide for more information.

The FXT Updater is not supported for FXall users.

FEATURES

Using the FXT Updater provides the following features.

• Simpler and quicker way to download and install FXT. You do not need to go to MyRefinitiv to download the software and then install it.

• You can choose which version you upgrade to. This can be the latest version of FXT or other supported versions of FXT. See FXT Supported Versions for details of which versions of FXT are supported.

• Simple mechanism for restoring your previous version of FXT.

NOTE The FQDN listed in the table below uses Port HTPPS: 443

FQDN Internet Thomson Reuters Domain

FQDN Internet Refinitiv Domain

Live

fxtupdater.thomsonreuters.com fxtupdater.refinitiv.com

159.220.24.77 (EMEA) changing to 155.46.24.53 (Nov 2019)

159.220.50.28 (HZL – USA)

Table 21 – FQDN for FXT Updater via the internet

FXT updater via the internet uses geographic load-balancing to direct users to the ‘closest’ end-point. We require that Clients networks can access all the IP address listed in the table above.

NOTE The FQDN listed in the table below uses Port HTPPS: 443

http://dxtra.markets.thomsonreuters.com/

http://dxtra.markets.thomsonreuters.com/

https://transactions.thomsonreuters.com/filebase/documents/components/9mCEZ51BJ3oqipKwh0ziTEVJiMH7jG%2B%27OimQYwvDVVA

https://transactions.thomsonreuters.com/filebase/documents/components/DRWQobKZCAr5svJqRgjkr79sgXU9Hb%27nH5yhELUy14w




FQDN Refinitiv Managed Connection Thomson Reuters Domain

FQDN Refinitiv Managed Connection Refinitiv Domain

Live

fxtupdater.trading.thomsonreuters.net fxtupdater.trading.refinitiv.net

159.43.17.154 (live) changing to 155.46.24.54

159.43.5.35 (Service continuity)

Table 22 – FQDN for FXT Updater via the Refinitiv Managed Connection

Chapter 7 FXT In-Trade Adaptor (DTF)




FQDNS, PORTS, PROTOCOLS AND IPS XX

The DTF adaptor consumes globally deployed HTTPS/443 services from the following Production endpoints:

NOTE The FQDNs listed in the table below use the Protocol Port 8443 (default LBN/Sock_Raw) or 443 (applet/Sock_Tunnel)

FQDN Thomson Reuters Domain FQDN Refinitiv Domain

Internet IP

Authoritative DNS Public Internet

FCN and Refinitiv Managed Connection IP Authoritative DNS Extranet DNS

emea1.login.cp.thomsonreuters.net emea1.identity.ciam.refinitiv.net 159.220.1.64 159.43.16.41



apac1.login.cp.thomsonreuters.net apac1.identity.ciam.refinitiv.net 155.46.33.15 159.43.32.41

emea1.feededge.trading.thomsonreuters.net emea1-feededge.trading.refinitiv.net 159.220.2.167 159.43.16.184

amers1.feededge.trading.thomsonreuters.net amers1-feededge.trading.refinitiv.net 159.220.41.131 159.43.2.99

apac1.feededge.trading.thomsonreuters.net apac1-feededge.trading.refinitiv.net 159.220.240.19 159.43.32.115



emea1.dealingws.trading.thomsonreuters.net* emea1-dealingws.trading.refinitiv.net 159.220.2.161 159.43.16.177

amers1.dealingws.trading.thomsonreuters.net* amers1-dealingws.trading.refinitiv.net 159.220.41.129 159.43.2.97

apac2.feededge.trading.thomsonreuters.net apac2-feededge.trading.refinitiv.net 159.220.20.211 159.43.34.51

Table 23 - In-Trade Feed Adaptor FQDNs





While an ICRL will improve network resilience and is recommended, its inclusion is not critical for the operation of the DTF adaptor given its pattern of use the associated tolerance of connection failure.

CRL AND OCSP

PKI certificates associated to the DTF adaptor currently have no CRL or OCSP responder resources specified.

Chapter 8 FXT Post Trade Adaptors (DTFE, TOF, Conversation and Ticket Print)



Chapter 8 FXT Post Trade Adaptors (DTFE, TOF,

Conversation and Ticket Print)

FQDNS, PORTS, PROTOCOLS AND IPS

FXT Post Trade adaptors consume a single resilient service globally using either SSL/8443 or HTTPS/443.

The following table lists the Production endpoints used by FXT Post Trade Feed Adaptors:

NOTE All FQDNs listed in the table below use Protocol Port SSL/8443 HTTPS/443

FQDN

Internet IP

Authoritative DNS Public Internet

FCN and Refinitiv Managed Connection IP Authoritative DNS Extranet DNS

Thomson Reuters Domain: pts.trading.thomsonreuters.net

Refinitiv Domain: pts.trading.refinitiv.net

192.165.220.164 159.43.18.8

DR 146.242.30.27 DR 159.43.10.13

Thomson Reuters Domain: pts-uat.trading.thomsonreuters.net

Refinitiv Domain: pts.ppe.trading.refinitiv.net 159.220.24.118 159.43.17.152

Table 24 – Post Trade Feed Adaptor FQDNs

*The IP address for both Live and DR sites are listed. The IP address for the DR site is NOT live unless DR is invoked


While an ICRL will improve network resilience and therefore continuation of service (and is recommended), its inclusion is not critical for the operation for the FXT Post Trade adaptors given their pattern of use the associated tolerance of connection failure.

CRL AND OCSP

CRL responder resources are specified in PKI certificates associated to FXT Post Trade adaptors, CRL checking is however disabled by default.

No OCSP responder resources are specified.

BANDWIDTH FOR FXT ADAPTORS

As a minimum the following bandwidth is required for FXT Adaptors:

Adaptor Required Bandwidth

Printer Adapters 16K per TCID

Feeds (TOF, DTF, DTFE) 24K per TCID

Table 25 – Adaptors Bandwidth

Chapter 9 Refinitiv FX Matching Credit Administration (MCA)



Chapter 9 Refinitiv FX Matching Credit

Administration (MCA)

Refinitiv FX Matching Credit Administration (MCA) is a standalone Java based tool for administrating credit for Matching. Matching users will need to install and access MCA. As such it is recommended that Matching Clients install and implement MCA at the same time as FXT. The Refinitiv FX Matching infrastructure is being updated as we transition our brand, products and technology from Thomson Reuters to Refinitiv. This impacts all MCA users.

MCA is available via Refinitiv Managed Connection or internet. The IP addresses used to access the MCA service are listed in the tables below.

Refinitiv MCA version 1.8 will support the Refinitiv Domain only. The tables below shows the FQDNs for both Thomson Reuters Domain (MCA version 1.7 or below) and the Refinitiv Domain (MCA version 1.8 or above)

NOTES All FQDNs listed in the table below use Port HTPPS: 443

The Subnets used on Refinitiv Managed Connection for the MCA IP addresses are 159.43.31.0/27 and 159.43.5.192/27

Refinitiv FX 26Matching Credit Admin uses DNS failover to switch between the live LD4 data center and the DR NY6 data center.

• Under normal running conditions LD4 is live and NY6 is DR

• Customers will target a DNS CNAME which will then resolve to one of two DNS A records depending on whether LD4 or NY6 is running live

• There are separate FQDNs for logins (creditws) and credit management (creditedge)

• Each of these has a CNAME and then two A records, one each for LD4 and NY6

• This makes six FQDNs in total for Refinitiv FX Matching Credit Administration

• If customers are using FQDN filtering on security appliances we highly recommend that the whole domain is allowed rather than individual FQDNs, e.g. thomsonreuters.net or refinitiv.net

Chapter 9 Refinitiv FX Matching Credit Administration (MCA)



FQDN AND IP ADDRESS TABLE

Purpose DNS entry type Current FQDN for MCA 1.7 or below New Refinitiv FQDN for MCA 1.8 or above Internet IP

Refinitiv Managed Connection IP

Login CNAME emea.matchingcreditws.trading.thomsonreuters.net emea1-matchingcreditws.trading.refinitiv.net Uses A record IP Uses A record IP

Login Live A record matchingcreditws-emea1.trading.thomsonreuters.net emea-matchingcreditws.trading.refinitiv.net 159.220.63.18 159.43.31.18

Login DR A record matchingcreditws-emea2.trading.thomsonreuters.net emea2-matchingcreditws.trading.refinitiv.net 146.242.57.2 159.43.5.194

Credit management

CNAME emea.matchingcreditedge.trading.thomsonreuters.net emea1-matchingcreditedge.trading.refinitiv.net Uses A record IP Uses A record IP

Credit management

Live A record matchingcreditedge-emea1.trading.thomsonreuters.net emea-matchingcreditedge.trading.refinitiv.net 159.220.63.19 159.43.31.19

Credit management

DR A record matchingcreditedge-emea2.trading.thomsonreuters.net emea2-matchingcreditedge.trading.refinitiv.net 146.242.57.3 159.43.5.195

Table 27 – FQDN and IP address table

The FQDN matchingcredit.trading.thomsonreuters.net has been removed, as MCA Webstart product is no longer supported. emea.matchingcreditws.trading.thomsonreuters.net and emea.matchingcreditedge.trading.thomsonreuters.net are used to connect to the replacement service “MCA standalone”.

Chapter 10 Refinitiv Deal Tracker FIX Archiver



Chapter 10 Refinitiv Deal Tracker FIX Archiver

The following table is the FQDN, IP address and port for each pre-defined environment for Trade Notification system. Deal Tracker FIX Archiver is supported via Refinitiv Managed Connection, or Internet. Deal Tracker FIX Archiver has these FQDN and port pre-define in system. The customer environment must ensure those FQDN can resolve to the correct IP address and there are no firewall block for these port.

For Refinitiv Managed Connection Network, Customer may require to configure DNS to use Refinitiv Refinitiv Managed Connection DNS in order to resolve these FQDN correctly.

NOTE All FQDNs listed in the table below use Port: 16000

FQDNs FQDN Thomson Reuters Domain

FQDN Refinitiv Domain IP address Primary Site

IP address

DR Site

Production Internet

pts.trading.thomsonreuters.net pts.trading.refinitiv.net 192.165.220.164 146.242.30.27

Production Refinitiv Managed Connection

pts.trading.thomsonreuters.net pts.trading.refinitiv.net 159.43.18.8 159.43.10.13

UAT Internet pts-uat.trading.thomsonreuters.net pts.ppe.trading.refinitiv.net 159.220.24.118 N/A

UAT Refinitiv Managed Connection

pts-uat.trading.thomsonreuters.net pts.ppe.trading.refinitiv.net 159.43.17.152 N/A

Table 28 – FQDNs for Deal Tracker FIX Archiver

Appendix A FXall (Siteminder) FQDNs



Appendix A FXall (Siteminder) FQDNs

FXall GUI uses different FQDNs when using FXall services that are configured via the FXall Admin Services (Siteminder). These are listed in the following document: FXT using FXall services over Delivery Direct.

https://transactions.thomsonreuters.com/filebase/documents/components/uMIb0cuRJOyManGkS8%275WJPAj1Nvk6eNmCHO1M4bO44


Document Version: 6.13

Refinitiv FX Trading (FXT) - Refinitiv FXall (AAA users)

Documents

Transcript of Refinitiv FX Trading (FXT) - Refinitiv FXall (AAA users)