Case 2:17-cv-00513-JRG Document 233-6 Filed 12/14/18 Page 1 of 4 PageID #: 14014
`Case 2:17-cv-00513-JRG Document 233-6 Filed 12/14/18 Page 1 of 4 PageID #: 14014
`
`(cid:0) (cid:0) (cid:0)
`
`EXHIBIT E
`  (cid:0) (cid:0)
`
`(cid:0)
`
`(cid:0)
`
`

`

`Case 2:17-cv-00513-JRG Document 233-6 Filed 12/14/18 Page 2 of 4 PageID #: 14015
`Case 2:17-ev-00513-JRG Document 233-6 Filed 12/14/18 Page 2 of 4 PageID #: 14015
`
`D27080
`
`23 September 1998
`
`host’s queue waiting for the first unicast message to be delivered to its
`destination.
`
`3. Prior to sending a unicast message to the attached router, the local host
`sets up a TCP connection with the destination host. To set up the TCP
`connection, the following happens:
`
`a. The local host sends a TCP SYN message to the attached router. The
`router routes the TCP SYN message to the exit gateway IP address.
`
`b. At this point, the setup of the EPLRS point—to-point circuit is the same
`as described above, except that a SINCGARS stub net gateway router will
`proxy—ARP for the destination host based on its client list. Multiple
`gateway routers could not respond to the ARP, but the hardware address in
`the first response will be used.
`
`c. The destination exit gateway router will read the source IP address of
`the 1P header on the TCP SYN message and add a return route to the
`source [P address into the routing table. The gateway router sends a RFC
`1256 advertisement onto the local SINCGARS net advertising the
`indicated source 1P address.
`
`d. The destination gateway router then routes the TCP SYN message via
`the stub net to the router attached to the destination host.
`
`e. The destination router should install a route for the originator’s source
`IP address Via the gateway router that has sent the RFC 1256
`advertisement referenced in paragraph c.
`
`f. At this point, the originating and destination hosts have a TC P
`connection setup and start transmitting the message data.
`
`4. The termination of the TCP connection and EPLRS point-to-point circuit
`is the same described in Section 3.5.1.2.1, paragraph A6.
`
`3.5.2
`
`Internal Threads
`
`3.5.2.1 SA Server Selection
`
`The following description provides an example of the dynamic server selection
`and client registration process. Refer to Figure 3.5—5.
`
`A. Upon initialization, each platform transmits a CRM on the local—area SA net.
`Based on the received CRMs, the platform with the highest server eligibility
`ranking (i.e., PL) is elected as the local—area SA server for the net.
`
`B. Once elected, the local-area SA server transmits a server coordination message
`intended as a registration acknowledgment to FBCBZ platforms, which are clients
`of the local-area SA server.
`
`3-39
`
`SIEGELOO’I 003
`
`

`

`Case 2:17-cv-00513-JRG Document 233-6 Filed 12/14/18 Page 3 of 4 PageID #: 14016
`Case 2:17-cv-00513-JRG Document 233-6 Filed 12/14/18 Page 3 of 4 PageID #: 14016
`
`D27080
`
`23 September 1998
`
`
`
`fi;\\
`
`/ Q
`v
`~©* fl
`4
`
`<>WM‘
`
`
`
`Figure 3.5-5 Dynamic Server Selection and Client Registration
`
`3.5.2.2 SA Self-Server Selection
`
`The following description provides an example of the self-server election process.
`
`A. Upon initialization, the platform transmits CRMs on the local-area SA net.
`
`B. Based on not receiving any CRMs or server coordination messages, the platform
`will designate itself as a self-server and disseminate its SA data directly onto the
`EPLRS SA CSMA needline.
`
`3.5.2.3 SA Server Selection (Fractured Net)
`
`The following description provides an example of the dynamic server selection
`process when the local—area SA net fractures (i.e., Platoon net). Refer to Figure 3.5—6.
`
`
`
`
`
`Figure 3.5-6 Dynamic Server Selection — Fractured Net
`
`A. The FL is elected as the local position server. Once elected, the server
`periodically transmits a server coordination message on the local-area SA net.
`
`B. After two minutes, PS and WMl consider themselves de—registered from the PL.
`
`C. PS and WMl broadcast CRMS
`
`3-40
`
`SIEGELOO’I 004
`
`

`

`Case 2:17-cv-00513-JRG Document 233-6 Filed 12/14/18 Page 4 of 4 PageID #: 14017
`Case 2:17-cv-00513-JRG Document 233-6 Filed 12/14/18 Page 4 of 4 PageID #: 14017
`
`D27080
`
`23 September 1998
`
`D. on the local-area SA net. After which, the PS designates itself as the local
`position server, then transmits a server coordination message.
`
`E, The PL and PS each periodically broadcast server coordination messages on the
`local—area SA net. After the PL hasn’t heard from both the PS and WM] for a
`
`period of 20 minutes, the PL will drop the PS and WMl from its active client list
`and transmit a server coordination reflecting the change.
`
`3.6
`
`NETWORK MANAGEMENT
`
`Network management consists of planning, changing monitoring, and corrective
`
`action.
`
`3.6.1
`
`Initial Planning
`
`TBS
`
`3.6.2 Configuration Changes
`
`TBS
`
`3.6.3 Network Monitoring
`
`3.6.3.1 EPLRS Network Monitoring
`
`TBS
`
`3.6.3.2 SINCGARS Network Monitoring
`
`TBS
`
`3.6.3.3 FBCBZ Network Monitoring
`
`FBCB2 will use a bottom—up, hierarchical approach to network monitoring.
`
`Every FBCBZ platform monitors its local router and radios via SNMP queries and
`traps for status / malfunctions and provides this information to the host in the form of
`COMM status. Additionally, SA client / server status and SA statistics are available to
`infer the health of the SA network. The host has the responsibility to monitor, fault
`isolate and repair (or call for repair of) the equipment associated with the platform.
`
`3—41
`
`SIEGELOO’I 005
`
`