Currently, Service Control Point Owner/Operators (SCP O/Os) are required to engineer connectivity to the TFNRegistry™ using the following minimum specifications:
- Each SCP O/O must have at least one Site-to-Site VPN tunnel into the Production/Sandbox TFNRegistry Environment (AWS us-east-1).
- Each SCP O/O must have at least one Site-to-Site VPN tunnel into the Disaster Recovery (DR) TFNRegistryEnvironment (AWS us-west-2).
The reason for this network architecture is to ensure that connectivity between an individual SCP O/O and the TFNRegistry is not interrupted by the failure of a single or multiple network components. In order to provide immediate access to the TFNRegistry, it is essential that the minimum connectivity requirements are met. For more information, please click here.
In the event that a disaster is declared and the Production TFNRegistry is no longer operative, the SCP O/O traffic will be moved to the DR TFNRegistry. Additionally, an SCP O/O will remain in contact with Somos® in the event that the primary circuit into the Production/Sandbox TFNRegistry fails.
Connectivity between all the SCP O/Os and the DR TFNRegistry is verified on a yearly basis during the annual DR test conducted by Somos.
|
SCP connectivity must be separate from any other Site-to-Site VPN tunnel use. |