RFI Long Haul Data Transport QA 20250527.docx

RFI Long Haul Data Transport Q&A

1) Will you please provide more details on the specific legacy systems and protocols currently in use that must be supported?

Answer: RS-232/422/530; point-to-point communication / point-to-multipoint communication of Common Digitizer- 2 radar data, and analog voice radios with push-to-talk capacity.

2) Are there any specific requirements for transport protocol conversion that we should be aware of, particularly for ASTERIX and MIL-STD 3011 JREAP?

Answer: Latency is a critical requirement (50-200ms). We anticipate protocol conversion may be necessary for ASTERIX and MIL-STD 3011 JREAP. We need proposers to outline their experience and capabilities in handling these protocols and their impact on latency.

3) Could you elaborate on the expected redundancy and failover mechanisms? Are there preferred methods or technologies for implementing PACE planning principles?

Answer: We expect solutions to address redundancy at the hardware, software, and network layers. Failover mechanisms should support both automatic and manual initiation. We are interested in understanding how proposers would leverage PACE planning principles to ensure communication path diversity and resilience. For example, we envision solutions that can dynamically switch between primary and alternate communication paths based on real-time network conditions and performance metrics.

PACE is a framework for planning and managing communication paths. It is not a specific technology or product.

4) What are the specific security requirements for integrating with NSA Type-1 certified devices? Are there any additional compliance standards we should consider?

Answer: Yes CNSS-15 can be found at https://csrc.nist.gov/csrc/media/projects/cryptographic-module-validation-program/documents/cnss15fs.pdf

5) What are the key performance indicators for centralized monitoring and management? Are there specific tools or platforms preferred for this purpose?

Answer: The key performance indicators are Availability and Reliability, Performance, Security, Efficiency and Cost, and Compliance.

The "best" tool depends on your specific needs, budget, technical expertise, and existing infrastructure. Our transport solution is a combination of DISA provided transport, contractor provided interface equipment and program managed systems of record which each utilize various systems to perform their monitoring, we believe that the solution should utilize industry best practices, while meeting all the DoD requirements to ensure availability, integrity, and reliability.

6) Can you provide more details on the expected data growth and future scalability requirements?

Answer: Unknown, ATT. If we integrate all our current facilities into a common transport solution and infrastructure with resiliency, our existing requirements process allows for increases of 2 – 10 % growth potential over a period of time as determined to meet mission will also be integrated via this common transport service provider.

7) Are there any specific challenges or constraints related to deployment models (on-premises, cloud-based, or hybrid) that we should be aware of, especially in remote and austere environments?

Answer: Remote site access requires coordination at a minimum of 2 business days prior to the requested visit and providing a primary and alternate date is highly recommended. Furthermore, proposers should be aware that some remote sites may have limited power and environmental control. We are open to considering on-premises, cloud-based, or hybrid deployment models. Proposers should outline the pros and cons of each approach, considering the specific challenges of remote and austere environments. Any cloud-based solutions must meet all applicable DoD security requirements and be able to operate in disconnected or intermittently connected environments.

8) What are the preferred methods for bandwidth optimization in constrained environments?

Answer: Most effective and efficient with minimum latency, as the radar, voice and data services being transported (*50-200 milliseconds).

ADS Surveillance Data (Radar):

· Constraints: High reliability and accuracy are paramount. Latency is critical, but some delays might be acceptable depending on the specific application (primary vs. secondary radar). Data volume can be significant.

· Preferred Methods:

· Data Filtering/Clutter Suppression: Aggressively filter out ground clutter, noise, and other irrelevant data before transmission. This reduces the amount of data that needs to be sent. Sophisticated signal processing techniques can be employed.

· Target Extraction and Reporting: Instead of transmitting raw radar data, extract target information (position, velocity, altitude, etc.) and transmit only that information. This significantly reduces the data volume. This is often done in modern radar systems.

· Lossy Compression (with careful evaluation): If necessary, use lossy compression techniques specifically designed for radar data, such as wavelet-based compression. Carefully evaluate the impact of compression on target detection accuracy and range/velocity resolution. Exceptionally low compression ratios may be the only acceptable option. Focus on compressing areas outside of detected targets more aggressively.

· Differential Encoding: Instead of transmitting absolute target positions, transmit the change in position from the previous update. This can be effective if targets are moving relatively slowly.

· Prioritized Queuing: Prioritize radar data packets over less critical data to ensure that they are transmitted with minimal delay.

