Skip to content

Latest commit

 

History

History
58 lines (38 loc) · 2.42 KB

README.md

File metadata and controls

58 lines (38 loc) · 2.42 KB

CloudBridge Laboratory Reports

Comprehensive laboratory and experimental reports supporting CloudBridge networking research and engineering decisions. These documents provide methodology, environment configuration, raw and processed results, and actionable conclusions.

Directory Overview

  • Experimental_QUIC_Laboratory_Research_Report.md

    • Foundational laboratory research on QUIC behavior under controlled conditions
    • Covers: testbed design, traffic models, latency/loss/congestion profiles, repeatability

  • Experimental_QUIC_Testing_Report.md

    • Consolidated experimental outcomes across multiple QUIC scenarios
    • Covers: test matrix, KPIs, stability observations, operational recommendations

  • QUIC_Laboratory_Research_Report.md

    • Baseline QUIC research focusing on protocol mechanics and transport tuning
    • Covers: handshake dynamics, congestion control variants, packet pacing

  • QUIC_Performance_Comparison_Report.md

    • Comparative performance analysis of QUIC implementations and configurations
    • Covers: throughput vs. latency trade-offs, fairness, variability across runs

  • MASQUE_Laboratory_Research_Report.md

    • MASQUE tunneling research for relay scenarios and encapsulation overhead
    • Covers: tunnel setup, header overhead, CPU footprint, end-to-end latency

  • PHASE1_PHASE3_TESTING_REPORT.md

    • Phase 1–3 program summary with objectives, methods, and results
    • Covers: test objectives, controlled environment, pass/fail criteria, next steps

How to Use

  1. Start with Phase report (PHASE1_PHASE3_TESTING_REPORT.md) to understand scope and objectives.
  2. Use foundational QUIC reports to study protocol behavior and baselines.
  3. Consult performance comparison for configuration decisions and trade-offs.
  4. Review MASQUE report when evaluating tunneling options for relay scenarios.

Reproducibility and Methodology

  • Testbeds: hardware profiles, kernel versions, and network emulation details are documented in each report.
  • Traffic Models: flows, durations, and distribution parameters are specified for repeatability.
  • Metrics: definitions for latency percentiles, jitter, loss, throughput, and CPU usage are standardized across reports.
  • Validation: each report includes verification steps and cross-checks where applicable.

Maintenance

  • Update this README when adding new laboratory reports.
  • Ensure each new report includes methodology, environment, metrics, and clear conclusions.