Sukkal Network

From Solas Tempus DB

The Sukkal Network is a reserve / emergency communications network operated for the Serenity Concord. The network itself consists of private, government, and business transceivers alike operated as a stateless mesh network. Each network node attempts to relay communications traffic to any other receivers in range using any protocol necessary, so long as it meets security guidelines. As a stateless network the system does not seek to maintain a direct status of connections but instead relies on network nodes to find the most efficient route through the network to a destination. If a singular network node goes down the system reroutes through any available communications channel.

Activation

Network activation is only to be used in times of emergency. The system is designed to remain dormant until needed, each node is responsible for maintaining the communications readiness of their link in the system. In the event a node receives an emergency activations signal, it will relay that signal through the rest of the network, activating any reachable nodes. Each node will verify activation of reachable nodes even if it is likely the previous node already activated those nodes.

Authentication

Each node maintains a localized authentication system to verify access, in the event the Concord cannot be reached to provide authentication individual nodes will compare authentication information with their own local data. Activation of the network requires a Level 4 command code or higher to activate from Solas Tempus or governmental equivalent activation code from Concord officials.

Qualifications for Activation

The network should only be activated in the event of an emergency situations where other communications methods (such as BlueNet) cannot be used. Within Solas Tempus the network is prohibited from being activated unless BlueNet is either compromised or the network is offline / cannot be reached. Within the Concord the decision to activate the network rests solely with the executive branch.

Communications Channels

The system is designed to use a variety of connection methods between network nodes. The communications methods and protocols need not be ubiquitous or consistent. Since this is an emergency network, the system will seek out the most secure and reliable transmissions method available between individual nodes. Any pair of network nodes can establish a connection to each other via any necessary means so long as the network method will handle encrypted / encapsulated network traffic. In this way the system will set up a secure virtual network within the system. Subspace and tachyon communications are preferred but conventional RF or direct line-of-sight laser communications will also be used if required.

Relay / Failsafe Configuration

In the event of emergency where communications must be sent with the highest priority but a contiguous connection is not possible, the network can operate in Relay configuration. In this configuration messages can be relayed through any known means by independent operators from one network node to another. This is particularly useful in the event of a catastrophic systems or infrastructure failure. In such configurations operators will relay messages via text or voice along the network nodes with otherwise would not be able to establish a proper data connection. This mode allows the use of temporary node relays.