Multi-Point Telemetry Correlation for Network Measurement

Introduction Distributed network measurement systems collect data at multiple points in the network. In forwarding-plane telemetry systems such as IOAM , each node along a packet's path may independently export measurement data. In time synchronization systems such as PTP , a Grandmaster may serve multiple slaves, generating timestamped messages that must be correlated with specific targets. A common challenge in both scenarios is ensuring that data collected at different points corresponds to the same set of packets or the same target. When each collection point independently selects packets for observation (per ), different points may observe different subsets of the same flow, making per-packet path analysis impossible. Similarly, when a time source generates timestamps for multiple targets, each timestamp must be associated with the correct target. This document specifies source-directed selection, in which a single node makes the selection or assignment decision and communicates it to other nodes via in-band signaling. Two specific applications are described in the following sections.

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.

Application to IOAM Direct Export IOAM Direct Export (DEX) defines an IOAM Option-Type that triggers each transit node to export telemetry data for a packet without embedding the data in the packet itself. The IOAM encapsulating node selects which packets carry the DEX option, and all downstream nodes export data for those packets.

Encapsulating Node The IOAM encapsulating node applies a sampling policy (e.g., 1-in-N, probabilistic, or hash-based per ) to monitored flows. Packets selected by the sampling policy are encapsulated with the DEX Option-Type per . Packets not selected are forwarded without the DEX option. The encapsulating node SHOULD also export its own local telemetry data for each DEX-carrying packet.

Transit and Decapsulating Nodes IOAM transit nodes export local telemetry data for every packet carrying the DEX option, per . Transit nodes MUST NOT apply independent sampling decisions to DEX packets; the presence of the DEX option is itself the selection indicator. The IOAM decapsulating node exports its local telemetry data and removes the DEX option before forwarding the packet beyond the IOAM domain.

Data Correlation Because all nodes on the path export data for the same set of packets, a collector can reconstruct the per-packet experience at each hop. Telemetry records from different nodes for the same packet can be correlated using the flow identifier and a packet-level identifier (e.g., a hash of invariant header fields, or a sequence number from the transport layer). The choice of packet-level identifier is outside the scope of this document.

Application to PTP Multi-Slave Topologies The Precision Time Protocol (PTP) supports time synchronization between a Grandmaster and multiple Ordinary Clock slaves. In Two-Step operation, the Grandmaster captures the egress timestamp of each Sync message in hardware and communicates it via a Follow_Up message. When the Grandmaster serves multiple slaves using multicast Sync messages, the hardware timestamp capture records must be correlated with the correct target slave.

Sequence ID Range Assignment The 16-bit PTP Sequence ID field provides 65,536 values. When N slaves are served by a single Grandmaster, the Sequence ID space can be divided into N non-overlapping contiguous ranges, each assigned to a specific slave. The Grandmaster transmits Sync messages for each slave using Sequence IDs from that slave's assigned range. The assignment of Sequence ID ranges to slaves MUST be agreed upon by the Grandmaster and all slaves before synchronization begins. The method of assignment (e.g., configuration, management protocol) is outside the scope of this document.

Grandmaster Timestamp Correlation In Two-Step mode, the Grandmaster retrieves captured timestamps from the hardware and identifies the target slave from the Sequence ID recorded with each timestamp. In One-Step mode, the hardware inserts the timestamp directly into each Sync message; the Sequence ID identifies the target slave for downstream processing.

Slave Processing Each slave receives all multicast Sync and Follow_Up messages but MUST process only those whose Sequence ID falls within its assigned range. Messages with Sequence IDs outside the assigned range MUST be silently discarded.

Security Considerations For the IOAM DEX application, the security considerations of apply. An attacker that can inject packets with the DEX option could cause telemetry export at all IOAM nodes. IOAM domain ingress filtering SHOULD discard DEX options on packets from untrusted sources. For the PTP application, misconfigured Sequence ID ranges that overlap could cause a slave to process timestamps intended for another slave. Implementations SHOULD validate range assignments for uniqueness. PTP authentication (Annex P of ) SHOULD be used in security-sensitive deployments.

IANA Considerations This document has no IANA actions.