· Selective Reporting: Report only changes in target status or position that exceed a certain threshold. This can reduce the amount of data that needs to be transmitted when targets are not changing rapidly.

· Protocol Optimization: Use lightweight protocols with minimal overhead, such as UDP, but ensure reliable delivery through application-level mechanisms (e.g., acknowledgments and retransmissions for critical data).

2. ADS Voice Services:

· Constraints: Real-time communication is essential. Low latency is critical. Voice quality must be acceptable. Bandwidth can be limited, especially in remote areas or during emergencies.

· Preferred Methods:

· Voice Codecs (Vocoders): Use low-bitrate voice codecs (vocoders) that provide acceptable voice quality with minimal bandwidth usage.

· Voice Activity Detection (VAD): Transmit voice data only when someone is speaking. This can significantly reduce bandwidth usage during periods of silence.

· Silence Suppression: Similar to VAD, silence suppression removes periods of silence from the audio stream.

· Prioritized Queuing (QoS): Prioritize voice traffic over other types of data to ensure that voice communication is not interrupted by other network activity.

· Real-time Transport Protocol (RTP): Use RTP for transmitting voice data over IP networks. RTP provides mechanisms for timing and sequencing voice packets, which are essential for maintaining voice quality.

· Header Compression: Compress RTP/UDP/IP headers to reduce overhead.

· Adaptive Bitrate: Dynamically adjust the bitrate of the voice CODEC based on network conditions. If bandwidth is limited, reduce the bitrate to maintain connectivity.

3. Joint Tactical Data Links (e.g., Link 16, SADL):

· Constraints: Extremely challenging environments with limited bandwidth, high mobility, and potential for interference and jamming. Security is paramount. Data must be delivered reliably in harsh conditions.

· Preferred Methods:

· Message Prioritization: Prioritize critical messages (e.g., threat warnings, target information) over less time-sensitive messages.

· Data Filtering and Aggregation: Filter out irrelevant data and aggregate multiple messages into a single transmission to reduce overhead.

· Robust Modulation and Coding: Use modulation and coding schemes that are resistant to interference and jamming. Examples include frequency hopping spread spectrum (FHSS) and direct sequence spread spectrum (DSSS).

· Forward Error Correction (FEC): Use FEC to protect data from errors caused by noise and interference.

· Data Compression (Carefully): Use data compression techniques but be aware of the potential for increased latency and the need for robust error handling. Consider compression algorithms designed for resilience, not just size reduction.

· Time Division Multiple Access (TDMA): Use TDMA to allocate time slots to different users, preventing collisions and ensuring fair access to the network.

· Network Centric Warfare (NCW) Principles: Apply NCW principles to ensure information superiority and efficient use of resources.

· Adaptive Power Control: Adjust transmission power based on network conditions to minimize interference and conserve energy.

· Link Layer Protocols: Implement robust link layer protocols that provide reliable data delivery in challenging environments.

· Situational Awareness Optimization: Focus on transmitting information that directly contributes to situational awareness, minimizing the transmission of redundant or irrelevant data.

Important Considerations Across All Three Areas:

· Security: Bandwidth optimization techniques should not compromise security. Encryption and authentication mechanisms should be used to protect data from unauthorized access.

· Interoperability: Ensure that bandwidth optimization techniques are compatible with existing systems and standards.

· Testing and Validation: Thoroughly test and validate bandwidth optimization techniques to ensure that they meet the performance requirements of the application.

· Dynamic Adaptation: Implement systems that can dynamically adapt to changing network conditions and adjust bandwidth usage accordingly.

In summary, the preferred methods for bandwidth optimization in constrained environments for ATC surveillance data, ATC voice services, and Joint Tactical Data Links depend on the specific constraints and requirements of each application. Prioritization, efficient coding, data filtering, and robust protocols are essential for maximizing bandwidth efficiency while maintaining acceptable performance. A system-level approach is required to ensure that all components of the system are optimized for bandwidth usage.

9) Can you provide more details on the expected performance metrics for redundancy and resilience, such as specific latency requirements and acceptable levels of data loss?

Answer: Solutions should provide transport capabilities that meet or exceed 0.9999 reliability, with 50-200 milliseconds latency, and fully integrated redundancy options to ensure reliability and latency requirements are achieved.

10) Are there specific DISA STIGs, SRGs, or other DoD cybersecurity mandates that the solution must comply with? Will you please provide more details on these requirements?

