Framework
1. In-situ Flow Information Telemetry Framework
Publication: IETF Individual Draft
Publication History: 2018-10
Publication URL: https://tools.ietf.org/html/draft-song-opsawg-ifit-framework-00
Description:
In-situ Flow Information Telemetry (IFIT) is a framework for applying techniques such as In-situ OAM (iOAM) and Postcard-Based Telemetry (PBT) in networks. It enumerates several key components and describes how these components can be assembled to achieve a complete working solution for user traffic telemetry in carrier networks.
IOAM
1. Export User Flow Telemetry Data by Postcard Packets
Publication: IETF Individual Draft
Publication History: 2018-10
Publication URL: https://tools.ietf.org/html/draft-song-ippm-postcard-based-telemetry-00
Description:
This document describes a proposal which allows network OAM applications to collect telemetry data about any user packet. Unlike similar techniques such as INT and in-situ OAM, the Postcard-Based Telemetry (PBT) does not require inserting telemetry data into user packets, but directly exports the telemetry data to a collector through separated OAM packets called postcards. Two variations of PBT are described in this document: one requires inserting an instruction header to user packets to guide the data collection and the other only marks the user packets to invoke the data collection. Each has its own pros and cons. Either way, the postcards for a single user packet are from multiple devices and need to be correlated at the collector, which is a unique issue pertaining to PBT. Whereas, PBT provides an alternative to INT and address several implementation and deployment challenges of the INT-based solutions.
2. In-situ OAM Direct Exporting
Publication: IETF WG Draft
Publication History: 2020-02
Publication URL: https://tools.ietf.org/html/draft-ietf-ippm-ioam-direct-export-00
Description:
In-situ Operations, Administration, and Maintenance (IOAM) is used for recording and collecting operational and telemetry information. Specifically, 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.
3. Approaches on Supporting IOAM in IPv6
Publication: IETF Individual Draft
Publication History: 2020-03
Publication URL: https://tools.ietf.org/html/draft-song-ippm-ioam-ipv6-support-00
Description:
It has been proposed to encapsulate IOAM tracing option data fields in IPv6 HbH options header. However, due to size of the trace data and its location in the IPv6 header packets, this arrangement creates practical challenges for implementation, especially when other extension headers, such as routing header, also exist and require in- network processing. We propose several alternative approaches to address this challenge, including separating the IOAM trace data to a different extension header, using the postcard-based telemetry (e.g., IOAM DEX) instead, and applying the segment IOAM trace export scheme, based on the network scenario and application requirements. We discuss the pros and cons of each approach and foster standard convergence and industry adoption.
4. In-situ OAM Processing in Tunnels
Publication: IETF Individual Draft
Publication History: 2018-06
Publication URL: https://tools.ietf.org/html/draft-song-ippm-ioam-tunnel-mode-00
Description:
This document describes the In-situ OAM (iOAM) processing behavior in a network with tunnels. Specifically, the iOAM processing in tunnels with the uniform model and the pipe model is discussed. The procedure is applicable to different type of tunnel protocols.
Alternate Marking
1. Enhanced Alternate Marking Method
Publication: IETF Individual Draft
Publication History: 2018-10
Publication URL: https://tools.ietf.org/html/draft-zhou-ippm-enhanced-alternate-marking-00
Description:
This document proposes several ways to encapsulate the alternate marking field with enough space. More information can be considered within the alternate marking field to facilitate the efficiency and ease the deployment.