In-situ Flow Information Telemetry (IFIT) is a new fashion data plane telemetry technique. Different from the active and passive OAM schemes, IFIT will not generate additional test traffic, but to insert the telemetry instruction into the user traffic, and measure the real user traffic.
1. IFIT Framework [EN]
Publication URL: https://tools.ietf.org/html/draft-song-opsawg-ifit-framework
Efficient network operation increasingly relies on high-quality data-plane telemetry to provide the necessary visibility. Traditional Operation, Administration and Maintenance (OAM) methods, which include proactive and reactive techniques, running both active and passive modes, are no longer sufficient to meet the monitoring and measurement requirements. The complexity of today’s networks and service quality requirements demand new high-precision and real-time techniques.
We used to apply active OAM tools for data plane test. Like Ping, and TWAMP. They will generate test traffic and measure the delay, loss of the test traffic to simulate the user traffic. Now there is a trend to apply the IFIT techniques. They will not generate additional test traffic, but to insert the telemetry instruction into the user traffic, and measure the real user traffic. So there are many advantages:
- It can provide fine grained flow SLA monitoring. Active OAM can only provide the path level precision.
- It can measure the real user traffic. Not the simulation way.
- It can monitor very packet behavior in the network. So we can see the sequence of devices the packet visited along its path. The time the packet spent buffered in every switch. The set of rules the packet matched at every device along the way. The flows that the packet shared each queue with. And so IFIT can provide abundant data plane information to enable big data and AI.
1. IFIT Data Plane
IPv6 Application of the Alternate Marking Method
Publication URL: https://tools.ietf.org/html/draft-ietf-6man-ipv6-alt-mark
This document describes how the Alternate Marking Method can be used as the passive performance measurement tool in an IPv6 domain and reports implementation considerations. It proposes how to define a new Extension Header Option to encode alternate marking technique and both Hop-by-Hop Options Header and Destination Options Header are considered.
Encapsulation For MPLS Performance Measurement with Alternate Marking Method
Publication URL: https://tools.ietf.org/html/draft-cheng-mpls-inband-pm-encapsulation
This document defines the encapsulation for MPLS performance measurement with alternate marking method, which performs flow-based packet loss, delay, and jitter measurements on live traffic.
Enhanced Alternate Marking Method
Publication URL: https://tools.ietf.org/html/draft-zhou-ippm-enhanced-alternate-marking
This document defines data fields for the alternate marking with enough space. The main idea is that more information can be considered within the alternate marking field to facilitate the efficiency and ease the deployment. The definition aims to be general, even if for some protocols there can be dedicated solutions
Data Fields for In-situ OAM
Publication URL: https://tools.ietf.org/html/draft-ietf-ippm-ioam-data
In-situ Operations, Administration, and Maintenance (IOAM) records operational and telemetry information in the packet while the packet traverses a path between two points in the network. This document discusses the data fields and associated data types for in-situ OAM. In-situ OAM data fields can be encapsulated into a variety of protocols such as NSH, Segment Routing, Geneve, IPv6 (via extension header), or IPv4. In-situ OAM can be used to complement OAM mechanisms based on e.g. ICMP or other types of probe packets.
In-situ OAM Direct Exporting
Publication URL: https://tools.ietf.org/html/draft-ietf-ippm-ioam-direct-export
IOAM allows telemetry data to be pushed into data packets while they traverse the network. This document introduces a new IOAM option type called the Direct Export (DEX) option, which is used as a trigger for IOAM data to be directly exported without being pushed into in-flight data packets.
In-situ OAM Flags
Publication URL: https://tools.ietf.org/html/draft-ietf-ippm-ioam-flags
This document presents new flags in the IOAM Trace Option headers. Specifically, the document defines the Loopback and Active flags.
In-situ OAM IPv6 Options
Publication URL: https://tools.ietf.org/html/draft-ietf-ippm-ioam-ipv6-options
This document outlines how IOAM data fields are encapsulated in IPv6.
Inband Flow Analyzer
Publication URL: https://tools.ietf.org/html/draft-kumar-ippm-ifa
In-band Flow Analyzer (IFA) records flow specific information from an end station and/or switches across a network. This document discusses the method to collect data on a per hop basis across a network and perform localized or end to end analytics operations on the data. This document also describes a transport-agnostic header definition that may be used for tunneled and non-tunneled flows alike.
2. IFIT Control Plane
BGP SR Policy Extensions to Enable IFIT
Publication URL: https://tools.ietf.org/html/draft-ietf-idr-sr-policy-ifit
Segment Routing (SR) policy is a set of candidate SR paths consisting of one or more segment lists and necessary path attributes. It enables instantiation of an ordered list of segments with a specific intent for traffic steering. In-situ Flow Information Telemetry (IFIT) provides a reference framework that supports network OAM applications to apply dataplane on-path telemetry techniques acquiring data about a packet on its forwarding path. This document defines extensions to BGP to distribute SR policies carrying IFIT information. So that IFIT behavior can be enabled automatically when the SR policy is applied.
PCEP SR Policy Extensions to Enable IFIT
Publication URL: https://tools.ietf.org/html/draft-chen-pce-sr-policy-ifit
Segment Routing (SR) policy is a set of candidate SR paths consisting of one or more segment lists and necessary path attributes. It enables instantiation of an ordered list of segments with a specific intent for traffic steering. In-situ Flow Information Telemetry (IFIT) provides a reference framework that supports network OAM applications to apply dataplane on-path telemetry techniques acquiring data about a packet on its forwarding path. This document defines extensions to PCEP to distribute SR policies carrying IFIT information. So that IFIT behavior can be enabled automatically when the SR policy is applied.
In-situ Flow Information Telemetry (IFIT) Node Capability Advertisement
Publication URL: https://tools.ietf.org/html/draft-wang-lsr-ifit-node-capability-advertisement
For advertising In-situ Flow Information Telemetry (IFIT) node capabilities within the entire routing domain, this document extends a new optional TLV to the OSPF RI Opaque LSA, a new optional sub-TLV to the IS-IS Router CAPABILITY TLV, and a new Node Attribute TLV that is encoded in the BGP-LS attribute with Node NLRIs to carry IFIT node capabilities information. Such advertisement allows entities (e.g. a centralized controller) to determine whether a particular IFIT functionality can be supported in a given network.
3. IFIT Management Plane
A YANG Data Model for In-Situ OAM
Publication URL: https://tools.ietf.org/html/draft-zhou-ippm-ioam-yang
This document defines a YANG module for the IOAM function.
UDP based Publication Channel for Streaming Telemetry
Publication URL: https://tools.ietf.org/html/draft-ietf-netconf-udp-notif
This document describes an UDP-based notification mechanism to collect data from networking devices. A shim header is proposed to facilitate the streaming of data directly from line cards to a collector. The objective is to rely on a lightweight approach to allow for higher frequency and better transit performance compared to already established notification mechanisms.
Subscription to Multiple Stream Originators
Publication URL: https://tools.ietf.org/html/draft-ietf-netconf-distributed-notif
This documents describes extensions to the YANG notifications subscription to allow metrics being published directly from processors on line cards to target receivers, while subscription is still maintained at the route processor in a distributed forwarding system.
1. Reactive In-situ flow information Telemetry
Publication URL: https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=59544
The present document will describe the motivation, requirements, and challenges of using flow-oriented on-path telemetry techniques which provides relevant measurement or event reports to the AI-enabled network entities. The present document will outline a reference framework, named as “In-situ Flow Information Telemetry (IFIT)” and identify technical requirements, including: modes of flow-oriented on-path telemetry; IFIT-based reactive telemetry framework; and technical requirements, including intelligent flow and packet selection, intelligent data export, dynamic network probe, on-demand underlying technique selection.
1. Technical requirement of automatic In-situ Flow Information Telemetry (IFIT) for carrier network
2. Dataplane technical requirement of automatic In-situ Flow Information Telemetry (IFIT) for carrier network
1. IFIT: Intelligent Flow Information Telemetry
Publication URL: https://dl.acm.org/doi/pdf/10.1145/3342280.3342292
This is short paper accepted by the SIGCOMM2019 Posters and Demos session.
2. Discover IP new techniques: IFIT
Video URL: https://support.huawei.com/enterprise/en/doc/EDOC1100134313
1. Beijing Unicom and Huawei successfully complete the pilot of IFIT solution on the 5G transport network [EN]
Publication URL: https://www.techgenyz.com/2019/06/28/beijing-unicom-and-huawei-ifit-solution-on-the-5g-transport-network
2. Huawei’s IFIT Solution Wins Best of Show Award Special Prize at Interop Tokyo 2019 [EN]
Publication URL: https://www.capacitymedia.com/articles/3823905/huaweis-ifit-solution-wins-best-of-show-award-special-prize-at-interop-tokyo-2019
3. Huawei launches NetEngine 8000 series of routers [EN]
Publication URL: https://www.lightreading.com/huawei-launches-netengine-8000-series-of-routers/d/d-id/757743