Answer: Yes, DISA STIGs (Security Technical Implementation Guides, DISA SRGs (Security Requirements Guides), DoD Cybersecurity Policies and Mandates, and Compliance Process.

DoD Instruction 8500.01, Cybersecurity: This instruction establishes the DoD's cybersecurity policy and assigns responsibilities for implementing and enforcing cybersecurity requirements. It is the foundational document.

DoD Instruction 8510.01, Risk Management Framework (RMF) for DoD Information Technology: This instruction implements the Risk Management Framework (RMF) for DoD IT.

RMF is critical. It is the process by which DoD systems are assessed, authorized, and continuously monitored. You must follow the RMF process to obtain an Authority to Operate (ATO) for your solution.

RMF Steps:

Categorize: Determine the security categorization of the system based on the sensitivity and criticality of the data it processes.

Select: Select the appropriate security controls from NIST Special Publication 800-53.

Implement: Implement the selected security controls. This is where STIGs and SRGs come into play.

Assess: Assess the effectiveness of the implemented security controls.

Authorize: Obtain an Authority to Operate (ATO) from the appropriate authorizing official.

Monitor: Continuously monitor the system for security vulnerabilities and compliance.

NIST Special Publication 800-53, Security and Privacy Controls for Information Systems and Organizations: This publication provides a catalog of security and privacy controls that can be used to protect federal information systems. DoD uses this as the baseline for security control selection in RMF.

CNSSI 1253, Security Categorization and Control Selection for National Security Systems: Provides guidance on security categorization and control selection for National Security Systems (systems that process classified information).

DFARS (Defense Federal Acquisition Regulation Supplement) Clause 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting: This clause requires DoD contractors to implement specific security controls to protect Covered Defense Information (CDI) and to report cyber incidents to the DoD.

Zero Trust Architecture (ZTA): The DoD is moving towards a Zero Trust Architecture. Solutions should be designed with Zero Trust principles in mind, such as least privilege access, micro-segmentation, and continuous authentication and authorization.

Other Relevant Policies: Depending on the specific nature of your solution, other policies may apply, such as those related to Personally Identifiable Information (PII), Protected Health Information (PHI), or Controlled Unclassified Information (CUI).

11) What are the key milestones and timelines for the implementation process? Are there specific training requirements for personnel at remote locations?

Answer: Key milestones and implementation would be developed based upon industry capabilities to provide a holistic end-to-end transport capability. Training requirements would also be based upon the industry’s capabilities and any lateral support the industry would request from remote site or data processing center technicians.

12) What are the expected levels of technical support and maintenance? Are there specific response times or service level agreements (SLAs) that must be met?

Answer: 0.9999 reliability, with a minimum 4-hour response time should be applied across the board, restoration times may depend upon site access as described in Q7.

13) Can you provide more details on the preferred pricing models and licensing options? Are there specific budget constraints or considerations we should be aware of?

Answer: We are developing this RFI to understand industry capabilities which will drive the budgeting process for developing an actual implementation plan or contract vehicle to acquire a holistic end-to-end transport solution.

14) Can you provide examples of similar implementations in comparable DoD or government environments? What were the key benefits and outcomes related to redundancy, reliability, performance, and security?

Answer: The RFI was developed because we are unaware of any specific current DoD or government environments, outside of the FAA and their FAA Telecommunications Infrastructure (FTI) and FAA Enterprise Network Services (FENS) programs.

15) Are there specific FAR and DFARS regulations that the solution must comply with? Can you provide more details on these requirements?

Answer: We do not know, great question for contracting office.

16) Are there any additional requirements or considerations that were not mentioned in the RFI but are critical for the solution design?

Answer: None of which we are aware of.

17) What specific CONR-AFNORTH missions will this transport solution support?

Answer: The data is used for all CONR-AFNORTH missions, we do not believe this question is relevant to any responses to the RFI.

18) What mission end devices will transmit data across the transport solution? For example: ground-based radar, radio antennas, etc?

Answer: Yes, ground-based radars, line-of-sight radios, data link radio services and others as needed based upon site capacity. This question is vague, and transport solutions should be developed to interface across diverse formats and protocols as outlined in RFI

19) Do any of the sites require traversing water for connectivity?

Answer: Yes there are several facilities on islands that should be accounted for any proposed solution delivered.

20) Why is CONR-AFNORTH planning for this solution now? What compelling events or circumstances are driving the RFI?

Answer: We are interested in understanding industry capabilities that allow for a holistic end-to-end transport solution vice a multi-segmented, multi-vendor, based solution whereby DISA provides contracted circuits, DITCO provides contracted integrators, and USAF provides oversight/management.