Quantum FWM Control Protocol (QFCP) for IP Optical Environments

Introduction Hybrid quantum-classical networking is emerging as a foundation for distributed quantum information processing. Recent experiments on commercial fiber networks have shown that quantum states can be dynamically routed by classical headers embedded in IP-like packets. To configure downstream optical switches and mitigate errors, a lightweight, extensible protocol is needed. QFCP is intended to be that protocol, running over UDP and supporting modular Type-Length-Value (TLV) extensions. QFCP supports applications aligned with scenarios defined by the IRTF Quantum Internet Research Group (QIRG) .

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Protocol Overview QFCP defines a fixed header followed by TLV-encoded fields. The header carries version and flag information; TLVs encode control-plane parameters such as quantum link layer protocol, polarization state, center frequency, or error-mitigation metadata. UDP provides transport simplicity and compatibility with existing IP infrastructure. Unknown TLVs MUST be ignored to ensure forward compatibility.

QFCP Packet Format The QFCP packet consists of a fixed header followed by a sequence of Type-Length-Value (TLV) payloads. Packet Format:

QFCP Packet Header and TLV Payloads

Version (4 bits): Protocol version number (currently 0x1).
Flags (4 bits): Reserved for future use.
Reserved (24 bits): Set to zero; ignored on receipt.
TLV Payloads: Sequence of variable-length TLVs.

TLV Structures Each TLV consists of a type, a reserved field, a length (in bytes), and a value. All fields are in network byte order. TLV Format:

TLV Format Defined TLV Types:

Initial TLV Type Assignments

Example Use Cases This section illustrates how the Quantum FWM Control Protocol (QFCP) can be applied in practical network environments.

Dynamic ROADM Configuration QFCP packets carrying TLVs for ROADM Output Port ID () allow classical headers to steer entangled photons through commercial reconfigurable optical add-drop multiplexers (ROADMs). This enables dynamic path selection across metro and campus-scale optical networks, as demonstrated in recent hybrid IP packet experiments ().

Real-Time Error Mitigation TLVs containing polarization parameters and error-mitigation vectors (Type 0x08) allow active compensation of SU(2) rotations induced by deployed fiber (). Classical light encodes detection signals in the header, enabling dynamic updates to the error mitigator without disturbing quantum states.

Hybrid IP Packet Orchestration The QFCP framework aligns with the IRTF QIRG goals and use-cases (). By transporting control-plane metadata in TLVs, classical headers and quantum payloads can be synchronized and routed through existing IP infrastructure.

Timestamp Alignment TLVs carrying local and photon arrival timestamps can provide synchronization similar to RTP (). This enables sub-nanosecond correlation of entangled photon arrivals across nodes.

WDM/TDM Extensions Additional TLVs may specify per-wavelength parameters, enabling wavelength-division multiplexing (WDM) or time-division multiplexing (TDM) of entangled states (). This supports scaling of quantum internet bandwidth across multiple frequency channels while preserving compatibility with ITU-T DWDM grids ().

UDP Port Assignment Implementations SHOULD use a configurable default port. IANA is requested to allocate a well-known port for QFCP.

IANA Considerations - Allocate a UDP port for QFCP. - IANA is also requested to establish a QFCP TLV Types Registry with initial assignments as defined in Section 4.

Security Considerations QFCP inherits the risks of UDP: spoofing, injection, replay. It MUST be run in trusted environments or protected by DTLS/IPsec. TLVs may reveal network state information and SHOULD be protected if confidentiality is required.