Postcard-based In-band Flow Data Telemetry
draft-song-ippm-postcard-based-telemetry-02
IPPM H. Song, Ed.
Internet-Draft T. Zhou
Intended status: Standards Track Z. Li
Expires: September 8, 2019 Huawei
J. Shin
SK Telecom
March 7, 2019
Postcard-based In-band Flow Data Telemetry
draft-song-ippm-postcard-based-telemetry-02
Abstract
The Postcard-Based Telemetry (PBT) allows network OAM applications to
collect telemetry data about any user packet. Unlike the E2E and
trace modes in in-situ OAM (IOAM), PBT does not require user packets
to carry the telemetry data, but directly exports the telemetry data
from the data collecting node to a collector through separated OAM
packets called postcards. Two variations of PBT are described: one
requires inserting an instruction header to user packets to guide the
data collection and the other only marks the user packets or
configure the flow filter to invoke the data collection. PBT
provides a complement to IOAM and address several implementation and
deployment challenges of it.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 8, 2019.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Song, et al. Expires September 8, 2019 [Page 1]
Internet-Draft Postcard-Based Telemetry March 2019
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. PBT-M: Postcard-based Telemetry with Packet Marking . . . . . 4
2.1. New Requirements . . . . . . . . . . . . . . . . . . . . 5
2.2. Solution Description . . . . . . . . . . . . . . . . . . 6
2.3. New Challenges . . . . . . . . . . . . . . . . . . . . . 7
2.4. Considerations on PBT-M Design . . . . . . . . . . . . . 7
2.4.1. Packet Marking . . . . . . . . . . . . . . . . . . . 7
2.4.2. Flow Path Discovery . . . . . . . . . . . . . . . . . 8
2.4.3. Packet Identity for Export Data Correlation . . . . . 8
2.5. Avoid Packet Marking through Node Configuration . . . . . 9
3. PBT-I: Postcard-based Telemetry with Instruction Header . . . 9
3.1. Solution Description . . . . . . . . . . . . . . . . . . 10
3.2. PBT-I Telemetry Instruction Header . . . . . . . . . . . 11
3.3. Considerations on PBT-I Design . . . . . . . . . . . . . 12
4. Postcard Format . . . . . . . . . . . . . . . . . . . . . . . 12
5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
9. Informative References . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Motivation
In order to gain detailed data plane visibility to support effective
network OAM, it is important to be able to examine the trace of user
packets along their forwarding paths. Such in-band flow data reflect
the state and status of each user packet's real-time experience and
provide valuable information for network monitoring, measurement, and
diagnosis.
The telemetry data include but not limited to the detailed forwarding
path, the timestamp/latency at each network node, and, in case of
Show full document text