A new individual Internet-Draft, Post-Quantum Secure Transport (PQST), proposes a datagram transport in which a cryptographic session can persist while its network path changes. Filed November 2, the proposal combines post-quantum key establishment, session recovery, rekeying, authorization, and explicit state-management rules.
This is not an IETF standard, has no working-group endorsement, and may never become one. Its value today is architectural: it exposes how much cryptographic state lives above and below an algorithm name. Any organization evaluating a design like this needs an inventory that can represent sessions, epochs, paths, identities, durable recovery state, implementations, and operational evidence together.
The session becomes an infrastructure object
Traditional inventories often attach cryptography to an endpoint, certificate, or listening service. A transport that treats the session as persistent while paths are replaceable complicates that model. The protected relationship may outlive an address, interface, carrier, or route.
A useful inventory should connect:
- protocol and draft version, conformance profile, enabled options, and negotiated suite;
- session identifier, peer identities, authorization grants, generation, epoch, sequence state, and lifecycle status;
- ML-KEM, AEAD, KDF, hash, signature, parameter set, key identifier, and intended role;
- current and prior network paths, addresses, interfaces, carriers, tunnels, regions, and failover relationships;
- continuity record, recovery identifier, durable-storage location, protection boundary, backup, and atomic-update mechanism;
- application, service, device, host, environment, owner, supplier, and physical or cloud location;
- implementation, library, firmware, version, build, configuration, and test-vector result;
- rotation, re-anchor, rollback, failure, incident, and destruction evidence; and
- discovery source, observation time, scope, confidence, and known coverage gaps.
Those relationships let operators determine whether a recovered session still represents the intended peers and authorization, rather than merely observing that encrypted packets resumed.
Durable state becomes a security dependency
The proposal places strong requirements on continuity records and atomic updates. That is a reminder that storage behavior can be part of a cryptographic protocol’s security boundary. A correct algorithm implementation cannot compensate for rollback, torn writes, cloned state, weak access control, or inconsistent replication.
Inventory should identify where authoritative state lives, which process owns mutations, what backup and recovery do to freshness, and how concurrent instances coordinate. For virtualized or containerized deployments, teams should test snapshots, restore, migration, scaling, and failover rather than assuming the storage platform preserves protocol invariants.
The associated evidence should include exact versions, storage configuration, failure injection, timestamps, and results. “Encrypted tunnel available” is an availability observation, not proof that recovery and epoch state remained sound.
Path change and security change are different events
A mobile or intermittently connected system may move between interfaces without changing its intended peer relationship. Conversely, a path can remain stable while identity, authorization, keys, or session generation changes. Operational systems need to distinguish those event classes.
Monitoring should link network telemetry to the canonical session and peer records. That makes it possible to ask whether a path change was expected, whether a re-anchor used fresh material, whether authorization remained applicable, and whether a new session was created instead of recovered.
Incident response benefits from the same separation. A compromised carrier, stolen device, leaked continuity record, and faulty implementation require different containment actions even if the symptom is a failed tunnel.
What organizations should do next
First, model current secure transports beyond endpoints and ciphers. Record session identity, state ownership, key epochs, recovery data, path relationships, and authorization.
Second, test state transitions under loss, reordering, reboot, rollback, cloned storage, failover, and concurrent processing. Confirm that unauthenticated inputs cannot cause unbounded work or authoritative state changes.
Third, connect protocol findings to canonical devices, hosts, services, locations, owners, and suppliers. A session record without an accountable asset is difficult to govern.
Finally, treat PQST as research material. Compare its assumptions with mature alternatives, independent review, implementation evidence, and actual use requirements before considering experiments.
How Vista Platform helps
Vista Platform is a proprietary, self-hosted infrastructure inventory and DCIM platform with cryptographic posture built in. It serves as a cryptographic system of record through discovery, canonical inventory, evaluation, action, and proof. Teams can connect cryptographic implementations and policy to applications, devices, hosts, locations, owners, suppliers, exceptions, and migration evidence.
Core is free of charge and includes discovery, inventory, compliance and PQC assessment, and CBOM generation without asset, sensor, seat, or time caps. Vista tracks and governs post-quantum migration; it does not generate PQC keys or perform every migration. Selected-asset Active Scan is targeted rather than indiscriminate network scanning. Vista is not a vulnerability scanner, and discovery gaps are not proof of absence.
Explore Vista’s cryptographic inventory, post-quantum migration, and CBOM and compliance resources.
Where uncertainty remains
The proposal is a version-zero individual draft with no formal standing in the IETF standards process. Its security claims, wire design, state machine, interoperability, performance, and recovery behavior require substantial independent review. The existence of a detailed specification is not evidence of safe production deployment, and discovering a component is not proof that all session paths or state copies are known.
Source
- Post-Quantum Secure Transport (PQST), draft-henry-pqst-00, individual Internet-Draft, November 2, 2026.