Attachment_2_-_Tactical_Mesh_MANET_Requirements_Doc.docx

Tactical Mesh/Mobile Ad hoc Network Requirements Document SOW Annex I – Technical Specifications The purpose of this Annex is to describe the functions and features of Tactical Mesh/Mobile Ad hoc Network (MANET).

The DOJ is seeking a Tactical Mesh/mobile ad hoc network (MANET) solutions that will enhance the DOJ’s collections capability for special events, provide alternate means of data egress, and transport video streams back to a central receive point(s). Tactical Mesh is an alternative to the use of commercial cellular networks. Tactical mesh may be leveraged for joint operations with multiple government law enforcement agencies. Tactical Mesh capabilities will provide a cost effective and dynamic high-bandwidth network over a specific coverage area or mobile environment.

Technical Requirements:

The requirements for the tactical mesh are presented in below. Mandatory requirements (utilizing “shall” in the description) are listed for each category. In addition, capabilities desired by the Government are also listed (using “should” in the description). Any proposed system must comply with the set of mandatory requirements.

General:

1. The solution shall be non-developmental, Commercial-off-the-Shelf (COTS) radio-based communications system for establishing Tactical Mesh deployable systems.

2. The solution shall support integration with other networks and communication capabilities.

3. The solution shall support Layer 2/Internet Protocol (IP) based data exchange and integration with other devices and networks.

4. The solution shall support data exchange from edge devices, such as cameras, sensors, or other IP network-ready devices to central receive locations.

5. The solution shall support the transmission of required data types to include sensor data, voice, video, images, text, and position location information.

Management:

6. The solution shall support local update capabilities and configurations.

7. The solution shall support local management.

8. The solution shall support secure remote update capabilities.

9. The solution shall support secure remote management.

10. The solution shall support secure remote configuration.

11. The solution shall support the ability to use configuration file or templates to adjust frequency bands or channels.

12. The solution shall provide a health and capacity monitoring capability for the status of the network and individual nodes.

13. The solution shall include logging and auditing capabilities.

14. The solution should support role based access control to devices, e.g. administrator, user.

15. The solution should support Simple Network Management Protocol v3 (SNMPv3) monitoring.

16. The solution shall define and provide Quality of Service (QOS) model.

17. The solution should support automated export of logs to enterprise service.

Network and routing

18. The solution shall be compatible with the DOJ Channel Plan (S and C Bands).

19. The solution should use bandwidths of 5, 10, and 20 Megahertz (MHz), with an optional desired bandwidth of 2.5 MHz.

20. The solution shall provide capability to change bands locally.

21. The solution shall be capable of locally tuning channels in 1 Megahertz increments within a band.

22. The solution shall support data throughput of 25 Megabits per second (Mbps) with a desired 60 Mbps – 300Mbps.

23. The solution shall support Virtual Private Network (VPN) connections.

24. The solution shall support the capability of multiple secure means for egress of separate surveillance data.

25. The solution shall have the capability of expanding to at least 10 nodes without nominal service degradation to the quality of the network.

26. The solution shall implement routing protocols to minimize the number of hops from an access point to wired Ethernet egress connections.

27. The solution shall support alternate routing without data loss in the event a node is unavailable or compromised.

28. The solution shall prevent unidentified, unauthorized traffic from "transiting" through the network.

29. The solution shall support the ability for nodes to seamlessly join and leave the network.

Security/Integrity

30. The solution shall provide transmission encryption.

31. The solution shall support transport of encryption data.

32. The solution shall support the ability to remotely change encryption keys for updates to remote devices.

33. The solution shall provide End-to-End security.

34. The solution shall provide Node-to-Node security.

35. The solution shall not broadcast Service Set Identifiers (SSID) or other identifying information of the node or system.

36. The solution shall support the ability to hide or spoof manufacturer chipset ID as commercial device.

37. The solution shall support the capability of Wi-Fi chipsets or BlueTooth to prevent a network sniffer from being able to detect the manufacturer ID of Wi-Fi or BlueTooth equipment components,

38. The solution shall demonstrate a low probability of detection (LPD) and a low probability of interception (LPI).

39. The solution shall provide the capability to disable/wipe nodes remotely if the node is compromised.

40. The solution shall support Advanced Encryption Standard (AES) 256-bit non-proprietary encryption or better.

41. The solution shall support built-in encryption support for Secure Hash Algorithm-3-Hashed Message Authentication Code (SHA-3-HMAC) for data transmission.

42. The solution shall support protection of data at rest/in transit in accordance with Federal Information Processing Standards (FIPS) 140-2, for any information at rest or in transit through a device or in the network.

43. The solution shall support secure data transit from an edge device to the central collection server.

Deployability

44. The solution shall be adaptable to support 110-220 volts alternating current (VAC) or 12-24 volts direct current (VDC)

45. The solution should provide Power over Ethernet (PoE) to edge devices

46. The solutions shall be protected from damage from low voltage conditions

47. The solutions shall have the ability to put units into remote standby/activate to save power;

48. The solution shall support 16 -128 Quadrature Amplitude modulation (QAM) with a desired 128- 1064 QAM.