%% You should probably cite draft-song-opsawg-ifit-framework-21 instead of this revision. @techreport{song-opsawg-ifit-framework-06, number = {draft-song-opsawg-ifit-framework-06}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-song-opsawg-ifit-framework/06/}, author = {Haoyu Song and Zhenbin Li and Tianran Zhou and Fengwei Qin and Huanan Chen and Jaewhan Jin and Jongyoon Shin}, title = {{In-situ Flow Information Telemetry}}, pagetotal = 16, year = , month = , day = , abstract = {For efficient network operation, most operators rely on traditional Operation, Administration and Maintenance (OAM) methods, which include proactive and reactive techniques, running in active and passive modes. As networks increase in scale they become more susceptible to measurement accuracy and misconfiguration errors. With the advent of programmable data-plane emerging on-path OAM techniques, such as flow telemetry, provide unprecedented insight and fast notification of network issues (e.g., jitter, increased latency, packet loss, significant bit error variations, and unequal load- balancing). In-situ Flow Information Telemetry (iFIT) provides a method for efficiently applying underlying on-path flow telemetry techniques, applicable across various network environments. This document outlines an iFIT framework, which enumerates several critical functional components and describes how these components are assembled together to achieve a complete and closed-loop working solution for on-path flow telemetry.}, }