{"id":"337bbb0b-3634-44e0-80fd-ddc52eaff8d4","arxiv_id":"2607.06075","paper_version":1,"verdict":"CONDITIONAL","confidence":"MODERATE","novelty_score":6.0,"correctness_risk":"unknown","formal_verification":"none","parameter_count":3,"one_line_summary":"New IPv6 Extension Headers are proposed to enable quantum teleportation, quantum routing (path superposition), and superpositions of quantum processes within the IP layer of the Quantum Internet.","lead":"The paper proposes new IPv6 Extension Headers to enable quantum teleportation, quantum path-superposition routing, and superpositions of these processes at the IP layer. A smart generalist might read it because it offers a concrete, backward-compatible pathway for migrating classical Internet infrastructure toward quantum networking without abandoning existing protocol design.","discovery_kind":"unclear","skeptic_critique":{"model":"glm-5.2","headline":"The paper's central novelty — superposition of quantum processes at the IP layer — requires that classical header processing preserves quantum coherence, but no analysis demonstrates this for any specific header setting combination.","rationale":"The reader identified the superposition-preservation constraint as weakness (2) but elevated quantum memory (Assumption 1) as the primary load-bearing concern. I partially agree: the memory concern is real but practical, and the paper acknowledges it with a plausible near-term path via fiber-loop memories (ref [32]). The coherence-preservation concern is more fundamental because it directly undermines the paper's central novelty claim — even with perfect quantum memory, if the classical header processing decoheres the quantum state, the architecture cannot deliver on its promise of enabling superposition of quantum processes at the IP layer. The paper is honest about this gap (footnotes 10 and 17), but honesty about a gap does not close it. The paper remains a legitimate architectural proposal, and CONDITIONAL is the appropriate verdict: the design is conceptually sound and internally consistent at the level of individual header fields, but the central claim requires validation that at least some header setting combinations preserve quantum coherence through the full classical processing pipeline. This is not a matter of outside-consensus disagreement; the underlying physics (quantum routing, teleportation, superposition of processes) is well-established. The concern is internal to the paper's argument: the architecture claims to enable outcomes that its own analysis does not verify are achievable. The reader's other concerns (flawless classical communication, deferred operational details) are valid but secondary to this core issue. I recommend UNCHANGED because the reader's CONDITIONAL verdict already accounts for the need for validation, and my concern refines rather than replaces the reader's assessment of where validation is most needed.","tokens_in":16146,"tokens_out":5405,"duration_ms":292140,"concrete_test":"Analyze the two-path superposition scenario depicted in Fig. 6 using a quantum channel formalism: model the classical header processing (copying, reading Path List fields, making next-hop routing decisions) at each router as a quantum operation on the joint system of quantum payload + classical header + environment, and compute whether the off-diagonal elements of the quantum state's density matrix survive after all routers have processed their headers. If coherence is lost for any router action that the header design requires (e.g., different next-hop addresses on different paths), the architecture's central claim weakens.","verdict_should_be":"UNCHANGED","load_bearing_attack":"The paper's primary novelty claim is that its architecture 'enables a wider range of outcomes allowed by quantum mechanics,' specifically superpositions of quantum routing and teleportation (§IV.C, Fig. 6). For this to hold, the classical IPv6 header processing at each router must not decohere the quantum state. The authors acknowledge in footnote 10 that 'the designs outlined do not automatically guarantee maintenance of superposition for all setting combinations,' and in footnote 17 that 'any measurement of a control qubit... can collapse the superposition unless that classical information is stored (unread) in some ancilla state.' However, the paper provides no analysis — analytical, simulational, or formal — of which specific combinations of header settings preserve coherence and which do not. Consider the basic path-splitting scenario (§IV.A): the classical header is 'copied into all paths and sent separately to the quantum payload,' and each router reads the Path List field and makes routing decisions. While the classical header content is identical across copies, the routing actions taken at different routers differ (different next-hop addresses per path), and these actions are correlated with the path. Whether this classical processing constitutes extractable which-path information that decoheres the quantum superposition depends on implementation details that are not analyzed. For the superposition of processes (§IV.C), teleportation requires Bell measurements and classical communication of outcomes — inherently decohering operations — and the paper does not analyze whether the IPv6 header structure can accommodate the ancilla-based workaround mentioned in footnote 17. The referenced physics [28] establishes that superposition of processes is possible in principle, but does not account for the additional classical processing overhead introduced by the IPv6 header architecture. Without at least one worked example showing that a specific combination of header","agreement_with_reader":"partial"},"referee_report":{"model":"glm-5.2","summary":"This paper proposes three new IPv6 Extension Headers — a Quantum Routing Header, a Quantum Teleportation Header, and a sketched Quantum Superposition Header — to enable quantum teleportation, path-superposition routing, and superpositions of these processes at the IP layer. The approach is positioned as backward-compatible: classical routers ignore the new headers while quantum-capable routers act on them. The paper is an architectural design proposal; it contains no mathematical derivations, simulations, or experimental results. The quantum-mechanical processes invoked (teleportation, path superposition, superposition of processes) are established in the referenced literature, and the IPv6 Extension Header mechanism is correctly described per RFC 8200.","tokens_in":16885,"tokens_out":1157,"duration_ms":198368,"significance":"The paper addresses a legitimate gap: prior quantum network architecture work has not deeply explored how path-superposition routing and superpositions of quantum processes could be surfaced at the IP layer via IPv6 Extension Headers. The backward-compatibility argument is a practical strength, and the header field designs (Figs. 3–5) are concrete enough to seed future standardization discussions. The paper is honest about its limitations — it explicitly states it claims no optimality and that detailed standardization is left to the community. However, the central novelty claim — that the architecture 'enables a wider range of outcomes allowed by quantum mechanics' — is not substantiated by any analysis showing that the proposed header processing preserves quantum coherence for specific operational scenarios.","major_comments":[{"comment":"§IV.A, footnote 10: The paper's central novelty is enabling superposition of quantum processes at the IP layer (§IV.C, Fig. 6). Footnote 10 acknowledges that 'the designs outlined do not automatically guarantee maintenance of superposition for all setting combinations,' and footnote 17 notes that measurements of control qubits can collapse superpositions unless classical information is stored unread in an ancilla. However, no analysis — analytical, simulational, or formal — is provided for which specific header-setting combinations preserve coherence and which do not. Consider the basic path-splitting scenario (§IV.A): the classical header is copied into all paths, and each router reads the Path List field and makes routing decisions. Whether this classical processing constitutes extractable which-path information that decoheres the quantum superposition depends on implementation details","section":null},{"comment":"§IV.C: The Quantum Superposition Header is the least developed of the three proposed headers. The SUP field and its Sub Data Field are described in only two paragraphs, with no figure showing the header layout (unlike Figs. 3 and 5 for the other two headers). Given that superposition of quantum processes is the paper's primary novelty claim relative to prior work, the absence of even a suggestive field-level diagram makes it difficult to assess whether the proposal is sufficiently specified to be actionable. A figure comparable to Figs. 3–5, even labeled as suggestive, would substantially strengthen the contribution.","section":null}],"minor_comments":[{"comment":"Abstract: 'optimally' should be 'optimality' (the same error appears in the Introduction: 'We do not claim any optimally in our design').","section":null},{"comment":"§III.A, Assumption 1: The requirement for quantum memory on all routers is acknowledged as potentially droppable but not pursued. Footnote 3 cites fiber-loop circulation [32] as evidence that required memory timescales are available, but no quantitative argument is given for whether microsecond-scale coherence suffices for IP-layer processing including optical-to-electrical conversion. A brief quantitative estimate would strengthen this assumption.","section":null},{"comment":"§IV.A, Path List field: The description states that after path splitting, 'all paths must be routed to the original destination IPv6 address.' It is unclear how this is enforced if intermediate routers pick next-hop addresses autonomously (as described for the case where the next hop is not in the local routing table). Clarifying the enforcement mechanism would help.","section":null},{"comment":"Fig. 4: The sub-figures (a)–(d) are referenced in the text but the figure caption does not describe what each sub-figure represents. Adding brief labels or a more descriptive caption for each example would help readers.","section":null},{"comment":"§IV.B: The statement 'the link layer can intelligently adopt to information in this new header and override previous settings' uses 'adopt' where 'adapt' is likely intended.","section":null},{"comment":"§V: The paper delegates entanglement distribution to 'a presumed operational entanglement distribution process' but does not discuss how entanglement fidelity requirements or decoherence during entanglement swapping interact with the header-level decisions. Even a brief discussion of whether the IP-layer teleportation requests can be satisfied given realistic entanglement distribution rates would make the architecture more assessable.","section":null},{"comment":"References [7], [9], [10], [20], [49] are dated 2026. Please verify these are not preprints mislabeled with future dates and confirm citation details for accuracy.","section":null}],"recommendation":"major_revision","confidential_remarks":"The paper is a design proposal with no formal validation, which limits how deeply one can assess correctness. The stress-test concern about coherence preservation under classical header processing is legitimate and load-bearing: the paper's central novelty claim depends on it, yet the analysis is absent. I do not think this is unfixable — the authors could add a worked example or formal analysis for at least one concrete header-setting combination (e.g., the Fig. 6 scenario) showing coherence is or is not preserved. Without that, the contribution is an interesting but unvalidated architectural sketch. The self-citation to [27] is proportionate and not circular."},"author_rebuttal":{"model":"glm-5.2","summary":"We thank the referee for a careful and constructive reading of the manuscript. The referee correctly identifies the paper as an architectural design proposal and acknowledges the backward-compatibility argument and the concreteness of the header field designs. The two major comments both concern the superposition-of-processes aspects of the paper: (1) the absence of any analysis of which header-setting combinations preserve quantum coherence, and (2) the under-specification of the Quantum Superposition Header, including the lack of a field-level diagram. We agree with both points and will revise the manuscript accordingly. Specifically, we will add a new subsection presenting a concrete coherence-preservation analysis for the basic path-splitting scenario and at least one teleportation-superposition scenario, and we will add a field-level diagram for the Quantum Superposition Header comparable to Figs. 3 and 5. We also clarify below why a complete enumeration of all setting combinations is beyond the scope of an architectural proposal but why the referee's request for specific worked examples is well-founded and will be addressed.","responses":[{"response":"The referee is correct that the manuscript provides no analysis of coherence preservation for specific header-setting combinations, and we agree this is a genuine gap that should be addressed. We will revise the manuscript to include a new subsection (to be placed in §IV.A or as a new §IV.D) that works through concrete scenarios in detail. For the basic path-splitting scenario the referee highlights, the analysis proceeds as follows. The classical header is copied into all paths, but only the quantum payload is placed in superposition. The key question is whether the classical processing at each router — reading the Path List field, updating the Time to Send field, and making routing decisions — constitutes extractable which-path information. We will argue that it does not, provided the classical header information is identical on all paths (which the architecture mandates: the header is copied, not modified differently on different branches). The which-path information would only become extractable if a router's classical processing left a record that is correlated with a specific path — for example, if the Time to Send field were updated to different values on different branches. The default settings (TS field set to -1,-1,-1, meaning no action) avoid this. When the TS field is active, coherence is preserved only if the same values are written on all paths, which the router can ensure because it processes the header classically before the quantum payload arrives. We will also analyze the teleportation-superposition scenario from §IV.C (Fig. 6), where the referee's concern about control-qubit measurement is directly relevant. Here, footnote 17 already identifies the key condition: classical measurement outcomes must be stored unread in an ancilla rather than read by a ","revision_made":"no","referee_comment":"§IV.A, footnote 10: The paper's central novelty is enabling superposition of quantum processes at the IP layer (§IV.C, Fig. 6). Footnote 10 acknowledges that 'the designs outlined do not automatically guarantee maintenance of superposition for all setting combinations,' and footnote 17 notes that measurements of control qubits can collapse superpositions unless classical information is stored unread in an ancilla. However, no analysis — analytical, simulational, or formal — is provided for which specific header-setting combinations preserve coherence and which do not. Consider the basic path-splitting scenario (§IV.A): the classical header is copied into all paths, and each router reads the Path List field and makes routing decisions. Whether this classical processing constitutes extractable which-path information that decoheres the quantum superposition depends on implementation details"},{"response":"We agree entirely. The Quantum Superposition Header is the least developed of the three headers, and given that superposition of quantum processes is the paper's central novelty claim, the absence of a field-level diagram is a legitimate weakness. We will add a new figure (to be labeled Fig. 7 in the revised manuscript) showing the header layout for the Quantum Superposition Header, comparable in structure to Figs. 3 and 5. The figure will depict the Next Header field, the Header Extension Length field, and the Data field broken down into sub-fields including the SUP field (indicating which processes are to be placed in superposition), the Sub Data Field (for additional instructions and clarifications on how the superposition is to proceed, including where and when superpositions are to occur and which control qubits trigger them), and a Control Qubit Identifier field (specifying which control qubit governs the superposition, consistent with the schematic in Fig. 6). We will also expand the text in §IV.C from two paragraphs to a fuller description that parallels the level of detail provided for the Quantum Routing Header (§IV.A) and the Quantum Teleportation Header (§IV.B), including a discussion of default values, precedence rules, and the relationship between the SUP field and the TEL=3 setting in the Teleportation Header. As with the other headers, the figure and field descriptions will be explicitly labeled as suggestive rather than definitive, pending community standardization. (yes)","revision_made":"no","referee_comment":"§IV.C: The Quantum Superposition Header is the least developed of the three proposed headers. The SUP field and its Sub Data Field are described in only two paragraphs, with no figure showing the header layout (unlike Figs. 3 and 5 for the other two headers). Given that superposition of quantum processes is the paper's primary novelty claim relative to prior work, the absence of even a suggestive field-level diagram makes it difficult to assess whether the proposal is sufficiently specified to be actionable. A figure comparable to Figs. 3–5, even labeled as suggestive, would substantially strengthen the contribution."}],"tokens_in":15803,"tokens_out":1170,"duration_ms":214298,"standing_objections":[]},"desk_editor":{"model":"glm-5.2","letter":"The core idea is straightforward and new: define new IPv6 Extension Headers that carry classical instructions for quantum routing (path superposition), teleportation, and superpositions of these processes, all at the IP layer. Nobody has previously mapped these quantum operations onto the IPv6 Extension Header mechanism, and the backward-compatibility argument — classical routers simply ignore the new headers — is clean. The paper correctly describes how Extension Headers chain via the Next Header field, and the field-level designs (Path List, Quantum Multicast, TEL settings) are reasonable starting points for a standards discussion. The references to the underlying physics (teleportation, path superposition, superposition of processes) are accurate and appropriately cited; the paper does not misrepresent those results. Credit is due for framing a concrete, standards-adjacent question that the quantum networking community has not directly addressed. The stress-test concern about coherence preservation is the right thing to worry about, but I think it lands harder than the paper actually deserves. The paper is explicitly a design proposal and says so repeatedly. Footnote 10 and footnote 17 acknowledge that not all header-setting combinations preserve superposition and that measurement-induced decoherence is a real issue. The paper does not claim to have solved this; it flags it as a constraint on future standardization. Asking for a worked coherence analysis would strengthen the paper, but its absence is not a load-bearing flaw given the paper's stated scope. The more substantive soft spot is Assumption 4 (flawless classical communication). This is genuinely unrealistic for any real deployment, and the paper does not discuss error handling or fallback behavior when classical channels drop or corrupt header data. That said, it is a design-specification paper, not a protocol evaluation, and the assumption is clearly labeled. The deferred operational details — entanglement distribution, field bit sizes, TLV coding — are all acknowledged as requiring community standardization. This is honest about what it is and what it is not. The paper is for network architects and standards-minded quantum networking researchers who want a concrete starting point for IP-layer quantum integration. It is not for someone seeking protocol validation or simulation results. It deserves a serious referee who can assess whether the header designs are internally consistent and whether the IPv6 framing holds up under scrutiny from both the networking and quantum sides. I would send it to review.","headline":"Architectural proposal for quantum-aware IPv6 Extension Headers — novel framing, but the superposition-of-processes claim is underspecified.","tokens_in":16991,"tokens_out":542,"would_cite":false,"duration_ms":65692,"reading_group":"no","serious_thinker":"no","would_accept_peer_review":true},"rs_alignment":null,"lean_confirmation":null,"pith_extraction":{"msc":[],"pacs":[],"model":"glm-5.2","headline":"IPv6 Extension Headers Can Carry Quantum Routing Instructions","keywords":["quantum internet","IPv6","extension headers","quantum routing","quantum teleportation","path superposition","packet switching","backward compatibility"],"falsifier":"If quantum memory with sufficient coherence time and fidelity cannot be deployed at every router at IP-layer processing timescales, the entire architecture cannot function, because every header field depends on the router holding a quantum state while reading and acting on classical instructions.","tokens_in":16297,"feed_emoji":"🌐","tokens_out":1050,"duration_ms":199619,"temperature":0.7,"pith_summary":"This paper proposes adding three new Extension Headers to the IPv6 packet standard to let routers direct quantum-mechanical processes at the network layer. The first header, the Quantum Routing Header, instructs routers on where to split a photon's path into a superposition of routes, how long to hold quantum states in memory, and whether to initiate quantum multicast. The second, the Quantum Teleportation Header, tells routers whether and where to teleport a quantum state using pre-distributed entanglement, with precedence rules governing how teleportation interacts with path superposition. The third, sketched but not fully specified, is a Quantum Superposition Header that would place different quantum processes themselves into superposition at designated routers. The key architectural choice is that all header information remains classical, traveling ahead of the quantum payload in separate light pulses. Classical routers that do not understand the new headers simply ignore them, preserving backward compatibility. The paper does not prove optimality or demonstrate an implementation; it argues that this minimal modification to IPv6 is sufficient to expose a wide range of quantum routing behaviors, including path superposition, teleportation, and superpositions of the two, at the IP layer.","feed_headline":"IPv6 Extension Headers Can Carry Quantum Routing Instructions","feed_subtitle":"New header designs let routers split photon paths, teleport states, and superpose processes, all while classical routers ignore them.","key_machinery":"IPv6 Extension Headers carrying classical instruction fields (Path List, Quantum Multicast, Teleportation, Superposition) that direct quantum routers to split paths, teleport states, or superpose processes, with the quantum payload traveling as a separate light pulse stored in local quantum memory during header processing.","core_discovery":"The central claim is that three new IPv6 Extension Headers, all carrying classical data, can instruct routers to perform quantum routing (path superposition), quantum teleportation, and superpositions of these processes, while remaining invisible to classical routers that lack quantum hardware. The paper specifies the sub-fields of the Quantum Routing Header in detail, outlines the Quantum Teleportation Header with several instruction modes, and sketches a Quantum Superposition Header. The load-bearing mechanism is the separation of classical header data from quantum payload, synchronized in time so each router can store the quantum state in local memory while processing classical routing指令.","pith_inferences":["The architecture implicitly requires a network-wide clock synchronization at picosecond precision (stated for the Time to Send field) and reliable entanglement distribution; if either is unavailable, the teleportation and path-splitting features degrade to classical single-path routing, but the paper does not analyze this degradation path.","The separation of classical headers from quantum payload means the headers could be spoofed or modified by a classical adversary without touching the quantum state, raising security questions about header integrity that the paper flags via reference to existing IPv6 Extension Header security concerns but does not resolve.","The Quantum Multicast field, which places a state into a superposition of all single-hop paths from a router, could in principle create an exponentially growing number of path branches across multiple hops, but the paper does not analyze the scaling behavior or resource cost of such branching."],"forward_implications":["If adopted and standardized, network operators could incrementally add quantum routing capabilities to existing IPv6 infrastructure by upgrading routers with quantum memory and the new header-processing logic, without replacing classical traffic handling.","The Quantum Routing Header's Path List and Quantum Multicast fields would enable a photon to traverse multiple network paths simultaneously, opening the door to quantum random access memory distributed across routers and to communication advantages such as error filtration and two-way communication with a single particle.","The Teleportation Header's precedence rules (TEL=0 through TEL=3) would let the IP layer dynamically choose between direct transmission and entanglement-based teleportation hop by hop, creating a hybrid transport mode that could route around failed quantum channels.","The sketched Quantum Superposition Header would provide a standardized interface for future quantum communication protocols whose advantages are not yet known, future-proofing the architecture against new discoveries in superposed quantum processes."],"fun_headline_variants":["Three IPv6 Extension Headers Enable Quantum Routing at the IP Layer","Quantum Teleportation and Path Superposition via Small IPv6 Additions","Classical IPv6 Headers Can Instruct Routers to Split and Teleport Quantum States","Minimal IPv6 Changes Open Wider Range of Quantum Routing Outcomes","Quantum Payloads Pair with Classical IPv6 Headers for Superposed Routing"],"cache_read_input_tokens":0,"weakest_assumption_plain":"Every router must have quantum memory capable of storing incoming quantum states while the router processes classical header data and makes routing decisions. The paper notes that fiber-loop memories with microsecond coherence times exist, but does not demonstrate that this suffices for real IP-layer processing including optical-to-electrical conversion in a live network.","fun_headline_variants_meta":{"raw":{"variants":["Three IPv6 Extension Headers Enable Quantum Routing at the IP Layer","Quantum Teleportation and Path Superposition via Small IPv6 Additions","Classical IPv6 Headers Can Instruct Routers to Split and Teleport Quantum States","Minimal IPv6 Changes Open Wider Range of Quantum Routing Outcomes","Quantum Payloads Pair with Classical IPv6 Headers for Superposed Routing"]},"model":"glm-5.2","effort":"high","cost_usd":0.0,"raw_usage":{"total_tokens":541,"prompt_tokens":445,"completion_tokens":96,"prompt_tokens_details":null},"tokens_in":445,"tokens_out":96,"duration_ms":24264,"temperature":1.0,"reasoning_tokens":null,"cache_read_input_tokens":0,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-07-08T17:19:48.109253+00:00","model_set":{"reader":"glm-5.2"},"falsifier":"If quantum memory with sufficient coherence time and fidelity cannot be deployed at every router at IP-layer processing timescales, the entire architecture cannot function, because every header field depends on the router holding a quantum state while reading and acting on classical instructions.","supporting_citations":[],"review_version":1}